About

How TestYourBrowser™ works

What TestYourBrowser™ is

TestYourBrowser™ is a set of browser diagnostics and troubleshooting guides. We help you answer practical questions like “Does this browser support WebGL?”, “Why won’t my camera work in Meet?”, or “Why is storage blocked in an iframe?”.

Ownership and editorial accountability

The project is maintained by the team listed on our Team page. We publish under clear author and reviewer bylines, and each guide shows publish/update/review dates so you can evaluate recency and responsibility.

If you find a mistake, send it through Contact with reproduction details. We treat corrections as first-class work and update timestamps when guidance changes.

How the tests work

Our tests run in your browser and use standard web APIs to detect support and common failure modes. For example, a WebRTC test checks whether the browser can access media devices and establish peer connection primitives; a storage test performs safe write/read round-trips to confirm whether cookies, localStorage, and IndexedDB work in the current context.

Start here if you’re troubleshooting: Browser Capability Test and the Browser Testing Hub.

Privacy by design

We do not use invasive fingerprinting techniques. For details on what we collect and what we don’t, see our Privacy Policy.

How our guides are written and reviewed

Our guides are written to be verifiable: they reference official documentation (for example, MDN and browser vendor support pages), include specific steps, and include “verify” instructions so you can confirm the fix worked. Each guide shows publish/update dates and review metadata.

Read the full standards here: Editorial Policy. Meet the team: Team.

Learn why we built the site: Mission and vision. If you want to work with us: Careers.

See what we provide: Our services.

How to verify fixes

We publish a test-first workflow:

  1. Run the relevant diagnostic and capture the failing result.
  2. Apply one scoped change at a time.
  3. Re-run the same diagnostic to confirm the result changed.
  4. Only then move to app-level retesting (Meet, Teams, checkout, etc.).

Start with the Browser Capability Test or browse the Browser Testing Hub.

Written by Avery Collins. Reviewed by Dana Brooks.

Contact

Questions, corrections, or an issue to report? Visit Contact or email [email protected].