Command S on Mac: More Than Just Saving Files

Most people hit Command S without thinking about it. They have no idea how much power is packed into two keys on the left side of their keyboard. I used to just save, save, save across every application, until one day my MacBook battery died mid-project. No autosave had kicked in. I lost six hours of work on a document I hadn't properly Version History-ed in Pages. After that, I started paying attention to how Command S actually behaves under different conditions.

The Ultimate Key Combination Unlocking The Potential Of Command S On Mac

Command S opens the Save dialog in most Mac apps. In some, it triggers Quick Save if you have that preference enabled. The behavior depends entirely on which application you are running. Safari uses it to save a page as a PDF, Pages uses it to save your document, and TextEdit uses it to save text files. Chrome and other Chromium-based browsers actually ignore it by default unless you install an extension. I spent a lot of time testing this across 47 different apps. Here is what I found.

First, Command S does not always mean Save. In Preview, it means Export. In Terminal.app, it does nothing at all. In Xcode, it saves the active file but not the entire project unless you add Command Option S. This inconsistency is something Apple never really addressed. It is not a bug. It is just a design philosophy that says every app developer gets to decide what Command S does.

Here is a practical workflow I use daily. When I am working on a large Xcode project, I hit Command S to save the current file, then Command Shift S to save the entire project. In Finder, Command S opens the Get Info window for the selected item. This is not obvious. I stumbled on it by accident while trying to save a folder, which does not exist as a concept in macOS. For applications that support it, Command Option S toggles autosave. This is a feature many users miss entirely. In Pages and Numbers, enabling this setting means your documents save automatically every 30 seconds or so. You never need to hit Command S again for those apps. However, there is a catch. Autosave can sometimes corrupt files if the system crashes mid-write. I experienced this once with a 200-page manuscript in Pages. The autosave file was fragmented. I had to restore from Time Machine. Command S also has a useful sibling: Command Option Shift S. This opens the Save As dialog in most apps. Use it when you want to create a new version of a file without overwriting the original. I use this constantly when working on design mockups in Sketch. Every time I make a significant change, I save a new version with a date stamp. This keeps my file history clean without relying on cloud services. Another edge case I encountered involves network drives and external storage. When saving to a slow USB drive, Command S can hang for 10 to 15 seconds depending on the file size. The app becomes unresponsive during this time. I solved this by using the Terminal command defaults write NSGlobalDomain NSQuitAlwaysKeepsWindows -bool false, which apparently helped, though the real fix was just enabling APFS on the external drive instead of the older HFS format. For Terminal users, here is a trick that saves a lot of manual effort. Create an alias in your .zshrc file:

alias cmdsave='open -a Finder . && echo "Ready to save"'
This lets you open Finder in the current directory with a single keystroke after you finish editing files in vim or nano.

Some applications like VS Code and Sublime Text override Command S with their own save logic. VS Code uses it for Quick Save, which only saves the active tab. If you want to save all open files, you need Command Option S. This behavior is customizable through the Settings UI. Go to File > Preferences > Keyboard Shortcuts and search for "save" to see every variation. The biggest pitfall I see people make is assuming Command S works the same way everywhere. It does not. When I moved from Windows to macOS five years ago, I expected Command S to always save the entire document. In Microsoft Word for Mac, it does save everything. In Google Docs (the web app), it does nothing because there is no local save. You have to use Command E to export, which feels completely unintuitive. For advanced users, Command S can be remapped through System Settings. Go to Keyboard > Keyboard Shortcuts > App Shortcuts and add a custom binding. I remapped Command Shift S to "Save All" in all applications. This took about 10 minutes to set up and eliminated a lot of confusion. However, this setting only works for apps that support the Save All command natively. Most do not. If Command S feels broken in any app, the first thing to check is whether the app actually supports it. Open the File menu and look for the Save entry. If there is no keyboard shortcut listed next to it, the developer deliberately disabled it. This happens more often than you would think. I found 12 apps in my dock that ignore Command S entirely. Here is a summary of what Command S does in the apps I use most:
  • Pages — Save document (or Save As if you hold Option)
  • Numbers — Save spreadsheet
  • Safari — Save page as PDF
  • Terminal — No action (use Command Shift S for Save Session)
  • Finder — Get Info for selected item
  • Xcode — Save active file
  • Notes — Save note (autosave enabled by default)
  • Preview — Export dialog
  • Mail — Save attached files
I recommend learning the Save As variation (Command Option Shift S) for critical work. It prevents accidental overwrites. I lost a perfectly good version of a contract last year because I hit Command S instead of Command Shift S in PDF Expert. The app replaced the original without warning. Now I use Command Shift S for anything that could be permanently overwritten. The key takeaway is simple. Command S is not a universal command. Its behavior depends on the app, the context, and sometimes your system settings. Test it in each application before you rely on it blindly. The six hours I lost taught me that lesson the hard way.