What to include in a report
Note the tool name, URL, language, device and browser. Describe what you expected, what happened and the exact error message. A small example without private information helps reproduce the issue.
Do not share passwords, identity documents or confidential files. Check the guides and help first for limits and options.
Contact channel
Email [email protected] with reports, suggestions or issues. Include the details needed to reply and avoid attaching private content. This page does not collect data through a form.
Template for reporting a problem
Complete the fields with what happened. Include exact steps and settings so we can reproduce it. Where possible, replace real data with the tool’s sample.
Tool and URL: Device, browser and version: Steps and settings used: Expected result: Actual result or error message:
Preparing a reproducible example
Start by trying the tool’s practice case. If it works but your input does not, compare size, format and options without sending private files. Prepare a small sample retaining only the feature triggering the issue: a line containing a symbol, a fictitious table with quotes or a test PDF with matching orientations. The purpose is to describe the problem with the minimum information needed, rather than reproduce an entire confidential document.
Write steps in their actual order, including changes made after generation. State whether failure occurs during loading, calculation, copying or opening a download. Each stage needs a different investigation. Copy an error message exactly when present. A screenshot can describe layout, but inspect it for personal content, credentials and unrelated tabs before including it. Keep examples fictitious so review can focus on behaviour without exposing source information.
Distinguishing output from its destination
If a download opens correctly but another application rejects it, identify that destination and its visible requirement. A valid file can have a format, dimensions or byte size outside the receiver’s limits. Record pixels and bytes separately for images, units or timezones for dates, and handling of spaces and duplicates for lists. Those details explain discrepancies without guessing what the input was intended to represent.
For a tool suggestion, describe the task, source format and required output. A fictitious case helps explain limits and acceptance criteria. Email is the stated communication channel; this page does not send tool contents or include a support form. Save useful results on the device before writing so they are not lost when changing pages. A focused description of expected and observed behaviour makes the request easier to understand and reproduce.