Betaflight backup: how to save and restore diff all

Before you change your rates, apply a preset or flash new firmware, back up your settings. One command in the CLI tab of the Betaflight App does it: diff all. Here is how to save the output to a file and restore it, when dump fits better and why you shouldn’t paste everything back after a firmware update. Checked against the source code of Betaflight 2026.6.2 (firmware and App) and the Betaflight docs, as of November 12, 2026.

Back up in four steps

The setup guide in the Betaflight docs puts it simply: “Before making any changes, back up your current configuration.” In the Betaflight App 2026.6:

  1. Connect: plug the quad into your computer with a USB data cable, click “Connect” in the App, battery off. The App itself recommends making sure that no battery is connected before entering commands in the CLI, because some commands can spin up the motors.
  2. Clear the window: open the CLI tab and click “Clear output history” at the bottom. “Save to File” takes everything in the window (useCli.js), so this way the file holds only the backup.
  3. Send the command: type diff all and press Enter. The output is complete when it ends with save.
  4. Save: click “Save to File”. The App suggests a .txt file whose name contains your quad’s name (craft name), the date and the time. Or click “Copy to clipboard” and paste it into a text file.
# Target quad: <name of your quad>
diff all

Everything after # is a comment that Betaflight ignores (cli.c). Backing up changes nothing. When you click “Disconnect” or switch tabs afterwards, the App sends exit and the flight controller (FC) reboots; nothing is lost. Keep a second copy of the file somewhere else, for example on a USB stick.

What’s in the file

diff all only lists what differs from the defaults, but for every profile. The output is a ready-made restore script. Its structure according to the source code (cli.c, function printConfig):

Line in the fileWhat it does
# version, followed by # Betaflight / … MSP API: …A comment with the firmware version, target, build date and MSP version. The version command prints the same line.
batch startStarts a batch: Betaflight remembers every error until the save at the end.
defaults nosaveResets everything to defaults, without saving and without a reboot. Only your changes are added after that.
board_name …, manufacturer_id …, mcu_id …Board and manufacturer (only if set) and the ID of the processor. mcu_id only displays it and changes nothing.
# name: …Your quad’s name (craft name) as a comment.
feature …, serial …, aux …, set … = …Everything outside the profiles, such as ports, modes and OSD, each only where it differs from the default.
profile … with set … = …Every PID profile with its changes, then your active profile again. The CLI counts from 0: profile 0 is profile 1 in the App.
rateprofile …, battery_profile …Every rate profile and every battery profile, then your active selection again.
saveSaves and reboots the FC.

diff or dump? When to use which

The CLI help describes them like this (cli.c): diff lists “configuration changes from default”, dump the whole configuration.

CommandWhat’s in itUse it for
diff allChanges from the defaults, every PID, rate and battery profileThe backup. On restore it resets everything first and ends with save.
diffChanges, active profiles onlyA quick look at what you changed. Resets nothing, ends without save.
dump allEvery value, defaults included, every profileComparing two states line by line. Ends with save but resets nothing.
dumpEvery value, active profiles onlyLike dump all, shorter. Ends without save.
diff ratesThe active rate profile onlyLooking up your rates.

For a backup, use diff all: short, with every profile and already built as a script. diff and dump take two extra options: defaults (for example diff all defaults) writes the default value as a comment above every changed line, bare leaves out batch, defaults nosave, save and mcu_id.

Restore on the same firmware version

  1. Check the version: type version in the CLI tab. The version number must be the same as in the version line at the top of your file. If it isn’t, read the section on firmware updates first.
  2. Load the file: click “Load from file” and pick the .txt file. The App first shows the content in a preview: “Note: You can review and edit commands before execution.” “Execute” sends it to the FC line by line. Or copy the content into the input field and press Enter.
  3. Let it run: defaults nosave resets, your lines are added, save saves and reboots.
  4. Check: reconnect and go through the tabs, especially receiver, modes and motors. If the quad won’t arm afterwards, status shows the reason; every reason is listed in Quad won’t arm: all arming flags.
# Target quad: <name of your quad>
# 1. Show the version and compare it with the version line at the top of your file
version
# 2. Then paste the whole content of your file and press Enter.
#    It starts with batch start and ends with save.

When a line doesn’t fit

