How does Milton save your work without a save button?

Milton saves your work automatically after every change, so there is no save button to press. According to the project's own description, "Your work is saved every time you make a change. There is no need for a save button." This applies to anyone using Milton on a supported platform (Windows 7 and up; it also compiles on Linux). The practical effect is that you never have to decide when to save — the file on disk always reflects your latest edit.

What "no save button" actually means

Milton is described as a free and open-source infinite canvas paint program. Its save behavior is tied to how it stores work:

• Every change is written automatically. You do not trigger a save, and there is no separate "unsaved changes" state to manage.
• Undo and redo are unlimited and persist after you close the app. Because the edit history survives closing and reopening, the app is keeping more than just the current image — it retains the sequence of changes.
• Milton files are very small. The project states this directly, which is consistent with storing work as vectors rather than a large pixel grid.

Why the files stay small

Milton "feels raster-based but it works with vectors." You draw with what the project calls infinite detail on an infinite canvas, but the underlying data is vector-based. Vector data describes shapes and strokes rather than storing every pixel, which is why files remain small even on a large canvas. When you need a pixel image, you export instead: Milton exports to JPEG or PNG "at any resolution your machine supports," and to bitmaps of any size.

A concrete example

Suppose you are painting a detailed illustration and step away without saving. Under a traditional paint program, closing the window might prompt "Save changes?" and an accidental discard could lose the session. In Milton, the latest change is already saved, and your undo history is still there when you reopen the file — so you can step backward through edits made before you closed the app.

The trade-off to plan for: since the working file is vector-based, the way to get a flat raster image is the export step. Decide your target resolution at export time, because the export — not the save — is where pixel dimensions are set.

What to check before relying on it

• Platform: Windows 7 and up is the supported Windows range per the project; Linux builds compile, and the project notes work is being done on a for-profit macOS version. If you are on macOS, confirm current availability before depending on it.
• Export, not save, for sharing: plan to export to PNG or JPEG at the resolution you need when handing work to others.
• Version: the site footer credits Sergio Gonzalez and shows a 2015–2019 range, so verify you have a current build from the official download page rather than an old copy.

If automatic saving with persistent undo and small vector-backed files matches how you like to work, Milton's model removes the save step entirely; if you need a specific raster size for delivery, treat export as the final step of every session.