A parametric EQ for Windows that's pleasant to use, and honest about what you can actually hear.
A modern frontend for Equalizer APO, with built-in level-matched blind listening tests.
⬇ Download for Windows · Features · Getting started · Build from source
Equalizer APO is the best system-wide EQ engine on Windows, but editing it means text files or dated interfaces. Fletcher gives it a fast, modern editor, and adds the thing no EQ app has: a way to find out whether your tweak actually sounds different.
When two settings differ in loudness, the louder one almost always "sounds better," even when nothing else changed. Fletcher level-matches every comparison so loudness can't cheat, then lets you run blind ABX tests with real statistics. Was that 13 out of 16 skill, or luck? Fletcher tells you.
It's named for the Fletcher–Munson curves, the classic measurements of how our hearing depends on loudness.
Drag handles to set frequency and gain, scroll to change Q, or dial in exact values in the filter strip. Peaking, shelf, pass and notch filters are all supported. Preamp is calculated automatically so your EQ never clips, and changes are applied system-wide the instant you make them.
Click ⤢ on any filter for a larger editor: its own curve with your whole EQ behind it, sliders and exact values for frequency, gain and Q, and every filter type as a small preview drawn from your current settings. Hover a type to read what it does, click to switch. Pop it out into its own window and it follows whichever filter you select.
Tell Fletcher which headphone is on each output and the EQ graph can show what you're actually hearing: your headphone's measured response, the same response with your EQ applied, and a target to aim for, all lined up by shape. Drag a filter and the "with your EQ" line follows as you drag, so you can watch it meet the target.
- Your headphone: search 5,000+ measurements from AutoEQ, each naming who measured it and on which rig, or import your own measurement, with a file per ear if you have both.
- Targets: AutoEQ's Harman, diffuse-field and rig-specific targets, searchable, or your own: start from any target and turn bass, ear gain, treble and tilt with a live preview, or import a file. Each target shows which rig it was made for and that rig's ear response.
- Preference bounds: add a band around a target (its upper and lower edges) to see how far from it the sound can go and still be liked.
- Make a preset from it: New preset… › A target… fits your headphone to any target with AutoEQ's own method (checked against AutoEQ's published results, within 0.06 dB) and gives you an ordinary preset to tweak. With a measurement for each ear and per-ear editing on, each ear gets its own fit.
- Honest about its limits: treble above 6 kHz is shaded, because there a measurement depends more on how the headphone sits on your head than on the headphone itself. Smoothing from none to 1/3 octave or ERB.
Everything lives in the EQ view (the ⚙ at the top right of the EQ page), which also pops out into its own window. How each import works and what happens to the data: docs/IMPORTS.md.
Ears and headphones aren't perfectly symmetric. Turn on per-ear editing in Settings and every preset gets its own left and right curves, starting out identical. Edit one ear at a time, show both on one graph, or put them side by side, with the other ear shown faintly for reference. Each ear keeps its own undo history, and A/B comparisons and blind tests use both ears as they are.
Type a headphone name and pick from the AutoEQ database. The correction imports as your own preset, ready to tweak. You can also copy Peace's chain, import a REW filter file, or paste Equalizer APO filter lines. Every import, its file formats and what happens to the data: docs/IMPORTS.md.
Press Ctrl+Shift+A anywhere in Windows to flip between your EQ and flat. Both sides are matched in loudness, so you're comparing the sound, not the volume.
Every edit is saved to a history tree. Jump back to any version, branch off in a new direction, and see exactly how two versions differ. Unsure whether a change was worth it? Start a blind test between the two versions with one click.
- ABX tests: are A and B actually distinguishable to you?
- Blind preference tests: which one do you prefer when you don't know which is which?
- Test on whatever is playing system-wide, or on your own music clips.
- Exact p-values, plus optional adaptive tests that stop early once the answer is clear.
Import tracks from files or a link, scrub through them on a waveform and spectrogram, and mark the passages that reveal differences. A live FFT at the playhead shows the music's spectrum with your EQ overlaid, so you can see where it boosts and cuts. A built-in signal generator makes test tones and noise.
Measure your own hearing's equal-loudness profile per headphone, without a microphone, using timed listening comparisons.
Fletcher adds a single Include: fletcher.txt line to Equalizer APO's config and only ever writes its own file. It backs up your config before the first change, never edits files that belong to other tools like Peace, and never makes your audio suddenly louder.
- Install Equalizer APO and enable it for your headphones or speakers in its Configurator. Reboot if it asks.
- Download the latest installer from Releases and run it.
- Open Fletcher, search for your headphones, and pick a correction. Press Ctrl+Shift+A to hear the difference.
Note
The installer isn't code-signed yet, so Windows SmartScreen shows an "unknown publisher" warning. Click More info → Run anyway.
Fletcher is in early development (0.x). Expect rough edges, and please open an issue if something breaks.
You'll need Rust, Node.js and Windows 10 or 11 with Equalizer APO installed.
cd app
npm install
npm run tauri dev # run with hot reload
npm run tauri build # build the installersRun the checks with cargo test --workspace and cargo clippy --workspace --all-targets.
Fletcher is built with Tauri, Rust and React. For the architecture, design decisions and roadmap, start at CLAUDE.md and the docs folder.