# Paperling is a Markdown editor that opens a file and gets out of the way

> Paperling is a Tauri, React and TypeScript desktop application for reading and editing Markdown files, with live preview, math and chemistry rendering, Mermaid diagrams, a command palette and an optional bring your own model AI that proposes inline edits. It is Apache 2.0 licensed, ships on Windows, macOS, Linux and Android, and is deliberately not a vault.

**Razee4315/Paperling** — A minimal, distraction-free markdown editor built with Tauri, React, and TypeScript

- Repository: https://github.com/Razee4315/Paperling
- Website: https://razee4315.github.io/Paperling/
- Stars: 586 · Forks: 40
- Language: TypeScript
- License: Apache-2.0
- Published: 2026-10-22 · Updated: 2026-10-22 · Language: en
- Canonical page: https://hysenlabs.com/projects/razee4315-paperling

## The complaint that produced the project

The Why Paperling section is the most useful paragraph in the README, because it names the problem rather than listing features. The author works with Markdown files for documentation, notes and project READMEs, and the frustration of opening .md files in Notepad or basic text editors, only to see raw unformatted text with all the symbols and syntax cluttering the content, is what prompted the build. The design goal that follows is specific: something you just open and write in, which renders Markdown beautifully while keeping the raw text one keystroke away. The comparison with Obsidian is explicit and fair, since the author acknowledges those tools are powerful but that vaults, graphs and plugins are overkill if you only want to open a file and edit it. Paperling stays out of that complexity and adds the parts the author actually reaches for, live math and chemistry rendering and an optional free AI that brings its own model and proposes edits you accept or reject right in the text. The positioning is deliberately narrow, and the no-setup claim in the title is the whole pitch: no vaults, no plugins, no heavy app.

## A local desktop app, not a web service with a sync account

The build stack explains where the boundaries are. Paperling is built with Tauri, React and TypeScript, and the platform badge lists Windows, macOS, Linux and Android, with the Android build available as an APK from the releases page and a reader mode screenshot showing a document with a task list and inline math. Tauri means the shell is a Rust binary with a web view inside, so the app is distributed as a native executable rather than a website, and the file system access goes through the Tauri plugins rather than a browser sandbox. The repository listing confirms the shape, with a src-tauri/ directory for the Rust side, a src/ directory for the React code, a packaging/ directory, a public/ directory, index.html as the Vite entry point, and both vite.config.ts and vitest.config.ts at the root, so the front end is built with Vite and tested with Vitest. The build scripts in the package manifest make the workflow plain, with a dev script that runs Vite, a build script that runs tsc and then vite build, a preview script, and separate test and test:watch scripts for Vitest. There is also a tauri script, a flake.nix for the Nix side, and a bun.lock, so the front end toolchain is Bun and the dependency set is locked.

## What the editor does that a text editor does not

The writing feature list is where the effort went, and the entries are specific enough to be useful. The view modes are Reader, Code and Split, with Ctrl+E to toggle and Ctrl and backslash for split with bidirectional scroll sync, so you can see the source and the rendered result side by side and keep them aligned. Focus mode dims non active lines so you can think, and typewriter mode keeps the caret vertically centred. Formatting is a toggleable toolbar plus shortcuts for bold, italic, link and code, and slash commands give you headings, lists, tables, math, Mermaid and callouts by typing a slash at the start of a line. There is auto pairing of brackets, quotes and code marks, list and quote continuation on Enter, Tab moving between table cells and creating new rows, and a visual table editor that appears when the caret is inside a table. Find and Replace has regex and a match counter, and the replace operation works across a whole folder from the folder search. Multiple cursors use Ctrl+D to select the next occurrence and Ctrl or Cmd click to add one. Lists and tasks are fully keyboard driven, with Tab nesting, numbered lists renumbering, and Ctrl+Enter ticking a task. Smart paste converts a URL to a link, rich HTML to Markdown and TSV to a GFM table. That list is long, and it is the list of a person who writes Markdown every day.

## Rendering: GitHub Flavored Markdown, KaTeX, mhchem and Mermaid

The preview side is built on a well known set of open source renderers, and the package manifest makes the choices explicit. The markdown pipeline is react-markdown with remark-gfm for GitHub Flavored Markdown including task lists, tables and strikethrough, plus remark-math and rehype-katex with katex 0.16.47 for math, and the chemistry rendering uses mhchem. The README shows the inline and block math delimiters, $inline$ and $$block$$, and states that math is loaded only when needed, which is the right call for a desktop app that might open a plain README with no formulas in it. Diagrams are Mermaid, with mermaid 12.1.0 in the dependencies. Code blocks get syntax highlighting through rehype-highlight. The chemistry support is the unusual part, since mhchem is not a common inclusion in a Markdown editor, and the README names what it handles, formulas, ions, isotopes and Kröger Vink defects, which are the point defects notation used in solid state chemistry. rehype-raw with rehype-sanitize are both present, so raw HTML is allowed and then sanitised, and remark-flexible-markers and remark-definition-list cover less common Markdown extensions.

