Skip to Content
Platform.Ontology

Audio fingerprint (OfflineAudioContext)

Renders a sound offline and reads tiny numeric differences.

Gets silentlyGraphics and fingerprintingRenderingWeb browsersWhen the page loadsWhile you use it

In one line

Can make a silent test sound to tell your device apart from others

Renders a sound offline and reads tiny numeric differences.

Audio stack differences give a device specific value without ever playing sound or asking permission. LinkedIn uses OfflineAudioContext(1,44100,44100).

What it can and can't do

What the user does: Nothing. It happens when the page loads

It can

  • Process a short sound in memory without playing it
  • Measure tiny number differences that depend on your device and browser
  • Combine that number with other signals to recognise you later

It cannot

  • Play sound through your speakers
  • Record from your microphone
  • Ask you first, since there is no pop up
  • Work as an ID on its own, because many similar devices give the same result

Browser support

BrowserStatusFirst versionReleasedNote
ChromeSupported352014-05-20None
EdgeSupported122015-07-29None
FirefoxSupported252013-10-29None
SafariSupported14.12021-04-26None
Safari on iPhoneSupported14.52021-04-26None
Chrome on AndroidSupported352014-05-20None
Samsung InternetSupported3.02015-04-10None

How a site asks for it

APInew OfflineAudioContext(1, 44100, 44100)
Browser compat keysapi.OfflineAudioContext
How access is grantednone
What the user seesNone (no browser prompt)
Needs a secure context (HTTPS)No
Needs a user gestureNo
How long it lastsNot listed
How to take it backNot listed
Inside an iframeNot listed

Typical flow

  1. Script reads the value
  2. Value joins the fingerprint payload

Data you get

What comes back: Audio fingerprint (OfflineAudioContext)
Shape: hash
How often: static per setup

FieldTypeUnitRangePrecision
audio_sumfloatNonehash of samplesfloat precision

Technical limits

  • Noise added by some privacy browsers

The story

What it is

A page plays a sound silently in memory and reads tiny number differences that vary by device.

For you

You hear nothing and see no prompt. The page just does some math that a sound chip would do, and the answer helps it recognize your device later.

For makers

Trackers and fraud teams add this to a bundle of signals to build a device ID. It is cheap, needs no permission, and is hard for people to notice. The real feature exists so audio apps can process sound offline.

Where you see it

TypeExampleApps
musicA web music studio renders a finished track to a file offline, much faster than playing it back.BandLab, Soundtrap
gamesA browser game builds echo or reverb effects ahead of time so sound effects play instantly in battle.None named
securityA bank's fraud script plays a silent tone and compares the result with the last visit to confirm it is the same device.None named
adsAn ad tech script adds the audio result to a device ID to recognize you across sites without cookies.None named
analyticsA visitor counting tool uses the audio hash to avoid double counting the same person who cleared cookies.FingerprintJS
creativeA podcast editor in the browser exports a mixed episode by rendering all tracks offline.None named
accessibilityA page prepares sound effects for screen reader users before they hear them.None named

Risks

  • Works without asking
  • Hard to reset
  • Browsers are adding noise to fight it

What the platform says

  • MDN: OfflineAudioContext. Renders audio faster than real time into a buffer, without playing it to the speakers, for effects and analysis.

Good uses and abuse

Legitimate uses

  • Audio rendering tests

Known abuse

  • Fingerprint input

Scores

ScoreValueMeaning
Sensitivity2 of 5How revealing the data is
Utility3 of 5How useful it is to honest apps
Friction0 of 5How much the user has to do
Fingerprint bits5Rough identifying entropy, when known

A real example: LinkedIn

Collector key(s): audio. BleepingComputer confirms audio.

Sources

How well checked: Based on official documentation.

On this page