Octarine Logo

Octarine guide

What is the best local-first Markdown app for writers?

A practical comparison of what writers should look for in a local-first Markdown app, where Octarine fits, and when a different notes app is the better choice.

By Rajat Kulkarni · Reviewed August 17, 2026

“Local-first” is useful only when it describes what happens to your work. For a writer, the decisive questions are simple: Where is the draft stored? Can it be opened without the app? Does writing still work without a connection? Can the folder move with the backup or sync system you already trust?

Octarine answers those questions with ordinary files. A workspace is a folder you choose, and notes inside it are Markdown. You can open an existing folder instead of importing it into an Octarine-owned library. Core writing works offline, and another text editor can read the same files.

That makes Octarine a particularly good fit for personal essays, journals, research notes, newsletters, books, and other work where the draft needs to outlast the current tool. The app provides a visual editing surface, while the underlying document remains portable text.

The criteria that matter more than a feature count

Your draft should have an address on disk

A local-first writing app should let you identify the folder and file that contain a draft. In Octarine, the workspace is not an opaque database. You can inspect it in Finder or Explorer, include it in a backup, put it under Git, or open a note in a different editor. Octarine also watches the workspace for external changes, so editing a file elsewhere does not require a special export cycle.

This makes recovery straightforward. If a writing tool has a bad release, loses a feature you depend on, or simply stops being the right tool, the manuscript is still a folder of readable Markdown files.

The editor should stay out of the sentence

Some Markdown writers prefer a source editor with visible punctuation. Others want headings, links, lists, and emphasis to look like the finished document while they type. Octarine takes the second approach: it is a WYSIWYG Markdown editor backed by Markdown files.

This is a real preference, not an objective advantage. If you enjoy working directly with Markdown syntax, a source-first editor may feel faster. If syntax markers break your concentration, Octarine’s visual editor is likely the better fit.

Organization should support writing, not become the work

Octarine supports folders, tags, links, backlinks, YAML properties, search, and views. Those tools can organize research without forcing every paragraph into a database. Inbox and Quick Capture provide a place for fragments before they become durable notes. Daily Desk gives date-based notes a predictable home.

The useful test is whether the system helps you find source material and return to a draft. A graph with thousands of nodes is not automatically a better writing environment.

A sensible Octarine workflow for a long project

Create or open one workspace for the body of work. Keep the draft and its supporting notes in folders that make sense outside the app, such as Drafts, Research, and Sources. Add properties only when they answer a recurring question—for example, status, publication, or interview subject. Use links when two notes have a meaningful relationship, not to manufacture a dense graph.

For backup, include the whole workspace rather than copying only the visible Markdown files. Octarine keeps workspace settings and some supporting data in hidden folders alongside the notes. The workspace documentation and data-storage guide explain what lives where. Built-in Git Sync is available, and a workspace can also live in a folder managed by services such as iCloud, Dropbox, OneDrive, or Syncthing.

When Octarine is not the best answer

Choose another tool if any of these requirements is central:

  • You want a large marketplace of community plugins and themes. Octarine is deliberately more opinionated and does not try to match Obsidian’s plugin ecosystem. Obsidian documents both its local file model and community plugins, making it the more natural choice when customization is the point.
  • You need several people editing the same document at the same time. Octarine is built first for personal work, not live multiplayer documents or a team knowledge base.
  • You need a generally available mobile app today. Octarine has a Pro-only iOS beta through TestFlight, not a public App Store release. There is no Android app.
  • You need a full manuscript-production tool with page layout, citations, tracked changes, or publisher-specific export. Octarine can hold and shape a draft, but it is not a replacement for every final-production tool.

A ten-minute way to decide

Take a copy of three real notes: one long draft, one link-heavy research note, and one note with an image or attachment. Open the copied folder as an Octarine workspace. Write for several minutes, close the app, and inspect the files in a plain text editor. Then test search, links, and your preferred backup method.

Keep Octarine if the editor makes the writing quieter and the files remain as understandable as you expect. Do not switch because a checklist calls it the best. Switch only if that small test improves the part of the process you repeat every day.