Production guides · Meme Plugins · 1 November 2026
Use a high-pass filter when unwanted low-frequency material interferes with the source or the arrangement. Choose its cutoff and slope against the actual passage, then compare in the full mix. Keep the useful body of the instrument; a cleaner-looking spectrum is not a sufficient reason to remove it.
1. Identify what should disappear
Name the unwanted event: a low rumble between phrases, a sustained keyboard layer covering the bass, or a recording bump below the useful part. If you cannot identify a problem, keep the unfiltered version while you establish the balance.
iZotope’s high-pass guide explains both low-frequency cleanup and the loss of depth that can follow excessive filtering. It does not justify applying one cutoff to every instrument.
2. Separate cutoff from slope
A high-pass, also called a low-cut filter, attenuates the lower range while passing the higher range. The cutoff describes the transition region; the slope determines how steeply the attenuation develops. A normal finite-slope filter does not remove everything below one frequency instantly.
FabFilter’s band-control reference documents separate shape, frequency and slope controls. Use the equivalent controls in your EQ and check whether resonance or other shape settings also change the response.
Start conservatively, raise the cutoff until you hear useful weight being lost, then back it down and compare with bypass. This is a listening test, not a universal frequency prescription.
Example: a keyboard that supports two sections
Imagine a keyboard playing a low voicing in a sparse verse and the same part under bass in a chorus. This is a hypothetical comparison, not recorded or auditioned audio.
- Baseline: save the unfiltered part. Note what gives the verse its body and what becomes crowded in the chorus.
- First candidate: apply a gentle high-pass and compare the chorus with bass and drums present. Keep the keyboard’s fader fixed during this first test.
- Solo check: listen briefly to identify what the filter removed, then return to the arrangement. A thin solo sound can be acceptable in context, but it is not the goal.
- Verse check: hear the sparse section again. If the keyboard no longer supports it, lower the cutoff, compare a shelf, or use a section-specific change instead of sacrificing the whole part.
Write two separate observations: the chorus’s clarity and the verse’s weight. A useful compromise must serve both, unless you deliberately automate the treatment.
3. Check alternatives and related paths
If the useful low range only needs to be quieter, compare a low shelf rather than a more severe cutoff. If the issue occurs on one note, compare a local edit or dynamic treatment. First check the basic level balance and the roles of kick and bass.
For related microphones or parallel copies, compare the combination after filtering. A tonal change can also alter their relationship. Use the phase and polarity workflow if the sum becomes unexpectedly weak.
4. Verify the delivered result
Compare at a similar playback level, check the quieter section and reopen the export. Keep the smallest useful change. For congestion from several sources, follow the muddy-mix diagnosis.
Should everything except kick and bass be high-passed?
No. Decide from the actual source, its role and the arrangement. Low-frequency information can be part of an instrument’s useful character.