Your unfinished session
comes back.

Type into a new tab, quit without saving, and the tab is still there next time. That is the Notepad++ trick, and it is the one behaviour people miss most when they move to a Mac editor that treats every buffer as a file or nothing.

Studio 1.4.0 · macOS 14+6.5 MB download

What is written, when, and where.

Two things are kept: a manifest describing the window, and the text of any buffer with unsaved work. They are separate because most tabs need only the first.

01

A manifest describes the window

Which buffers were open, the ids in each pane in tab order, which tab was on top of each pane, and which pane was active. A buffer showing in two panes appears in both, so a split is restored as a split rather than as two copies.

02

Only dirty buffers get their text backed up

A saved file with no edits records no backup — the disk is the truth for those, so reopening picks up whatever changed while the app was closed rather than restoring a stale copy over it.

03

Untitled tabs keep their number

“new 3” comes back as “new 3” rather than being renumbered, because the number is stored with the buffer and is also what Save As offers you.

04

Language, encoding and line endings travel with the tab

A file you had reinterpreted as Shift-JIS is still Shift-JIS after the restart. The tab’s format is part of the snapshot, not something re-guessed on open.

05

Backups are written while you type

Off the main thread, through one serial queue so writes land in order — and the queue is drained before the process exits, so a normal quit does not race the last keystroke.

06

Retired backups are kept for fourteen days

Superseded backups are moved aside rather than deleted, into a folder that is swept after two weeks. Long enough that somebody who notices the next morning still has it; short enough that it is not an archive.

What returns, and what does not.

The boundary matters more than the feature. Recovery here means Linelark’s snapshot of your session, and nothing wider than that.

After a quit or a crashRestored?
An untitled tab you never savedYes, with its text and its number.
Unsaved edits to a saved fileYes, from the backup written as you typed.
Which files were open, and in which paneYes, including one buffer shown in two panes.
The pane layout and the active paneYes.
Each tab’s language, encoding and line endingsYes.
A saved file with no unsaved editsReopened from disk, so external changes are picked up.
A file you closed before quittingNo. Closing a tab takes its backup with it.
A file you deleted in FinderNo. This is not a filesystem undo.

Read from the Linelark Studio 1.4.0 source, not from its documentation. Where the two disagree, this is the one that ships.

What this is not.

Session recovery is easy to oversell into sounding like a backup system. It is not one, and the difference is worth being blunt about.

  • It is not a backup of your filesBackups exist only for buffers with unsaved work, they live in the app’s own Application Support folder, and they are discarded when the tab is closed. Nothing is written next to the files you keep.
  • Closing a tab is a decisionA closed tab takes its backup with it. Recovery protects you from a crash and from quitting, not from having tidied up.
  • It is not version historyOne snapshot of the current state, not a timeline. There is no way to go back to what a buffer held an hour ago.
  • Retired copies expireA superseded backup is reachable for fourteen days and then swept. That window is deliberate, but it is a window.

Open it on
your own files.

Apple-notarized, macOS 14 and newer, Intel and Apple silicon.

Choose a release 6.5 MB · versioned checksums on the download page