All articles

LoveMarkDown · LoveMarkDown Guide

LoveMarkDown for Mac: Local Markdown Writing, Preview, and Export

LoveMarkDown is a lightweight Markdown editor for Mac that opens local files directly, adds live preview for technical Markdown, and exports to Markdown, HTML, Word, PDF, or PNG without requiring a repository, workspace, vault, or cloud account.

Published Updated
LoveMarkDown Split mode showing the source and rendered table of our public handoff demonstration document.
On this page

LoveMarkDown works from the Markdown file you already have: open it, make a change, check the rendered result, save the source, and export a copy for a reader who needs another format. You do not need a repository, vault or NgSense account for that local-file workflow.

Start with a disposable copy of a README or note. Use LoveMarkDown download options for current Mac requirements and channels; the steps below are about the document, not a promise that every Markdown extension or export layout will match another app.

Open one file and confirm what you are editing

  1. Use File > Open File or drag a local .md, .markdown or .txt document into LoveMarkDown.
  2. Confirm the expected content appears in the active tab. If you received an image folder with the file, keep that folder beside it.
  3. Make a small change and check it in Preview. Use the document outline for longer files rather than scrolling without an anchor.
  4. Use File > Save or Cmd+S. An opened file saves back to its location; an untitled document needs a filename and destination on its first Save.

Check the result: reopen the saved Markdown file and confirm your change remains. Draft recovery is not a substitute for choosing a destination or keeping your own backup.

For a file that will not open or save, use opening and saving support.

Check the structures that matter to this document

ContentWhat to inspect in Preview
Headings and listsHierarchy, order and outline entries
Relative imagesThe expected image, resolved from the opened document’s folder
Tables and fenced codeColumns, wrapping, delimiters and the intended language
Mermaid and mathWhether the actual diagram or formula renders, not just its source text

For a relative reference such as images/example.png, the image must exist at that location relative to the Markdown file. Moving only the Markdown can break the reference. Use relative image support or technical Markdown support if one small example fails.

The screenshot above uses our own demonstration document. It shows source and rendered content in Split mode, not a customer file or proof that every document renders identically.

Save the source; export the handoff

Keep the Markdown source for future edits. Choose an export format for the recipient, and use a separate destination so you do not overwrite the source or an earlier deliverable.

FormatIntended handoffCheck before sharing
MarkdownAnother Markdown workflowReopen the text and keep referenced assets together
HTMLA browser-readable copyOpen it and inspect images, links and technical blocks
Word / DOCXAn office-document reviewOpen in the recipient’s editor and inspect structure and layout
PDFA fixed-layout review copyInspect page breaks, images, code and text selection
PNGA visual snapshotInspect resolution and cropping; it is not editable or searchable text

Preview is a preparation step, not an export-fidelity guarantee. Long tables, code, diagrams and images need a check in the actual output.

An excerpt from LoveMarkDown's real PNG export of the public handoff demonstration document, showing a heading and table.
PNG export excerpt from our demonstration file, not a screenshot of the editor or an entire PDF.

Try the sample Markdown and compare its actual PDF export. These are public example files, not a compatibility benchmark. For output problems, use export support.

Source notes

Inspect a real source-to-export example

Our public handoff document has an editable Markdown source, a LoveMarkDown Split-view capture, an excerpt from its actual PNG export, and the complete PDF output. Download and compare the files instead of judging export quality from the editor alone.

  • The source and the PNG excerpt share the launch heading and deliverables table. The PNG shown here is an output excerpt, not a screenshot of a PDF viewer.
  • The full PDF is a separate one-page output with text and embedded fonts. The editable source remains available separately.
  • In this archived PDF, the task entries appear as a bullet list rather than displaying the Markdown checkbox states. Inspect task-list formatting in the file you plan to share.
Capture context and test coverage
Product-page editor captures
October 16, 2026; LoveMarkDown Direct 1.3.0; macOS 27.0.1 (26A434); Apple Silicon. Split and Visual show the public sample. Network access was denied during capture and the bottom path strip was cropped out. The linked older Split capture below is retained as historical evidence.
Original PDF creation metadata
2026-09-22 at 13:07:06 UTC. This is the file's recorded creation time, not a new export test date.
PDF producer metadata
macOS Version 26.6.2 (Build 25G83), Quartz PDFContext. This identifies the PDF's recorded renderer, not a cross-version compatibility test.
App version, build, and Mac architecture
Not recorded with the original export. The example must not be attributed to the current LoveMarkDown release or to both Mac architectures.
Document coverage
Our own heading, paragraph, table, checklist, quotation, and short code example. No customer document or private image path is included.
  • The new 1.3.0 editor screenshots do not re-date or re-verify the archived PNG or PDF exports. No new Word, HTML, PDF or PNG export was tested in this capture session.
  • The PNG illustration is cropped; use the full PDF and source for the complete document. The editor screenshot and output are different captures, not a continuous recorded session.
  • This example does not establish Word or HTML export fidelity, relative-image handling, Mermaid, math, or long-document pagination. Check those structures in your own exported format.
  • File metadata and a demonstration document are not a signed benchmark or a guarantee of identical output in another viewer.

Example documentation reviewed 2026-10-16. This is not a new device or export test date.

Keep the workflow local and deliberate

LoveMarkDown does not automatically upload your Markdown text, filenames or complete local paths. Saving to a folder synchronized by another service is a separate storage choice.

A document can contain remote image URLs that require network fetching; Web-to-Markdown also requests a webpage when you ask it to convert a URL. Anonymous product measurement and feedback you actively submit are separate from uploading the document. Review LoveMarkDown privacy before using sensitive content.

If checks still fail, send feedback with the app/macOS version, format, action, expected result and visible error after removing private details. Share only an example you intentionally choose to disclose; do not include a private document, credentials or complete local paths by default.

When this workflow is not enough

Use a system designed for shared collections when the main requirement is collaboration, cloud synchronization, backlinks or repository-wide tooling. LoveMarkDown focuses on local documents; it does not turn a file into a hosted team workspace or guarantee another editor’s Markdown extensions.

If the workflow fits, choose a LoveMarkDown installation channel. The product page shows the broader capabilities and boundaries.

FAQ

Can I edit one README without opening a project?

Yes. Open the local file directly. It can remain in its existing folder, whether or not that folder belongs to a Git repository.

Does Save create a PDF?

No. Save keeps the local source workflow. Use Export when you need another format, then open the resulting file to check it.

Why does a relative image disappear after I move the file?

The reference is relative to the Markdown document. Keep the expected assets at the referenced location or update the reference; a preview in a different app does not establish that the moved bundle is complete.

Will a PDF always look exactly like Preview?

Do not assume that. Check the generated PDF’s page breaks, images, tables and text selection. Output format and document structure affect the result.

Do I need an account for this local workflow?

No NgSense account is required for opening, editing, saving or exporting local Markdown. This is not a promise of cloud sync or simultaneous editing.

Next with LoveMarkDown

Download LoveMarkDown View on the Mac App Store LoveMarkDown Support