Switching rates by switch: rate profiles in Betaflight

Betaflight does not store your rates just once but in rate profiles you can switch between: in the App, in the CLI, in the OSD menu or with a switch on your radio. Here is how many profiles there are, how a rate profile differs from a PID profile, how each way of switching works, how the OSD tells you which profile is active, and what goes wrong when the switch and the CLI mean different profiles. Checked against firmware and App 2026.6.2 and the Betaflight docs, as of November 15, 2026. Example values for profiles are left out on purpose.

Short answer

  • How many: four rate profiles and four PID profiles. The App counts 1 to 4, the CLI 0 to 3.
  • By switch: not in the Modes tab but in the Adjustments tab, with “Rate Profile Selection” and the whole range from 900 to 2100. A 3-position switch reaches profiles 1 to 3; at power-up the switch position decides.
  • In the CLI: rateprofile shows the active profile, rateprofile 2 switches to rate profile 3, save makes it stick. set lines always write to the active rate profile.
  • In the OSD: the element “Profile: PID and rate” shows, for example, “1-3”: PID profile 1 and rate profile 3.
  • fpvrates: the CLI block from the tuning pass starts its commands with rateprofile 2 and writes to rate profile 3. If profile selection sits on a switch, that switch has to be on profile 3, or you fly your old rates.

How many rate profiles are there?

In Betaflight 2026.6.2 there are four. It is fixed in the source code: CONTROL_RATE_PROFILE_COUNT 4, right next to PID_PROFILE_COUNT 4 (common_pre.h). The App docs say the same for the PID Tuning tab: “4 profiles that can be configured for Rate settings.” The number has not always been the same. In Betaflight 4.3, boards with more than 128 KB of flash had six rate profiles and smaller ones three; since 4.4 it has been four everywhere (common_pre.h in 4.3.2, in 4.4.0). Since Betaflight 2025.12 (MSP version 1.47, msp_protocol.h) the App asks the flight controller for the number and assumes four with older firmware (PidTuningTab.vue).

Keep the two ways of counting apart. The App labels the profiles “Rateprofile 1” to “Rateprofile 4”, the CLI counts from 0: rateprofile 0 is Rateprofile 1, rateprofile 3 is Rateprofile 4. Any other number gets RATE PROFILE OUTSIDE OF [0..3] from the CLI (cli.c). Out of the box rate profile 0, that is Rateprofile 1, is active (config.c).

Rate profile or PID profile?

Betaflight has two separate kinds of profile. The docs: “A Rate Profile is a set of Rate related settings. These profiles store the settings for Rate Type, RC Rate, Super Rate, Expo for Pitch, Roll, & Yaw.” The PID profile, on the other hand, holds PIDs, filters, feedforward and anti-gravity. The two used to be tied together, with each PID profile having rate profiles of its own; “Betaflight 3.2 broke this link, giving us independent Profiles and Rate Profiles.” So you pick the PID profile and the rate profile separately, and any combination works. The OSD shows both numbers with a hyphen, see OSD.

What exactly a rate profile holds is set in settings.c: every setting marked PROFILE_RATE_VALUE belongs to it (settings.c). The table lists them with the firmware default, which is the same in all four profiles (controlrate_profile.c). The default is the value after flashing, not a recommendation.

