Audio-level guide

dBFS vs dB SPL: what a browser audio level can and cannot tell you

Understand why a browser reading such as -24 dBFS describes a digital signal, not the physical loudness at your ears.

A browser setting of -24 dBFS is a digital signal reference. It does not tell you how loud the sound is at your ears, at a microphone, or elsewhere in the room. That distinction matters whenever you use a tone, sweep, or noise signal. dBFS helps you repeat a browser test. dB SPL describes measured air pressure and needs a physical measurement method.

Start with the short answer

dBFS means decibels relative to digital full scale. It describes a value inside a digital audio path. In common Web Audio work, each channel is represented as floating-point samples, and a nominal magnitude of 1 maps to full scale. MDN's Web Audio API guide explains the usual -1 to 1 sample range and the relationship to 0 dB full scale. A negative dBFS value leaves level below that digital reference.

dB SPL means decibels relative to a physical sound-pressure reference. NIST defines a sound-pressure level in decibels relative to 20 micropascals. That number comes from pressure measured in air, not a browser gain value. See NIST's Guide to the SI for the reference quantity. The two units share the word decibel, but their reference points and measurement paths are different.

Keep the two references separate

QuestiondBFSdB SPL
What is the reference?The maximum digital scale used by the signal path.A physical reference pressure in air.
What does a browser test control?The level of the generated digital reference.Nothing by itself. A physical meter and method are required.
What can change the result?The selected source level or signal processing in the digital path.Volume, output hardware, headphone fit, speaker distance, room, microphone, and measurement method.
What does it establish?That two browser references were generated at the same stated digital level.The sound pressure at a stated physical measurement point, if the meter and method support it.

This is why -24 dBFS is not a safe-volume promise and cannot be converted to one fixed dB SPL number. The same digital signal can produce very different physical sound levels through a laptop speaker, powered monitor, wired headphones, USB interface, or wireless headset. System volume and endpoint controls sit after the browser's signal control. With headphones, seal and placement add still more variation.

What the -24 dBFS control is for

Use the level control in the WaveLocus tone generator as a repeatability tool. It gives you a modest digital starting point for a short listening reference. Keep the computer's output volume at a comfortable low setting. If you need to repeat the test later, record the browser, output path, signal type, selected frequency, dBFS setting, and system-volume position. That is enough to make a controlled comparison without pretending to have calibrated the room or headphones.

For example, you may run a 440 Hz tone at -24 dBFS through the same wired headphones today and tomorrow. If the tone is unexpectedly distorted today, repeating the identical digital source while changing only one endpoint element can help narrow the path. The repeated setting gives the listening test a stable input. It does not say whether the endpoint is producing a particular sound pressure or whether the signal is safe for a particular duration.

Why one conversion number does not exist

A conversion would need information the browser does not have. It would need the electrical output level of the device at the chosen volume, the endpoint's sensitivity, any amplifier or interface gain, and a defined physical measurement point. Speaker measurements also depend on distance and room reflections. Headphone measurements need a coupler or other defined method because the result changes at the ear. Even a physical meter needs appropriate calibration and placement for the claim being made.

The browser can create a known digital waveform, but it cannot see the acoustic pressure that leaves a speaker or reaches an ear. Web Audio exposes digital channel data and graphs, not a universal microphone calibrated to every endpoint. MDN's AudioBuffer channel-data reference is a useful illustration of that boundary: it describes PCM data for a channel, not a measured room level.

Use the level safely in a browser test

  1. Begin with hardware volume low. A familiar dBFS number does not predict the output of an unfamiliar device. Start at a low physical volume and raise it only to a comfortable level.
  2. Choose one short reference. Use a tone, noise signal, or short sweep for the specific listening job. Do not leave a test signal running simply because the digital level is negative.
  3. Keep the path fixed while comparing. Hold the browser, output, connection, endpoint, dBFS setting, and system volume still. Change only the one element you are checking.
  4. Describe what you heard, not a made-up SPL. Record statements such as “the same reference distorted through Output A but not Output B.” Do not label it as an SPL result without a physical measurement.
  5. Stop when the sound is uncomfortable. Lower the physical volume or stop the test. A browser reference is not a hearing test or exposure assessment.

What a browser dBFS result can and cannot prove

A fixed dBFS setting can support a useful comparison: the browser was asked to create the same stated digital reference each time. It can also help avoid accidentally starting a simple test at a full-scale source setting. It cannot prove that a speaker is calibrated, that two headphones have the same loudness, that an endpoint is safe, or that a person's hearing is normal. It also cannot identify the cause of audible distortion by itself. The endpoint, operating system, connection, and room may all still differ.

For a signal that returns electrically to a suitable input, use the electrical loopback test instead. It can report conditional digital measurements for a documented electrical path, with eligibility rules. Even that is not an acoustic dB SPL measurement. Use a properly selected and calibrated physical sound-level method when your real question is physical level in air.

Next step

Use the tone generator at a comfortable physical volume, then write down the dBFS setting and path before changing one variable. If the same reference changes across browsers, outputs, or endpoints, continue in guided diagnosis. The useful finding is a controlled difference in the path, not a guessed loudness number.

Sources and method

This guide distinguishes a browser-local digital reference from a physical sound-pressure measurement. MDN's Web Audio API guide documents the digital full-scale convention used in its examples, and NIST's Guide to the SI gives the physical pressure reference for sound-pressure level. WaveLocus does not convert its dBFS controls into dB SPL, provide a hearing assessment, or claim a calibrated acoustic measurement.