Betaflight Autotune in 2026.6: how it works and how it compares
Betaflight 2026.6 added an experimental Autotune tab to the Betaflight app. You fly a chirp test, a hover during which Betaflight sweeps a test signal through a range of frequencies. The tab reads the blackbox log of that flight, measures how the quad responds at each frequency, and recommends simplified tuning slider values. It is free, built in, and marked experimental. It needs 2026.6 firmware and Expert Mode in the app.
How Betaflight Autotune works
- Set up the chirp test. Assign the chirp mode to a switch, set the debug mode the Autotune instructions ask for, and log at a high rate, about 2 kHz.
- Fly it. Take off, hover steadily on a calm day, and switch the chirp on. The quad excites itself across the frequency range while you hold the hover.
- Analyse. Open the Autotune tab and import the log. It computes the closed-loop frequency response and looks at bandwidth, phase margin, the resonant peak and the noise floor.
- Apply. It recommends slider values. With the flight controller connected, Apply Gains writes them over USB.
The analysis runs in the app without a flight controller connected, so you can study a log anywhere. Since a 2026.6 fix, it never recommends less D-term filtering than you already have.
What the chirp test is good at
A chirp is a controlled measurement. The input is known and covers the whole frequency range, so the frequency response it produces is cleaner than anything you can get from stick inputs. Phase margin and bandwidth come straight from that response, and they describe how close the loop is to oscillating. Control engineers tune with these numbers, and the chirp gives you them directly.
Its limits today
- Experimental. Betaflight labels it experimental and keeps it behind Expert Mode. Early reviews of the development builds advised checking its suggestions before flying them.
- 2026.6 and newer only. Quads on 4.3, 4.4, 4.5 or 2025.12 need a firmware update first. On boards with an IIM-42652 gyro that update also means re-tuning from scratch, because 2026.6 corrected that gyro’s scale. See what changed in 2025.12 and 2026.6.
- Sliders, not every setting. It works through the simplified tuning sliders. Settings outside them, such as I-term relax, anti-gravity, TPA, the dynamic notch or the RPM filter, stay as they are.
- A hover, not real flying. The chirp measures the quad holding a hover. Propwash, punch-outs and full-throttle behaviour aren’t part of the test, so they aren’t part of the result either.
- You judge the result. It gives one recommendation from one flight. Deciding whether it flies better, and what to do if it doesn’t, is up to you.
Betaflight Autotune compared with FPV PID Tune
| Betaflight Autotune | FPV PID Tune | |
|---|---|---|
| Firmware | 2026.6 and newer | 4.3 to 2026.6 |
| Test flight | A chirp test during a hover | A normal test pack in rounds 1 and 2 (throttle sweep, snap rolls and flips, yaw spins, split-S and punch-outs), then your own flying |
| What it measures | Frequency response: bandwidth, phase margin, resonant peak, noise floor | Step response per axis, noise spectrum against throttle, filter delay, motor temperature |
| What it can change | Simplified tuning slider values | Filters, P and D, feedforward, I-term relax, anti-gravity, TPA, in raw values or slider values to match your setup |
| How many flights | One analysis per log | Four rounds, one battery each, with each round checked against the last |
| Safety | Never less D-term filtering than you had | Backup before the first write, fixed limits on every value, read-back after Apply, one-click Undo |
| Where it runs | The Betaflight app | Desktop Chrome or Edge |
| Price | Free | $10 per quad, within 30 days |
Which one to use
Use Autotune if you’re on 2026.6, comfortable with Expert Mode and the CLI, and you want a direct frequency-response measurement without paying. Treat its numbers as a recommendation to check. Make sure you can put your old values back.
Use FPV PID Tune if your quad is on an older Betaflight version, if you want the filters, feedforward, I-term and TPA tuned as well as the sliders, or if you want each change checked against a follow-up flight. It works from the moves you already fly, so there is no chirp mode to set up.
Both start from the same place: a sound quad, a blackbox log and calm air. If you’re new to reading logs, start with how to read a step response and blackbox logging for tuning. The tuning tools comparison puts Autotune next to PIDtoolbox and the other options.
How FPV PID Tune handles it
FPV PID Tune doesn’t use a chirp test. It reads a normal flight in your browser, the two-minute test pack in rounds 1 and 2 and your own flying after that, and measures the step response, noise and filter delay. It then tunes in four rounds: filters, P and D, feedforward, I-term and TPA, then fine-tuning. Every value stays inside fixed safety limits and is read back from the quad after Apply.