Why compare logical settings instead of lines?
A Betaflight export is executable CLI text, not a stable line-oriented data format. diff all includes only non-default configuration across master, PID-profile, and rate-profile scopes, while firmware builds can add, remove, rename, or reorder settings. This tool therefore keys set values by name and profile context, and indexed command families by their slot or resource identity. Source line numbers remain visible so every result can be checked against the original.
The official Profiles documentation explains that PID profiles and rate profiles are independent scopes and recommends diff all or dump all to include all of them. A p_roll value in PID profile 0 is not merged with the same name in profile 1.
Firmware version is part of the configuration
Betaflight’s CLI documentation explicitly warns against pasting a diff or dump into a different firmware version because variable names and ranges change. This comparator places firmware, MSP API, target, board, and manufacturer evidence above the setting table and raises stronger findings for version, target, or board differences.
The grouping and explanations are review aids, not a version-aware settings database. They do not validate a value against the source build, translate renamed variables, know custom defaults, or establish that a removed line should be reset. Use get <name>, the CLI help, and the documentation for the exact installed build.
A safe review sequence
- Confirm both version headers, targets, board names, and manufacturer IDs.
- Review hardware, port, receiver, mode, motor, and failsafe changes before tuning differences.
- Check every profile scope, not only the currently active profile.
- Verify intended changes in the matching Betaflight App or CLI without blindly pasting the report.
- Bench-test with propellers removed, confirm receiver and failsafe behavior, then use controlled flight tests and Blackbox evidence for tune changes.
This page does not judge airworthiness, generate a migration script, recommend PIDs or filters, verify wiring, arm a craft, or replace the matching Configurator and manufacturer documentation.
Frequently asked questions
Can I compare dump all with diff all?
The parser can index both, but the result is asymmetric: a dump usually contains defaults while a diff omits them. The page flags inputs without a # diff marker and never calls one-sided lines effective changes without that qualification.
Why is a missing line not shown as “reset to default”?
Because the other export does not state a default value. Defaults depend on firmware, target, build options, and custom defaults. “Present only” is the strongest claim supported by the files.
Does the tool understand every Betaflight command?
No. It has a bounded index of common configuration command families and reports unindexed non-comment lines. New or target-specific commands must be reviewed in the source version’s CLI help.
Can the report be pasted back into Betaflight?
No. It is evidence for review, not executable migration output. Values shown as removed, profile context, ordering, defaults, firmware compatibility, and save behavior all need explicit decisions.