Use an audio equalizer instead of manual editing when you need a repeatable, broad tonal adjustment across a whole track with Bass, Mid, and Treble controls.
The practical dividing line is simple: an equalizer suits a small set of broad frequency adjustments, while a full editor is better when precision or special processing matters. Here, “manual” means changing frequency and export choices one by one in a fuller workflow; using three EQ bands is still a deliberate decision. The Audio Equalizer applies three disclosed peaking filters locally and creates a new PCM16 WAV without uploading the source. It is not a graphic ten-band system, automatic room correction, or a linear-phase mastering processor.
The practical dividing line
Choose the equalizer when the goal is to change the overall tonal balance of a recording: reduce bass heaviness, add midrange presence, or soften treble. Start with the band that matches the problem and make a modest move. A peaking EQ affects a broad region around its center rather than acting like a hard on/off frequency switch.
- Use it for broad, whole-file changes that can be described with Bass, Mid, and Treble adjustments.
- Keep manual editing for exact center frequencies, adjustable Q, automation, or clip-by-clip decisions.
- Use a full editor for spectrum analysis, linear-phase processing, loudness metering, dithering, codec selection, or metadata preservation.
- Do not expect the equalizer to choose settings, analyze a room, or promise that every recording will improve.
| Task | Three-band browser equalizer | Manual or full-editor workflow |
|---|---|---|
| Broad tonal balance across one file | Good fit: Bass, Mid, and Treble adjust the complete processed result. | Possible, but it can add steps to a simple tonal change. |
| Exact center frequency or adjustable bandwidth | Not supported; the centers are disclosed and Q is fixed at 1. | Use parametric or other detailed manual controls. |
| Automation and spectrum analysis | Not provided. | Use an editor that supports the required view or control. |
| Linear-phase, loudness-targeted, or dithered mastering | Not provided; peak protection is not loudness normalization. | Use a full audio editor or dedicated mastering process. |
| Output format and metadata | Creates a new PCM16 WAV without the source tags or container metadata. | Use an editor when codec choice or metadata preservation matters. |
Manual work is not inherently better; it is simply more capable. If the goal is a stable three-band tonal adjustment, the equalizer may be enough. If the project depends on exact frequencies, changing bandwidth, automation, or a specialized deliverable, use the tool designed for those requirements.
Apply a three-band EQ in the browser
Use the supported workflow in this order:
- Choose one file. Select a browser-decodable source no larger than 50 MiB. Its decoded audio must be five minutes or shorter, contain one through eight channels, use a sample rate from 8,000 through 192,000 Hz, and contain no more than 30 million channel samples. Over-limit files are rejected before filtering, and the tool never silently truncates the end.
- Set the three gains. Choose whole-number Bass, Mid, and Treble values from -12 through +12 dB. Start with one band and a modest adjustment. Zero on all three controls creates a genuine flat filter path rather than applying three nonzero filter sections.
- Apply the equalizer locally. The tool runs three Q=1 peaking biquads in Bass, Mid, then Treble order using the W3C Audio EQ Cookbook equations. It filters every decoded channel independently with identical settings and reports the effective band centers.
- Check the reported values. Review the raw peak, output peak, safety scale, sample rate, and frame count. These numbers confirm processing limits and file structure, but they do not establish whether the tonal result is desirable.
- Preview and compare. Listen on the speakers or headphones that matter, keeping the perceived level similar to the original. A louder processed file can seem better even when its tonal balance is worse.
- Download the result. Save the complete PCM16 WAV after the listening check. It is a new interleaved, signed 16-bit little-endian file rather than a repackaged version of the source.
Know what each control actually changes
The disclosed centers keep the three controls understandable. Bass and Mid remain fixed, while Treble normally stays at 10,000 Hz. At a lower decoded sample rate, its center moves down so the filter remains below the Nyquist limit.
| Control | Filter center | Gain range | Effect |
|---|---|---|---|
| Bass | 100 Hz | -12 to +12 dB | Boosts or cuts energy around the bass region. |
| Mid | 1,000 Hz | -12 to +12 dB | Boosts or cuts energy around the middle of the spectrum. |
| Treble | 10,000 Hz when permitted; otherwise 45 percent of the decoded sample rate | -12 to +12 dB | Boosts or cuts energy around the upper-frequency region. |
Each section uses Q=1, the tool’s broad, fixed-Q choice. Positive values boost energy around a center, while negative values cut it. Because the three sections are cascaded, several boosts can interact and raise the peak level. A moderate cut is often safer than stacking several strong boosts, especially if the source already contains rumble, sibilance, noise, or distortion.
Interpret peak scaling and output levels
After filtering, the tool measures the absolute peak across every processed sample and channel. If the raw peak exceeds 0.99, it applies one uniform safety scale to the entire result so the largest magnitude becomes 0.99. The interface reports the raw peak, output peak, and exact safety scale. This prevents the PCM encoder from chopping individual peaks, but it can reduce the overall level.
- A safety scale below 1 means the complete processed result was reduced to prevent clipping.
- Peak scaling is not loudness normalization and does not target LUFS, RMS, ReplayGain, or a streaming-platform specification.
- The preview and reported numbers are checks, not proof of a good mix.
Listen after applying any automatic-looking peak protection, because a uniform reduction may require a new comparison against the original at a matched perceived level.
Judge the result by listening at matched levels
Compare the original and processed files on the same playback system. Avoid choosing a setting only because the equalized version sounds louder. Strong boosts can also emphasize problems already present in the recording, so listen for noise, harshness, low-frequency rumble, and distortion rather than judging only by the apparent strength of bass or treble. The A/B listening-test guide provides a structured way to compare the two versions. If a small adjustment improves clarity without creating a new problem, keep it; if it does not, return to zero rather than compensating with more extreme settings.
Check file, browser, and format limits
Format support depends on the actual codec, not merely the file extension. Web Audio can decode selected MP3, WAV, M4A, AAC, Ogg, WebM, or FLAC files when the current browser and operating system support the codec. A familiar extension is not a guarantee because a container can hold a codec the browser cannot read. A decode failure produces an error, and no stale download is presented.
- Processing remains in the current browser tab. Lizely does not receive the source bytes, decoded samples, EQ settings, filename, or result.
- The browser’s Web Audio AudioBuffer model holds the decoded channel samples. Web Audio may resample while decoding, so the tool reports and writes the decoded sample rate rather than claiming that the source container rate survived unchanged.
- Float samples are converted to signed 16-bit little-endian PCM and interleaved by frame. The WAV header records the actual channel count, sample rate, byte rate, block alignment, bit depth, and complete data length.
- The export does not retain the original codec, bitrate, compression mode, tags, artwork, chapters, loop markers, or container-specific metadata.
Make the final method choice
Use the equalizer instead of manual editing for a bounded tonal change that three broad bands can express and for which a new PCM16 WAV is an acceptable deliverable. Move to manual or full-editor processing when you need adjustable Q, exact centers, automation, spectrum analysis, linear-phase work, loudness targets, dithering, codec selection, or preserved metadata. The equalizer’s role is deliberately narrow: disclosed three-band local processing, preview, peak safety, and a complete WAV export.
For a deeper look, see When to Use Audio Speed Changer Instead of Manual Edits.