TexFaber

Blog / From the notebook

AI Generated Content

Backup for Writers Compared: Dropbox, Google Drive, Time Machine and Git (2026)

Backup, version control and file management for writers compared: Dropbox, Google Drive, Syncthing, Time Machine and Git, with prices, version history and Scrivener advice.

Jamie Heerlyn28 min read

Illustration of nested boxes holding copies of a manuscript, sheltered beneath a navy and orange umbrella.

This modular research dossier provides a structured, source-cited analysis of backup, version-control, and file-management tools and practices for writers in 2026.

1. Tool Matrix & Profiles

Field Dropbox Google Drive (Google One) Syncthing Time Machine Git (GitHub / GitKraken)
Pricing Basic (Free): 2GB Plus: ~$11.99/mo or $119.88/yr (2TB) Professional: ~$19.99/mo or $199/yr (3TB) Free: 15GB (shared w/ Gmail & Photos) 100GB: ~$1.99/mo or $19.99/yr 2TB: ~$9.99/mo or $99.99/yr Free: Open-source ($0). No subscription or storage tiers; storage is limited only by your own hardware. Free: Included with macOS. Requires an external drive (~£50–£150 for 1–2TB). Free: Core Git, GitHub Free (unlimited private repos), GitHub Desktop, and GitKraken Free (local & public/limited private repos).
What it protects Multi-device sync, file version history, offsite storage of working files. Multi-device sync, native Docs history, offsite storage of working files. Peer-to-peer multi-device continuity. Local network and encrypted internet sync. Hardware failure, accidental deletion, OS corruption via local snapshots. Granular, chronological change history (commits) across multiple text files.
What it does not do Sync is not backup. Deleting a file locally deletes it in the cloud. It does not offer true archival backup unless files are decoupled from sync. Sync is not backup. Deletions propagate. Uploaded binary files (DOCX, Scrivener zips) have limited, decaying version histories. Not a backup. Synchronises deletions and corruptions instantly across connected devices. No offsite copy unless a peer is stored offsite. Not offsite. If the laptop and the external drive sit in the same room, fire, flood, or theft destroys both. Not a standalone backup. A local Git repo on your laptop dies with your laptop. You must push to a remote server (GitHub) to achieve offsite protection.
Versioning depth Plus: 30 days. Professional: 180 days (Extended Version History add-on extends to 1 year). Accessed via web UI: Version History. Google Docs: Indefinite granular history (File → Version history). Uploaded Files (DOCX/PDF): 30 days or 100 versions, whichever comes first. None by default. Optional "File Versioning" (Trash Can, Simple, Staggered, External) must be manually configured per folder. Hourly for past 24 hours; Daily for past month; Weekly for all previous months until the drive fills (oldest deleted first). Infinite. Every manual "commit" saves an immutable snapshot of the entire project. Accessed via git log, GitHub web UI, or GUI clients.
Restore process Log into Dropbox web, navigate to Deleted Files or Version History, click Restore. Fast for single files; slow for entire drives. Web interface: Right-click file → Manage versions → Download, or restore from Trash (held 30 days). Restore from the hidden .stversions folder on a peer device (if versioning was enabled). Otherwise, manual recovery is impossible. Plug in drive, enter Time Machine interface, scroll back in time, click Restore. Very fast for single files or full system recovery. Via GUI (GitHub Desktop/GitKraken), select the specific historical commit and click Revert or Checkout. Requires basic fluency in Git concepts.
Best for (Writer Profile) Working novelists needing reliable, cross-platform sync and a 30–180 day safety net. Zero-budget writers, Google Docs native drafters, and collaborative editors. Privacy-focused writers with multiple devices who refuse to pay cloud subscriptions. Any Mac-based writer who wants automated, "set and forget" local hardware protection. Series writers, technical authors, and plaintext/Markdown writers wanting a permanent commit log.
Key limitation You are renting your version history; once the 30/180-day window passes, old iterations are permanently purged. Terrible at versioning non-native formats (e.g., Scrivener projects) compared to native Docs. Requires both devices to be turned on and online simultaneously to sync changes. Useless if you forget to plug in the drive, or if the drive is stolen alongside the laptop. Terrible with binary files (.docx, .pdf); tracks plain text (.txt, .md) brilliantly, treats Word docs as opaque blobs.
Last Verified Date November 2026 November 2026 November 2026 November 2026 November 2026

Scroll sideways to see all columns →

2. Pairing Matrix

Dropbox vs Google Drive

Dropbox vs Syncthing

Google Drive vs Syncthing

Time Machine vs Dropbox

Time Machine vs Google Drive

Git vs Dropbox

Git vs Time Machine

Syncthing vs Time Machine

Cloud Sync vs Local Backup

Sync vs Backup

Free Option vs Paid Option

