Core workflow
Open a local Markdown file, navigate, write with preview, save, then export if needed.
The app does not require sign-in for the core workflow.
Start here for document outlines, opening and saving Markdown, Finder and tab actions, relative images, clearer export, Direct updates, Web-to-Markdown, or feedback.
These points cover the most common first-use questions without requiring a long troubleshooting path.
Core workflow
The app does not require sign-in for the core workflow.
Release channels
Version 1.2.1 is awaiting Apple review for the Mac App Store.
Image behavior
Version 1.1.4 also handles mismatched file extensions and safe Pandoc image attributes more reliably.
Network behavior
Normal local editing does not need network access.
Feedback
Feedback is separated by app_name=LoveMarkDown in the shared receiver.
Start with these checks before sending feedback.
Use File -> Open File or drag a local document into the app. For a new untitled document, Save opens the native destination picker. For an opened local file, Save writes back to that file; export creates a separate portable copy.
Press Cmd+F to open Find, Cmd+R to replace the current match, or Cmd+Shift+R to replace all matches. The result count, previous and next navigation, and synchronized Edit and Preview highlights stay in the document context.
Open the outline from the workspace or press Command-Shift-O. If a heading is missing, confirm that the source uses a valid H1-H6 Markdown heading and reload the document from disk.
Path-dependent actions are available only for saved documents. Untitled tabs keep them disabled, and reloading a modified document asks for confirmation before replacing editor content.
Use relative Markdown image paths such as ./images/example.png or images/example.png. Version 1.1.4 handles files whose extension differs from their actual image format and applies safe Pandoc width, height, class, and ID attributes without exposing attribute text.
If a technical block does not render as expected, reduce the example to a small Markdown snippet and send that snippet only if you are comfortable sharing it.
Choose export for the output format you need. Version 1.1.4 keeps PDF text searchable through the primary native path and produces sharper PDF and PNG output without the previous image double-compression.
The Direct build can check a signed release and installs only after you choose to proceed. Mac App Store builds do not use the Direct update feed and continue to update through Apple.
Web-to-Markdown performs a network request only for the URL you enter. The app does not use this path during ordinary local editing.
Use Help -> Send Feedback when you want to report a bug, request a feature, or describe a workflow issue. Contact information is optional, and document content is not attached automatically.
Use this checklist before assuming the app or file is broken.
Start with a simple .md, .markdown, or .txt file from a user-selected folder.
Open the H1-H6 outline, then confirm basic headings, lists, tables, code blocks, Mermaid, math, or images using one small example at a time.
Use Save for the opened local file, the native destination picker for a new untitled document, and Export for Markdown, HTML, Word, PDF, or PNG copies.
If something still fails, send the smallest safe example and avoid private document content unless you intentionally choose to share it.
Navigate long documents locally, then export only when needed.
Use the H1-H6 outline for long documents, save through the native file workflow, and export searchable PDF or sharper PNG output when you need a portable artifact.
Open the outline from the workspace or with Command-Shift-O, then select a heading to jump there in Edit, Preview, or split view.
Version 1.1.4 keeps PDF text searchable through the native path and produces sharper PDF and PNG output.
LoveMarkDown support is separate from ScopeDock camera support, but the same local-first privacy principle applies across NgSense products.
LoveMarkDown 1.2 adds editable Visual Markdown, Source and Split modes, rich technical content, synchronized workflows, and safer local file saving on Mac.
Read article
Structured feedback and anonymous analytics answer different questions. Keeping them separate makes the product easier to trust and makes support workflows easier to reason about.
Read articleStraight answers for common setup, file, preview, export, network, and feedback questions.
Choose the Apple Silicon Direct download for an M-series Mac or the Intel Direct download for an older Intel-based Mac. Direct version 1.2.1 is available now. The public Mac App Store version remains 1.2.0 while Apple reviews 1.2.1.
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.
Press Cmd+F to open Find, Cmd+R to replace the current match, or Cmd+Shift+R to replace all matches. The result count, previous and next navigation, and matched highlights stay synchronized between Edit and Preview.
For a new untitled document, Save or Cmd+S opens the native destination picker. For an opened local file, Save writes back to that file. Draft autosave is for recovery and does not replace choosing a destination.
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. Version 1.1.4 also handles files whose extension does not match their actual image format and applies safe Pandoc width, height, class, and ID attributes without showing the attribute text in Preview or exports.
LoveMarkDown supports export to Markdown, HTML, Word, PDF, and PNG. Direct version 1.1.4 keeps PDF text searchable through the primary native path and produces sharper PDF and PNG output.
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.
Direct-download builds can check for a signed NgSense update and install it only after you choose to proceed. Mac App Store installations do not use the Direct update feed and continue to update through Apple.
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.
Choose the correct LoveMarkDown installer, use in-app Help -> Send Feedback when possible, or contact NgSense if the app path is unavailable.