Back Up a Local Writing App: Save Your Novel

This guide walks you through backing up a local-first writing app (like Scrivener, Ulysses, Obsidian, or iA Writer) so you never lose your manuscript. You’ll learn where your files live, how to create a full backup, and how to verify it actually works. Before starting, make sure you know which app you use and where it stores its projects—this is usually in your Documents folder or an app-specific data directory.

What You’ll Need

An external hard drive, USB stick, or cloud storage account (Google Drive, Dropbox, OneDrive)
Your writing app installed and your project open at least once
File Explorer (Windows) or Finder (Mac)
Optional: version control software like Git, or a backup utility like Time Machine (Mac) or File History (Windows)

Step-by-Step

Close your writing app completely. This ensures no files are locked or mid-write. On Windows, check the system tray; on Mac, press Cmd+Q.
Locate your project files. Open File Explorer or Finder and navigate to the default save location. For most apps, this is Documents or Documents/[App Name]. If you’re unsure, open your app, go to Preferences/Settings, and look for “Storage,” “File Location,” or “Library.” Some apps (like Obsidian) store everything in a single folder you chose when creating the vault.
Identify the actual data files. Look for a folder with your project’s name. Inside, you’ll typically find a file with an extension like .scriv, .ulysses, .md, or a package file that looks like a single file but is actually a folder (on Mac, right-click and select “Show Package Contents” to see the inner files).
Copy the entire project folder (or package) to your backup destination. Do not copy individual chapters or notes—copy the whole thing. Drag it to your external drive or upload it to your cloud folder. If you’re using a USB stick, make sure it has enough free space.
Rename the backup with a date. For example, MyNovel_2025-06-15. This prevents overwriting older backups and lets you roll back to a specific version if needed.
Verify the backup. Open the backup location and double-click the copied file or folder. If it’s a package, try opening it with your writing app. If it opens and shows your latest chapter, the backup is good. If it fails, re-copy and try again.
Set up automatic backups (optional but recommended). On Mac, turn on Time Machine and point it to your external drive. On Windows, enable File History and select the folder containing your writing projects. For cloud sync, move your project folder into your Dropbox/Google Drive folder and let it sync continuously.
Test restoring from backup once a month. Delete a dummy file from your project, then restore it from the backup. This confirms your backup process actually works before you need it in an emergency.

Common Mistakes

Only copying the text file, not the project bundle. Many apps store formatting, metadata, and research in separate files. If you copy only the .txt or .md, you lose all that.
Backing up to the same drive as the original. If your hard drive fails, both copies are gone. Always use a separate physical drive or cloud service.
Not closing the app before copying. This can result in a corrupted backup because files are still being written.
Overwriting your only backup. If you name every backup “backup” and copy over it, you lose the ability to recover from an earlier point in time.
Assuming cloud sync is a backup. If you accidentally delete a chapter and the deletion syncs to Dropbox, your cloud copy is also deleted. Cloud sync is not a substitute for a versioned backup.

Tips

Use the “3-2-1 rule”: keep 3 copies of your novel, on 2 different types of media, with 1 copy offsite (cloud or a friend’s house).
Export a plain-text or Markdown copy of your manuscript every time you finish a writing session. This gives you a universal fallback that any text editor can open.
If your app supports it, enable its built-in backup feature (e.g., Scrivener’s “Backup” settings) and set it to save a zip file to a folder you designate.
For long projects, consider using Git. Initialize a repository in your project folder, commit after each chapter, and push to a private GitHub or GitLab repo. This gives you unlimited version history.
Label your backups clearly with dates or chapter milestones, not just “final” or “newest.”

Troubleshooting

Backup file won’t open. First, check if the file extension is correct. If it’s a package (like .scriv), make sure you copied the whole bundle, not just the contents. Try opening it on a different computer. If it still fails, look for a .bak file inside the project folder—your app may have created an automatic backup.
Cloud upload stalled. Large project folders with many images can take a while. Check your internet connection, pause and resume the sync, or split the project into smaller folders. If the cloud service has a file size limit, compress the folder into a zip file first.
External drive not recognized. Try a different USB port or cable. On Mac, check Disk Utility; on Windows, check Device Manager. If the drive is corrupted, you may need data recovery software, but that’s a last resort.
Accidentally deleted your project and the backup is old. Check your app’s trash or recycle bin. Many apps keep a local history. If you use Time Machine or File History, you can restore a version from before the deletion. If you have a cloud sync, check the cloud’s version history (e.g., Google Drive’s “Version history” for files).
Backup is too large for your USB stick. Compress the project folder into a zip file (right-click → Compress). This also preserves file structure. Alternatively, split it into two archives using a tool like 7-Zip.
App says “file is locked” when copying. Close the app fully, including background processes. On Windows, open Task Manager and end any processes with the app’s name. On Mac, use Activity Monitor. Then try copying again.

Frequently Asked Questions

How often should I back up?

At minimum, after every writing session. If you write daily, that means a daily backup. Automatic tools (Time Machine, cloud sync) make this painless.

Is cloud storage safe for my unpublished novel?

Yes, if you use a reputable provider with encryption in transit and at rest (Google Drive, Dropbox, iCloud). Enable two-factor authentication on your account to protect against unauthorized access.

What’s the difference between a backup and sync?

Sync mirrors changes—if you delete a file, it’s deleted everywhere. A backup is a snapshot in time. You need both: sync for convenience, backup for recovery.

Can I just copy the exported Word or PDF file?

You can, but you’ll lose your project’s structure, notes, and research. It’s better to back up the native project file. The export is a bonus, not a substitute.

My app stores data in a database, not files. How do I back that up?

Some apps (like Ulysses) use a library. In that case, back up the entire library folder, or use the app’s built-in export/backup feature to create a portable copy. Check the app’s documentation for the exact location.

What if I only have one computer and no external drive?

Use a free cloud service. Upload your project folder to Google Drive or Dropbox. You can also email a zip file to yourself as a last resort, but that’s not a long-term solution.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →