No bundled browser runtime
The interface is SwiftUI and AppKit. There is no embedded Chromium, which is the single largest line item in most modern editors’ memory use.
A guide to a much-abused word
“Lightweight”
is a measurement, or it is marketing.
Every editor calls itself lightweight. Almost none of them publish a number, and the ones that do rarely say what they measured or on what. Here is our number, what it is, and — more usefully — what it is not.
Studio 1.4.0 · macOS 14+6.5 MB download
The mechanism
What makes an editor heavy, and what we did about each.
Weight in an editor comes from a short list of decisions. Naming them is more useful than a number, because they tell you how the app will behave on your files rather than on ours.
No continuous project indexing
Nothing walks your folder in the background building a symbol database. Folder search reads files when you search and not before, which is why there is no “indexing…” state to wait out.
Tools wake when the file needs them
The document map, the lexer and the diff view do work in response to what you are doing, rather than maintaining a live model of a project you have not asked about.
A 6.4 MB download
The whole notarized disk image. Size on disk is not the same as memory use, but it is the one number nobody can fudge.
Session restore instead of staying resident
Layouts, tabs, untitled documents and unsaved edits come back after a quit or a crash, which removes the reason to leave an editor running purely to avoid losing state.
No LSP, no ctags, no symbol index
The features that make an editor heavy are absent, and that is a trade rather than an achievement — see the limits below.
Specifics
The published snapshot, in full.
One session, one machine, one build. It is offered as evidence that we measured something, not as a ceiling or a promise about your files.
| Measurement | Value |
|---|---|
| Activity Monitor | 69.9 MB |
| Physical footprint (Apple’s footprint tool) | 70.3 MB |
| Peak footprint in the session | 106.7 MB |
| Session length | 2 h 34 min |
| Machine | Apple M5 Pro · 24 GB |
| System | macOS 26.5.2 |
| Build observed | Studio 1.0 |
| Date observed | 26 August 2026 |
Read from the Linelark Studio 1.4.0 source, not from its documentation. Where the two disagree, this is the one that ships.
Before you rely on it
Why you should not treat that number as a benchmark.
Published with its caveats attached, because a memory figure without them is worth nothing and everybody knows it.
- It is one observed session, not a controlled testNo competing editor was run alongside it under the same conditions. It is not a cross-editor benchmark and is not presented as one.
- Your files decide your numberOpen files, pane layouts and active terminals all cost memory. A session with four panes and three shells will not look like this one.
- It was measured on Studio 1.0The current release is 1.4.0. The figure has not been re-measured for every release since, and it says so.
- Lightweight means features are missingNo language server, no symbol indexing, no project model. If you want those, an editor that carries them is the right tool and will weigh more for good reason.
Free, and staying free
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