Configuration Files

The Configuration Files section lets you store and organize firmware configuration snapshots. This is useful for keeping a history of your tune iterations, comparing settings across versions, or archiving known-good configurations for quick restore or reference.

There are three ways to add a configuration: upload a file from your computer, create one by pasting content directly, or edit an existing config to produce a new versioned copy.

Uploading a configuration file

Scroll to the Configuration Filessection in the detail view. You'll see an upload form at the top:

• Config Name — A label for this snapshot (e.g., “High Acro”, “Racing Tune v2”, “Conservative PID”, “Baseline_2025-02-15”)
• Select File — Click to choose a file from your computer

Accepted file types: .txt, .csv, .json, .bbl, .ini, .conf, .config, .xml, .yaml, .yml, .dump

Both the Config Name and the file are required. Fill in both and click Upload.

Creating a config from text (no file needed)

Click the Create New button next to Upload to open the built-in text editor. This is the fastest way to save a Betaflight diff all or dump output without creating a file on disk:

1. Copy the CLI output from Betaflight Configurator (or any other source).
2. Click Create New to open the editor modal.
3. Enter a Config Name in the name field.
4. Paste the content into the text area.
5. Click Save. The config is uploaded and appears in your list immediately.

Editing an existing config

Every saved configuration shows a pencil (Edit) button to the left of the download button. Clicking it opens the same text editor pre-filled with the current file content and the name pre-set to the next version (e.g., My Tune v2).

Make your changes in the editor and click Save. UAV Desk will:

• Upload the edited content as a new entry with the versioned name.
• Leave the original config untouched — it remains in your list.
• Automatically increment the version suffix: v2 → v3 → v4 …

Managing your configurations

Once uploaded, each config appears in a list below the form. For each entry you see:

• Config Name (bold) — The label you gave it
• Filename (subtitle) — The stored filename
• Edit button (pencil icon) — Open the config in the editor to create a new versioned copy
• Compare button (compare icon, right of the pencil) — Quickly diff this config against a Betaflight CLI dump you paste in, with the option to save that text as a new config. See Config File Diff Viewer.
• Download button (arrow icon) — Retrieve the file to your computer
• Delete button (red trash icon) — Remove it from your records. A browser confirmation dialog appears before deletion.

Best practices

• Descriptive names: Use clear, meaningful Config Names like “Race Tune - High PID Gains” or “Conservative - Smooth FPV”. Avoid generic names like “config.txt” or “backup”.
• Date your uploads: Include a date in the name (e.g., “PID_2025-02-15”) to track when changes were made. This helps you remember the order of iterations.
• Archive known-good configs: Keep a snapshot of settings that fly well, even if you later modify them. Being able to quickly restore a known-good config is invaluable for troubleshooting.
• Use Edit rather than re-uploading: The Edit workflow automatically tracks the version number and keeps the parent entry intact, making your history easier to follow than manually uploading renamed files.
• Use the diff viewer: After editing, select the original and the new version and click Compare to see exactly what changed. See Config File Diff Viewer for details.