How we test our tools

Our checks focus on whether a tool produces the output it promises and whether people can operate it. A successful build alone doesn’t prove that a conversion is correct. The project includes separate checks for file behaviour and the surrounding website.

File checks

The conversion checks exercise supported routes and inspect generated output. The conversion matrix check compares the supported formats with the published conversion pages so a page doesn’t advertise a route the tool doesn’t implement.

For data tools the useful comparison includes the values in the output rather than just the existence of a downloaded file. For image and PDF work the original should remain available for a visual comparison. A result that opens successfully can still have the wrong page order or an unintended background.

Browser and page checks

The repository includes browser checks for keyboard access and accessibility along with light and dark themes. Navigation and layout checks look for problems such as controls that don’t fit the available width. Other checks inspect structured data and internal links.

The automated workflow is configured to run its browser checks with Chromium. That isn’t a claim that every browser and device has been individually verified. A browser update or a different memory limit can change behaviour even when the same file worked elsewhere.

What these checks don’t establish

A fixture represents a particular input. It doesn’t cover every malformed document or every file exported by another application. OCR output still needs checking against the source, especially for names and numbers. A compression result still needs a readability check.

We don’t claim that a successful test establishes legal suitability or acceptance by an upload portal. Keep originals and check the receiving service’s requirements before using a modified document.

Report a repeatable problem

Use Contact with the tool name and browser version. Describe what you expected and what happened. If possible reproduce the issue with a small non-sensitive file rather than sending private documents.

File processing and website measurement are different activities. The tools process files locally while the shared page layout includes Google Analytics. Don’t interpret local file processing as a promise that an ordinary page visit makes no network requests. See the privacy policy for the site’s broader data practices.

Methodology reviewed on September 21, 2026. This date describes the review of this page rather than a certification that every check passes on every device.