How to Check Installed Presets in Betaflight

So you flashed your flight controller. You loaded Betaflight. Everything works. Or at least… you hope it does. Now you’re wondering: How do I check which presets are installed? Great question. Because presets can completely change how your quad flies.

If you are new to Betaflight, don’t worry. This guide keeps things simple. Short sentences. Clear steps. No fluff. Let’s get into it.

TL;DR: Open Betaflight Configurator and connect your quad. Go to the Presets tab to see available presets, and check CLI or the Backup file to confirm what was applied. You can also compare current settings against stock defaults to verify changes. Always save a backup before making changes.


What Are Presets in Betaflight?

Presets are ready-made setting packages.

They change:

  • PIDs
  • Filters
  • Rates
  • OSD layout
  • Features like RPM filtering

Think of them as “performance profiles.” Instead of tweaking 50+ settings manually, you apply one preset. Boom. Done.

But here’s the catch.

Once applied, Betaflight does not scream: “Preset Installed!” forever. So if you forget what you installed, you need a way to check.


Method 1: Check the Presets Tab

This is the easiest method.

Step 1: Connect Your Quad

  • Plug in your USB cable
  • Open Betaflight Configurator
  • Click Connect
Image not found in postmeta

Step 2: Open the Presets Tab

On the left side menu, click Presets.

You will see available presets grouped by:

  • Recommended
  • Community
  • Manufacturer

If a preset was recently applied in your current session, it may show as applied. But here’s the important part:

The Presets tab does not show a permanent “installed list.”

That surprises many people.

So if you applied a preset last week and forgot which one, the tab alone won’t always tell you.


Method 2: Compare Current Settings to Default

This method works every time.

Presets change specific values. If you know what those values are, you can check if they’re active.

How to Do It

  1. Go to the PID Tuning tab.
  2. Look at P, I, and D numbers.
  3. Compare them with Betaflight default values.

If the numbers are very different, a preset was likely applied.

For example:

  • Default Master Multiplier: 1.0
  • Preset may change it to 1.3 or higher

You can also check:

  • Filter Settings
  • Rates Profiles
  • Dynamic Idle

If those match a known preset configuration, then yes, it’s installed.

This method takes a little detective work. But it’s reliable.


Method 3: Use the CLI (Advanced but Powerful)

This is the most accurate method.

The CLI shows everything.

Step-by-Step

  1. Click the CLI tab.
  2. Type: diff all
  3. Press Enter.

You will now see a list of all settings that differ from default.

This is pure gold.

Why?

Because presets modify values. And diff all shows exactly what was modified.

If you saved the preset name earlier, you can compare the CLI output with the preset description online.

It’s like matching fingerprints.

Bonus Command

Type:

dump

This shows every single setting. Even ones that match default.

It’s long. Very long. But useful for full backups.


Method 4: Check Your Backup File

Did you save a backup before applying the preset?

If yes, you’re a genius.

If not, start doing it now.

How Backups Help

When you apply a preset, Betaflight usually asks:

“Do you want to backup first?”

If you clicked yes, you have a file on your computer.

Open it with a text editor.

You’ll see lines of configuration commands.

Compare that file with your current diff all output.

Differences = preset changes.


Method 5: Look for Feature Clues

Many presets enable specific features.

So check if those features are active.

Go to the Configuration tab.

Look for:

  • Bidirectional DShot
  • RPM Filtering
  • Dynamic Idle
  • Anti Gravity gain changes
Image not found in postmeta

If these are enabled and you did not turn them on manually… a preset probably did.

This is not 100% proof. But it’s a strong clue.


Quick Comparison of Methods

Method Difficulty Accuracy Best For
Presets Tab Easy Low Recent installs
PID Comparison Medium Medium Quick checks
CLI diff all Medium Very High Precise confirmation
Backup File Medium Very High Before/after comparison
Feature Clues Easy Medium General idea

Common Mistakes to Avoid

1. Assuming It Saved Automatically

After applying a preset, you must click Save and Reboot.

If you didn’t, it’s gone.

2. Installing Multiple Presets

Stacking presets can get messy.

One may overwrite another.

Then you won’t know which values belong to which preset.

3. Not Backing Up First

This is the biggest mistake.

Always:

  • Go to CLI
  • Type diff all
  • Save it to a file

Do this before every major change.


Pro Tip: Label Your Builds

Simple trick.

Create a folder for each quad.

Inside it:

  • Date-stamped backups
  • Preset name used
  • Your rate profile details

This makes troubleshooting easy.

If the quad flies weird, you can roll back fast.


How to Know If You Should Reinstall a Preset

Sometimes checking isn’t enough.

If:

  • The quad feels unstable
  • You suspect partial configuration
  • You updated firmware recently

It might be smarter to:

  1. Flash firmware fresh
  2. Apply preset again
  3. Test hover carefully

Firmware updates can reset or alter settings. So presets may not carry over cleanly between major versions.


Does Betaflight Store a Preset Name Internally?

Short answer: No.

Betaflight stores values. Not labels.

Once applied, the preset becomes regular settings.

There is no “Preset ID” field stored inside your flight controller.

That’s why CLI checking is so important.


Final Thoughts

Checking installed presets in Betaflight is not hard.

You just need the right method.

If you want fast and simple, look at the Presets tab and PID values.

If you want accuracy, use diff all in the CLI.

And if you want peace of mind, always save backups.

Betaflight gives you power. A lot of power.

Presets make tuning easier. But only if you track what you install.

Now you know how.

Plug in your quad. Open Configurator. Take control.

Happy flying.