Hardware diagnostics should explain, not merely animate.

The MeterSee project maintainer

MeterSee is an independent browser-diagnostics project. Its maintainer develops and maintains the browser tools, updates troubleshooting guides, organizes linked official references, and handles feedback and corrections. The guides help users interpret test results and decide which microphone, camera, audio, display, or peripheral setting or device to check next.

For editorial or technical feedback, contact the project maintainer at hello@metersee.com or use the contact page.

How guides are prepared

Guide drafts and translations may use AI assistance. We compare selected, explicitly identified claims with linked primary documentation and check descriptions of MeterSee tools against their implemented behavior. Hypothetical cases are illustrations, not customer studies or physical-device results.

Each revised long-form guide identifies one dated source check and its narrow scope. That check does not certify every assertion, the complete translation, or manufacturer compatibility. We update text when a source or product menu changes and mark browser measurements separately from conclusions that need a real device or another application.

Corrections and feedback

Send the guide URL, the exact disputed statement, and a supporting primary source to hello@metersee.com, or use the contact page. We assess the report, amend affected languages when warranted, and revise the visible modification date for material changes. Do not send private recordings, passwords, or device serial numbers.

hello@metersee.com

Why this project exists

A moving microphone meter does not tell you whether the right device is selected, whether a meeting app can use it, or whether your hardware needs replacing. MeterSee pairs observable results with practical next steps and explicit measurement limits.

Start with the device you are having trouble with, repeat the check after one change, and compare with the operating system or the application where the problem occurs. A browser result is one piece of evidence, not a repair diagnosis.

What our tools actually measure

• Microphone: digital signal levels from browser-delivered audio, expressed in dBFS. These are not calibrated room loudness or microphone sensitivity measurements.
• Webcam: settings reported by the browser and delivered video frames when the relevant API is available. Frame timing alone cannot identify the faulty component.
• Connection: repeated HTTPS requests to MeterSee. Their timings and failure rate are not RTP jitter, UDP packet loss, broadband speed, or measurements of a Zoom, Teams, or Meet server.
• Display and peripherals: browser animation timing, input events, and visual or audible patterns. Several checks require your observation; software cannot see dead pixels or hear your headphones.
• PC slowdown: browser responsiveness and optional local workloads, together with system readings you enter. A webpage cannot inspect installed programs, malware, all processes, temperatures, or physical RAM usage.

See our measurement methodology for formulas, screening bands, and limitations.

Validation and honest uncertainty

We check calculation rules with known inputs, review the wording against the implemented tools, and use browser tests to check interactions. The current release record separates deterministic calculation tests, browser-interface tests, and any device tests that were actually performed; unavailable hardware is recorded as unverified rather than simulated.

Read the public verification record.

These checks do not amount to laboratory certification or proof of compatibility with every device. We do not claim an independently certified hardware lab, peer-reviewed research, or manufacturer endorsement. A passing check applies only to the observations collected during that run. Unsupported, untested, or unavailable readings must remain unknown.

Local media processing, with clear boundaries

Microphone audio, webcam frames, and diagnostic report contents are processed in your browser, not uploaded to MeterSee for analysis. PDF reports are generated locally. Any report you download remains on your device until you delete it.

Loading the website and running connection checks still sends ordinary web requests. Hosting, consent choices, optional analytics, and advertising have separate data implications described in our Privacy Policy. Local media processing does not mean zero network traffic.

Independence and funding

MeterSee is not affiliated with device manufacturers or meeting platforms. Their names identify products discussed in troubleshooting instructions, not endorsements.

The tools are free. We intend to support the site with advertising, subject to the advertising provider’s approval. Advertising is not a certification of our diagnostic results and must remain separate from test controls.

Report something we can reproduce

Use the Contact page or email hello@metersee.com. Include the tool, browser and operating-system versions, expected result, observed result, and steps to reproduce it. Do not send private audio, video, credentials, or serial numbers.