Inkline is a native Mac editor built for the files that "break" everything else
Inkline is built to keep multi-million-line JSON, JSONL, logs, exports, and generated text usable.
Every developer I know has a version of the same story. A log export lands in your downloads folder, you double click it, and your editor spends the next ninety seconds deciding whether it wants to live.
Inkline, a new Mac editor from Swedish developer Viktor Nyberg, is built around exactly that moment, and after digging through what it claims to do, I think it is aiming at a real gap rather than a marketing one.
This is a small, native, single purpose app that wants to be the thing you open when a file is too big or too ugly for the editor you love.
What is Inkline
Inkline is written in Swift with AppKit, which the developer is very clear about. It is not a web view wearing a Mac window. That distinction matters more than it used to, because most of the editors people reach for now are Electron apps that carry a browser around with them.
The download is 3.7 MB. Not gigabytes. Megabytes.
It requires macOS 14 or later and a Mac with Apple silicon, so Intel holdouts are out of luck here.
The headline feature is large file handling. Inkline claims it will open, search, scroll, and edit JSON, JSONL, logs, and generated exports with millions of lines while staying responsive, with streaming formatters, visible progress, and the ability to cancel a reformat that is taking too long.
That last detail is the one that tells me the developer has actually lived this problem.
The feature list is genuinely deep
Where this gets interesting is how much is packed in beside the editor. There are 19 bundled syntax languages covering the usual suspects (Swift, TypeScript, Rust, Go, Kotlin, YAML, TOML and so on), with support for Zed compatible language extensions when your project uses something outside that set.
Then there are 78 text commands. These run on a selection or the whole document, and they cover the stuff you normally solve with a throwaway script or a sketchy website, sorting and deduplicating lines, normalizing line endings, converting between CSV, TSV, JSON, dotenv, Java properties, and query strings, encoding and decoding Base64 and JWTs, generating hashes, inserting UUIDs, switching identifier casing, formatting HTML, CSS, and SQL.
On top of that sit ten Developer Tools that open beside your document. Regex, Diff, Markdown preview, Password, QR Code, File Base64, File Converter, File Integrity, Unicode Inspector, and Cron. The Unicode Inspector is the one I would probably use most, because tracking down an invisible character that is quietly breaking a parser is a special kind of misery.
There is also a terminal with tabs, a Git changes panel, debug launch profiles, split editors, a minimap, a command palette, and quick open. That is a lot of surface area for a 3.7 MB app.
The privacy stance
No analytics. No telemetry. No advertising. No crash reporting. The App Store privacy label backs this up with a flat "no data collected," and the app only touches the network when you go fetch a theme or an extension yourself.
In 2026, an editor shipping without an account, without a sync layer, and without an AI assistant bolted to the sidebar is close to a statement of intent.
Some people will read that as missing features. I read it as a developer who decided what this app is for and completed that goal.
It is early. The App Store history shows version 1.0 arriving in mid July with 1.1 following almost immediately, and the developer describes the app as under active development.
It is Apple silicon only, and macOS 14 or later. It is also a paid app rather than a subscription, which I appreciate, the price varies by region ($14.99 in the US)
The good news is you don't have to buy blind. There is an interactive browser demo that lets you poke at the file tree, tabs, terminal output, Git review, and command palette before you commit. More small developers should do this.
It is not trying to replace Xcode or your main editor, and it is smarter for not trying. It wants to be the fast, quiet, native utility you keep in the dock for the moment a 400 MB JSON file shows up and ruins your afternoon. If it holds up under that specific pressure, that is a very easy app to justify owning.
