Introduction
If you’re a developer, game designer, video editor, or writer, where you save your work matters. One wrong decision could cost you hours, days, or even weeks of progress.
In this post, we’ll explore why saving to your root drive (like C:\) is a terrible idea, why version control matters, and how proper backup strategies can save your sanity.
The Risk of Saving to Your System Drive
Many users default to saving their projects directly on the OS drive, usually C:\ on Windows or / on Linux/macOS. It seems convenient, but it’s risky.
Why It’s a Problem:
- OS drives are constantly changing, they’re updated, patched, and rebooted often.
- System crashes or reinstalls can wipe everything.
- Backups treat OS drives differently, many exclude them by default or de-focus on them.
- Corporate backup software often deduplicates data across systems, risking user-specific data loss (more on that shortly).
Smarter Save Locations
Instead of dumping your files onto the system drive, use:
C:\Users\<username>- A secondary internal drive
- A dedicated external SSD/HDD
- A NAS or SAN (e.g., Synology)
- A file server or mapped network location
Why? These drives are isolated from the OS and easier to back up or restore independently.
What About Those OneDrive Folders?
Open C:\Users\<username> and you may see folders named OneDrive and OneDrive - <Company>. You did not make these. Windows creates them when you sign in with a Microsoft or work account, and they are local copies of files that sync up to Microsoft’s cloud.
Here is what that means for where you save:
- Files inside a OneDrive folder sync to the cloud, so they get an offsite copy automatically. That counts as a backup as long as you stay signed in and trust the account.
- Windows 11 often redirects your Desktop, Documents and Pictures into OneDrive, so work saved there syncs too, even though it still looks like a normal
C:\folder. - Anything you save outside OneDrive, like a loose project folder on
C:\or a quick download, syncs nowhere. Those are the files this post is warning you about.
So the OneDrive folders are not the danger. The danger is the work you save next to them that never gets backed up. Know which of your folders sync and which do not, then pick a save location you control and back it up on purpose.
Backup Tools You Should Know
If you’re working solo, here are options that help:
OS-Level Backups
- Windows: File History or full system backups
- macOS: Time Machine
- Linux: rsync, Borg, Timeshift, and more
Network Backups
- Synology NAS: Includes software for Mac, Windows, and Linux
- WD My Cloud: A solid external backup option
- Other tools: Acronis, Macrium Reflect, Veeam (free edition), and more
Enterprise-Scale: The Deduplication Trap
In larger orgs, backups are often handled by tools like:
These tools use deduplication to save space, which can unintentionally destroy unique user files if everyone saves similar data (like cloned repos).
Real-World Example
Imagine four devs clone the same GitHub repo to their C:\ drive. They each make different changes.
A backup system deduplicates the files, keeping only the latest change (change 4). If change 2’s author needs a restore, their version is gone. Deduplication thought the files were redundant.
This is why each user should save work in their user folder (C:\Users\<username>) or another uniquely identifiable path. Backup tools are designed to treat these areas as personal data sources, and retain them as such.
Best Practices Summary
- Never save critical files to your root/system drive
- Use a dedicated location: external drive, second internal disk, NAS/SAN
- Enable and monitor backup tools that fit your setup
- In enterprises, stick to user folders to avoid dedup wipeouts
- Use version control for code and project changes (see Part 2)
Up Next: Version Control
This is just one part of the equation. In Part 2, we dive into why version control isn’t optional in 2025, and how to implement it without pain.
Read Part 2: Git Good, Why Version Control Is Mandatory in 2025
// comments