Email support
For product questions and troubleshooting, email [email protected].
Support.
Vanilla Markdown support is focused on practical product questions: install issues, file-opening behavior, Markdown rendering, local folder access, keyboard navigation, and basic compatibility. This page gives you the direct support contact, the App Store route for purchase-related issues, and a short troubleshooting checklist so you can find help without going on a scavenger hunt.
If the question is about installing the app, opening files, rendering Markdown, or understanding the product scope, start here.
App Store issues
For purchase, billing, or storefront delivery problems, use the App Store support route alongside direct product support.
Platform requirements
Vanilla Markdown is built for macOS 13 and later. iOS and iPad support are planned but not part of the current launch scope.
What to include in a support email
Share your macOS version, the file type or folder setup involved, and the exact behavior you expected versus what happened.
Troubleshooting basics
Start with the usual suspects.
File type check
Confirm the file uses a supported Markdown or plain-text extension and opens locally on your Mac.
Folder access check
If a docs folder is involved, verify the app has access to the selected folder location and the files inside it.
Link target check
If a local link does not resolve, confirm the target file or heading exists where the document expects it.
Version check
Include your app version and macOS version in support requests so issues can be reproduced accurately.
More scoops
Other useful stuff while you’re here
FAQ
Check the most common product, pricing, privacy, and compatibility questions.
Privacy
Understand local-file handling, analytics, and support email data usage.
Reference
Review the product feature set if you are evaluating whether a behavior is supported.
Markdown viewer for Mac
Return to the main macOS-specific positioning page.
One last scoop
Still stuck? Send a note.
If the product scope and support path are clear but the app is still acting odd, send support the details and we can look at the mess together.