EQ Conflict Detector
When two tracks both own the same frequency band, your listener hears a smear instead of two distinct elements. Drop a 5-band EQ curve for each of two tracks and this tool overlays them, shades the conflict zones where both are boosting the same band or pushing against each other, and recommends a give-and-take split.
Two EQs to compare
Conflict heat-map
20 Hz – 20 kHz · ±18 dBShaded red bands = both tracks are boosting in this range. Yellow = one boost, one cut. Cyan / fuchsia curves = each track's full EQ shape.
Per-band energy share
Recommended give-and-take
How to use
- Type a label for each track (vocal lead, synth pad, bass, kick, etc.) so you remember what the visualisation is comparing.
- For each of the 5 bands per track, choose whether it's a shelf or a bell, set its centre frequency, its gain in dB and (for bells) its Q width.
- Watch the conflict heat-map turn red where both tracks are boosting the same band — those zones are the worst offenders.
- Read the per-band energy share: which track currently owns each part of the spectrum.
- Apply the give-and-take suggestions to one or both tracks' EQs and re-check.
How to read the result
- Red band: both tracks are boosting at the same time. This is a "fight" zone — usually you assign one of them to cut slightly so each element gets room.
- Yellow / orange band: one boosts, one cuts — fine if intentional (e.g. a high-pass on the vocal lets the synth own the lows), but watch for unintentional masking.
- Cyan curve is Track A's EQ. Fuchsia curve is Track B's. The dashed zero dB line is the un-EQ'd reference.
- Per-band energy share — this is approximate, not a real measurement, but it tells you whether you've accidentally handed one band to one track.
- Start with the lowest frequency row and work upward — sub / low end is where EQ mistakes cause the most obvious "muddy" outcomes on a small speaker.
Limitations
This is a 5-band approximation, not a spectrum analyser. Real parametric EQs have 4–8 bands; this tool models 5. The curves shown here are mathematical functions, not what you'd see on a spectrum analyser (which depends on the actual audio).
We do not know the tracks' actual frequency content. A vocal track doesn't have a +4 dB bump at 60 Hz because you want the kick — but this tool can't see that. It only sees what you've told it.
"Conflict" is a starting point, not a verdict. Sometimes two elements are supposed to occupy the same band (a pad and a vocal both at 1 kHz during a melodic moment). Trust your ears over the heat map.
Masking is loudness-dependent. Real masking depends on the relative level of the two tracks at the same moment in time, not just their EQ curves. This tool gives a static "where would the fights happen?" view.