Markdown Viewer - Write Markdown and render diagrams, math, maps, and 3D

by
Markdown Viewer is a local-first workspace for developers, writers, students, and researchers who need more than a basic preview. Write and organize documents, review with anchored comments, and render diagrams, math, maps, charts, 3D models, and music in one place. Everyday editing stays on your device; sharing is optional. No account, subscription, ads, analytics, or telemetry. Open source for the browser, PWA, desktop, and Docker.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt 👋 I’m Baivab, the developer behind Markdown Viewer. I originally built it on my PC as a small personal viewer because I wanted Markdown to be easier to read, edit, preview, and share. The first version did little more than let me type and see the result. But every rough edge—and every issue, PR, screenshot, and suggestion from users—showed me how much work still happened outside the editor. The problem was fragmentation: one tool for writing, another for diagrams, another for math, another for reviewing, plus manual exports and loose files. I wanted a focused workspace that kept Markdown portable while making technical documents much richer. Markdown Viewer has grown into a local-first workspace where you can: • write in Editor, Split, or Preview mode; • organize documents with folders, tabs, search, Recent, and Favorites; • render Mermaid, LaTeX, maps, charts, 3D STL models, and more; • add anchored comments, export, back up, and optionally share a snapshot or live session. 🔒 Normal editing, preview, autosave, local import, and most exports stay on your device. No account, subscription, ads, analytics, or telemetry. It is open source under Apache 2.0. Network features are optional and documented—sharing, GitHub import, some renderers, external assets, and web dependencies can use network services. I hope it is useful to developers, technical writers, students, researchers, and anyone whose Markdown has outgrown a single text box. ❤️ Thank you to everyone who has reported bugs, proposed improvements, translated the interface, or contributed code. This project is better because people cared enough to explain what was confusing. I’d love practical feedback: what part of your Markdown workflow still makes you switch tools, and which renderer or review workflow should I improve next?