3-2-1 vs "I have Dropbox"

3. Cost Mathematics (2026 Verified)

Note: UK (£) and US ($) conversions are approximate. Verify exact regional store rates at checkout.

Profile A: Zero-Budget Debut Novelist

Setup: One laptop, one manuscript.

Profile B: Working Novelist

Setup: Two devices (laptop + desktop), three active books, research folders.

Profile C: Series Novelist / Complex Projects

Setup: Multi-book Scrivener projects, heavy research, years of drafts, collaborators.

Summary Break-Even Reasoning

Paying ~£120/year for Dropbox Plus or a dedicated backup drive breaks even the exact second it prevents the loss of a single chapter. Over a 10-year writing career, spending £1,200 to protect multiple intellectual properties worth tens of thousands in advances and royalties is an insignificant operational cost.

4. Sync Is Not Backup

5. The 3-2-1 Rule for Writers

The 3-2-1 rule is the universal standard for data survival. Translated for a solo writer, it requires:

Mapping the Minimum Viable 3-2-1 Setup

  1. Copy 1 (Working): Novel.docx on your laptop's internal SSD (Media 1: Internal Drive).
  2. Copy 2 (Local Backup): Time Machine running to an external USB drive on your desk (Media 2: External Drive).
  3. Copy 3 (Offsite Sync): Dropbox or Google Drive syncing that folder to remote servers (Media 3: Cloud Server, Offsite).

The "Paranoid" Upgrade (4-3-2)

Add a second cloud service (e.g., manually drag a zipped copy of your manuscript to a free Google Drive once a week even if you use Dropbox) OR keep a second external Time Machine drive at your office or a friend's house, swapping it with your desk drive once a month.

What 3-2-1 Does Not Cover

The standard 3-2-1 rule protects the existence of the current file, not its history. If you cut 10,000 words on Tuesday, and your backups run Tuesday night, all three copies now reflect the cut. You fix this vulnerability by ensuring Copy 2 (Time Machine) and Copy 3 (Dropbox Version History or Git) maintain historical snapshots rather than simple file mirrors.

6. Version Naming Conventions

A chaotic folder full of Book_final_v2_REALLYFINAL_edits.docx causes writers to edit outdated drafts and overwrite new work. Follow these non-negotiable naming rules:

  1. The Date-First Rule: Format every version starting with ISO 8601 dates: YYYY-MM-DD_ProjectName_Descriptor.ext.
  • Example: 2026-11-14_Starlight_Draft02_Ch07.docx
  • Why: Alphabetical sorting automatically becomes chronological sorting.
  1. Never Use "Final": Ban the word "final" from your vocabulary. There is always another proofread, a copyedit, or a typo fix. Use draft numbers (Draft01, Draft02) or stage tags (DevEdit, Copyedit, Proof).
  2. The Draft-Number Rule: Increment the draft number (Draft01 → Draft02) only on substantial structural shifts or before sending the manuscript to an external reader (beta reader, agent, editor). Do not increment on daily saves.
  3. The Working / Archive Split:
  • Keep one live working file in your sync folder (e.g., Starlight_WORKING.docx or 2026-11_Starlight_Draft03.docx).
  • Keep an _ARCHIVE subfolder alongside it. Every Monday morning (or at the end of a milestone), copy the working file into _ARCHIVE with the date stamp. Never edit files inside the archive.
  1. The Scrivener-Specific Rule: A .scriv file on macOS/Windows is not a single file; it is a disguised folder containing hundreds of individual .rtf and .xml files. Never sync a live Scrivener project across multiple machines using Google Drive or iCloud (Dropbox is the only cloud service Scrivener officially tolerates, and even then, you must let syncing finish 100% before opening the project on another machine).
  • Best Practice: Set Scrivener’s automatic backups (Preferences → Backup) to "Back up on project close" as a Zipped file (.zip), and point that backup folder to your cloud sync drive. Syncing a single .zip file eliminates database corruption.
  1. The "Open the Archive" Test: Once a month, click into your _ARCHIVE folder, pick the oldest file, and double-click to ensure it opens cleanly without corruption.
  • Verdict for "How should I name my manuscript files?": Date-first (YYYY-MM-DD), draft-numbered, never use "final," and strictly separate your live working file from your frozen archive folder.

7. Disaster Recovery

