Test the audio signal exposed by your browser
This local test uses the Web Audio API to process a fixed signal and hashes the output. It does not play sound, use your microphone or upload the result.
Your browser audio result
Computed for this visitRunning the test locally in your browser…
How this signal works
Audio fingerprinting measures small differences in how a browser and operating system process the same generated sound. The test can use an offline audio context, which calculates the waveform without sending anything to speakers. The numerical output is then condensed into a hash.
Audio is normally one modest component in a larger browser fingerprint. On its own it is less descriptive than a full collection of canvas, WebGL, font, screen and browser signals. Its value comes from comparing it with other observations rather than treating it as a unique identifier.
What this result cannot tell you
- Some browsers disable or standardize audio processing in privacy-sensitive modes.
- Operating-system, browser and audio-library changes can alter the result.
- The API reports processing behavior only. It cannot hear the room, inspect files or access a microphone without permission.
Use browser and network signals in your app
The verification API collects the broader fingerprint, binds it to the network request and returns the result to your backend.