How to switch Nostr clients without losing anything

The biggest thing that makes Nostr different from any centralized social network: switching clients costs nothing. Two minutes, paste your key, done. Everything moves with you.

This guide walks through the mechanics, the edge cases, and what to check on arrival.

TL;DR. Your Nostr identity is a key pair. Export your nsec from the old client, paste it into the new one, give it ten seconds to sync, and you are on. Followers, posts, profile, DMs, everything is there because all of it lives on relays indexed by your public key, not in the client.

When you are ready, grab your @nostr.blog address →

Why switching is this easy

A Nostr identity is a cryptographic key pair generated on your device. The public key (npub1...) identifies you on the network. The private key (nsec1...) is what signs your posts and proves ownership.

No server holds your account. Nostr clients are interchangeable windows into the same network, all keyed by the same public key. Your data (posts, profile, follows, DMs) lives on relays, not in any particular client.

This is why switching is trivial. The client is the window; the account is the key. Change windows, keep the account.

The five-minute switch

For most users on most clients, the process is:

1. In your current client: open settings, find "Keys", "Account", or "Backup". Export your private key (nsec). It looks like nsec1... followed by 58 characters.
2. Save it somewhere safe: a password manager entry labeled "Nostr nsec". Not a text file on the desktop; not a note synced to the cloud without encryption.
3. In the new client: at first launch, choose "Sign in" or "Import existing account" (the exact label varies).
4. Paste the nsec. Some clients offer a QR code scan option, which is faster if you are moving between devices with cameras.
5. Wait ten seconds. The client fetches your profile, follow list, and recent notes from your configured relays. Your feed populates.

You are in the new client with everything intact.

What moves with you

Confirming the full list of what transfers:

• Profile. Name, bio, picture, banner, Lightning address. All stored as kind:0 events on relays.
• Follow list. Stored as kind:3 events. The new client reads the same list.
• Your post history. Whatever your configured relays still hold. Posts older than those relays' retention might be missing, but anything recent is there.
• DMs. Stored encrypted on relays. The new client decrypts them with your private key.
• Reactions, reposts, bookmarks. All public Nostr events signed by your key; readable by any client.
• NIP-05 identity. Your you@nostr.blog handle is tied to your public key, not your client. It continues to verify.

What might need a second look

A few things are worth checking after you arrive.

Relay list. Your relay preferences (kind:10002 relay list event) usually transfer, but the new client might have its own defaults layered on top. Open the relay settings and confirm the list looks right.

Lightning wallet settings. If you use a custodial wallet like Wallet of Satoshi, your Lightning address still works. If you use NWC (Nostr Wallet Connect) with a non-custodial wallet, you may need to paste the pairing string again in the new client. This is not a Nostr issue; it is that the NWC pairing lives in the client settings, not on the relays.

Notifications. "Read" status is client-local by default. A new client might show you notifications as if they are all new. Some clients now sync this; it varies.

Private mute list. If you maintain muted users, check whether the new client honors the list. Most do, but the feature is not universal.

Drafts. Drafts are client-local. If you have unposted drafts in the old client, they stay there. Export them manually if you need them.

When you have a NIP-07 extension

Users with a browser extension (Alby, nos2x, Flamingo) that holds the private key separately have an even smoother path. The extension is the source of truth; clients ask it to sign events.

1. Open the new client.
2. Choose "Sign in with extension" (or the equivalent).
3. The extension prompts for permission.
4. You are in.

No pasting of keys. Nothing to re-import. The same extension signs for the new client the same way it signed for the old.

This is why we recommend the NIP-07 pattern for desktop and web use: switching clients gets reduced to a single click.

When you have a signer app (Android Amber)

Android users with Amber (a signer app that holds the key) follow a similar pattern.

1. Open the new Android client.
2. Choose "Sign in with Amber".
3. Amber prompts for permission.
4. You are in.

Again, no nsec copying. The key lives in Amber; new clients pair to Amber through Android intents.

Moving between platforms

Switching from iOS to Android, or from phone to desktop, is the same operation.

The transfer method is typically a QR code. Your current client displays a QR encoding your nsec; the new client scans it. Takes a few seconds per device.

If the new device does not have a camera (a desktop without a webcam), the fallback is pasting. Copy the nsec from the old device's client, paste it into a secure channel (a password manager synced across devices; a temporary note you delete after), and paste into the new client.

Never paste the nsec into a public chat, a regular email, or any document that might sync to a cloud without encryption. Your private key is the account; anyone who gets it can impersonate you forever.

Switching clients to escape a bad one

Sometimes you want to leave a client because you dislike it or it stopped being maintained. This is the single best feature of Nostr: the "switching cost" approaches zero.

Compare to Twitter, Instagram, or Facebook, where your identity, your post history, and your followers are hostage to the platform. If you hate what Twitter is doing, leaving means starting from scratch somewhere else.

On Nostr, if you hate what your current client is doing, open a different client. Paste the nsec. All your followers, all your posts, all your relationships are there. The old client goes in the trash. This is the whole point.

Trying multiple clients simultaneously

You do not have to pick one. A realistic active user setup is:

• Primary phone client: Damus (iOS) or Amethyst (Android). This is where 80% of interaction happens.
• Web client for desktop: nostr.blog or Primal web as a PWA. This handles long-form writing and bigger sessions.
• Backup native: A different mobile client occasionally, to compare features or in case the primary has issues.

All three are logged into the same key pair. Posts from any show up everywhere. There is no "syncing" needed; the relays are the sync layer.

Edge cases worth knowing

A client that will not export the key. Every reputable Nostr client shows you the nsec on request; most ask for explicit confirmation (protecting you from accidental reveal). If you cannot find it, check "advanced", "security", or "developer" settings. If it truly is not exportable, the client is misusing your trust and you should leave it, but note that you may have to abandon anything encrypted to that key pair if you cannot recover it. Generate a new account on a client that respects you.

A client that never showed you the key. Some older clients generated keys internally and only let you sign in via their proprietary login. This was non-standard. Most have been updated; a few holdouts still exist. Same advice: move to a standard client, and if the key was truly unrecoverable, accept the loss and start fresh.

A corrupted or old key file. If you saved your nsec years ago and are not sure it is current (some users rotate keys, though rotation is unusual on Nostr), the way to check is to paste it into any client and see whether your profile appears. If your bio and followers load: correct key. If the client shows an empty account: wrong key.

Losing the key during a switch. If you paste the nsec into a new client and the old client had it stored encrypted behind a PIN you forgot, you may have no way back. This is why the first thing we tell users to do at signup is save the nsec to a password manager. Key loss is the one scenario Nostr has no recovery for.

Pattern for trying a new client risk-free

A specific workflow for users who want to sample something without committing:

1. In your current client, open settings and confirm your nsec is backed up somewhere you trust.
2. Install the new client on any device.
3. Sign in with nsec or NIP-07 extension.
4. Use it for a few days alongside the old one.
5. Keep whichever you prefer; delete the other.

Nothing is staked on this experiment. The account continues to work in both simultaneously. The question is just which UI you like for active use.

What this enables

Client switching being free changes how you think about the software. A client that starts adding ads, shipping a bad redesign, or making privacy-hostile decisions can be replaced overnight. A new client with a great feature can be tried without commitment.

Developers know this, which keeps them honest. Users know it, which keeps their options open. It is the market structure that centralized social networks cannot have, and it is the reason Nostr's client ecosystem evolves as fast as it does.

Your account is yours. The client is just a window. Change windows as often as you want.