Where Does NoScript Store Permissions and Settings?
NoScript keeps per-site permissions and settings in per-profile browser extension storage, with export for moves.
Last updated
NoScript stores its allowlists in extension storage under the active browser profile. Per-site permissions, XSS settings, and options share that space. There is no user-facing config file.
Fresh profiles start locked down, which is the point but also the migration pain. Every trusted site re-prompts until the export file restores the lists. The options export covers permissions and settings in one step.
Where NoScript stores this, by platform
%AppData%\Mozilla\Firefox\Profiles\<profile>\storage (per profile)
Permissions database per profile, mostly a Firefox story. Export from options before wiping. Import restores trusted lists without re-prompting every site.
~/Library/Application Support/Firefox/Profiles/<profile>/storage (per profile)
Same storage model on Mac. Chromium builds keep it under the Chrome profile tree. One export file covers permissions, XSS, and general settings.
~/.mozilla/firefox/<profile>/storage (per profile)
Profiles under ~/.mozilla with the same export workflow. Back up before distribution upgrades that reset profiles. Settings file beats folder copies.
Frequently asked questions
How do I move NoScript settings to a new browser?
Open the options page and export settings to a file, then import on the new profile. Trusted and untrusted site lists travel in that file. Default-deny posture restores with it.
Do NoScript permissions sync between profiles?
No. Each profile holds its own permissions database in extension storage. Sync the file manually or the new profile starts from default-deny and re-prompts everywhere.
Notice an outdated path? Let us know.