Betaflight CLI Diff Checker
Paste a Betaflight diff all and see which lines a release rejects - unknown, renamed or out-of-range settings - and which only restate the default.
What it checks
Every set name = value line of the pasted diff all is read against the
release you pick, from the same files the settings reference
is built from:
- Not a setting of this release - the name is not in the release's
settings.c, so the CLI rejects the line with an invalid-name error. - Renamed - the name is gone, and the firmware's own pull request says
a new name is the same setting (for example
dshot_idle_valuebecamemotor_idlein 2025.12). Change the name and keep the value. - Out of range / not a value - a number outside the setting's minimum and maximum, a word that is not in its value list, or an array with the wrong number of entries.
- Equals the default - the line sets what the firmware already sets, so it can go. Board configs can change defaults, so on a board whose target sets this value differently the line still matters.
Other commands (aux, serial, resource, feature, map...) are
counted but not checked: they depend on the board, not on the release.
Moving a diff between releases
If the diff starts with its # Betaflight / ... 4.5.1 line, the checker
reads the version it came from and tells removed settings apart from
names that never existed. The per-release changes are listed in full on
the 4.4 → 4.5,
4.5 → 2025.12 and
2025.12 → 2026.6 pages.
Nothing is uploaded: the page downloads the release's params.json once and compares in your browser.