## The optional AI layer, and who provides the model

The AI feature is described as an optional free AI that proposes edits you accept or reject inline, and the qualifier that matters is bring your own model, which appears in the Why section. That is a fundamentally different design from a product that bundles a hosted assistant, because the operator picks the endpoint and the model and the keys, and the application itself does not stand between the user and a model provider. The README frames it as optional in both places it appears, once in the summary paragraph and once in the feature rationale, so an installation that never touches it is a supported configuration rather than a degraded one. The dependency list gives a hint about the shape of the implementation, with the tauri plugins for the dialog, the file system, the opener, the process and the updater, plus a plugin for the updater specifically, and the presence of turndown, which is the library that converts HTML back to Markdown, and @turbodocx/html-to-docx, which converts HTML into a Word document. Those two point at an export path, so the application can hand a document to another tool as well as read and write Markdown. The wording about the AI remaining optional is the honest test, and it is the first thing to check when you install, since an editor that silently sends your documents somewhere is a different product.

## Faster releases than most desktop apps, and where the docs live

The release cadence is worth noticing. The recent tags are v1.1.1 from 2026-10-09, v1.1.0 from 2026-10-02 and v1.0.51 from 2026-09-26, so a patch release every few days, which suggests an active development cycle rather than a stable maintenance mode. The repository is not archived and the last push was on 2026-10-19, the same day as the latest source change, and there is a CHANGELOG.md, a ROADMAP.md, a SECURITY.md, a CODE_OF_CONDUCT.md, a CONTRIBUTING.md, a TEST-CHECKLIST.md, an AGENTS.md and a PR_REVIEW file dated 2026-10-16, which is a lot of process for a project that presents itself as minimal. There is also a docs/ directory and a release-notes/ directory, and the project site is at razee4315.github.io/Paperling. The licence is Apache 2.0, with both a LICENSE and a NOTICE file at the root, so the terms are the standard permissive ones with the notice requirement. The CodeMirror dependency set explains the editing behaviour, with the state, view, commands, search, autocomplete, language and merge packages alongside lang-markdown, and a separate package for the language server protocol, and vim keybindings through a separate reimplementation, which is the kind of thing a developer asks about in the first five minutes of using any CodeMirror based editor.

## Conclusion

Paperling suits a developer or writer who works in Markdown files scattered across a repository and wants a fast reader and editor for them without moving everything into a vault, since opening a .md file gives a rendered view, live preview, and a set of editing conveniences that a plain text editor lacks. It is the wrong tool if your note system depends on backlinks, plugins or a graph, because those are exactly the features the author set out to avoid. It is also the wrong tool for a shared team note base with a permission model, since it is a local desktop application. Before you adopt it, decide whether the AI editing feature is something you want enabled, since the model is bring your own, and check the release notes in the repository, because the version numbering moves in patch increments every few days.

## FAQ

### What is Paperling and what is it built with?

Paperling is a no-setup Markdown reader and editor for the desktop, built with Tauri, React and TypeScript. It opens any .md file, renders it with live preview including math, chemistry and diagrams, and provides an optional AI that proposes edits you accept or reject inline.

### Which platforms does Paperling run on?

The platform badge lists Windows, macOS, Linux and Android. The Android build is distributed as an APK from the GitHub releases page, and desktop builds are downloaded from the same releases, with the project site hosted on GitHub pages.

### Does Paperling include a vault, backlinks or a plugin system?

No, and that is deliberate. The author states that tools like Obsidian are powerful but that vaults, graphs and plugins are overkill when you only want to open a file and edit it, so Paperling stays out of that complexity. The editor instead focuses on view modes, focus and typewriter modes, slash commands, visual table editing, find and replace across a folder, multiple cursors and keyboard driven lists and tasks.

## Sources

- [License: Apache-2.0](https://github.com/Razee4315/Paperling/blob/main/LICENSE)
- [Project website](https://razee4315.github.io/Paperling/)
- [Razee4315/Paperling on GitHub](https://github.com/Razee4315/Paperling)
- [README](https://github.com/Razee4315/Paperling/blob/main/README.md)
- [Releases](https://github.com/Razee4315/Paperling/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/razee4315-paperling