Write to us

This is the most useful thing you can report, and also the trickiest, because we can't see your file. So please describe it instead of sending it:

If you've found input that produces HTML containing something executable — a surviving event handler, a javascript: URL, a tag that should have been removed — please write, and please include the exact input that triggers it. That's the one class of bug here that could hurt someone downstream, and it gets fixed ahead of anything else.

Please report it privately first rather than publishing it. There's no bug bounty; there is a fast fix and a genuine thank you.

The point of this site is that your files stay on your computer. Emailing one to us defeats that on your end and puts us in a position we'd rather not be in on ours. If you can reproduce the problem with a file that doesn't matter — a couple of headings and a table typed into a fresh document — that's genuinely more useful anyway, because it isolates the bug.

If a problem truly can't be reproduced without the original file, write first and we'll work out what's needed. Usually the answer is a description of the structure, not the content.

This site is in six languages. English is the original and the rest were translated with care, but a native speaker will still catch things a careful translation misses — a phrase that's technically right and reads oddly, a term the local software world says differently.

If you spot one, tell us which language and which page, and quote the phrase. Small corrections are welcome and get applied quickly.

Feature requests are read and often built, especially small ones — a knob for an output style, support for a format variant, a delimiter we don't detect, a CSS hook you need in the output.

Some things are out of scope by design, and asking won't change them: uploading files to a server, a Google Drive integration, user accounts, or reproducing Word and Excel styling exactly. The last one isn't a limitation we're apologising for — clean markup is the product.

Questions about what data this site collects, or requests concerning your data under GDPR, CCPA or similar law, go to the same address. Read the privacy policy first — the short version is that we don't collect anything that identifies you, which makes most such requests moot, and the policy explains exactly why.