Choosing the right approach to use an audio equalizer means deciding, before you touch a single slider, what kind of tonal change your file actually needs and which tool is honest enough to give you that change without hiding side effects. A peaking equalizer with a fixed Q value, fixed centers, and a fixed gain range is a deliberate trade: you give up a graphic 10-band interface in exchange for a small, disclosed set of decisions that you can predict on every file. The approach you pick should match your file format, your listening goal, and your tolerance for hidden clipping. With the Audio Equalizer on Lizely, the approach is a three-band peaking equalizer centered at 100 Hz, 1 kHz, and 10 kHz (with the treble center reduced to 45% of the sample rate at low rates), Q=1, integer gains from -12 to +12 dB, all processing in the current browser tab, and a uniform safety scale to 0.99 before the result is written as a PCM16 WAV. That contract is the answer to "which approach" because every limit and every number is visible on the page.
What "choosing an approach" actually means with an audio equalizer
Most people read "approach" as "which preset" or "which plugin." In practice, the choice happens earlier, on three axes that determine whether any equalizer can do what you want.
- Filter shape. A peaking filter changes a region around a center frequency; a shelf filter changes everything below or above a corner frequency; a linear-phase filter holds the phase of the source. Each shape solves a different problem.
- Center frequencies and bandwidth. Three bands with broad Q values cover broad tonal decisions. Ten narrow bands cover surgical moves. Choosing the right approach is partly choosing how many decisions you actually want to make.
- Output policy. Some tools normalize to a target loudness, some prevent clipping with a uniform gain reduction, and some leave peaks alone and let the encoder chop them. Your file and your destination decide which policy is safe.
The Audio Equalizer commits to a specific point in this space: three peaking filters, broad Q=1, disclosed centers, and one uniform safety scale that fires only when the raw peak after EQ exceeds 0.99. The cascade order is Bass, then Mid, then Treble, using the peaking-EQ biquad equations published in the W3C Audio EQ Cookbook.
Match the approach to your file and your goal
The right approach depends on what you are trying to fix or improve. Three broad cases cover most listener-facing decisions.
- Tonal balance. The track sounds muddy, harsh, thin, or boomy but has no obvious defect at a single frequency. A three-band peaking approach with a small cut on the band that bothers you is usually the safest first move.
- Specific resonance. A ring, whistle, or rumble sits at a known spot. A three-band EQ can attenuate the closest band, but the band is broad, so the cut spreads. If the resonance needs a narrow notch, the three-band approach is the wrong tool.
- Playback environment. Headphones, earbuds, and small speakers make the same recording sound different. A three-band EQ can compensate for a missing frequency range, such as boosting bass on earbuds, but it cannot fix room acoustics or a bad source recording.
A peaking filter affects a region around its center rather than every frequency below or above a hard boundary, and Q=1 is a broad adjustment by design. That is why the right approach with this tool is usually one careful cut, not three stacked boosts. Strong boosts may emphasize noise, sibilance, rumble, or existing distortion, and a cut is often safer than stacking several boosts.
Use the Audio Equalizer: a three-band peaking workflow
The following ordered steps match the verified operating contract of the tool.
- Choose one browser-decodable audio file within the 50 MiB and five-minute decoded limits. The supported containers are MP3, WAV, M4A, AAC, Ogg, WebM, and FLAC, provided the current browser and operating system can decode the actual codec inside the container. A familiar extension is not a guarantee, and a decode failure produces an error with no stale download presented.
- Set Bass, Mid, and Treble to whole values from -12 through +12 dB. Bass targets 100 Hz, Mid targets 1 kHz, and Treble targets 10 kHz. On a low sample rate, Treble becomes 45% of that rate so the center stays below the Nyquist limit instead of asking an invalid digital filter to operate outside the available spectrum.
- Apply the equalizer locally. Three peaking biquads from the W3C Audio EQ Cookbook run in Bass, then Mid, then Treble order with Q=1 on each section. The page converts the selected decibel gain into the coefficient parameter defined in that note, normalizes every coefficient by a0, and runs the resulting second-order recursive filter over each decoded channel. Zero on all three controls is a genuine flat path: the tool copies the decoded samples without running a non-zero filter.
- Check the raw peak, output peak, safety scale, sample rate, and frame count reported on the page. If the raw peak after EQ is above 0.99, one uniform scale factor brings the output peak down to 0.99. The same scale is applied to every channel and every sample.
- Preview the result on the speakers or headphones that matter, then download the PCM16 WAV. The download is a new uncompressed file. It does not keep the original codec, bitrate, tags, artwork, chapters, loop markers, or container metadata.
For a practical walkthrough of the same three-band logic, the guide How to Equalize Audio: A Practical Three-Band Walkthrough covers the reasoning behind each band in more detail.
Reading the numbers after you apply EQ
The page reports five numbers: raw peak, output peak, safety scale, sample rate, and frame count. Reading them in order tells you whether the approach worked.
- Sample rate and frame count confirm what was actually decoded. Web Audio may resample while decoding, so the reported rate can differ from the source container rate. The WAV header will write this decoded rate, not a guessed original.
- Raw peak is the absolute maximum across every processed sample and every channel, before any safety adjustment. If it is 0.99 or below, no scaling was needed and the safety scale should be 1.
- Output peak is the value written into the WAV after scaling. By design it is never above 0.99, because the encoder converts each float sample into signed 16-bit little-endian PCM and any float above 1.0 would clip.
- Safety scale is the single uniform multiplier applied to all channels when the raw peak exceeded 0.99. It is not loudness normalization and does not target LUFS, RMS, replay gain, or a streaming-platform specification.
A single worked example: if a +6 dB bass boost, +3 dB mid boost, and +6 dB treble boost produce a raw peak of 1.05, the tool computes the safety scale as 0.99 ÷ 1.05 ≈ 0.943. The same 0.943 is then applied to every sample across every channel, so the output peak lands at 0.99 and the WAV can be encoded without clipping. Use the preview and reported numbers as checks, not as proof of a desirable mix, and avoid judging only from louder output.
When the three-band approach is the wrong fit
The product description is explicit about what this equalizer is not. It is not a graphic 10-band system, not a linear-phase mastering processor, not an automatic room correction system, and not a promise that one setting improves every recording. Knowing when the approach is wrong is part of choosing the right approach.
The three-band approach is the wrong fit when any of the following is true.
- You need a center frequency that is not 100 Hz, 1 kHz, or 10 kHz.
- You need a Q value other than 1, especially a narrow notch for a single resonance.
- You need linear-phase processing to keep transients intact.
- You need loudness normalization to a specific target such as -16 LUFS for streaming.
- You need the original codec, bitrate, tags, artwork, or container metadata preserved in the output.
In those cases, a full audio editor with precise center frequencies, adjustable Q, spectrum analysis, automation, linear-phase processing, loudness metering, dithering controls, codec selection, and metadata preservation is the right tool. The Audio Equalizer on this page is the right tool when the decision is broad, fast, and reversible, exactly the case where "which approach" matters less than "will it actually change the right band."
For verification of what the downloaded file contains, see Check the Result After Using an Audio Equalizer. For a comparison against common mistakes, the guide on common audio equalizer mistakes is also useful background.
Comparing the approaches at a glance
The table below summarizes when each kind of approach is appropriate. The "directional" columns describe the relationship qualitatively; exact figures for any specific file come from the tool.
| Your situation | Three-band peaking EQ | 10-band graphic EQ | Full parametric or linear-phase editor |
|---|---|---|---|
| Broad tonal balance fix on a clean recording | Strong fit | Strong fit | Strong fit, more decisions than needed |
| Narrow resonance or single-frequency notch | Wrong fit (Q is fixed at 1) | Limited fit | Strong fit |
| Headphone or earbud compensation | Strong fit | Strong fit | Strong fit |
| Mastering for streaming loudness targets | Wrong fit (no LUFS target) | Wrong fit | Strong fit |
| Preserve original codec, tags, and metadata | Wrong fit (always writes PCM16 WAV) | Wrong fit | Strong fit |
| Privacy-sensitive file | Strong fit (local only) | Varies | Varies |
The privacy point is worth highlighting because it is part of the approach decision. The Audio Equalizer runs in the current browser tab; Lizely does not receive the audio bytes, the decoded samples, the EQ settings, the filename, or the result. Limits protect the tab from unexpectedly large decoded data: input is capped at 50 MiB, decoded audio must be five minutes or shorter, have one through eight channels, use a sample rate from 8,000 through 192,000 Hz, and contain no more than 30 million channel samples. The tool rejects an over-limit file before filtering and never silently truncates the end.
Picking the right approach in practice
Choosing the right approach to use an audio equalizer is less about picking the perfect preset and more about matching a tool's disclosed contract to the decision you actually need to make. For broad tonal balance on a file you are willing to export as a new PCM16 WAV, the three-band peaking approach on the Audio Equalizer is fast, local, and reversible. For surgical notches, linear-phase mastering, or metadata preservation, the right approach is a full audio editor with adjustable centers, Q, and loudness targets. Read the raw peak, the output peak, and the safety scale on the page, preview on the speakers that matter, and avoid judging from louder output alone. Each accepted channel keeps the same number of sample frames, all channels are filtered independently with identical settings, and the final WAV uses the already-tested shared PCM16 encoder rather than accepting a visible success message alone.