Speaker Test
Run a left/right speaker test with finite tones, center, frequency checks, and a sweep. Record what you hear locally; the browser cannot listen or certify speaker health.
- Browser capability-dependent
- No device permission
- Optional history in this browser
- No account or upload
Important
- You must confirm what you hear. The page cannot measure real dB SPL or certify speaker health.
This controls browser-generated signal gain only, up to 0.4. System, amplifier, powered-speaker, DAC, and headphone levels remain separate. It is not calibrated dB SPL or a guaranteed safe loudness. Lower system volume first and stop if the sound is uncomfortable.
Choose a known signal
Each button starts one finite, locally generated signal. Listen to the selected output path, then record what you heard for that exact signal.
Observation for the last successful signal
Play a signal successfully before recording an observation.
- Audio status
- Ready
- Playing
- No
- Last signal
- —
- Signals tested
- 0
- Observations
- 0
Recent listening checks
Up to five self-reported checks are stored in this browser only. No microphone, camera, recording, or upload is used.
No saved listening checks yet.
How to use
- Lower the system, amplifier, or powered-speaker volume before starting; App output gain controls only this page's browser signal.
- Confirm the intended speakers, soundbar, display, Bluetooth device, or other output is selected in the operating system.
- Play Left, Right, Both / Center, or Alternating at 440 Hz to check whether the requested browser channel reaches the side you expect.
- Use the 120 Hz, 440 Hz, and 4 kHz signals briefly to compare audibility, weakness, or artifacts at the same app gain.
- Optionally run the bounded 200–4000 Hz sweep or short chord; neither measures a response curve.
- After each successful signal, record one observation for that exact signal rather than making a general hardware verdict.
- Use Stop all sounds at any time; generated audio also stops when the tab becomes hidden.
- Save the listening check only after at least one signal has a bound observation. Up to five records stay in this browser.
- Compare the saved observations and retry with one controlled change, such as the output device, cable, profile, or app gain.
- Use the manufacturer or operating-system guidance if the same issue persists with a known source outside this page.
What the result means
- Heard clearly as expected means the browser-to-OS-to-output path produced the selected signal in the direction you expected. It does not certify speaker hardware.
- Sound from an unexpected side can indicate routing, channel remapping, wiring, a mono path, or a device profile. The page cannot identify which part caused it.
- Heard nothing means no audible output was confirmed for that signal. Check the selected device, mute and volume stages, then compare with a known source before suspecting hardware.
- Heard weakly is a same-app-gain listening comparison. Output processing, placement, the room, and the source chain can all affect it.
- Buzz, rattle, or distortion is a prompt to lower the level and compare another frequency or known source; it is not proof of a blown driver.
- A quieter or missing part of the sweep can reflect speaker bandwidth, room acoustics, processing, or individual hearing. It is not a measured frequency response or automatic failure.
- Unsure preserves uncertainty and is a useful reason to repeat the signal under a more controlled setup.
Limitations
- The page controls generated digital routing and app gain, but it cannot hear acoustic output or inspect the physical speaker, amplifier, cable, room, or listener.
- App output gain is capped at 0.4, but system volume, amplifier gain, powered-speaker gain, DAC gain, and speaker sensitivity remain outside the page.
- The signal is not calibrated in dB SPL and does not guarantee a safe or equal acoustic loudness across devices or frequencies.
- Left and Right require browser StereoPanner support. Those controls are disabled rather than silently played in the center when support is unavailable.
- Bluetooth codecs, HDMI routing, accessibility audio, mono output, spatial audio, and device profiles can alter channel position or frequency character.
- This is not a hearing test, medical assessment, component diagnosis, response measurement, repair report, or hardware certificate.
Troubleshooting
- No sound
- Confirm the system output device, browser or tab mute, system and hardware volume, then click a signal again. Compare with a known local source before drawing a hardware conclusion.
- Left and Right are reversed or both play from one side
- Check OS balance, channel mapping, cables, dock or receiver routing, and whether mono audio or a spatial profile is enabled. Retest after changing one item.
- One side sounds weaker
- Keep App output gain unchanged, swap the source or cable path if practical, and compare a known source. Placement, room reflections, balance settings, and hardware may contribute.
- Buzz, rattle, crackle, or distortion
- Stop or lower the level first. Retry briefly at another frequency and with a known source; the browser cannot determine whether the signal chain, enclosure, room, or speaker caused it.
- Bluetooth output is delayed or changes character
- Confirm the active Bluetooth profile and reconnect the device. Codec, profile, wireless conditions, and processing can affect timing and tone.
- HDMI or display audio uses the wrong output
- Select the intended HDMI or display device in system settings and check the display, receiver, or dock volume. The page cannot choose a physical output device.
- Directional signals are disabled or do not separate
- The browser may lack StereoPanner support, or the output may be mixed to mono or processed by spatial audio. Use the enabled center signals and check system audio settings.
- Part of the sweep is hard to hear
- Do not raise volume aggressively. Speaker bandwidth, room response, processing, and hearing all affect audibility; use a calibrated measurement setup for response data.
Related tools
FAQ
Does Speaker Test use my microphone or record audio?
No. Signals are generated locally with Web Audio. The page does not request a microphone or camera, record output, or upload audio.
What is saved locally?
Only the listening-check data you choose to save: timestamp, tested signal labels, your per-signal observations, and the page's App output gain. Up to five records are kept in this browser's localStorage.
Can this test prove a speaker is broken?
No. It provides known browser-generated signals and preserves your observations. The browser cannot isolate a speaker from OS routing, cables, amplifiers, processing, the room, or the listener.
Why test Left, Right, and Both separately?
Separate browser pan requests help you compare expected channel direction with a centered signal. Audible direction still depends on browser support and the complete output path.
Does the sweep measure speaker frequency response?
No. It requests a local sine sweep from 200 to 4000 Hz for listening comparison. It does not use a calibrated microphone or produce a response curve.
Should every frequency sound equally loud?
No. Device response, processing, room acoustics, playback level, and hearing affect perceived loudness. Equal app gain is not equal acoustic loudness.
When should I use Headphone Test, Stereo Test, or Tone Generator?
Use Headphone Test for headphone-specific channel and phase listening, Stereo Test for stereo image and routing checks, and Tone Generator when you need a chosen continuous frequency or waveform rather than this guided speaker workflow.