Scenario What Happened The Recovery Step The Lesson
The laptop drive dies Sudden hardware failure; screen won't turn on; internal SSD is dead. 1. Buy/borrow replacement computer. 2. Plug in Time Machine drive and restore directly via Migration Assistant (fastest) OR sign into Dropbox/Google Drive web and download the folder (slower). Time Machine provides the fastest full-system recovery; Cloud is your backup if the drive also corrupted.
File deleted by mistake You deleted a scene or whole file; cloud sync propagated the deletion instantly. 1. Go to Dropbox.com or drive.google.com → Deleted Files / Trash and restore. 2. If past 30 days, plug in Time Machine, enter Time Machine interface, scroll back to last week, hit Restore. Sync spreads accidents. Version history and local snapshots are the actual cures.
Cloud account is locked Expired credit card, hacked account, or false-positive automated ToS violation locks you out of Dropbox/Google. 1. Do not panic. Your active files are still on your laptop's local drive. 2. Your historical versions are safe on your Time Machine drive. 3. Move your working folder to a new provider while disputing the lock. Never let a cloud company hold the only copy of your manuscript.
Ransomware encrypts files Malware locks your local drive; sync uploads the encrypted junk to the cloud. 1. Immediately disconnect computer from Wi-Fi and unplug external drives. 2. Wipe the infected computer. 3. Restore clean files from your disconnected Time Machine drive, or use Dropbox Version History to "Rewind" the folder to the hour before the attack. Unplug your external backup drive when not actively backing up; rely on cloud versioning to roll back encrypted syncs.
House burns down / Theft Laptop and external desk drive are physically destroyed or stolen together. 1. Log into Dropbox/Google Drive/GitHub from a new device. 2. Download the entirety of your working folder and archives. Offsite storage is completely non-negotiable. Local backups alone fail catastrophic physical events.
Scrivener project corrupted Sync conflict caused missing scenes, blank pages, or binder errors. 1. Close Scrivener immediately. 2. Locate your automatic .zip backup folder (Scrivener → Preferences → Backup → Open Backup Folder). 3. Unzip the most recent clean copy and replace the broken project. Never rely on syncing live .scriv package folders without automated .zip backups enabled.

Scroll sideways to see all columns →

The Universal Recovery Rule: A backup you have never tested is a backup that will fail. Once per quarter, delete a dummy test file, restore it from Time Machine, restore a version from your cloud web interface, and confirm both open cleanly.

8. "Best For X" Angles

