Back up and restore settings
What should you keep?
| Item | Purpose | Does not replace |
|---|---|---|
| Settings profile | Save a group of settings and apply selected items | An external backup |
| File backup | Store settings on a phone or PC | Full OS, driving-log or source-code recovery |
| QR backup | Transfer supported settings | A clone of every internal state |
| Branch and commit notes | Identify the affected version | The setting values themselves |
Before updating
- Park and open Carrot Web.
- Record vehicle, device, branch and commit under Tools → Info.
- Save a profile named with the date and vehicle.
- Download a file backup under Tools → Settings.
- Check that the file was actually saved on your phone or PC.
Example filename: 2026-10-30_vehicle_carrot-wip_10bf0a56.json.
Restore
- Check that the backup matches the vehicle and branch.
- Back up the current values first.
- Compare the backup and current values in the restore preview.
- Select the required items; review invalid, excluded or failed items.
- Follow restart prompts and verify the resulting state.
The Defaults button does not restore your previous personal values. Catalogue defaults can differ from initial Params values, and updates may preserve stored settings.
Items that do not transfer
DriverMonitoringEnabled is not transferred by file, QR or profile. Restore does not import another device's disabled-DM choice or change the current device's choice. Check driver monitoring after restoring.
Do not apply another vehicle's complete settings as a recommended preset. Units, allowed ranges and vehicle applicability can differ even for the same key.
Units and defaults · After-update troubleshooting.
Source reference
Reference checked 2026-10-30 · carrot-wip · 10bf0a56.
docs/user/ko/carrot-web.md · docs/user/ko/settings.md · docs/user/ko/driver-monitoring.md · openpilot/selfdrive/carrot/server/features/params.py
The development branch continues to change. Check your device’s branch, commit and current settings together.