Why the Save Conflict Happens
Few things break a coding flow like a blocked save. You hit Ctrl+S, but instead of the usual quick flash, a notification pops up in the bottom corner. It tells you the file on disk is newer. This isn't a bug—it's a safety net.
VS Code keeps a "snapshot" of your file when you open it. If a background process or another person changes that file on your hard drive while you still have unsaved edits, the timestamps no longer match. To prevent you from accidentally overwriting work you haven't seen yet, VS Code freezes the save process and asks for your input.
Typical Triggers
Most of the time, this error isn't a mystery. It usually stems from one of these 4 scenarios:
- Git Maneuvers: You pulled the latest changes (
git pull) or switched branches in an external terminal while the file was still open. - Aggressive Tooling: Background scripts like a
huskypre-commit hook or an externalprettier --writecommand modified the code for you. - Cloud Latency: Dropbox or OneDrive synced a 2KB update from a teammate, making your local version "old" in the eyes of the OS.
- Ghost Instances: You have the same project open in two different VS Code windows or a separate editor like Vim.
Step-by-Step Fixes
Method 1: The Compare Tool (Smartest Choice)
Use this when you aren't 100% sure what changed on the disk. It prevents code loss on both sides.
- Click Compare in the error toast.
- VS Code launches a side-by-side Diff view. The left pane shows the File on Disk (the intruder), and the right pane shows Your Version (your current work).
- Review the lines. If you see a function on the left that you need, copy it over to the right.
- When the right side looks perfect, click Overwrite in the top action bar.
Method 2: Force Overwrite (Quickest Choice)
Only do this if you know your current editor window contains the "Source of Truth."
- Look for the Overwrite button directly in the notification.
- Selecting this nukes the version on your hard drive and replaces it with your current buffer. The external changes will be gone forever.
Method 3: Revert Changes
Choose this if you realize your local edits were a mistake and the disk version is actually what you want.
- Click Revert.
- VS Code clears your unsaved work and reloads the file from the disk. Note: You cannot "Undo" (Ctrl+Z) a revert, so be certain before clicking.
Tweak Your Settings
If you face this error five times a day, your workflow might be clashing with VS Code’s default behavior. You can change how the editor reacts in your settings.json.
Change the Conflict Strategy
Search settings for Save Conflict Resolution. The default is askUser. Switching this to overwriteFileOnDisk stops the warnings but makes your saves "destructive"—it will silently kill any external changes.
// settings.json
"files.saveConflictResolution": "askUser" // Stay here for safety
Enable Auto Save
Conflicts often happen because we leave files unsaved for too long. Shorten that window by saving automatically when you switch tabs.
// settings.json
"files.autoSave": "onFocusChange"
Pro-Tips for Prevention
To keep your workspace tidy, bring your tools inside the editor. If you use Prettier, install the VS Code extension instead of running a terminal watcher. This allows the extension to talk to the editor directly, preventing timestamp mismatches. Also, get into the habit of saving all files (File > Save All) before running major Git commands in your terminal. This keeps the disk and the editor in perfect sync.