Import/Export Settings & Preferences for Faster Setup #46192
Labels
feature/importer
feature/settings
feature-request
OS/Desktop
priority/P5
Not scheduled. Don't anticipate work on this any time soon.
Platforms
all
Description
Setting up a fresh Brave installation—whether on desktop or mobile—currently requires manually tweaking each preference: tracker-blocking level, rewards toggle, default search engine, site-specific blocking rules, and more. This process can be repetitive and time-consuming, especially when you want the same configuration across multiple devices.
I propose adding a Settings Import/Export feature that lets you:
Export all your Brave settings & preferences into a single file (e.g. JSON).
Import that file on a new Brave install (desktop or mobile) to automatically apply your preferences.
Motivation
Speed & Consistency: Instantly replicate your preferred setup across devices without clicking through every toggle.
Backup & Restore: Save a snapshot of your custom configuration before testing updates or switching devices.
Cross-Platform Ease: Ensure identical behavior on Windows, macOS, Linux, Android, and iOS—no manual reconfiguration needed.
Proposed Solution
1.Export button in brave://settings (and Settings on mobile) that serializes all adjustable preferences to a file.
2.Import button in the same UI that reads and applies a previously exported settings file, with a confirmation dialog.
3.Version Tagging: Include a Brave version identifier in the export to warn of any compatibility mismatches.
4.Selective Export: Optionally choose subsets of settings (e.g., privacy settings only).
Additional Context
Other browsers offer profile or policy export, but a native Brave solution focused solely on settings & preferences would be more streamlined.
This feature would be especially valuable for power-users, testers, and anyone who frequently switches between desktop and mobile environments.
Thanks for considering this enhancement—happy to help refine the file format or prototype the UI! 😄
The text was updated successfully, but these errors were encountered: