Where Does SingleFile Save Pages and Settings?
SingleFile saves pages as HTML files in Downloads with its settings in per-profile extension storage.
Last updated
SingleFile splits output from options. Saved pages land as self-contained HTML files wherever downloads go. Settings, filename templates, and destination rules sit in extension storage per profile.
That split makes migration two-part. Copy the options file for behavior and move the saved pages like any documents. Batch saves queue in the background without further prompts.
Where SingleFile stores this, by platform
%LocalAppData%\Google\Chrome\User Data\Default\Extensions (per profile)
Options and templates per profile. Saved pages land in Downloads by default. Move both halves for a complete migration.
~/Library/Application Support/Google/Chrome/Default/Extensions (per profile)
Same model on Mac across Chromium and Firefox builds. Point the save folder at synced storage to roam archives automatically.
~/.config/google-chrome/Default/Extensions (per profile)
Chromium profiles under ~/.config and Firefox under ~/.mozilla. Same export workflow. Filename templates travel in the options file.
Frequently asked questions
How do I move SingleFile settings to a new browser?
Open the options and export settings to a file, then import on the new profile. Saved pages themselves live in Downloads and move as regular files.
Can SingleFile save into cloud folders?
Yes through the save location option. Point it at a synced folder and archives follow automatically. Filenames template from page title plus date.
Notice an outdated path? Let us know.