How we test our tools
Trust claims require evidence. Before we say a tool runs in your browser without upload, we verify it — and we re-verify when browsers or dependencies change.
Our testing process
- 1
Functional verification
Each tool is exercised with representative inputs — common formats, edge cases (large batches, transparency, multi-page PDFs), and error paths like invalid JSON.
- 2
Privacy verification
We monitor network activity during file operations to confirm payloads are not uploaded for browser-based tools. Regressions are treated as release blockers.
- 3
Cross-browser smoke tests
Critical tools are checked on current Chrome, Firefox, Safari, and Edge releases. Mobile smoke tests cover high-traffic converters.
- 4
Performance sanity checks
Large but realistic files are processed to ensure the UI remains responsive and memory use stays within practical browser limits.
- 5
Documentation alignment
Knowledge Center guides and on-page copy are reviewed when tool behavior changes so we do not overclaim privacy or features.
If a tool fails, include browser name and version, operating system, file type, approximate file size, and steps to reproduce. Screenshots of the network tab help for privacy-related questions. Use the contact page.
Related: Technology, Editorial Policy, Knowledge Center