How We Test

• The tool runs correctly across the full user flow — start, stop, mode switches, and error states — checked with automated browser tests, not just a quick manual click.
• No console errors, hydration mismatches, or crashes on load or during interaction.
• Audio always requires a real tap or click to start, never autoplays, and always has a working Stop control.
• Health- or measurement-adjacent tools (Hearing Test, dB Meter) are explicitly labeled as approximations, not calibrated instruments.

We haven't yet run a systematic physical test across a large set of real devices (different phone brands, iOS versions, Android skins). Where we make a claim about how a tool behaves on a specific platform, we base it on the underlying web standard's documented behavior, not an invented statistic. As we test on more real hardware, we'll update tool pages with genuine findings — including where something doesn't work as well as we'd like.

We don't publish success rates, "X% of users" claims, or device-specific specs we haven't verified against an official source. If a tool page states a fact about a specific device, it's either general engineering knowledge (like how small speakers struggle with bass) or something we can point to a source for — never a made-up number to sound more convincing.

Some of this site's content is drafted with AI assistance. See our editorial policy for how that content is reviewed.