Contact and report a problem
Report tool problems, suggest a practical feature or point out a documentation error. Learn what helps reproduce an issue without sharing private files.
When a tool behaves unexpectedly
Check troubleshooting and try the tool’s built-in example. Include the tool name, browser and version, input format and approximate size, selected options, expected result and actual outcome.
If only one file fails, reproduce its structure with fictional data where possible. Do not submit an entire private document to demonstrate an issue; the form does not accept file attachments.
Suggest a tool or content improvement
Describe the task, available input and required output instead of asking only for “another converter”. Explain when the need occurs and the step missing from the existing tools.
For a documentation correction, include the page address, relevant passage and a verifiable reference. We do not promise a feature launch date or a fixed response time.
Remove sensitive material before submitting
Do not include passwords, access tokens, JWTs, SAML login responses, identity documents or original customer data. Email is optional; include it only if you want follow-up contact. When the feedback service is unavailable, the page says so and does not claim the message was saved.