Markdown Viewer and Editor: Browser markdown editor that keeps files on your machine

What it does

Markdown Viewer and Editor is a browser-based tool for viewing and editing markdown files. Users drag and drop .md files into the browser, where they are rendered and can be edited. The editor supports standard markdown formatting, syntax highlighting for code blocks, tables of contents, Mermaid diagrams, and LaTeX via KaTeX. Files can be exported to HTML, PDF, or PNG formats. Critically, all files remain on the user's machine—nothing is uploaded to a server.

The tool also works as a Chrome or Edge app that can open markdown files directly from the desktop by double-clicking them.

Who it is for

This targets markdown users who want a free, lightweight editor without needing to install software or manage cloud storage. It suits writers, developers, and documentation creators who work with .md files locally and want a straightforward rendering and editing interface. The browser-based approach appeals to users who prefer not to commit files to external servers.

Pricing

Free. The code is available under the MIT License on GitHub.

How it stands out

The core differentiator is the local-file-only model. No account, no uploads, no backend—the tool processes everything in the browser. This removes common friction points: no login required, no syncing delays, no privacy concerns about file content. The desktop app integration (drag-and-drop or double-click opening) bridges the gap between browser and filesystem without additional steps.

Support for Mermaid diagrams and LaTeX rendering appeals to technical users who need these features in markdown. Export options (HTML, PDF, PNG) cover common workflows without requiring separate tools.

What a founder should check

First, verify the switching costs for incumbent markdown editors. Users of VS Code, Obsidian, Notion, or dedicated markdown apps have established workflows and may not see enough advantage to change—especially if they already have rendering and export built in.

Second, investigate the moat. The browser-based, local-file approach is straightforward to replicate. Competitors could build similar tools quickly. Without network effects, exclusive features, or community lock-in, retention depends entirely on feature breadth and user experience competing against free and open-source alternatives.

Third, confirm pricing pressure. The tool is free with open-source code. Any monetization would require a compelling reason to pay when the open-source version exists. Consider whether premium tiers (cloud sync, collaboration, advanced export) could work without undermining the core local-file value proposition.

Thinking of building something like this?

Every launch here is a competitor to somebody's idea. If yours is close, check it against the market before you build: the Full Check names the rivals, the prices and the gaps.