The CLI shows every error as a line with ###ERROR IN …###: INVALID NAME for a setting that doesn’t exist, INVALID VALUE with the allowed range for a value outside it, UNKNOWN COMMAND, TRY 'HELP' for an unknown command (cli.c). Because diff all runs as a batch, the save at the end then doesn’t save: Betaflight reports ERRORS WERE DETECTED - PLEASE REVIEW BEFORE CONTINUING and PLEASE FIX ERRORS THEN 'SAVE' (cli.c).

At that point the FC has taken half of the file but saved nothing. Type exit: it reboots with your old settings (“leaving CLI mode, unsaved changes lost”). Then fix or delete the line with the error in the file and load it again.

A file from a different flight controller

Here the board_name line often fails right away: if the new FC has a different board name stored, Betaflight reports BOARD_NAME CANNOT BE CHANGED and the save at the end won’t go through (cli.c). So set up a new FC the same way as after an update: by hand, with the old file as a cheat sheet, taking over only single parts.

How well do your rates fit your stick? The free check measures it on your blackbox log. No account, the file stays with you.

Check my log for free

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

After a firmware update: don’t paste everything blindly

The CLI page of the docs is clear: “Never paste a diff or dump from one firmware version into a different version — variable names and valid ranges change between releases and will silently corrupt the configuration.” The Firmware Flasher page is softer: “Generally, we recommend full manual re-configuration. When the flash is from the same point version, usually it's OK to import a saved Preset, or paste a Diff. Parts of a diff can also be selectively pasted into the CLI, eg the VTX Table, or the modes and aux settings.”

Two examples of why. Betaflight 2026.6 dropped the setting pos_hold_without_mag, which 2025.12 still had; according to the 2026.6 release notes, a saved diff that contains it is rejected on load, and the CLI reports INVALID NAME. A diff from Betaflight before 4.3 gets dangerous with rates. The 4.3 docs warn: “If a user pastes in their Betaflight rates numbers from say a 'diff all', the rates_type information will not be included. The result will be that Actual Rates will be active, but with Betaflight CLI numbers. The quad will be un-flyable!”

How to handle an update:

  1. Back up first as above. If the FC is connected normally over USB when you flash, the App 2026.6 makes its own backup with diff all by default and asks where to save it; if you cancel, it doesn’t flash (useFirmwareFlashing.js). How the flashing itself works is in How to flash and update Betaflight firmware.
  2. Same version: restore the file as above.
  3. New version: set things up by hand in the tabs, with the old file open next to it. Parts the docs mention, such as the modes (aux) or the VTX table (vtxtable), you paste into the CLI on their own. With batch start in front, the save only saves if no line had an error.
  4. Rates: enter them again in the App as described in Setting up Betaflight rates. If you copy them from the file anyway, take the rates_type line along if it’s there.
  5. Before the first flight: “After flashing, always check that every setting is 'as it should be', before test flying.”
# Target quad: <name of your quad>
batch start
# paste the lines from your old file that start with aux here
save

What the Betaflight App 2026.6 backs up by itself

  • Presets tab: “Save backup” takes a diff all and saves it as a .txt file, “Load backup” applies such a file like a preset. If there are errors, the App lists the failed commands (“Configuration has been applied with CLI errors”) and asks: “Cancel” (nothing is saved) or “Save anyway”. Both need firmware 4.5.4 or newer (PresetsTab.vue). Before you apply presets, the App itself warns that without a backup there is no way to return to your previous configuration.
  • Firmware Flasher: the backup before flashing is on by default; if there is one, the App offers “Restore Backup” after a successful flash. The setting “Create a backup before flashing new target” sits in the advanced options, which the App only shows in expert mode.
  • Backups tab: backups in a Betaflight account in the cloud, with “Restore” to write one back. The tab only exists while you are logged in to the App (2026.6 release notes).

The CLI route needs no account, the file is readable text, and it also works with firmware older than 4.5.4.

Before you change your rates: back up first

You change rates in the App or with a CLI block. The CLI block fpvrates gives you with the tuning pass writes to rate profile 3 in the App and leaves your other rate profiles as they are. Back up anyway: diff all, save the file, then paste. That way you can always go back to your old settings. Whether your current rates fit how you use the stick, the free check shows you on your own blackbox log; how to record and download the log is in Blackbox logging: setup and downloading your log.

Sources

As of November 12, 2026, checked against Betaflight 2026.6.2 (firmware and App released September 16, 2026, the latest versions on that day):

Last updated: Nov 12, 2026 · checked with Betaflight 2026.6.2