Local Markdown editing with live preview
Write Markdown and keep the rendered document visible while staying in a focused Mac workspace.
Write Markdown with a clean live preview, keep files local, preview nearby images, render Mermaid and math, and export to Markdown, HTML, Word, PDF, or PNG.
A macOS Markdown editor for local files, relative images, Mermaid diagrams, math, appearance modes, and portable exports.
LoveMarkDown is a lightweight Markdown editor for macOS, built for local writing, technical notes, README files, product docs, and Markdown documents that reference nearby image assets.
The core workflow is intentionally simple: open a Markdown file, write with a live preview, save back to the original local file, and export when you need a portable copy. The page does not claim cloud sync, AI writing, collaboration editing, account features, or mobile support.
These screenshots use the actual Mac app UI so App Store reviewers and users can see the shipped workflow.
Write Markdown and keep the rendered document visible while staying in a focused Mac workspace.
Preview nearby image assets referenced by the Markdown file without turning the document into a cloud workflow.
Use technical Markdown features for diagrams, formulas, and structured documentation.
Work in a darker writing environment with document navigation visible.
These blocks answer review, privacy, and fit questions quickly.
What it is
Built for local writing, live preview, relative images, diagrams, math, and export.
Files
It does not require a cloud account or automatically upload document content.
Export
Export happens from the user's document workflow.
Not promised
The website should not imply features outside the submitted macOS binary.
Use LoveMarkDown when you want a compact Mac editor for local Markdown documents, README files, technical notes, and product docs.
Work with .md, .markdown, and .txt files from the File menu or drag and drop, then save back to the opened local file.
Keep editing and preview close together, with support for tables, task lists, code blocks, Mermaid diagrams, and math.
Export Markdown content to Markdown, HTML, Word, PDF, or PNG when you need to share or archive a rendered document.
The page focuses on shipped Mac editor behavior and avoids implying cloud, AI, collaboration, account, or mobile features.
Files
Open, edit, save, and revisit recent Markdown files without requiring a cloud account.
Preview
Preview common Markdown blocks, tables, task lists, code blocks, Mermaid diagrams, math, links, and document structure.
Images
Show nearby image assets referenced from the current Markdown file when they are available through local file paths.
Export
Generate portable output formats for documentation, review, handoff, or archive workflows.
Appearance
Choose the appearance that fits the current writing session and macOS environment.
Menus
Use macOS menu commands and shortcuts for file, save, export, appearance, and feedback actions.
Open a local document, write with preview, save, then export only when needed.
The core loop is intentionally short: open, write, preview, save, and export.
Start from a Markdown file, a Markdown-like text file, or a dragged document.
Edit Markdown while checking rendered structure, code, tables, diagrams, math, and images.
Save to the opened file or export a portable copy in the format needed for review or sharing.
LoveMarkDown is designed for focused local writing rather than cloud publishing or team collaboration systems.
Draft README files, product docs, release notes, and internal documentation with local assets close at hand.
Keep Markdown notes, code-adjacent docs, diagrams, and math-friendly snippets in a compact desktop editor.
Write notes, formulas, diagrams, and exported study material without turning the workflow into a cloud workspace.
Create portable Markdown or rendered copies for specs, handoffs, changelogs, and lightweight documentation loops.
Keep App Store review and user expectations aligned with the first macOS release.
LoveMarkDown is positioned as a macOS app. The website does not promise Windows, mobile, or browser versions.
The app is intended to work with user-selected Markdown documents and nearby relative image assets.
Preview support includes common Markdown content plus Mermaid diagrams and math in the shipped editor workflow.
Web-to-Markdown requests the network only when the user enters a URL for conversion.
LoveMarkDown should be easy to understand because it says what it is and what it is not.
The app is designed around user-selected local files and does not require sign-in for the core workflow.
The first release focuses on writing, preview, local assets, and export rather than hosted publishing.
Export options make the document portable without implying cloud storage or collaboration.
LoveMarkDown's privacy story is part of its product positioning.
LoveMarkDown does not automatically upload Markdown content, file names, or full local file paths.
Anonymous Matomo analytics use predefined product events and coarse attributes, not document text or source URLs.
Help -> Send Feedback sends only what the user chooses to submit, with optional contact information.
These answers keep App Store support and privacy expectations aligned with the first macOS release.
No. LoveMarkDown does not automatically upload Markdown document content, file names, or full local file paths.
LoveMarkDown is positioned for local .md, .markdown, and .txt files opened from the File menu or by drag and drop.
Relative image preview works when the Markdown document references nearby local image files, such as images stored next to the document or inside a relative folder.
LoveMarkDown supports export to Markdown, HTML, Word, PDF, and PNG in the first App Store release positioning.
Web-to-Markdown uses the network only when the user enters a URL and asks LoveMarkDown to convert that page. Ordinary local editing does not require this network request.
Feedback is sent only when the user submits it. Contact information is optional, and LoveMarkDown does not automatically attach Markdown content, file names, full paths, or screenshots.
Use the support and privacy pages prepared for the first macOS App Store release.