Buy

Saving & history

Free

The editor is built not to lose anything. It saves local files by itself, notices when a file was changed outside, tidies up on save if you want, and keeps earlier versions you can go back to, even without Git.

What you do here

Saving by hand

Action Shortcut or way
Save ⌘S
Save all ⌥⌘S
Reload file from disk File menu or command palette; discards unsaved changes after asking
Save with encoding click the encoding in the status bar (Encoding, line endings and language)

A dot in the tab shows unsaved changes. You also save images, PDFs and office documents in their viewers with ⌘S (Viewers for files without text).

Files on a server

Files you opened from a server are saved by ⌘S into the editor's working copy, not onto the server. You upload with Upload or Upload to … (Remote files). If a project is paired with a server folder and Upload on save is on there, every ⌘S also uploads the file. Files with credentials such as .env, wp-config.php or auth.json are never uploaded that way; the editor tells you to edit them directly on the server. See Sync.

Free and Premium

Saving, autosave and the local history are free. Files on servers and uploading are part of WebDonkey Premium.

Save automatically Free

The editor saves local files by itself as soon as you stop typing for a second. You don't have to think of ⌘S, and a build or a browser reload always sees your latest version.

Where to find it

Settings › Editor, group Typing: Save automatically. It is on out of the box.

When the editor saves

  • 1 second after the last keystroke. Every keystroke pushes the moment back, so it saves at every pause in your typing, not just once.
  • When the window loses the focus, for example when you switch to the browser: then every changed file at once.

If a save of the same file is still running, autosave waits another second, so an older version never lands last.

Where it doesn't apply

Case What happens
Files on a server saved only into the editor's working copy, never onto the server (Remote files)
File changed or deleted outside nothing is saved, the decision is yours (Conflicts with the disk)
Images, PDFs, Excel and Word in a viewer never automatically; you save such changes with ⌘S
Format on save (⌘S) formats only on ⌘S, never on autosave
Upload on save of a paired server folder uploads only on ⌘S, never at every typing pause
Line break at the end of the file not added on autosave while you type in the last line, so the cursor doesn't jump

When quitting and closing

When you quit (⌘Q), choose Reload window, close a project window, open another project in the same window, and before the restart after an update, the editor first saves everything autosave would have saved anyway. After that it only asks about what is left, such as viewers with changes: Save, Don't save or Cancel. The same question comes when you close a single tab with changes.

Troubleshooting

What you see Why What to do
The dot in the tab stays the file was changed outside, or autosave is off look at the notice above the file or press ⌘S
A file is saved before you are done autosave runs at every pause switch it off or go back with the local history

See also

Conflicts with the disk Free

If another program changes a file you have open, such as Git switching branches, a build or another editor, the editor notices. It never quietly overwrites someone else's version but lets you decide.

Where to find it

The editor watches your project's files and also checks when its window gets the focus back. A conflict shows as a bar above the file or as a question when saving.

You haven't changed anything

The file quietly reloads. Cursor, selection and the ⌘Z history are kept, because the editor only swaps the lines that changed.

You have unsaved changes

A bar appears above the file: "The file was changed outside the editor while you have unsaved changes." Autosave stops for this file.

Button What happens
Compare opens both versions side by side (see below)
Reload (discard mine) takes the version on disk, your changes are gone
Keep mine the bar disappears and your version stays; the next save asks again

If you save anyway, the editor asks “Name” was changed on disk. It recommends comparing both versions first:

Button What happens
Compare opens the comparison, nothing is saved
Overwrite writes your version over the file
Cancel nothing happens

The comparison

The comparison shows the version on disk on the left and yours on the right. The toolbar above it:

Button What it does
Previous change, Next change jumps between the differences
Inline view or Side by side switches the layout
Keep mine (overwrite) saves your version
Take version from disk loads the version on disk into your editor

You can keep editing the right side before you save. The top shows how many changes there are.

File deleted or moved

If the file disappears, the tab says: "The file was deleted or moved outside the editor." Your text stays in the editor. Save again creates the file with your text again.

In viewers

Images, PDFs and office files behave the same: without changes the viewer quietly reloads, with changes the bar with Reload (discard mine) and Keep mine appears. When saving, the editor asks "The file was changed on disk after you opened it. Overwrite it with your version?" with Overwrite and Cancel.

Files on a server

For files from a server the same applies, with the server instead of the disk. If the file changed there, the editor asks “Name” was changed on the server. More under Remote files.

Troubleshooting

What you see Why What to do
The bar shows up with every build the build writes files you have open close those files before building or Reload after it
Many tabs changed after a branch switch Git replaced the files without changes of your own the editor reloads quietly; otherwise compare

See also

Actions on save Free

When saving, the editor can tidy up the file: remove spaces at line ends, put a line break at the end of the file and format the code. An .editorconfig in the project takes precedence over your settings, so the whole team works with the same rules.

Where to find it

Settings › Editor, group On save. Everything is off out of the box.

Settings

Setting What it does Note
Remove trailing spaces removes spaces and tabs at the end of every line not in Markdown, where two spaces mean a line break, and never in the line the cursor is on
End files with a line break makes sure the file ends with a line break not on autosave while you type in the last line
Format on save (⌘S) formats the whole document like Format document only on ⌘S, never on autosave; only for languages with a formatter: JSON, CSS, HTML, JS/TS

Removing the spaces and the final line break go into the history together as one step. ⌘Z takes them back together.

.editorconfig

If the project has an .editorconfig, it applies per file ahead of your settings. The editor looks for it from the file's folder upwards, up to a file with root = true, and combines all it finds.

