[email protected] is the primary channel for bug reports, conversion issues, feature requests, and anything else about using or trusting the site. Most reports turn out to be conversion edge cases — a specific Markdown or HTML construct that didn't convert the way you expected — and the fastest way to get one fixed is to send enough context to reproduce it on the first try.
What to include in a bug report
Four things turn a vague report into a same-day fix:
- Which tool page you were on (the URL is enough).
- The input you used — or, better, a minimal version of it that still triggers the problem. A ten-line snippet that reproduces a bug is more useful than a ten-thousand-line file that also contains it.
- What you expected the output to look like, versus what you actually got.
- Your browser and OS, if the issue looks rendering-related — this matters most for the PDF, image, and slides exports, which lean on browser-specific canvas and print behavior.
What to expect back
This site is maintained by a small team, not a support desk running on SLAs. Most emails get a reply within a few business days; reports that arrive with a clear repro case tend to get looked at first, simply because they're the fastest to act on. If a week goes by with no response, it's fine to follow up — mail gets missed, and a nudge is never unwelcome.
Privacy and data questions
Because every tool runs entirely client-side — see the Privacy Policy and the About page for the specifics — there's rarely account data or server logs to go looking through in the first place. If your question is about what a particular tool does with your file, whether analytics are running, or how to exercise a data-protection request, use the same email address above and put “privacy” in the subject line so it doesn't get triaged as a conversion bug.
Discord
For quicker back-and-forth — especially useful when a question needs a screenshot or a one-line clarification rather than a full email — join the Discord server.
Before you write in
A few things are already documented and not bugs: nested Word lists flatten to one level when converted (see the Word to Markdown page's FAQ), footnotes aren't part of this site's Markdown support, and the “Save as PDF” button on Markdown to PDF opens your browser's own print dialog rather than generating a PDF on a server — that's by design, not a workaround.