What a rate profile holds (Betaflight 2026.6.2, settings.c): firmware default, the same in all four profiles, not a recommendation
Setting (CLI)In the AppDefaultWhat it is
rateprofile_nameRate profile nameemptyName of 1 to 8 characters. Shown by the OSD element and in the OSD menu; without a name the OSD shows RATE_1 to RATE_4.
rates_typeRates TypeACTUALRates model: BETAFLIGHT, RACEFLIGHT, KISS, ACTUAL or QUICK. Decides what the three numbers per axis mean.
roll_rc_rate, pitch_rc_rate, yaw_rc_rateCenter Sensitivity (with Actual)7 (= 70 deg/s)Center: slope of the curve at the middle of the stick. The CLI stores the value divided by 10.
roll_srate, pitch_srate, yaw_srateMax Rate (with Actual)67 (= 670 deg/s)Max: turn rate at full stick. The CLI stores the value divided by 10.
roll_expo, pitch_expo, yaw_expoExpo (with Actual)0 (= 0.00)Expo: moves the bend of the curve outwards without changing center or max. The CLI stores the value times 100.
roll_rate_limit, pitch_rate_limit, yaw_rate_limitno field, CLI only; the App folds it into the “Max Vel [deg/s]” column1998Hard cap in deg/s applied after the rates curve, 200 to 1998.
quickrates_rc_expono field, CLI onlyOFFQuick type only: applies expo to the stick instead of the rate.
thr_mid, thr_expo, thr_hoverThrottle MID, Throttle EXPO, Hover Point50, 0, 50Throttle curve: mid, expo and hover point in percent. Part of the rate profile, not the PID profile.
throttle_limit_type, throttle_limit_percentThrottle Limit, Throttle Limit %OFF, 100Throttle cap: OFF, SCALE or CLIP and 25 to 100 percent.

Source: settings.c, controlrate_profile.c

Not in the rate profile: TPA. In Betaflight 4.3 it still belonged there; since 4.4 tpa_rate, tpa_breakpoint and tpa_mode live in the PID profile (settings.c in 2026.6.2, 4.3.2, 4.4.0). The Profiles docs page and the App’s help text at the profile selector still list TPA as part of the rate profile; both describe the old state. What the three rates values do is in Setting up Betaflight rates, the formula in Actual Rates explained.

Switching in the App

The profile selector sits in the “PID Tuning” tab, sub-tab “Rate Profile Settings”, top left at “Rateprofile”. The tab always opens on the “PID Profile Settings” sub-tab, and the “Profile” at the top left there is the PID profile. The docs: “The action of selecting a Rate Profile also activates that rate profile for current use.” In the code, the App sends the choice to the flight controller right away (PidTuningTab.vue, msp.c); the FC only keeps it in RAM, though, and it becomes permanent with “Save”. While you have unsaved values in the tab, the selector is locked: “Save” or “Refresh” first (PidTuningTab.vue).

A profile picked this way stays: “Also, when changing our Rate Profile that profile will remain the active Profile even over power cycles, except when using the AUX channel option.” The exception is the switch, see the next section. The other way round, the App follows when the radio changes the profile while it is connected: it polls the status every 250 ms, moves the selector and logs “Flight controller set Rateprofile: 3”; with unsaved changes it does not (PidTuningTab.vue).

By switch: the Adjustments tab

The Modes tab has no mode for rate profiles; the firmware has no box for it (msp_box.c). The switch goes through the adjustments: function 12 “Rate Profile Selection” (rc_adjustments.h), in the App in the “Adjustments” tab, which only shows in expert mode (sidebar_items.js). The click path with all fields, “when channel”, “is in range”, “then apply”, “via channel”, is step by step in Setting up Betaflight rates. This section is about what happens behind it.

Both channel fields get the same AUX channel, and the range is the whole travel from 900 to 2100. The adjustments docs explain why: “The Range Channel and the Adjustment Channel can be the same channel. This is useful when you want a single 3 Position switch to be dedicated to a single adjustment function regardless of other switch positions.” The range says when the adjustment is active at all; the “via channel” channel supplies the position. The firmware splits 900 to 2100 into three equally wide positions of 400 µs: below 1300 is position 1, 1300 to 1699 position 2, from 1700 position 3 (rc_adjustments.c). Position 1 selects rate profile 0, that is Rateprofile 1, position 2 Rateprofile 2, position 3 Rateprofile 3. A 3-position switch cannot reach Rateprofile 4.

The firmware only looks when the channel value changes. If the selected profile differs from the active one, it switches, writes an event to the blackbox log and has the beeper beep as often as the position number: once for Rateprofile 1, twice for 2, three times for 3 (rc_adjustments.c). If the switch is already on the active profile, nothing happens. At power-up the first channel value read counts as a change, which is why “When BetaFlight boots the active profile is selected by the position of the AUX channel.” Nothing gets saved in the process, and it doesn’t need to be: the switch sets the profile again at every start.

