Core workflow
Open a local Markdown file, write with preview, save, then export if needed.
The app does not require sign-in for the core workflow.
LoveMarkDown Support
Help for local Markdown writing, preview, export, and feedback.
Start here if you need App Store support information for opening files, saving Markdown, previewing relative images, exporting formats, Web-to-Markdown, or sending feedback from the Help menu.
- macOS
- Local files
- Relative images
- Export
- User-initiated feedback
Support
Support starts from the local file workflow.
Open, save, preview local images, export, and send feedback only when you choose to.
Quick answer
LoveMarkDown support is product-specific
LoveMarkDown support is focused on the shipped macOS editor workflow: open local Markdown, write with preview, save local files, preview nearby relative images, export portable formats, and send user-initiated feedback when needed.
LoveMarkDown does not promise cloud sync, AI writing, collaborative editing, account-based workflows, mobile apps, or automatic document upload.
Support facts
The most important support answers
These points are written for App Store review and first-user setup.
Image behavior
Relative images are resolved from local files near the opened Markdown document.
Broken paths or moved assets are common causes of missing previews.
Network behavior
Web-to-Markdown requests a URL only when the user enters one for conversion.
Normal local editing does not need network access.
Feedback
Help -> Send Feedback is user initiated, and contact details are optional.
Feedback is separated by app_name=LoveMarkDown in the shared receiver.
Support paths
Choose the fastest support path
Use the support lane that matches where the workflow stopped.
Open or save Markdown
Use File -> Open File, drag and drop, and File -> Save for local .md, .markdown, or .txt documents. If save is unavailable, confirm the file was opened from a user-selected location.
Relative images do not appear
Check that image paths are relative to the opened Markdown file and that the image file is still next to the document or inside the expected folder.
Export a document
Use export when you need Markdown, HTML, Word, PDF, or PNG output for sharing, review, or archive workflows.
Web-to-Markdown network access
Network fetching is only expected when you enter a URL for Web-to-Markdown conversion.
Send feedback
Use Help -> Send Feedback in the app for product feedback. Contact information is optional.
Contact NgSense
Use website contact when you cannot reach the in-app feedback path or need a general business reply.
Troubleshooting
Common support lanes
Start with these checks before sending feedback.
Open or save Markdown
Use File -> Open File or drag a local document into the app. Save writes back to an opened local file; export creates a separate portable copy.
Relative local image preview
Use relative Markdown image paths such as ./images/example.png or images/example.png. If the Markdown file or image folder moves, update the path or move the assets together.
Mermaid, math, tables, and code blocks
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.
Export to Markdown, HTML, Word, PDF, or PNG
Choose export for the output format you need. Exported files are user-selected output artifacts, not automatic uploads.
Web-to-Markdown conversion
Web-to-Markdown performs a network request only for the URL you enter. The app does not use this path during ordinary local editing.
Feedback from Help
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.
First setup
First setup checklist
Use this checklist before assuming the app or file is broken.
Step 1
Open one local Markdown file
Start with a simple .md, .markdown, or .txt file from a user-selected folder.
Step 2
Check the live preview
Confirm basic headings, lists, tables, code blocks, Mermaid, math, or images using one small example at a time.
Step 3
Save or export intentionally
Use Save for the opened local file and Export for Markdown, HTML, Word, PDF, or PNG copies.
Step 4
Send focused feedback
If something still fails, send the smallest safe example and avoid private document content unless you intentionally choose to share it.
Local document editing stays separate from export output.
Export and local files
Support should keep the difference between save and export clear.
LoveMarkDown writes local files when the user chooses to save, and creates export artifacts only when the user chooses an export format.
Save is for the opened local file
Use Save when you want to write back to the current document.
Export is for portable output
Use export when you need Markdown, HTML, Word, PDF, or PNG output.
Related guidance
Related NgSense guidance
LoveMarkDown support is separate from ScopeDock camera support, but the same local-first privacy principle applies across NgSense products.
Why structured feedback should stay separate from anonymous analytics
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.
FAQ
LoveMarkDown essentials
Support answers for App Store review and first users.
Does LoveMarkDown upload my Markdown files?
No. LoveMarkDown does not automatically upload Markdown document content, file names, or full local file paths.
What file types can I open?
LoveMarkDown is positioned for local .md, .markdown, and .txt files opened from the File menu or by drag and drop.
How do relative images work?
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.
Which export formats are supported?
LoveMarkDown supports export to Markdown, HTML, Word, PDF, and PNG in the first App Store release positioning.
When does Web-to-Markdown use the network?
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.
What is sent when I use Help -> Send Feedback?
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.
Next step
Still need help with LoveMarkDown?
Use in-app Help -> Send Feedback when possible, or contact NgSense from the website if the app path is unavailable.