How tools are selected
Each tool must solve a distinct, practical task. We compare the expected workflow with established alternatives, confirm that the browser can perform the job reliably, and decline or narrow features that would produce misleading output.
How tools are tested
Every release is built from a structured catalog and automatically checked for unique metadata, valid lifecycle dates, working local references, consistent premium presentation, and required content. Core tools also use browser automation with real files or independently calculated expected answers—not only page-load checks.
What we verify
- Real downloadable output for file-processing tools.
- Independent arithmetic and boundary cases for calculators.
- Invalid-file, size-limit, and browser-capability errors.
- Keyboard, mobile-width, and status-message behavior.
- Privacy claims against the actual implementation and network policy.
What we do not claim
Automated checks cannot guarantee that every unusual file, browser extension, device, or future browser version will behave identically. Medical, financial, religious, legal, and security-related tools provide information or calculations—not professional advice or certification. Their pages state relevant limitations.
Corrections
If a result appears wrong, keep the original input and report the tool, browser, expected result, and actual result. Reproducible correctness and privacy problems receive priority.