Does Betaflight have autotune?
Short answer: not in the firmware. Betaflight does not tune your PIDs by itself in flight. Since Betaflight App 2026.6, though, there is an experimental “Autotune” tab that analyzes a special blackbox log and suggests values for the tuning sliders. Here is what it needs, what else Betaflight offers for tuning, which tools analyze blackbox logs and what other firmwares can do. Checked against the source code and docs of Betaflight 2026.6.2.
Short answer
- Firmware: no autotune. In the Betaflight 2026.6.2 source code the word only shows up in leftovers: three blackbox events marked “UNUSED” (
blackbox.h) and the comment “old autotune” on the flight mode bit that chirp mode uses today (runtime_config.h). - App: Betaflight App 2026.6 has an “Autotune” tab. According to the release notes it is experimental and only visible in expert mode. It analyzes a log and suggests values; it does not change anything in flight.
- In the past: Cleanflight, which Betaflight grew out of, had an autotune in 2014 and 2015, and Betaflight 2.x had G-Tune. Neither has been part of Betaflight since 3.0 (September 2016).
- What helps: defaults or a preset, fine-tuning with the tuning sliders, and tools that analyze your blackbox log. The overview is in the table below.
The Autotune tab in the Betaflight App
The 2026.6 release notes say: “A new Autotune tab provides a file-based workflow for analysing flight-controller tuning from a blackbox log.” The tab reads a log with a chirp test flight, works out the frequency response and recommends values for the tuning sliders (Simplified Tuning). With the quad connected, the “Apply Gains” button writes the values to the flight controller (FC) and saves them (useAutotune.js). For the analysis alone you don’t need a connection.
What the tab needs, according to the release notes, the docs and the App’s own texts:
- Firmware with chirp: chirp mode exists since Betaflight 2025.12 as the CHIRP build option, which is not selected by default. The build options docs describe it like this: “Adds a chirp signal generator flight mode for system identification and tuning analysis.” You select it in the Firmware Flasher tab before you flash.
- CHIRP mode: it is in the list of modes and goes on a switch in the Modes tab.
- A log with chirp data: according to the App, the log must be recorded with
debug_mode = CHIRPand chirp mode must have been active (messages.json). How to set up blackbox logging is in Blackbox logging: setup and downloading your log. - Expert mode: only then does the sidebar show the tab (
sidebar_items.js); switch it on in the options under “Enable Expert Mode”.
To put it in context: with ArduPilot (further down) the flight controller adjusts the values in flight by itself. With Betaflight, chirp mode only produces the test signal in flight; the analysis happens afterwards in the App. The tab is marked experimental, and on November 12, 2026 it had no docs page of its own, only the section in the release notes. The docs don’t describe how the test flight works, so there are no instructions for it here either. The release notes also list a fix so that the tab never recommends less D-term filtering than currently configured, explicitly as protection against a flyaway.
What Betaflight offers instead of autotune
The Betaflight 4.3 tuning notes, which introduced presets and today’s sliders, recommend a simple path: “4.3 should fly really well on defaults. Start there, or with a Preset that suits your purposes.” The same page says the defaults were originally made for 5-inch freestyle quads and that presets exist for other builds.
- Defaults: every quad flies with them after flashing. In 2026.6.2 the rates default to Actual Rates 70/670/0.00, that is center, max and expo (
controlrate_profile.c). How to adapt your rates is in Setting up Betaflight rates. - Presets: according to the docs, short CLI snippets that the App applies to your configuration, with whole tunes in the TUNE category. Presets with the status OFFICIAL are made or supported by the Betaflight team, COMMUNITY presets come from other pilots. The 4.3 tuning notes advise backing up your configuration before saving a preset, because saved changes can’t easily be undone.
- Tuning sliders: in the PID Tuning tab a few sliders set the PIDs indirectly instead of every number on its own (PID Tuning Tab docs). In 2026.6.2 they are on by default (
pid.c). These are exactly the sliders the Autotune tab suggests values for.
Comparison: what is there instead of autotune?
What each option sets, from which data and what it costs, as of November 12, 2026. The tools are described the way their own website or repository describes them. On purpose, there are no PID or filter values here.
| Tool or feature | What it sets | From which data | Cost | Source |
|---|---|---|---|---|
| Built into Betaflight | ||||
| Defaults | PIDs, filters and rates out of the box; rates 70/670/0.00 | none, the same for every quad | free | 4.3 Tuning Notes |
| Presets (Presets tab) | ready-made CLI snippets, including whole tunes for a quad and flying style | none: you pick by hardware and flying style | free | Presets Tab |
| Tuning sliders (PID Tuning tab) | PIDs and filters through a few sliders instead of single values | what you notice when flying | free | PID Tuning Tab |
| Autotune tab (App 2026.6, experimental) | suggests slider values, writes them on request | log of a chirp test flight, needs the CHIRP build option | free | Release Notes 2026.6 |
| Blackbox Viewer (formerly Blackbox Explorer) | nothing: shows traces and frequency spectra | any blackbox log | free | README |
| Separate tools for blackbox logs | ||||
| PIDtoolbox | analysis for PID tuning, as the maker describes it | blackbox log | Patreon, from €4 a month | ptblabs.ca, Patreon |
| Plasmatree PID-Analyzer | nothing: calculates the step response | blackbox log | free, last release from 2018 | GitHub |
| FPVtune | suggests PIDs, filters and feedforward as CLI | blackbox log from Betaflight 4.5 on, uploaded | US$9.90 per tune or a subscription | fpvtune.com |
| fpvrates | rates only: measures how you use the stick; no PIDs, no filters | blackbox log, the file stays with you | free check €0, suggestion with a Tuning Pass from €19 | Pricing |
How well do your rates fit your stick? The free check measures it on your blackbox log. No account, the file stays with you.
No log yet? See a real example · Turn on logging, with pictures
For your next flying day
- Betaflight App, Blackbox tab: logging device onboard flash or SD card, logging rate 1 kHz
- RC Commands, Setpoint and Gyro on, then “Save and reboot”
- Fly 3 to 5 packs of normal acro
- Then get the log off the quad and drop it into the free check
Tools that analyze blackbox logs
A blackbox log records what you asked for with the stick (setpoint) and what the quad did (gyro). These tools work from that:
- Blackbox Viewer: the former Blackbox Explorer, a tab of the Betaflight App since 2026.6. It shows the traces moment by moment and has a spectrum analyser that shows frequencies, also against throttle or motor RPM. It doesn’t suggest values. The standalone site is frozen, and according to the README the old repository will be archived on December 1, 2026. How to use it: How to use Blackbox Explorer.
- PIDtoolbox: analysis software for PID tuning of multirotors, as its maker PTB Labs describes it. pidtoolbox.com links to Patreon, where the standard version starts at €4 a month and the PRO version at €5.50 a month, plus tax (as of November 12, 2026). The former GitHub repository is no longer available.
- Plasmatree PID-Analyzer: according to its README it reads Betaflight logs and calculates the step response, that is how the quad follows a stick command. Free on GitHub; the last release, 0.52, is from June 2018.
- FPVtune: a web service. You upload your log (Betaflight 4.5 or newer) and, according to fpvtune.com, get PID, filter and feedforward values as CLI commands, calculated by a neural network. One tune costs US$9.90 according to the pricing page, and there are subscriptions. Its Crash Analyzer and Motor Health Check are free.
The descriptions come from the makers. fpvrates compares what the tools do by their own account, not how well they do it.
Autotune in INAV and ArduPilot
Other firmwares have an autotune that adjusts values by itself in flight:
- INAV: for airplanes only (fixed wing). In INAV 9.1.0 it tunes feedforward and rates according to the docs, never P or I. In the source code only the airplane autotune is switched on (
common.h). - ArduPilot Copter: according to the docs, AutoTune tunes Stabilize P, Rate P and D and the maximum rotational accelerations. The copter must already fly roughly in AltHold, because AutoTune twitches it on the roll and pitch axes. The docs warn that AutoTune can’t always find a good tune and may produce gains that make the copter unflyable and crash.
- ArduPilot Plane: according to the docs, AUTOTUNE is a flight mode like FBWA that learns the roll and pitch values from your attitude changes.
For a Betaflight quad, that would mean changing the firmware.
Did Betaflight ever have autotune?
Its predecessors did. Betaflight was forked from Cleanflight in 2015, as the Betaflight docs say. The code history shows:
- 2014: autotune in Cleanflight. It only ran in ANGLE and HORIZON modes, and the algorithm came from BradWii. Its own docs called it experimental and advised against using it. On October 6, 2015 it was removed with the commit “Delete autotune.”
- 2015 to 2016: G-Tune. Taken over from the Harakiri firmware, it only adjusted the P values in acro mode (docs). In Betaflight 2.4.0 it was switched on for 15 of 18 boards. After the commit “Remove gtune on a gentle way” in February 2016 it was 5 from 2.5.0 on, and none in Betaflight 3.0.
The flight mode bit that was still called AUTOTUNE_MODE in 2015 is used by chirp mode today. After that, the commit history has no autotune commits for ten years; only in 2026 came the debug channels for the App’s Autotune tab.
What fpvrates measures and what it doesn’t
fpvrates does no autotune and sets neither PIDs nor filters, not even as a suggestion. fpvrates measures your rates from your blackbox log: how much stick travel you really use, where your normal flying ends and how steep your curve gets towards the edge. With a Tuning Pass you get a rates suggestion from that. For PIDs and filters, use the tools from the table.
If your quad flies twitchy, first find out whether it is the rates, the radio, the props or the PIDs: Twitchy quad: causes and fixes. How to get the log: Blackbox logging: setup and downloading your log.
Sources
As of November 12, 2026, checked against Betaflight 2026.6.2 (firmware and App of September 16, 2026, the latest versions on that day):
- Betaflight docs: 2026.6 Release Notes, Build Options, Modes, 4.3 Tuning Notes, Presets Tab, PID Tuning Tab, About Betaflight.
- Firmware source code:
blackbox.h,runtime_config.h,msp_build_info.c,controlrate_profile.c,pid.c. - App source code:
sidebar_items.js,useAutotune.js,locales/en/messages.json. - History: Autotune.md (2015), commit “Delete autotune.”, Gtune.md (2.2.0), commit “Remove gtune on a gentle way”.
- Other firmwares: INAV 9.1.0, Autotune - fixedwing, ArduPilot Copter, AutoTune, ArduPilot Plane, AUTOTUNE.
- Tools: Blackbox Explorer, README, PTB Labs, PIDtoolbox on Patreon, Plasmatree PID-Analyzer, FPVtune, FPVtune pricing.
Last updated: Nov 14, 2026 · checked with Betaflight 2026.6.2