Sync Site Notes Across Devices Without an Account

You keep a note against a client’s dashboard, another against a supplier’s order page, a third against a job listing you mean to return to. Then you open the same sites on a second computer and every note is gone. Nothing was deleted. The notes are simply sitting in a different Chrome profile, and no browser feature carries them across.

This is the quiet failure built into per-site note taking. The notes are more useful than a single notebook because they sit beside the work, but that closeness also ties them to one machine. Sync is the feature that decides whether the habit survives a new laptop.

The Short Answer

Per-site notes sync when the extension stores them in a workspace that more than one browser profile can reach. Notes Wrangler does this with a random key rather than an account: the first device holds a key beginning ntwr_live_, and every profile that saves that key shares the same notes.

Sync runs automatically every hour while Chrome is running, and Sync now does it immediately. Local notes remain free and unlimited. Cross-device sync is part of the optional yearly plan.

Why Browser Notes Stop at the Profile Boundary

An extension writes notes into its own local storage inside the browser profile. Chrome treats that storage as private to the extension on that profile. The browser’s own sync service is built for a fixed list of things: bookmarks, passwords, history, open tabs, extensions and autofill profiles. Extension note data is not on that list, so switching on Chrome sync changes nothing for your notes.

The boundary appears in ordinary situations:

• A new laptop, where the old profile is not migrated.
• A work desktop and a home desktop, signed in to different Google accounts.
• A second Chrome profile kept for a separate client or a separate job.
• A profile reset or a reinstall after a corrupted browser.

In each case the notes still exist, but only where they were written. That is the gap a sync feature has to close, and it is the reason a per-site note tool without sync tends to be abandoned around the time someone changes computer.

The Three Ways to Move Notes, Compared

Export is still worth having, because a file you control is the backup of last resort. The point of sync is different: it removes the moment where you have to remember to do anything. The Markdown export guide covers the file side, and the one key sync guide covers the key mechanics in detail.

What Key Based Sync Does Differently

Most sync systems start with a sign up form. That form creates a database of email addresses and password hashes, a reset flow, and a support burden for people locked out of their own notes. Notes Wrangler removes that layer. The workspace is named by a random string, and possession of the string is the whole permission model.

The practical consequences are worth stating plainly:

• No sign in on a new device. Paste the key, save, and the notes arrive at the next sync.
• No password to reset. There is nothing to recover, which cuts both ways, because a lost key means a lost workspace.
• No profile graph on the server. The service holds notes against a random key, not against a name or an address.
• Deletions travel. A note removed on one device is removed on the others instead of reappearing.
• Newer edits win per note. Notes are matched by stable id, so one changed note does not replace the library.

The trade is that possession equals access. Anyone holding the key can read and write the workspace, with no read-only role. Treat it like the key to a filing cabinet, because that is exactly what it is.

Set Up a Second Device in Three Steps

1. On the first device, open Settings, reveal the sync key and copy it or download the key file.
2. On the second device, open Settings, paste the key into the sync key field and save. The field checks the shape on entry and says so when the key is incomplete.
3. Press Sync now on either device, or wait for the hourly run. The existing library is seeded into the workspace, then changes flow both ways.

Renewing the plan extends the same key, so devices never need to be rejoined. If a device is lost, rotate the workspace rather than trusting an old key that may still be in someone else’s hands.

What Syncs and What Stays Local

Note text, note titles and per-site associations sync, along with their deletions. Settings do not. Font scale, panel layout, onboarding state and connector credentials for Notion, Obsidian and Joplin stay on each device, because a work machine and a personal machine often need different rules, and because an API token for another service should not be copied around by default.

Sync requires the extension to be installed and Chrome to be running. It works in desktop Chrome profiles, including separate profiles on the same machine. Mobile browsers do not run extensions, so there is no phone client to sync with.

What Sync Does Not Protect Against

Synced notes are stored on project infrastructure and travel over an encrypted connection, so the other devices you add can read them. They are not end-to-end encrypted with a key that only you hold. That is a deliberate trade for a service that has to merge edits from several devices without asking for a password each time. Local notes, by contrast, never leave the device.

Two risks follow. A lost key cannot be recovered, because there is no account to prove ownership against. A shared key cannot be partly revoked, because there are no roles. Both are solved by the same habit: keep the downloaded key file somewhere safe, and store anything you would not want read by a key holder outside the synced workspace.

When Export Is the Better Answer

Use export when you want a copy that outlives the tool: before uninstalling, before a profile reset, or when notes need to reach Notion, OneNote, Obsidian or Joplin. JSON keeps every field for a faithful reimport. Markdown keeps the readable text for another app. The settings page produces both, and the files are plain enough to inspect in any editor.

The sensible arrangement is both. Sync for the working set that moves between machines, and a periodic export for the archive that must survive a mistake, a lost key or a change of tool.

Frequently Asked Questions

Related Articles