Where your edits are saved in Unmarked

Unmarked autosaves as you type, writing your changes straight back to the original file. There's no Save button and no unsaved-changes state to track. The one exception is a brand-new untitled document: save it once to give it a name and a place, and from then on it autosaves like everything else.

When you open a file in Unmarked, you're editing that file, not a copy of it. Type a sentence, toggle a task checkbox, fix a heading, and the change lands in the file on disk. No keystroke, no menu trip, nothing to remember. The little dot in the title bar that other apps use to mean "you have unsaved work" never shows up here, because there's never unsaved work.

How it works

1. Open a Markdown file with Open (⌘O), or pick one from Recent on the home screen.
2. Edit it. Press ⌘E to switch into Write mode, or stay in Read mode and tick a task checkbox.
3. That's it. Your changes are already saved to the file you opened.

The file Unmarked saves to is the exact one you opened, in the exact spot it lives. Put another way: if you opened a file out of an iCloud Drive or Dropbox folder, that's where each keystroke lands, and the sync happens from there like it does for anything else in that folder. Unmarked doesn't make a second copy or stash anything in a hidden folder.

The one time you'll press ⌘S

A new document started with New (⌘N) has no name and no home yet, so there's nothing to autosave into. Give it one:

1. Press Save (⌘S).
2. Choose a name and a folder.
3. From that point on, it autosaves like any other file. You won't press ⌘S again for that document.

⌘S here means "name this new file," not "save." Once a file has a name, the app handles the rest.

What about undo?

Because writes happen as you type, the file on disk always reflects the current state. Undo and redo (⌘Z / ⇧⌘Z) walk back your edits within the open document, and each step you walk back is saved as you go. Delete a paragraph, change your mind, hit undo, and it comes back. What undo won't do is reach a version from last week after you've closed the file. For that, lean on Time Machine or your sync service's version history.