Moving a code from the phone that received it
2026-09-25
This post contains affiliate links. As an Amazon Associate, ZAGO.TO earns from qualifying purchases.
Six digits arrive by text. You glance at your phone, type them into the laptop, done. That takes four seconds and nothing about it needs improving.
So let us be clear up front: the short codes that arrive by text are not a problem worth solving, and a tool that helps you move them is a tool nobody needs.
The problem is the other kind of code. The one that fills half a screen.
The codes that are actually hard
Turn on two-factor authentication anywhere and, somewhere in the setup, a screen appears with eight or ten backup codes on it. Each is a string of letters and numbers. The screen says to save them somewhere safe and warns that you will not see them again.
That screen is on your phone. The place you would want them, a password manager on the laptop or a printer, is not.
The same shape shows up everywhere once you start noticing it:
- Recovery keys for a locked drive or an account, often 25 to 48 characters
- App-specific passwords, which arrive as a wall of random characters
- Software licence keys
- Session tokens and invite codes that a support agent reads to you
- Recovery phrases shown once during setup of almost anything
All of these share three traits. They appear on one screen, they are too long to retype reliably, and they are shown once.
What people actually do
They screenshot it.
It is the obvious move and it is worse than it looks. The screenshot goes into your photo library. The photo library syncs to the cloud. It is now in a place designed to be shared easily, backed up widely, and searched by machine-readable text recognition. Modern phones index the text inside images, which means your backup codes are literally searchable.
Then it stays there. Nobody goes back and deletes the screenshot of their recovery key, because nobody remembers taking it.
The second-most common move is to message it to yourself, which puts a permanent copy in a chat thread that syncs to a desktop client. The third is to email it, which is the same thing with a longer memory.
All three work. All three quietly create a durable copy of exactly the thing that should not have durable copies.
Where the difficulty really is
Notice that the hard part is not moving the code. It is moving it without creating a copy that outlives the move.
If copies were free, screenshotting would be fine. The problem is that the convenient channels are all archives, and an archive is the wrong shape for a recovery key.
That reframing changes what you should reach for. You do not need a better transfer. You need a transfer that forgets.
What we do here
This is our own service, so weigh it accordingly.
ZAGO.TO takes text and gives you four digits. You type those four digits on the other device and the text appears, then it is deleted from the server about a minute after opening. Nothing is kept, on either side, because there is no account and no history.
For the backup-codes case it works like this. On the phone, select the codes and paste them in. On the laptop, open the site and type four digits. Paste them into your password manager, or print them. A minute later there is nothing on our end.
That is the whole benefit: the intermediate copy does not survive. Compared with a screenshot in your photo library, that is the entire difference and it is a real one.
The limits, which matter a lot here
This is a topic where being imprecise would be harmful, so:
Our server can read the text while it is there. There is no browser-side scrambling in place today. For backup codes, that means you are trusting us for about a minute with something valuable. Whether that is acceptable is your call, and it is a reasonable thing to decline.
The receiving device keeps what you paste. Your text sits in that machine's clipboard until something replaces it. If it is not your machine, copy something harmless afterwards.
Never move a seed phrase or recovery phrase this way. Or any way. A wallet recovery phrase does not travel between devices, through us or anything else. If it has to go somewhere, it goes onto paper by hand, and nowhere else. Anyone asking you to type one into a website, including this one, is running a scam.
This does not replace a password manager. It is a way to get something into one, not a place to keep it.
A simpler answer that is often better
Before reaching for any tool, consider whether the code needs to move at all.
Most password managers have a phone app. If yours does, paste the backup codes into a secure note on the phone and let the manager sync it. No intermediate copy, no transfer, nothing in a clipboard. That is the cleanest path and if it is available to you, take it.
The transfer question only matters when the destination is not something that syncs: a printer, a machine that is not yours, a password manager you have only on the desktop, or a piece of paper.
Print it, actually
One answer people dismiss too quickly is paper.
Backup codes exist for the day you lose the phone. If your only copy is in a password manager that you unlock with that phone, you have built a loop that closes on you at the worst moment. Paper does not have that failure mode. It does not sync anywhere, it cannot be searched remotely, and it works when every device you own is gone.
The reason people skip it is that the printer is attached to a different machine than the phone showing the codes, which is the transfer problem again. That is the case this whole article is about, and printing is the destination where a forgetting transfer fits best: the codes go from the phone to the screen to the printer, and nothing in the chain keeps them.
Write the date and the account name on the sheet, put it somewhere you would keep a passport, and delete the screenshot you already took.
The short version
The short ones that arrive by text are fine. Type them.
The long one-time strings are where the trouble is, and the common answer, a screenshot, creates a searchable permanent copy in the most-synced folder you own. Whatever you use instead, the property worth looking for is not speed. It is that nothing is left over when you are done.