In the CLI the same thing is called adjrange. The docs on In-Flight Adjustments explain the fields: index 0 to 29, then a 0 (a placeholder from old versions), the range channel counted from 0 (AUX1 = 0), start and end of the range, the function (12), the position channel, center and scale (both 0 for profile selection). The docs’ example for a switch on AUX4 is in the rates guide.

With rate_6pos_switch = ON, a CLI-only setting (OFF by default), the firmware splits the same travel into six positions of 200 µs (settings.c, rc_adjustments.c). Then a 6-position switch or a pot reaches Rateprofile 4 as well. Positions 5 and 6, from 1700 µs, change nothing with four profiles, because the firmware only accepts profile numbers below 4; according to the code the beeper still counts five or six times (controlrate_profile.c). The docs table of adjustment functions still says “3 or 6 rate profiles”, which dates from the time of six profiles. This has not been tested on a quad; it is read from the code.

In the CLI: rateprofile, diff rates, diff all

In the “CLI” tab, rateprofile without a number shows the active rate profile, rateprofile 2 switches to Rateprofile 3 (cli.c). As in the App, the switch takes effect at once but only in RAM; save writes it to flash and reboots the FC. For the PID profile the command is profile.

Important for every block you paste: set lines for rates values write to the rate profile currently selected in the CLI, so without a line of their own to the active one (cli.c). With a rateprofile 2 before the set lines, they land in Rateprofile 3, which becomes active at the same time. Without that line you overwrite whichever profile happens to be active.

For looking and backing up, diff and dump take the options master, profile, rates, hardware and all (cli.c):

  • diff rates shows only the active rate profile, and of that only the values that differ from the default. The output starts with rateprofile N, followed by the set lines (cli.c). dump rates shows the same profile with all values.
  • diff all first goes through all four PID profiles, then all four rate profiles, each with its rateprofile line in front, then the battery profiles (battery_profile). At the end come the comment line # restore original rateprofile selection and below it rateprofile X with the profile that was active before, then the same for the battery profile and finally save (cli.c). Paste such a backup back and it also restores the rate profile that was active back then.

For backups the docs point to the CLI: “Currently creating a backup from the Betaflight App only backs up the active Profile and Rate Profile. So the best way to see and backup all Profiles is to use CLI.” How to save and restore diff all is in Betaflight backup with diff all.

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

By stick command: only in the code

For PID profiles the docs describe stick commands (throttle low, yaw left, plus roll or pitch). For rate profiles the source code has some too, but they are not in the docs (Controls, rc_controls.c): throttle high, yaw center, plus pitch forward for Rateprofile 1, pitch back for 2, roll right for 3, roll left for 4. This only works disarmed, after holding the position for at least 50 ms, and once per position. In angle or horizon mode the same stick positions trim the accelerometer instead. According to the code the switch triggers no beep, unlike the PID profile (config.c). Since the docs say nothing about it and this has not been checked on a quad: better use the App, the CLI or a switch, and check the result in the OSD.

Display in the OSD and the OSD menu

Two OSD elements show the rate profile. “Profile: PID and rate” (CLI osd_pidrate_profile_pos) writes PID profile and rate profile with a hyphen, both counted from 1: “1-3” means PID profile 1 and Rateprofile 3 (osd_elements.c, settings.c). “Profile: rate profile name” (osd_rate_profile_name_pos) shows the name of the active rate profile in capitals; without a name it says RATE_1 to RATE_4 (osd_elements.c). You turn both on in the App’s “OSD” tab under “Elements”. The pop-up the OSD uses to confirm other adjustments stays off for the rate profile, because it has this element of its own (rc_adjustments.c).

You can also switch in the OSD menu: main menu “PROFILE”, then the line “RATE PROF” with number and name (cms_menu_main.c, cms_menu_imu.c). The change applies at once; the docs: “Make sure to Save + Exit or Save + Reboot to save settings.”

