How to Back Up Your Notes

Ask someone whether their notes are backed up and they will say yes, and mean that the notes are in iCloud. That is sync, and sync is not backup. It is the mechanism by which a mistake on one device arrives instantly on all the others.

Notes are unusually worth protecting, because unlike photos or documents they are almost entirely irreplaceable. A lost photo is a lost moment. A lost archive of ten years of thinking cannot be reconstructed from anywhere.

The three ways people actually lose notes

Not hardware failure. Drives fail, and sync handles that case fine. The real causes:

You deleted something and did not notice for six months. By far the most common. A folder gets dragged, a merge goes wrong, a bulk edit does something you did not intend. Sync propagates it everywhere in seconds, and by the time you notice, every copy agrees. Only a backup with history helps here.

The service changed or ended. The company shut down, moved to a plan you will not pay for, or altered the terms. You get a warning and an export button, and the export is a zip of HTML you have never opened. This is a slow-motion loss, and it is the one most people are actually exposed to.

You lost the account, not the data. Locked out, email compromised, subscription lapsed, region change. The notes exist and you cannot reach them, which is functionally identical to losing them.

Notice that a hard drive appears in none of these.

The rule worth knowing

The backup world's standard formulation is 3-2-1: three copies of the data, on two different kinds of media, with one copy off-site.

For a notes archive that translates cleanly:

• Copy 1: the live archive, in your app.
• Copy 2: an export on your own machine, and ideally on an external drive.
• Copy 3: that export somewhere else. A different cloud provider than the one syncing your notes, or a drive that lives at another address.

The important word is different. A copy inside the same account, the same provider, or the same app is not a second copy in the sense that matters, because every one of the three failure modes above takes them all at once.

What to actually do, by setup

If your notes are files (Obsidian, Logseq, a folder of Markdown)

You have the easy case, and this is the strongest practical argument for plain text notes.

1. Put the folder under Git. One command to start, one commit a day after that, and you get complete history: every version of every note, forever, with a diff. This solves the deleted-six-months-ago problem outright.
2. Push it to a private remote. That is your off-site copy, and it is free.
3. Add a Time Machine or equivalent local backup. That covers the case where you break the repository itself.

Total setup time is about twenty minutes and the ongoing cost is a scheduled commit.

If your notes are in a closed app (Apple Notes, Notion, Evernote, Bear)

Harder, because your only lever is the export button.

1. Find the export and use it now, before you need it. Learn what it produces and whether it is readable. Some exports are excellent. Some are a folder of HTML with mangled attachments, and you want to discover that today rather than during a migration.
2. Put the export somewhere outside that vendor's ecosystem. Apple Notes exported into iCloud Drive is not an independent copy.
3. Repeat quarterly, with the date in the filename. notes-export-2026-07.zip. Keep the last four. Dated copies are how you recover something you deleted in April.
4. Set a calendar reminder, because nobody remembers to do this voluntarily. Attaching it to the weekly review, monthly rather than weekly, works well.

If your notes are handwritten or on an iPad

Export to PDF, not to the app's own format. PDF opens everywhere in twenty years and a proprietary notebook file may not. The same quarterly rhythm applies. See how to take notes on an iPad.

The part everyone skips

A backup you have never restored is not a backup. It is a hope with a filename.

Once a year, do this properly. It takes about ten minutes:

1. Open your most recent export on a machine that does not have your notes app installed.
2. Find one specific note you remember writing more than a year ago.
3. Check that its attachments are there, its links are intact, and the text is readable rather than encoded.

If any of that fails, you do not have a backup, and it is far better to learn that on a quiet Sunday than during a crisis. Every failed restore I have seen came down to attachments or links, never the text.

Encryption, briefly

Notes are private in a way most files are not. If you are putting an export into a third-party cloud, encrypt the archive first. A password-protected zip is weak but far better than nothing; an encrypted disk image or an archive tool with real encryption is better.

Then store the password somewhere that survives you losing the laptop. A backup you cannot decrypt is a very thorough way of deleting your notes. See the best private notes app for the live-storage side of this.

A routine that fits in a year

• Continuously: sync, for device convenience. Not a backup, and do not count it as one.
• Daily, automated: Git commit, if your notes are files.
• Quarterly, ten minutes: export, date it, put it somewhere else.
• Yearly, ten minutes: restore test.

Roughly an hour a year, total. Against an archive you could not rebuild at any price, that is the cheapest insurance in your whole setup.

The related habit

Backups protect the notes. They do not protect your ability to leave, which is a separate and equally real risk. If your archive only makes sense inside one app, you are dependent on that app regardless of how many copies you hold.

The test for that one is simpler: could you move to a different app next month without losing structure? If the answer is no, the format is the problem rather than the backup. More in export your notes and the best markdown notes app.

More in how to organize your notes, how to declutter your notes, and the wider how to take notes section.