Where Does LocalCDN Store Mappings and Settings?
LocalCDN keeps its framework mappings and settings in per-profile browser extension storage, with export for moves.
Last updated
LocalCDN stores settings in extension storage inside the active profile. Framework mappings, custom rules, and statistics share that space. The bundled jQuery and font files update with the extension itself.
Statistics reset on fresh profiles, which only affects the counter display. Blocking behavior matches within a version. Custom rules for odd frameworks need the export file to survive a move.
Where LocalCDN stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile)
Mappings and settings per profile. Export from options before wiping. Bundled frameworks update with the extension, custom rules need the file.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile)
Same model on Mac across Chromium and Firefox builds. Firefox keeps it under ~/Library/Application Support/Firefox/Profiles. Prefer export.
~/.config/google-chrome/Default/Extensions (per profile)
Chromium profiles under ~/.config and Firefox under ~/.mozilla. Same export workflow. No local request log to rotate.
Frequently asked questions
How do I move LocalCDN settings to a new browser?
Open the options and export settings to a file, then import on the new profile. Custom rules and HTML filter lists travel in that file. Bundled frameworks refresh from updates.
Do LocalCDN rules sync between profiles?
No. Each profile holds its own copy in extension storage. The export file migrates custom rules. Fresh installs intercept CDN requests with defaults immediately.
Notice an outdated path? Let us know.