Back up your configuration
Export can help preserve local Shieldly settings such as site modes, allowlists, custom blocked domains and protection preferences.
Move settings between browsers
Import makes it easier to restore a setup in another Chrome profile or after reinstalling. Exported settings are local files and are not uploaded automatically.
Privacy-first portability
Import and export are designed for user-controlled portability rather than cloud sync. You decide when to export, where to store the file and when to import it again.
Create a backup before moving profiles
Open Backup in the Shieldly installation whose settings you want to keep and export its configuration. Store that text or file privately and label it so you can identify the source profile and date. A backup is useful before a larger settings cleanup as well as a browser move. It records configuration, not an independently verified history of every event the extension has blocked.
Import and inspect the destination
Install Shieldly in the destination browser profile, open Backup and use the import workflow with a Shieldly export. Keep a backup of the destination first if it already has settings you care about. After importing, check the global switch, protection mode, allowed sites and custom blocks. Reload representative websites to verify behavior. Do not assume that a successful import transfers every browser-managed permission or optional activation state.
Handle malformed or unfamiliar data carefully
If an import reports invalid JSON, return to the original exported content rather than deleting random characters until it is accepted. A copied fragment or extra surrounding text may explain the failure. Do not import a configuration from an unknown source without reading it, especially its site exceptions and domain rules. Those values can change what gets blocked or allowed even though the data is not an executable extension package.
Frequently asked questions
Is backup the same as automatic cloud sync?
No. This workflow is an explicit export and import of local configuration. It should not be treated as continuous synchronization.
Can I use a backup to move between supported browsers?
That is the intended configuration workflow. Verify imported settings and browser-specific permissions afterward because the environments can differ.
Related pages
See custom blocked domains, site controls and data deletion.