Audio base latency
AudioContext.baseLatency reveals the audio stack and hardware.
In one line
Can measure your audio delay to guess your system and audio hardware
AudioContext.baseLatency reveals the audio stack and hardware.
Typical values 0.005 to 0.04 seconds depending on OS and driver (macOS about 0.01, Windows 0.01 to 0.03, Android up to 0.04). Mild hardware signal; read without playing sound.
What it can and can't do
What the user does: Nothing. It happens when the page loads
It can
- Check the audio delay, usually 0.005 to 0.04 seconds
- Guess your system, such as macOS, Windows or Android
- Do this without playing any sound
It cannot
- Listen to you or record sound
- Ask permission first
- Name your exact headphones or speakers
- Know who you are by itself
Browser support
| Browser | Status | First version | Released | Note |
|---|---|---|---|---|
| Chrome | Supported | 58 | 2017-04-19 | None |
| Edge | Supported | 79 | 2020-01-15 | None |
| Firefox | Supported | 70 | 2019-10-22 | None |
| Safari | Supported | 14.1 | 2021-04-26 | None |
| Safari on iPhone | Supported | 14.5 | 2021-04-26 | None |
| Chrome on Android | Supported | 58 | 2017-04-25 | None |
| Samsung Internet | Supported | 7.0 | 2018-03-16 | None |
How a site asks for it
| API | new AudioContext().baseLatency |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | No |
| Needs a user gesture | No |
| How long it lasts | read fresh on every page load; nothing stored |
| How to take it back | none needed (no grant) |
| Inside an iframe | Readable from cross-origin iframes too (same values) |
Typical flow
- Page script reads the value
- No prompt is shown
Data you get
Shape: object
How often: static per session
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
baseLatency | float | seconds | 0 to about 0.1 | double precision |
Technical limits
- Does not need microphone
The story
What it is
A page reads how long your audio system takes to start sound, which hints at your hardware.
For you
You never see a prompt. You just get better timed sound in games and music apps. The same number can quietly tell a site if you use a phone, a laptop or a studio sound card.
For makers
Real time audio apps need this number to line sound up with the screen. Trackers and fraud tools add it to a device profile since it differs by hardware and operating system.
Where you see it
| Type | Example | Apps |
|---|---|---|
| games | A browser rhythm game uses your audio delay to shift the note timing so the beat matches what you hear. | None named |
| music | A web music maker adjusts its recording delay so a track recorded from the mic lines up with the backing. | BandLab, Soundtrap |
| video | A video call tool tunes its audio buffer to avoid echo and lag on your headset. | Google Meet, Zoom web client |
| live | A live streaming page keeps the sound and the picture aligned by checking audio output delay. | Twitch |
| security | A fraud tool sees an audio delay typical of a virtual machine and raises the risk. | None named |
| ads | A tracker puts the delay value in a device ID along with other audio numbers. | None named |
| education | A web music lesson app checks delay so it can tell you whether you played in time. | None named |
Risks
- Reveals audio hardware
- Adds to a device ID
What the platform says
- MDN: AudioContext.baseLatency. Reports the delay the audio system adds, so apps can keep sound and visuals in sync.
Good uses and abuse
Legitimate uses
- Latency tuning
Known abuse
- Hardware fingerprint
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 1 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 2 | Rough identifying entropy, when known |
History
- 2025-09, Safari 26: Web audio readback restricted for known fingerprinters
Sources
How well checked: Based on official documentation.