Backing Up Plain-Text Notes: A 3-2-1 Plan That Takes an Afternoon

Quick answer

A plain-text notes folder backs up in an afternoon. The files are tiny, the format is open, and there's no export step or proprietary converter standing in the way. The plan is the 3-2-1 backup rule: at least three copies of your data, on two different devices, with one copy kept offsite. If the only thing protecting your notes right now is syncing them across your iPhone, iPad, and Mac, that's not one of the three copies. Sync propagates a deleted or overwritten file exactly as fast as it propagates a real edit.

Step-by-step

Copy 1: the folder you're already working in

Your live notes folder — the one you write in every day. It's the thing being protected, not a backup of anything. Everything below exists so a mistake, a failed drive, or a lost laptop can't take this folder down with it.

Copy 2: a local backup on a second device

On a Mac, this means Time Machine backing up to an external drive. Once it's set up, Time Machine keeps hourly backups for the past 24 hours, daily backups for the past month, and weekly backups for everything before that, deleting the oldest ones automatically as the drive fills up. Apple recommends dedicating that drive to backups only, sized to roughly twice your Mac's storage.

The strict version of 3-2-1 calls for two different types of media. Most people run the practical version instead — just two different devices, which your laptop plus an external drive already satisfies. One catch: a drive that's sat unplugged in a drawer for six months isn't protecting anything you've written since.

Copy 3: an offsite copy

This one has to survive a fire, a flood, or a theft at home — a cloud backup service, or a dated archive uploaded somewhere off the property. And it has to be genuinely separate from copy 2. If your Mac and your external drive live in the same room, one bad afternoon can take out both at once.

Don't confuse this with cloud sync. A sync folder mirrors your live files, mistakes included, in real time. A backup shouldn't. Here's a one-line way to make an immutable snapshot before you upload it anywhere:

zip -r "notes-$(date +%F).zip" ~/Notes

Run that monthly, push the result to your offsite storage of choice, and you've got a point-in-time copy that nothing you do to the live folder afterward can touch.

A cheap fourth layer: version history

Already use Git for code? Your notes folder is small enough for the same treatment. Committing plain-text files to a repo turns every past version into something you can diff and restore — on top of the three copies above, not instead of them. See version-controlling your notes with Git if that workflow appeals to you. It's optional, not a requirement for a working 3-2-1 setup.

Putting the schedule together

Local backup runs on its own once Time Machine is pointed at a drive that stays connected. Offsite backup runs automatically with a cloud backup service, or monthly if you're uploading an archive by hand. The one step that doesn't run itself: verifying the backup actually works — covered next.

Common problems and fixes

"I thought iCloud was already backing this up." iCloud's automatic daily backup and a manual archive aren't the same thing. Apple's own guidance is to export a separate copy of anything irreplaceable, because if you accidentally delete a file, you need a copy that lives outside the place the deletion just happened. Sync and cloud backup both fail this test the same way. See syncing plain-text notes across devices if that's the confusion you're untangling.

"My external drive is from two years ago." That's a stale local copy, not a working one. Reconnect it and let Time Machine catch up before you trust it — or replace it if it's old enough that you're not confident it still spins up reliably.

"I don't know if my backup actually works." The most common failure mode, and a silent one, right up until the day you need it. The fix is the one-file restore test below. Do it once for each layer, right after you set it up.

Doing this with Carets

Carets keeps everything as plain text and Markdown, so every leg of a 3-2-1 plan works without a conversion step first — there's no walled-garden format to export before a backup tool can even read it. Your files stay plain text, so the same folder works unmodified in Time Machine, a cloud backup service, or a Git repo. Carets keeps that folder organized into files, projects, and tags, so pointing a backup tool at "everything in one place" is straightforward instead of a hunt across app-specific storage. And because Carets is native and fast on iOS and Mac, working in plain text day to day doesn't cost you anything next to a heavier note-taking app — you get the backup story for free just by choosing a format every backup tool already understands.

Carets is available for iPhone, iPad, and Mac on the App Store.

Frequently Asked Questions

Is iCloud Drive a backup for my notes?

No — iCloud Drive is sync, not backup. If you delete or overwrite a file, that change propagates to every synced copy. It's a great way to access notes across devices, but it doesn't count as any of the three copies in a 3-2-1 plan on its own.

Do I need an external drive if I already use Time Machine?

Time Machine backs up to an external drive, so they're the same step, not two separate ones. What Time Machine doesn't give you is an offsite copy — if your Mac and that drive are in the same room during a fire or theft, both copies are gone.

How often should I make an archive snapshot?

Monthly is enough for most personal notes folders. Plain-text files are tiny, so a dated zip of your whole notes folder costs almost nothing in storage and gives you an immutable point-in-time copy that a sync mistake can't touch.

What's the fastest way to check a backup actually works?

Copy one file from the backup — not the original — to a new location and open it. If you can't restore a single file in under a minute, the backup isn't done. Fix that before trusting it with your only copy of something important.

Conclusion

Three copies, two devices, one offsite. That's the whole plan. Plain-text notes make all three cheap to set up, since there's no format to fight along the way. Once the local and offsite legs are running on their own schedule, the only job left is an occasional restore test — so you find out the backup works before the day you actually need it to.