Best backup setup for a zero-budget debut author
Google Drive Free (15GB) + Time Machine on an existing external drive is the best zero-cost setup. You get automated local snapshots to protect against drive death and an offsite cloud copy for fire/theft protection without paying a penny in subscriptions. Runner-up: Syncthing + GitHub Free (if you don't own an external drive and write in plain text).
Best backup setup for a working novelist with two devices
Dropbox Plus (~£120/yr) + an external Time Machine drive (~£100 one-time) is the winning combination. Dropbox handles multi-device syncing and provides a 30-day version window, while Time Machine acts as the high-speed, deep-archive local net. Runner-up: Google One (100GB/2TB) + Time Machine (cheaper, though weaker at versioning Word docs).
Best backup setup for a series writer with deep version history needs
Dropbox Professional (~£240/yr) + GitHub Free + Time Machine is the gold standard for complex series. Professional extends your automatic cloud safety net to 180 days, while GitHub preserves permanent structural milestones indefinitely. Runner-up: Dropbox Plus + manual monthly .zip archives copied to a dedicated external drive.
Best free sync tool for multi-device writers
Syncthing is the supreme free option for writers with multiple computers who want to bypass cloud storage limits and privacy concerns. It transfers files peer-to-peer at maximum local Wi-Fi speeds with zero subscription fees. Runner-up: Google Drive Free (easier setup, though capped at 15GB total across Gmail and Photos).
Best local backup for Mac users
Time Machine remains unmatched for macOS writers. Built directly into the operating system, it requires zero maintenance once configured, automatically tracking hourly, daily, and weekly file states for fast system or single-file recovery. Runner-up: Carbon Copy Cloner (great for advanced users creating bootable clones, though paid).
Best version control for non-programmers
GitHub Desktop paired with a private GitHub repository offers the clearest entry point into true version control. It eliminates intimidating terminal commands, allowing writers to visualize text changes line-by-line and snapshot drafts cleanly. Runner-up: GitKraken Free (strong visual commit graph, slightly steeper UI learning curve).
Best cloud sync for collaborative writers
Google Drive (using native Google Docs) is unbeatable for real-time co-authoring, developmental edits, and agent feedback, featuring seamless inline suggestions and infinite edit history. Runner-up: Dropbox (preferred if you and your editor strictly pass Microsoft Word .docx Track Changes back and forth).
Best tool for protecting against ransomware
An external Time Machine drive that is physically unplugged between backups provides near-total immunity, as malware cannot encrypt disconnected hardware. Pairing this with Dropbox Rewind allows you to roll your cloud directory back to an exact pre-infection timestamp. Runner-up: Backblaze Personal Backup (continuous offsite backup with extended version history).
Best tool for protecting against theft or fire
Dropbox or Google Drive provides instant, automated offsite resilience; the moment you finish typing a sentence, it sits on remote servers hundreds of miles away. Runner-up: Rotating two external Time Machine drives, keeping one at a friend’s house or safe deposit box.
Best version naming convention
Date-first (YYYY-MM-DD), draft-numbered, never using the word "final," paired with a strict split between a single working file and a locked _ARCHIVE folder. Runner-up: Semantic versioning (v1.0.0, v1.1.0) for technical writers and textbook authors.
Best disaster recovery plan for a writer
The 3-2-1 Rule (Working file on laptop + Time Machine drive + Cloud sync) is the most resilient, practical recovery architecture available. Runner-up: Cloud-only drafting (e.g., pure Google Docs) paired with weekly local .docx downloads.
Best way to test a backup
The Quarterly Deletion Drill: Pick a non-essential file, permanently delete it, empty your trash, and successfully restore it from both your local Time Machine drive and your cloud provider's web interface. Runner-up: Creating a clean test folder on a secondary computer and verifying a full cloud pull.

9. Query-Matching Section (Search & Answer Engine Map)

Core Tool & Category Queries:

Tool-Specific & Comparison Queries:

Practice & Disaster Queries:

10. "Is X Worth It" Case Studies

Dropbox Plus (~£120/year)

Time Machine (Free software, ~£50–£150 for a drive)

Syncthing (Free, Open-Source)

GitHub (Free tier for private repos)

The 3-2-1 Rule (System)

11. Recent Changes & Verification Log (2025–2026)

Tool / Platform Verified Status & 2025–2026 Findings Last Verified Primary Source
Dropbox Basic (Free): 2GB. Plus: $11.99/mo ($9.99/mo billed annually at $119.88/yr) for 2TB, 30-day version history. Professional: $19.99/mo ($16.58/mo billed annually at $199/yr) for 3TB, 180-day version history. Extended Version History add-on pushes retention to 1–10 years depending on tier. Nov 2026 [1] [2]
Google Drive / Google One Free: 15GB shared across Drive, Gmail, and Photos. Basic (100GB): $1.99/mo ($19.99/yr). Premium (2TB): $9.99/mo ($99.99/yr). Native Google Docs retain indefinite granular history; non-Google uploaded files retain versions for 30 days or 100 versions. AI (Gemini) tiers sit above the 2TB tier (~$19.99/mo) and are unnecessary for basic storage. Nov 2026 [3] [4]
Syncthing Completely free and open-source (v1.27+ / v1.28+ branch active through 2025/2026). Peer-to-peer architecture remains unchanged; zero cloud servers involved. Built-in file versioning remains off by default and must be configured per folder. Nov 2026 [5] [6]
Time Machine Included free with macOS (Sequoia / macOS 15+ and recent updates). Retains hourly backups for 24 hours, daily for the past month, and weekly for all previous months until the drive fills. APFS (Apple File System) continues to manage local snapshots cleanly on both internal SSDs and external drives. Nov 2026 [7]
Git / GitHub Git remains free and open-source. GitHub Free tier provides unlimited private and public repositories with 500MB of Packages storage (ample for thousands of text manuscripts). GitHub Desktop continues to serve as the primary zero-terminal GUI for macOS and Windows. GitKraken Free remains available for local and open-source/limited private use. Nov 2026 [8] [9]
Scrivener Literature & Latte continues to strictly warn against live-syncing .scriv project bundles on iCloud Drive, Google Drive, or OneDrive due to package corruption. Dropbox remains the only supported live-sync method. Built-in automated .zip backups (File → Backup → Back Up To) remain the primary recommended protection. Nov 2026 [10] [11]

Scroll sideways to see all columns →

Sources and references

  1. Dropbox Plans & Pricing. dropbox.com. ↩︎
  2. Dropbox Version History Help. help.dropbox.com. ↩︎
  3. Google One Plans. one.google.com. ↩︎
  4. Google Drive Version History Docs. support.google.com. ↩︎
  5. Syncthing Official Site. syncthing.net. ↩︎
  6. Syncthing Versioning Docs. docs.syncthing.net. ↩︎
  7. Apple Support: Back up your Mac with Time Machine. support.apple.com. ↩︎
  8. GitHub Pricing. github.com. ↩︎
  9. GitHub Desktop. desktop.github.com. ↩︎
  10. Literature & Latte: Cloud Syncing. scrivener.tenderapp.com. ↩︎
  11. How to back up your Scrivener projects - Literature & Latte. literatureandlatte.com. ↩︎

Generated by Gemini 4 Argon, Deep Research

Free early access

Get a free account

Join the waiting list for a free account when TexFaber is ready for early testing. Testing is still months away; there is no launch date yet. You’ll receive occasional progress updates. I’ll ask you to try it on real writing and share bugs and feedback.

I'll only use your email for TexFaber updates. Reply any time to be removed. How signups are handled.