MarkEdit: A 4 MB Native Markdown Editor for macOS That Picks GFM Over Features
Just like TextEdit on Mac but dedicated to Markdown. MarkEdit MarkEdit is a free and open-source Markdown editor, for macOS.
At a glance
- What is it?
- MarkEdit is a free, open-source Markdown editor for macOS that keeps the installer at about 4 MB and builds editing on CodeMirror 6. It targets users who want native Mac behavior and strict GitHub Flavored Markdown compliance without Electron overhead.
- Who is it for?
- Adopt MarkEdit if you are a macOS user who wants a tiny, native Markdown editor that follows GFM strictly and integrates with Shortcuts and AppleScript. Do not adopt it if you need a cross-platform editor, a built-in preview pane by default, or a rich plugin ecosystem beyond CSS and JavaScript extensions.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository received new commits within the last day.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on September 15, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
The problem MarkEdit solves: native Markdown editing without bloat
Most Markdown editors on macOS fall into one of two camps. Electron-based apps like Typora or VS Code offer rich features but consume hundreds of megabytes of memory and disk. TextKit-based editors, such as the built-in Notes app, handle Markdown poorly and choke on large files. MarkEdit positions itself as the third option: a native macOS app that is about 4 MB in size and can handle 10 MB files with ease. The README explicitly says it does not claim to be the best in any single dimension, but aims to balance size, speed, native integration, and correctness. This makes it a pragmatic choice for writers and developers who spend all day in Markdown and want an editor that feels like a Mac app, not a web page in a window.
How it works: CodeMirror 6 for editing, native UI for everything else
MarkEdit's architecture is a hybrid. The editing surface is built on CodeMirror 6, a JavaScript-based code editor component. That gives it multi-caret editing, code folding, and other complex editing features that are hard to implement natively on macOS. The UI around the editor, including menus, toolbars, and dialogs, is native to macOS, so it supports force-touch word lookup, inline text predictions, and Writing Tools. This split is unusual: most editors either go fully native and sacrifice editing power, or go fully web-based and sacrifice native feel. MarkEdit's approach uses CodeMirror for correctness and performance, while keeping the chrome native. The README claims this is consistently faster than most macOS editors, but it does not provide benchmarks. What is clear is that the editor follows the GitHub Flavored Markdown (GFM) specification strictly, with no proprietary syntax. That means what you write is what you get on GitHub, which is a concrete advantage for developers who publish to GitHub.
Getting it running: two installation paths
There are two official ways to install MarkEdit. The simplest is to download the MarkEdit.dmg from the latest release on GitHub, open it, and drag MarkEdit.app into the Applications folder. The second is to use Homebrew with the command: brew install --cask markedit. After installation, the app checks for updates automatically, so you do not need to manually track releases. For older macOS versions, the project provides separate builds for macOS 12, 13, and 14, linked from the README. This is a thoughtful touch for users who cannot upgrade to the latest OS. The app is free and open source under the MIT license, so you can also build it yourself from source if you prefer, though the README points to a wiki page for development instructions. The Homebrew cask is a convenience for users who already manage apps with Homebrew, and it is the command I would recommend for most people.
Extensibility: CSS, JavaScript, and AppleScript, but no plugin marketplace
MarkEdit does not have a traditional plugin system like VS Code's extension marketplace. Instead, customization is done through CSS, JavaScript, and CodeMirror extensions. The project provides an API repository called MarkEdit-api, and there are official extensions: MarkEdit-preview for a preview pane, MarkEdit-theming for custom themes, and MarkEdit-ai-writer for Apple Intelligence on macOS Tahoe or later. This is a lightweight approach that keeps the core app small. If you want a preview pane, you install the extension; it is not built in. The integration with Shortcuts and AppleScript is another extension point, allowing automation that is native to macOS. This makes MarkEdit appealing to users who want to script their editor, but it also means that if you are used to a rich plugin ecosystem, you will find the options limited. The README mentions a wiki page for the manual and a separate skill for managing MarkEdit with an AI agent, but it does not give details on how to write extensions, so you would need to consult the API repository.
A real limitation: no built-in preview and strict GFM only
The most obvious limitation is that MarkEdit does not ship with a preview pane by default. The README lists MarkEdit-preview as an official extension, but you have to install it separately. For users who want a side-by-side view of rendered Markdown, this is an extra step. More fundamentally, MarkEdit strictly follows GFM and intentionally avoids proprietary syntax or invented features. That means if you use Markdown extensions like footnotes, tables (GFM does support tables, so that is fine), or custom containers, they will not render unless they are part of GFM. The README is explicit about this design choice, and it is a trade-off: you get correctness and portability, but you lose the conveniences that other editors add. For example, Typora supports footnotes and task lists that are not GFM, so if your workflow depends on those, MarkEdit will not handle them as you expect. The README also says the app is 'feature-poor' by design, which is a honest warning that you should not expect a lot of built-in functionality.
The alternative: TextEdit with Markdown support or a Rust-based editor
The most direct alternative is TextEdit itself, which is the app MarkEdit is modeled after. TextEdit is native, free, and already on your Mac, but it does not understand Markdown syntax, so you get plain text editing with no syntax highlighting or formatting. If you want a Markdown editor that is as native as TextEdit but understands Markdown, MarkEdit is the obvious choice. Another alternative is a performance-first editor built in Rust, such as Zed or Lapce. These editors are also fast and native, but the README argues that they lack native features like force-touch lookup and Writing Tools, because they are cross-platform and do not integrate deeply with macOS. The difference in approach is clear: Rust editors prioritize speed and cross-platform consistency, while MarkEdit prioritizes macOS integration and strict GFM compliance. If you work on multiple operating systems, a Rust-based editor might be more practical, but if you are a Mac-only user, MarkEdit's native integration is a real advantage.
Maintenance and licensing: MIT, active releases, and a small core
MarkEdit is licensed under the MIT license, which means you can use, modify, and distribute it freely, even for commercial purposes, as long as you include the original copyright notice. The project is actively maintained, with the latest release v1.34.0 pushed on August 9, 2026, and previous releases in June and May of the same year. This cadence suggests regular updates, which is a good sign for a tool you depend on daily. The app checks for updates automatically, so you do not need to manually track releases. The codebase is Swift, and the README credits CodeMirror 6 and ts-gyb for code generation, but it does not provide details on the build system. Because the app is intentionally minimal, the maintenance cost for users is low: there are few settings to configure and no plugin marketplace to manage. However, if you rely on extensions, you need to track their compatibility with each MarkEdit update, since the API may change. The project has a wiki with development instructions, so contributors can get started, but the README advises discussing behavior changes first, indicating that the maintainers are conservative about adding features.
Editorial conclusion
Adopt MarkEdit if you are a macOS user who wants a tiny, native Markdown editor that follows GFM strictly and integrates with Shortcuts and AppleScript. Do not adopt it if you need a cross-platform editor, a built-in preview pane by default, or a rich plugin ecosystem beyond CSS and JavaScript extensions. Before adopting, verify that your macOS version is supported (the latest release targets current macOS, with separate builds for macOS 12, 13, and 14) and that your workflow does not depend on proprietary Markdown syntax, which MarkEdit deliberately avoids. The project is actively maintained, with releases as recent as August 2026, so check the release notes for any changes to the extension API or GFM behavior before upgrading.
Community notes