Check the result after using an audio equalizer by reading the numeric metrics the tool reports, previewing the processed audio, and downloading the complete PCM16 WAV so you can verify it in another player. The Audio Equalizer surfaces five numbers after every run: the raw peak of the equalized signal, the output peak after the safety pass, the uniform safety scale that was applied, the decoded sample rate, and the total frame count across all channels. Those values let you confirm that your boost or cut took effect, that no silent truncation occurred, and that the WAV header matches what was actually processed. The preview plays the same samples that get written to the file, and the download preserves every channel with no reslicing or end-cutting. Treat the reported numbers as the primary check, the preview as a confirmation, and the WAV header fields as the final receipt that the file on disk matches the equalization you just heard.
The workflow is short because the verification is built into the same page that applies the equalizer. You do not need a second tool, an external meter, or an upload to confirm the result. Once you understand what each reported number means, the act of checking the result becomes a few seconds of reading the panel and a quick A/B against the original at a matched level.
What "Checking the Result" Actually Means Here
Equalizing an audio file produces two distinct things you may want to confirm: the audible change in the sound, and the numeric state of the processed samples. The Audio Equalizer is explicit about the second one, which is what most people searching for how to check the result after they use an audio equalizer actually need.
Specifically, the tool tells you:
- Whether your chosen bass, mid, and treble gains were applied to the signal at all (a flat result is reported as flat, not as a quiet success).
- Whether the cascaded filters pushed the signal above digital full scale and how much the safety pass reduced it.
- How many sample frames were processed, so you can compare against the source duration and confirm nothing was truncated.
- Which sample rate and channel count were actually written into the WAV header.
Audible confirmation through the preview and an external player is the second half of the answer. The numeric panel is the first.
How to Apply the EQ and Read the Result
- Open the Audio Equalizer and choose one browser-decodable audio file within the 50 MiB and five-minute decoded limits. The tool rejects files outside that window before filtering, so an over-limit file gives no stale result to download.
- Set Bass, Mid, and Treble to whole values from -12 through +12 dB. Leave all three at 0 if you want to verify a flat reference copy of the source.
- Click the apply action to run the three peaking filters locally. Processing happens in your current browser tab; no bytes leave the page.
- Read the reported panel: raw peak, output peak, safety scale, sample rate, and frame count. These are the values that confirm what the equalizer did to your signal.
- Use the in-page preview to listen to the exact samples that will be written, then download the PCM16 WAV to keep the processed version.
If the safety scale value reads exactly 1, no uniform scaling was needed and the raw peak was already at or below 0.99. If it reads below 1, the cascaded boosts exceeded digital full scale and the tool reduced every processed sample by that factor so the WAV encoder would not chop individual peaks.
Reading the Raw Peak, Output Peak, and Safety Scale
The raw peak is the absolute maximum magnitude across every processed channel, measured before any safety reduction. The output peak is the same measurement taken after the optional safety pass. The safety scale is the uniform multiplier that was applied to every sample to bring a too-hot result back to a 0.99 ceiling.
| Reported value | What it confirms |
|---|---|
| Raw peak | Highest sample magnitude produced by your Bass, Mid, and Treble settings across all channels |
| Output peak | Highest sample magnitude after any safety scaling; will be 0.99 whenever a scale was needed |
| Safety scale | Uniform multiplier applied to every sample; equals 1.0 when no scaling was required |
| Sample rate | Decoded rate actually used during processing and written to the WAV header |
| Frame count | Total sample frames across all channels; matches the decoded duration at the reported rate |
A single worked example makes the relationship clear. If the raw peak of your equalized signal is 1.05 and the safety scale prints as 0.943, every processed sample was multiplied by 0.943 so the new output peak became 0.99 (0.99 divided by 1.05 equals 0.943). That is the only case in which the scale moves below 1, and the page reports the exact factor it used rather than hiding it inside the encoder.
Two corner cases are worth noting. First, all three controls at 0 dB is a genuine flat path: the tool copies the decoded channel samples without running a nonzero filter section, so the raw peak equals the input peak and the safety scale equals 1.0. Second, a safety scale below 1.0 is not loudness normalization. It does not target LUFS, RMS, replay gain, or any streaming-platform specification; it only prevents the PCM encoder from clipping individual samples.
Preview and Download Verification
The preview button plays the same samples that will be written to the WAV, which makes it a direct confirmation that the equalization you dialed in is the equalization you can hear. Two habits improve this check. First, match the perceived loudness between the original and the processed version before judging tone. A safety scale below 1.0 will make the processed file quieter at the same playback volume, and a louder file is often mistaken for a better one. Second, listen on the speakers or headphones that matter for your final use case. The tool reports numbers that do not change with playback hardware, but the audible verdict on whether a bass boost cleaned up a muddy recording or made it boomy absolutely does.
The download is a new uncompressed PCM16 WAV. The header records the actual channel count, sample rate, byte rate, block alignment, bit depth, and complete data length, so opening the file in a hex editor or a WAV inspector will show fields that line up with the panel on the page. Float samples are converted to signed 16-bit little-endian PCM and interleaved by frame, and every accepted channel is filtered independently with identical settings. If you see a mismatch between the frame count reported on the page and the data length in the WAV header, the file did not come from this run.
| Band | Center frequency | Q value | Filter type |
|---|---|---|---|
| Bass | 100 Hz | 1 | Peaking biquad from the W3C Audio EQ Cookbook |
| Mid | 1,000 Hz | 1 | Peaking biquad from the W3C Audio EQ Cookbook |
| Treble | 10,000 Hz, or floor(sampleRate x 0.45) on low rates | 1 | Peaking biquad from the W3C Audio EQ Cookbook |
The treble row reflects a constraint the page enforces automatically: at a low decoded sample rate, the treble center is reduced to 45 percent of that rate so it stays below the Nyquist limit instead of asking an invalid digital filter to operate outside the available spectrum. For example, a 22,050 Hz decoded source gives a treble center of floor(22,050 x 0.45) = 9,922 Hz, well under the 11,025 Hz Nyquist ceiling. That adjustment is one of the checks worth confirming in the result panel so you know which treble frequency your boost or cut actually targeted.
Limits That Affect What the Result Can Show
Every numeric on the result panel is honest, but a few limits determine whether the result panel appears at all:
- Input size is capped at 50 MiB. Larger files are rejected before filtering and produce no result to check.
- Decoded audio must be five minutes or shorter, with one through eight channels, a sample rate from 8,000 through 192,000 Hz, and no more than 30 million channel samples. A file that exceeds any of these limits is rejected outright, not silently trimmed.
- Decoding depends on the browser and operating system supporting the actual codec inside the container. A familiar extension such as .m4a or .webm is not a guarantee; a decode failure produces an error and no stale download is presented.
- Web Audio may resample while decoding, so the sample rate reported on the result panel is the decoded rate rather than the rate advertised by the source container.
These limits exist so that the numbers you read on the result panel actually describe the bytes in the downloaded WAV. The page does not hide a partial decode behind a successful-looking preview.
When a Result Check Needs More Than This Page
The result panel is designed for verification, not mastering. It tells you what the equalizer did, not whether the equalization is a good idea. Use the preview and reported numbers as checks, then compare against the original at a similar perceived level rather than judging only from louder output. Strong boosts may emphasize noise, sibilance, rumble, or existing distortion, and a cut is often safer than stacking several boosts.
If your goal is finer verification than a three-band peaking equalizer can deliver, the right next step is a full audio editor with spectrum analysis, adjustable Q, automation, loudness metering, dithering controls, and metadata preservation. The Audio Equalizer gives you a transparent numeric receipt for a flat-to-+/-12 dB three-band pass and a complete PCM16 WAV you can load into that editor if you need to go deeper. For a broader view of common traps in this workflow, the guide on common audio equalizer mistakes pairs well with the verification steps above.
The download is intentionally minimal. It does not keep the original MP3 or AAC bitrate, compression mode, tags, artwork, chapters, loop markers, or container metadata, so do not rely on the WAV to round-trip a tagged library file. Use it as a processed working copy, then re-tag and re-encode in a tool that supports metadata if you need the result back in a tagged format. The WAV header itself uses the standard fields defined by the WAVEFORMATEX format, which is what lets any DAW, editor, or inspector read the file back with the same channel count and rate the result panel reports.
For a deeper look, see Choose the Right Approach to Use an Audio Equalizer.