How to back up a seed phrase properly (and test that it works)

In reader mail, permanent loss is almost never a broken wallet. It is a backup that was never tested, a photograph in cloud storage, or a phrase typed into a convincing website.

Write it down, physically

Pen and paper is fine to start. Ink fades and paper burns, so if the amount matters, move to stamped metal. What matters more than the material is that the phrase exists somewhere that does not depend on a device continuing to work.

Never let it become data

The moment a seed phrase is photographed, typed into a notes app, emailed to yourself or stored in a password manager that syncs, it has entered the class of things that get breached. Cloud photo backup is the single most common way we hear about this happening — people photograph the card as a “temporary” measure and forget.

Two copies, two places

One copy is a single point of failure against fire, flood and theft. Two copies in the same house is one copy. Put the second somewhere physically separate — a family member, a safe deposit box, a second property.

If a copy sitting elsewhere worries you, that is the right instinct: split-knowledge schemes exist for it. They also add ways to lose everything through complexity. For most people two whole copies in two locations is the better trade.

The test nobody does

This is the part that matters. Before you put a meaningful amount on a wallet:

1. Fund it with a small amount.
2. Wipe the device completely, factory reset.
3. Restore it using only your written backup — not the device, not your memory.
4. Confirm the small amount is there.

People discover at this step that they transposed two words, wrote the list in the wrong order, or recorded 23 words of 24. Discovering it now costs an evening. Discovering it when the device has already failed costs everything.

Nobody legitimate will ever ask

Not support, not the wallet vendor, not an exchange, not a “validation” page, not a firmware update. Any request to type a seed phrase anywhere is an attack. There are no exceptions and there is no context in which this is a false alarm.