Support
Report a bug
A tool that quietly produces the wrong result is worse than one that fails loudly. Tell us about either.
Two quick checks first
These resolve a fair number of reports before they are written. Reload the page with a hard refresh, which clears a stale cached script. Then try the same file in a different browser — if it works there, the bug is engine-specific and that fact alone is genuinely useful to us.
What to include
Because the tools run in your browser, we cannot see what went wrong from our side — there are no server logs of your session to inspect. Your description is the entire evidence base, so the more of this we get, the faster the fix:
Which tool
The name or the URL of the page you were on. Several tools accept the same file types, so this is rarely obvious from the description alone.
What you did
The steps in order, from opening the page to the moment it went wrong. Short and literal beats polished.
Expected vs actual
What you thought would happen, and what happened instead. "Wrong" means different things for a merge, a compression, and a conversion.
Browser and device
For example "Safari 18 on iPhone" or "Chrome 141 on Windows 11". A large share of bugs are specific to one engine.
The file, described
Type, rough size, and anything unusual — 400 pages, transparency, non-Latin text, deeply nested JSON. Describe it rather than sending it.
A screenshot
Of the error or the wrong-looking output. One image often replaces three rounds of email.
Please do not send the file itself
Nothing you process reaches us and we would rather keep it that way. Attaching a confidential document to a bug report hands us data we deliberately never collect. If the bug only reproduces with a specific file, recreate it with dummy content and send that instead.
Send the report
Open a prefilled bug report — it fills in the subject and the checklist above, so you only fill in the blanks.
Prefer to write it yourself? Email [email protected]with "Bug:" at the start of the subject line.
What happens next
We reproduce it, fix it, and reply when the fix is live — usually within a few days for anything that produces incorrect output, since that is the class of bug we treat as urgent. If we cannot reproduce it, we will come back with specific questions rather than closing it silently.
Not a bug but a gap? Request a feature instead. Wondering whether the behaviour is intentional? The FAQ and disclaimer cover the known trade-offs.