Tool Testing Methodology
The checks every tool passes before — and after — it goes live.
Last updated: June 2026
Functional testing
Each tool is tested against a range of representative inputs — typical files, edge cases, very large and very small inputs — to confirm it produces correct, predictable results and fails gracefully when it should.
Privacy verification
We verify, using the browser's network inspector, that interactive tools perform their work locally and do not transmit your file contents. Any external request (for example, loading a library from a CDN) is limited to code, never your data.
Cross-browser & device testing
Tools are checked in current versions of Chrome, Firefox, Safari and Edge, and on mobile, to ensure consistent behaviour and a responsive layout across screen sizes.
Performance
We watch load size and runtime so pages stay fast. Tool-specific code is loaded only on the page that needs it, and third-party libraries are fetched on demand rather than upfront.
Accessibility
We test keyboard navigation, focus visibility, labelling and colour contrast so the tools are usable by as many people as possible. See our Accessibility Statement.