Key Effect
trim_trailing_whitespace remove trailing spaces, also in Markdown if the file asks for it
insert_final_newline line break at the end of the file
indent_style, indent_size, tab_width indentation, applied when the file opens
end_of_line line endings for new, empty files

When you save a changed .editorconfig, it applies to every file you open or save afterwards. For files on a server the editor doesn't read an .editorconfig.

More actions

Action What it does
Save all (⌥⌘S) saves every file with changes
Reload file from disk loads the version on disk; with unsaved changes the editor asks "Discard your changes?" and offers Discard and reload or Cancel
Compare with HEAD shows your changes since the last commit in a comparison
Save with encoding saves in another encoding, see Encoding, line endings and language

Troubleshooting

What you see Why What to do
Spaces stay the setting is off, the file is Markdown, or the cursor is in that line check the setting, move the cursor and save again
A file's indentation differs from your settings an .editorconfig sets other values adjust the .editorconfig
Format on save does nothing there is no formatter for the language, or you saved automatically press ⌘S; for other languages run a formatter in the terminal

See also

Local history Free

Every time you save, the editor keeps the previous version of the file. That way you get back, even without Git, for files that aren't in the repository, after an autosave at the wrong moment or after a change Claude made.

Where to find it

  • File › Local history in the menu bar (for the active file)
  • right-click a file in the project tree › Local history
  • command palette: Local history

How to do it

  1. Open the file's local history. A tab opens with the file's name and an arrow in front of it.
  2. Under Versions on the left are the saved versions, newest first, with the time since they were saved.
  3. Pick a version. On the right, the comparison "Earlier version ↔ name now" shows the difference to the current state.
  4. Click Restore.

For text files, the old text comes into the editor as one step. ⌘Z takes it back, ⌘S keeps it. For images, PDFs and office files, the editor writes the chosen version straight back and reports "Version restored". The version it replaces goes into the history itself, so you can go back again.

If nothing has been saved yet, it says there are no earlier versions.

What is kept

Text files Images, PDFs, office
up to a size of 2 MB 50 MB, adjustable
versions per file at most 40 at most 10
kept for 30 days 30 days
  • At most one version per five minutes is kept. If you save more often, for example through autosave while typing, the state before that stretch of work is the one kept.
  • A version identical to one already kept isn't stored twice.
  • Before a Replace in files, the editor keeps a version of every affected file so the replace can be taken back (Find).

You set the size for images and documents under Settings › Files & formats, group Local history: Keep binary files in the local history up to (0 to 200 MB, 0 turns it off).

What happens in the background

The history covers files on your Mac. The editor stores it in its own folder, under ~/Library/Application Support/app.webdonkey.editor/history/, not in the project. It therefore never ends up in the repository and takes no space there.

Troubleshooting

What you see Why What to do
No earlier versions the file hasn't been saved since it was opened, or it is larger than the limit save once; use Git for large files
Local history opens nothing the active file is on a server the history only exists for files on your Mac
A version from six weeks ago is missing versions are kept for 30 days use Git for older states

See also

Cookie preferences

This website uses cookies to ensure the best experience possible. Your choice applies to webdonkey.io and the shop at shop.webdonkey.io. More information...

Technically required

Cookies required for this website to function:

Always on
WebDonkey
WebDonkey
Provider: BuI Hinsche GmbH, Neumarkt 7, 06712 Zeitz, Germany
Purpose: Your consent, colour scheme and language for website and shop, price switches; with wd_debug in the address, the measurement events in the developer console for troubleshooting
Cookies and storage: Cookie wd_consent on .webdonkey.io, shared with shop.webdonkey.io (12 months); cookies wd_theme and wd_lang on .webdonkey.io, shared with shop.webdonkey.io, only when you switch colour scheme or language yourself (365 days); localStorage wd:consent, wd:theme, wd:lang; sessionStorage wd:acc, wd:term, wd:debug (only with wd_debug in the address; until the tab closes)

Statistics

Shows us which pages and products people look at on webdonkey.io and in the shop, where visitors come from and how they get to a purchase (with order number, amount and products, without name or email address). Provider: Google. Transfer to the USA possible (EU-US Data Privacy Framework). Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Google Analytics 4
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Google Analytics 4
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Usage statistics: page views, clicks, scroll depth, sources, devices, load times; in the shop also basket, checkout, purchases, registration and sign-in
Cookies and storage: _ga, _ga_<ID> (2 years)
Privacy policy

Marketing

Measures whether our ads on Facebook, Instagram and TikTok lead to visits and downloads on webdonkey.io and to registrations and purchases in the shop, and builds audiences for ads. Providers: Meta and TikTok, with whom we are jointly responsible for this. With this consent Google may also set advertising cookies (_gcl_…). Transfer to the USA and other countries outside the EU possible. Your choice applies to webdonkey.io and the shop together.

Google Tag Manager, Meta Pixel (Facebook, Instagram), TikTok Pixel
Google Tag Manager
Provider: Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland
Purpose: Loads the services you agreed to, here and in the shop. Sets no cookies of its own.
Cookies and storage: none
Privacy policy
Meta Pixel (Facebook, Instagram)
Provider: Meta Platforms Ireland Limited, Merrion Road, Dublin 4, D04 X2K5, Ireland
Purpose: Ad measurement and target groups on Facebook and Instagram, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _fbp (3 months), _fbc (3 months, only if you arrive through an ad), fr on facebook.com (3 months)
Privacy policy
TikTok Pixel
Provider: TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland
Purpose: Ad measurement and target groups on TikTok, also in the shop (basket, checkout, purchases, registration)
Cookies and storage: _ttp, _tt_enable_cookie (13 months)
Privacy policy