Skip to main content
leaftext ships pre-built binaries for macOS (Apple Silicon), Windows (64-bit), and Linux through the GitHub Releases page. There is no package manager step, no runtime to install separately, and no account required — download the file for your platform and follow the steps below.

Platform instructions

Requirements: Apple Silicon Mac (M1 or later).
  1. Go to the Releases page and download the latest .dmg file.
  2. Open the DMG and drag leaftext.app onto the Applications shortcut in the window.
  3. Eject the DMG.
First-launch gatekeeper warningmacOS quarantines applications downloaded from the internet and will block leaftext from opening if it was not installed through the App Store or signed with an Apple notarization certificate. If you see a dialog saying the app cannot be opened because it is from an unidentified developer, run the following command in Terminal after dragging leaftext to Applications:
xattr -cr /Applications/leaftext.app
This removes the quarantine extended attribute from the app bundle. After running it, open leaftext normally from Applications or Spotlight.
You only need to run the xattr command once. Subsequent launches will open without any warning.

After installing

1

Launch leaftext

Open leaftext from your Applications folder (macOS), Start Menu (Windows), or directly from the terminal (Linux). You will be greeted by the no-file view, which shows your recent files if any exist.
2

Open a Markdown file

Press Ctrl+O on Windows or Linux, or Cmd+O on macOS, to open the file browser. Navigate to any .md file and select it. leaftext will render it immediately.You can also drag and drop a .md file directly onto the leaftext window to open it.
3

Start reading

That’s it. leaftext renders your file with full CommonMark + GFM support, syntax highlighting, and a minimap for navigation. See the Quickstart for a tour of the interface.
WebView2 browser data on Windows is stored in %LOCALAPPDATA%\ryanallen\leaftext\data\webview2, not beside leaftext.exe in Program Files. This is intentional: the user profile directory is always writable without elevated permissions, so leaftext can read and write its rendering data regardless of where the binary was installed.