Profile names and copying

Each rate profile can carry a name of 1 to 8 characters: rateprofile_name in the CLI, the field “Rate profile name” next to the profile selector in the App (settings.c, PidTuningTab.vue). The name shows in the OSD element and in the OSD menu next to the number. What you use names for is up to you; the App’s help text gives the type of flying as an example.

Copying only works in the App: the “Copy rateprofile” button at the top right of the Rate Profile Settings sub-tab, then pick the target profile. The dialog warns: “All values on the destination profile will be wiped and overwritten”. The firmware copies the whole profile as one block, so name, rates type and throttle curve too, at first only in RAM; you have to save afterwards (controlrate_profile.c, msp.c, PidTuningTab.vue). There is no CLI command for copying (command list in cli.c). In the CLI the detour via diff rates helps: its output starts with rateprofile N; change that number before pasting the text back and the values land in the other profile.

Common problems

  • The switch does not change anything, or only in the middle. When you enable a row, the App sets the range to 1300 to 1700 (useAdjustmentsData.js). With the same channel in both fields, the adjustment is then only active in the middle position and selects Rateprofile 2 there; low and high do nothing. Set the range to 900 to 2100. Also check in the “Receiver” tab that your switch really goes below 1300 and above 1700; the docs: “Range Start/End values should match the values sent by your receiver.”
  • The wrong profile is active after power-up. With a switch on profile selection, only the switch position counts at start, not the profile picked in the App or CLI. Put the switch on the profile you want to fly and check the OSD element.
  • The CLI block wrote to the wrong profile. Without a rateprofile line, set lines go to the active profile. Use diff all to see which profile got the values, and paste the block again with the right line.
  • The profile selector in the App is grayed out. There are unsaved changes in the tab. “Save” or “Refresh”, and the selector works again.
  • The beeper counts five or six times, the profile stays. rate_6pos_switch is ON and the switch is in position 5 or 6, for which there is no profile with four profiles. Use positions 1 to 4 or set rate_6pos_switch = OFF.
  • Rateprofile 4 cannot be reached with a 3-position switch. That is by design: three positions, three profiles. For profile 4 you need rate_6pos_switch with a 6-position switch or a pot, the App, the CLI or the OSD menu.
  • The App’s help text talks about three profiles and TPA. The text is older than the firmware. 2026.6.2 has four rate profiles, and TPA lives in the PID profile.

The fpvrates CLI block and your rate profile

The CLI block that the tuning pass builds from your blackbox log names the target quad as a comment in line 1, the profile in line 2, and starts the commands with rateprofile 2. So it writes to Rateprofile 3 in the App and makes it active; your other profiles stay as they are. The save at the end saves and reboots the FC. If you already use Rateprofile 3, change the line to a free profile before pasting: rateprofile 0 for Rateprofile 1 or rateprofile 1 for Rateprofile 2.

Three things go with it. First the backup: before pasting, type diff all and save the output (Betaflight backup with diff all); that gets you back to all four profiles at any time. Second the switch: if your profile selection sits on an AUX switch, the switch position decides at the next power-up, not the block. Put it on Rateprofile 3, or you fly the old rates and wonder why. The OSD element “Profile: PID and rate” shows you what applies. Third the log for the next round: the blackbox header holds the rates of the profile that was active when the log started (blackbox.c), and fpvrates reads your rates from exactly that header. So don’t switch profiles in the middle of a flight you want to analyze, or header and flight data won’t match. How to record logs: Blackbox logging: setup and downloading your log. If an old profile still has Betaflight rates (RC Rate, Super Rate, Expo), the converter turns them into Actual Rates.

The free check shows you on your own log whether your current profile suits your stick: five stick zones per axis and the steepness of your curve, no account, the file stays with you.

Sources

As of November 15, 2026, checked against Betaflight 2026.6.2 (firmware and App from 16 September 2026, the latest versions on that day) and the Betaflight docs (repository as of November 15, 2026):

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