You’re mid-call, the other person’s voice buried under a thick, resonant low end, and turning down the master volume only made everything quieter. To reduce bass in Chrome, cut the 250 Hz and 500 Hz peaking bands. The 32 Hz shelf stays intact. A 10-band EQ with per-site memory sticks the cut to that one site.

Key takeaways

• Chrome’s sound settings expose per-tab volume and mute but no frequency-band control. A 10-band EQ extension is the path to a surgical cut.
• Per-site memory means the tuning you dial in for one podcast site applies only to that hostname.

Which Two Bands to Cut

The low-end rumble that buries a voice or a podcast host sits in two specific places on the frequency spectrum: the 250 Hz peaking band and the 500 Hz peaking band. These are not the 64 Hz band. They are the upper bass and lower midrange where room resonances and compressed production pile up.

Cutting both (negative gain on a peaking filter is attenuation) turns down the frequencies in those bands while leaving:

• The 32 Hz low shelf at 0 dB, so the fundamental body of music and low-end instrumentals survives.
• The 1000 Hz and above bands unchanged, so midrange clarity, presence, and brightness hold.
• Overall loudness stable, because you are removing energy from two narrow bands rather than turning down the whole signal.

The master-volume workaround dims everything at once. Treble and speech drop along with the bass. Two targeted band cuts avoid that trade-off entirely.

How the 10-Band Layout Works

SuperchargeAudio (free on Chrome and Microsoft Edge, no paid tier, live version 1.1.0 as of October 2026) builds its equalizer on the Web Audio API. The signal path runs through BiquadFilterNode objects inside an AudioContext, ending at the output destination. Each node is one of three filter types:

• Low shelf (32 Hz): boosts or attenuates everything below the centre frequency. Frequencies above are unchanged.
• High shelf (16 kHz): the mirror. Everything above the centre is boosted or attenuated.
• Peaking (eight bands at 64 / 125 / 250 / 500 / 1000 / 2000 / 4000 / 8000 Hz, Q 1.4): boosts or attenuates a narrow range around the centre. The Q parameter controls band width.

Each band’s gain is clamped to plus or minus 12 dB and defaults to 0 dB (flat). The Q of 1.4 on the peaking bands sets each one’s width.

Dialing In the Cut

Open the SuperchargeAudio popup. It lists every audible tab with a per-tab volume slider, a per-tab mute toggle, and a mute-all button. Open the 10-band EQ for the tab that is causing the problem.

You see ten sliders, one per band. Drag the 250 Hz slider down. Then the 500 Hz slider the same. The rest stay at 0. If the podcast still feels boxy after the first pass, lower both a little further. Do not push the cut too far without re-listening, because on two adjacent bands you start hollowing out the low-mid region that gives voice its body.

Ten built-in presets ship with the extension: Flat, Bass Boost, Vocal/Voice, Treble, Loudness, Rock, Pop, Electronic, Acoustic, and Small Speakers. You can also save up to 24 custom presets; names are trimmed and capped at 32 characters, and a name matching a built-in preset is rejected. Call yours “Podcast” and load it next time.

The popup has a global switch. Flipping it off returns every open tab to passthrough (100% volume, flat EQ). Toggle it on and off while the podcast plays to A/B test whether the cut is doing what you want.

Per-Site Memory

Volume, EQ, and stereo width are remembered per hostname. The cut you dial in for podcastexample.com sticks for that site only. A different podcast on a different domain still runs flat until you tune it.

chrome:// pages, browser settings, and the new-tab page cannot be boosted directly, but the other tabs and the default EQ still apply there. On regular web pages the band cut applies, but DRM-protected content cannot be processed, except on spotify.com.

The extension sends no usage analytics or telemetry. Nothing about what you are listening to or how you are tuning it goes to a server or a third-party service.

If the Problem Is Loudness, Not Tone

If after cutting the 250 and 500 Hz bands the sound still feels off, the issue is likely in a different range. A harsh, sibilant quality points at the 4000 or 8000 Hz bands. A tinny, lifeless feeling usually means the 125 Hz band was accidentally turned down. The 10-band layout lets you isolate each region and work through them one at a time.

If your real complaint is that the overall volume is too low rather than that the tone is muddy, the band cuts will not help. The per-tab volume boost (0 to 600%, 100% is passthrough) on the same extension handles that side. The slider has 70 detents: 1% steps to 9, then 10% steps. The Chrome audio too quiet guide covers the volume-specific walkthrough.

If the low end on one particular site keeps coming back, the per-site memory is your safety net. The cut you set holds the next time you visit that hostname. You do not have to re-dial it.