How to turn on auto save in VS Code on Mac: File menu steps for 2026

Auto save is off until you switch it on. VS Code expects you to save by hand, and on a Mac that means ⌘S. Most people forget that step at some point. A stray app switch can cost you a block of typing if the file never reached the disk. Auto save covers that gap by writing your changes for you.

Turn on auto save from the File menu

The fastest route is the File menu. The official Basic editing docs call File > Auto Save the easiest way to turn it on. The item works as a switch. Turn it on and VS Code saves on a timer. Turn it off and the timer stops. You never open a settings file to use it.

The toggle changes one setting, files.autoSave. It sets that value to afterDelay. The rest of your settings stay the same, so you can come back to the menu later without undoing other choices.

Choose a save trigger that fits how you work

Auto save has four values, and the menu toggle only covers one of them. The table shows what each value does and who it suits.

afterDelay is the one most people want. The timer resets each time you type, so VS Code waits for a pause before it writes. With the default of 1000 ms, a pause of one second triggers the save. The file on disk stays a little behind your typing, but only by that pause.

onFocusChange and onWindowChange work differently. They do not save while you type. They save when you move somewhere else. They suit people who switch between the editor, a terminal, a browser, and a chat app many times a day.

Set the delay and see what it does

The delay lives in files.autoSaveDelay and is measured in milliseconds. The default is 1000. A higher number waits longer before it writes. A lower number writes sooner, which protects more of your work but also means more writes to disk.

Here is a common case. You write a function in a Python file, pause to check a variable name, and keep typing. If your pauses are shorter than one second, VS Code keeps waiting. The save happens only when you stop for the full delay.

Change the value in small steps and test each one. Type a sentence, stop, and watch how long the dot on the tab takes to clear. If the wait feels too long or too short, adjust and test again. There is no single right number. Pick the one that matches your pauses.

Edit settings.json when you want full control

The JSON route puts every auto save option in one file. Open Settings with ⌘, and search for files.autoSave to see the current value. For the raw file, run the Command Palette command Preferences: Open User Settings (JSON). User settings apply to every project on your Mac.

Workspace settings are a separate file. They live in the .vscode folder inside a project, and they override your user settings. A project can quietly turn auto save off. If your change does nothing, check that folder first.

Auto save for some folders and languages

VS Code 1.86, released in January 2024, let you set every Auto Save option per folder or per language. The official docs show an example that turns auto save off for LaTeX files. That pattern helps when one file type needs manual saves while the rest of your project saves on its own.

Two more settings narrow the rule. files.autoSaveWhenNoErrors skips auto save when a file has error markers. files.autoSaveWorkspaceFilesOnly limits auto save to files inside the workspace, so files you open from elsewhere stay under manual control.

Common mistakes with auto save

The first mistake is assuming auto save commits to Git. It writes files to disk. It does not record a commit. If you want a history, commit on your own schedule. The Git setup guide walks through that part.

The second mistake is treating auto save as undo. It saves whatever state the file is in. If a half-finished edit breaks your code, auto save writes that break to disk too. Use Undo with ⌘Z to back out the edit, and commit your work as checkpoints.

The third mistake is trusting the menu checkmark alone. Test with a real edit. Type, pause, and watch the tab. That check takes only seconds and tells you more than the menu does.

The fourth mistake is pressing ⌘S out of habit and assuming it is wasted. It is not. A manual save still helps when you want the file written at an exact moment, such as right before you run a script.

Auto save in VS Code for the web

The browser version at vscode.dev handles auto save differently. When it is on, auto save applies to local files. Edits to a remote repository stay in browser local storage until you commit them. A change that looks saved in a remote repo is not in the repository yet. Commit it to make it permanent.

Check your version before you search for the item

The current stable release is VS Code 1.145, released November 4, 2026. Its release notes do not mention Auto Save, files.autoSave, or File menu changes. The last documented Auto Save change is in the 1.86 release notes from January 2024.

If your File menu looks different from this guide, update VS Code first. Then compare the menu with the official docs. The docs give the Settings path as File > Preferences > Settings, but some Mac menus show it under Code. Use ⌘, to skip the guesswork.

Turn auto save off again

Open File > Auto Save and click it again to switch it off. You can also set files.autoSave to off in settings. Either way, your files go back to manual saves, and ⌘S saves them as before.

Where to go next

Once auto save runs, you may want to tune the rest of your editor. Read how to toggle the integrated terminal in VS Code on Mac next, or set up Git in VS Code on Mac so your saved files get committed. The VS Code page lists more guides for the same app.