Equalize audio in Audacity without installing it by using the Audio Equalizer, a browser-based tool that applies three disclosed peaking filters at 100 Hz (Bass), 1,000 Hz (Mid), and 10,000 Hz (Treble) with integer gains from -12 to +12 dB, and exports the result as a PCM16 WAV that you can reopen in Audacity for further editing. The page runs entirely in your current tab: Web Audio decodes your MP3, WAV, M4A, AAC, Ogg, WebM, or FLAC locally, the EQ filters are applied to the decoded channel samples, and only the final WAV leaves your machine. This approach replaces Audacity's multi-band Filter Curve EQ with a compact three-band layout that mirrors its Bass, Mid, and Treble sliders, which is enough for common voice cleanup, podcast tone shaping, and music tone shaping. Because the tool is browser-only, there is nothing to install, no plugins to update, and no project file to manage — just choose a file, set three values, and download.
What Audacity's Equalizer Does vs. the Browser EQ
Audacity exposes its equalization through the Filter Curve EQ and Graphic EQ effects, both of which give you a row of sliders across the frequency spectrum. Most casual users, however, only touch three of those sliders: Bass, Mid, and Treble. The browser-based Audio Equalizer strips that experience down to exactly those three bands and tells you which center frequency each one uses, which is information Audacity hides inside its preset names.
Both tools rely on the same underlying idea: a peaking filter is a biquad that boosts or cuts energy around a chosen frequency without hard-cutting everything below or above it. The W3C Audio EQ Cookbook publishes the canonical coefficient formulas, and the Audio Equalizer applies them with a fixed Q of 1, which is a broad musical adjustment rather than a surgical notch. If you have ever typed +3 dB at 1,000 Hz into Audacity's Filter Curve EQ, you have already used the same shape of filter this browser tool applies.
The differences are practical rather than theoretical:
- The browser tool has exactly three bands. Audacity's Filter Curve EQ has many more, but you rarely use them all.
- The browser tool's centers are locked at 100 Hz, 1,000 Hz, and 10,000 Hz (with the treble center reduced at low sample rates). Audacity lets you click and drag any frequency you like.
- The browser tool's Q is fixed at 1. Audacity lets you reshape the curve by dragging multiple points.
- The browser tool runs in your tab and never uploads the file. Audacity is a desktop install.
Inputs the Tool Accepts and Hard Limits
Because the Audio Equalizer runs in a browser, it cannot accept an arbitrarily long file without exhausting the tab's memory. The page enforces four hard limits and rejects a file that exceeds any of them before filtering starts — it never silently truncates the end.
| Limit | Maximum value | What happens when exceeded |
|---|---|---|
| Source file size | 50 MiB | File rejected before decoding |
| Decoded duration | 5 minutes | File rejected before filtering |
| Channel sample count | 30,000,000 frames across all channels | File rejected before filtering |
| Channel layout | 1 to 8 channels | File rejected before filtering |
| Decoded sample rate | 8,000 Hz to 192,000 Hz | File rejected before filtering |
The supported source containers are MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC, but only when your current browser and operating system can actually decode the codec inside that container. A familiar extension is not a guarantee: a download renamed to .mp3 may carry a codec your browser cannot read, in which case the tool raises a decode error and offers no download. If you need a longer file, an unusual channel layout, or a codec the browser does not support, Audacity remains the right place for that work — for everything inside these limits, the browser EQ is a faster path.
Equalize Audio with the Three-Band Browser EQ
The whole workflow fits in three actions: pick a file, set three integer values, download the WAV. The processing happens locally in your current tab, so closing the tab discards everything.
- Open the Audio Equalizer page and choose one browser-decodable audio file. Verify it falls inside the 50 MiB and five-minute limits above.
- Set Bass, Mid, and Treble to whole-number values between -12 and +12 dB. Zero on all three is a genuine flat path that copies the channel samples without running any nonzero filter section.
- Apply the equalizer locally. The page cascades three peaking biquads in Bass, Mid, then Treble order over each decoded channel, with Q fixed at 1.
- Check the raw peak, output peak, safety scale, sample rate, and frame count that the page reports after processing. Use the inline preview to confirm the tonal change before downloading.
- Download the result. The file is a complete PCM16 WAV whose header records the actual channel count, decoded sample rate, byte rate, block alignment, bit depth, and total data length.
If you want more context on what each slider does musically, the practical three-band walkthrough covers the same tool with worked listening examples. For people moving from Audacity specifically, the only habit change is that the controls are integer dB rather than the decimal values Audacity's Filter Curve EQ accepts.
Reading the Raw Peak, Output Peak, and Safety Scale
Three numbers appear in the result panel after you apply the equalizer, and they each answer a different question:
- Raw peak — the largest absolute sample value across every processed channel and every frame, before any safety adjustment. This is what the cascaded biquads actually produced.
- Output peak — the largest absolute sample value in the WAV that the encoder writes. In a flat pass, this equals the raw peak.
- Safety scale — the single uniform factor that was applied to every processed sample to keep the output peak at or below 0.99.
The safety scale kicks in only when the raw peak exceeds 0.99. If you stacked +6 dB on Bass and +6 dB on Treble against a source that already sat close to full scale, the raw peak might rise to 1.18. Dividing 0.99 by 1.18 gives a safety scale of about 0.839, and every processed sample is multiplied by that factor before encoding. The page applies the scale uniformly across all channels rather than independently compressing each one, which prevents the PCM encoder from chopping individual peaks but can reduce the overall level slightly.
The peak-to-amplitude relationship inside the biquads themselves is governed by the W3C coefficient formula. For one band set to +12 dB, the intermediate amplitude term A equals 10(12/40), which works out to about 1.995. That is the multiplier the cookbook uses when it computes the peaking filter's A coefficient, and it is the reason why a +12 dB boost can push the raw peak well above the original source peak even before any safety scale is needed.
What the Downloaded WAV Contains and What It Drops
The download is a brand-new file, not a re-wrap of your source. Web Audio may resample while decoding, so the WAV you receive is written at the decoded sample rate, not the rate the original container advertised. Float samples are converted to signed 16-bit little-endian PCM and interleaved by frame, and the WAV header records every field honestly: actual channel count, sample rate, byte rate, block alignment, bit depth, and a complete data length that matches the file.
What the new file does not preserve:
- The original MP3, AAC, Ogg, or FLAC codec and its bitrate
- Compression mode and any psychoacoustic encoder settings
- ID3, Vorbis, or MP4 tags, including track titles and artist fields
- Embedded artwork, chapter markers, loop markers, and container-specific metadata
That trade-off is the price of moving audio through a JavaScript audio graph. If you need the result back in MP3 or AAC for upload to a podcast host or streaming platform, you re-import the WAV into Audacity (or any encoder) and export from there. The browser tool's job ends at producing a clean, full-length PCM16 master.
When to Switch Back to a Full Editor
The three-band browser EQ is intentionally compact. It is the right tool when you want a quick tonal adjustment on a voice memo, a podcast intro, or a music demo and you are happy with three fixed centers and integer dB steps. It is the wrong tool when any of the following apply:
- You need precise center frequencies that fall between 100 Hz, 1,000 Hz, and 10,000 Hz.
- You need a tunable Q for a narrow notch or a sharp shelf.
- You need spectrum analysis, automation curves, or linear-phase mastering.
- You need loudness metering, dithering controls, or codec-specific export settings.
- You need to preserve artwork, chapter markers, or ID3 tags in the result.
For those jobs, Audacity, a dedicated DAW, or a specialized loudness tool is the right environment. The browser Audio Equalizer is best understood as the fastest way to ship a tone-shaped WAV from any computer with a modern browser, leaving more involved mixing decisions for an application designed for them.