How to export and import SingleFileZ settings between browsers

SingleFileZ was merged into SingleFile. The maintainer’s documented route is to install or open SingleFile in the destination browser, open its options, and use the settings import instructions shown in the options-page help. The public documentation does not establish a universal export file, exact button labels, or a guarantee that every setting maps identically, so check the options and test a saved page after importing.

What changes when you move SingleFileZ settings

This is a migration from the legacy SingleFileZ extension into its successor, SingleFile—not a general transfer of browser data between two browsers. The project README says, “SingleFileZ has been completely merged into SingleFile,” and adds, “Alternatively, you can simply import your existing settings in SingleFile.” Those are the maintainer’s stated instructions.

Browser-native profile migration may move bookmarks or other browser data, but the reviewed project documentation does not say it automatically transfers SingleFileZ’s extension-specific settings. Follow SingleFile’s own import help instead.

Before you start

Keep the source browser profile intact. Do not uninstall SingleFileZ, clear extension data, or remove the old profile until you have verified the new setup. This is a precaution, not an official recovery procedure.
Install SingleFile in the destination browser if it is not already installed. The project lists Chrome, Firefox (desktop and mobile), Microsoft Edge, Safari, Vivaldi, Brave, Waterfox, Yandex Browser, and Opera as compatible browsers. Use the official browser-store links from the SingleFile README.
Open SingleFile’s options page. Find the extension’s options through your browser’s extension controls.
Read the options-page help. Follow the settings-import route described there. The available documentation does not establish stable control names or an identical interface across browsers, so use the help in the installed extension rather than relying on a guessed click path.

Import and verify the settings

In the destination browser, open SingleFile’s options page.
Use the import instructions in the page’s extension help to import the existing SingleFileZ settings.
Review the options that matter to your workflow. Do not assume that every legacy value has an identical destination or that every setting was imported.
Save a representative page and inspect the resulting file. Check the parts affected by your configuration, such as page content and the save behavior you depend on.
Keep the old profile until you are satisfied with the result. If something is missing, refer to the original profile and the destination extension’s help before making changes that erase source data.

SingleFile’s README directs users to the in-page extension help for detailed options and technical notes. That is the best place to resolve differences between versions or browser-specific options.

What is and is not established about the transfer

Question	What the project documentation supports
Is SingleFileZ still the destination extension?	No. Its project says it has been merged into SingleFile.
Is there a documented continuation path?	Yes. The maintainer says to import existing settings in SingleFile.
Will browser-native migration carry the settings?	This is not established by the reviewed sources. Use SingleFile’s import instructions.
Does every setting transfer identically?	No per-setting compatibility guarantee or complete matrix was found. Inspect the imported options and test your workflow.
Are the controls identical in every browser?	The reviewed documentation does not establish that. Consult the installed extension’s options help.

Troubleshooting

Problem	Likely explanation	What to do
You cannot find a SingleFileZ export file or the same export controls in SingleFile.	The documented migration route is to import existing settings in SingleFile; the reviewed sources do not specify a universal export filename or exact controls.	Open SingleFile’s options and read its in-page help for the import procedure. Avoid assuming a file format or menu label.
Browser data migration completed, but SingleFile options look unchanged.	Browser-native migration is not documented as transferring SingleFileZ extension settings.	Use the import instructions in SingleFile’s options page.
The import option or help is not where you expect.	Exact UI labels and identical control placement across browsers are not established in the reviewed documentation.	Open the options page for the installed SingleFile extension and consult its in-page help. Check the project README for supported browsers and official store links.
Some settings appear different or are missing.	The project material does not provide a complete per-setting compatibility matrix.	Review the destination options, consult the extension help, and test a representative save. Keep the source profile until the new setup works for you.
You have already removed the old extension or profile.	The reviewed sources do not describe an official recovery procedure.	Check whether the original browser profile or an existing backup is still available. Avoid further cleanup until you have checked. Treat recovery as uncertain; do not assume the settings can be reconstructed automatically.

Privacy and extension settings

SingleFileZ’s FAQ says its storage permission lets the extension store its settings and that SingleFileZ does not upload data to third-party servers. That statement is about SingleFileZ; it does not establish how browser profile migration handles extension configuration. See the SingleFileZ FAQ.

Or skip the browser setup

If your goal is to capture a webpage rather than preserve a browser-extension configuration, ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. It does not import SingleFileZ settings or save a page as a SingleFile archive.

For example, this cURL call captures a page. Replace the URL with the page you need and provide your API key. See the ScreenshotNeo API documentation for options and response details.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Equivalent Python:

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)

Equivalent Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
const image = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', image));

Cookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000.

FAQ

Can I move settings directly from SingleFileZ to another browser?

The maintainer documents importing existing SingleFileZ settings in SingleFile. Install SingleFile in the destination browser and follow its options-page help.

Can I keep using SingleFileZ?

The project says SingleFileZ has been merged into SingleFile, its successor. Use SingleFile for the migration.

Will all my settings be preserved?

The project confirms the import route but the reviewed documentation does not guarantee every setting or provide a full compatibility matrix. Check the imported options and test a save.

Does this process transfer saved pages too?

The maintainer’s statement concerns existing settings. The reviewed sources do not describe it as a transfer of saved page files.

Sources

SingleFileZ repository README — merger notice and settings-import instruction.
SingleFile README — supported browsers and options-page help.
Mozilla Add-ons listing for SingleFileZ — legacy listing metadata.
SingleFileZ FAQ — storage permission and privacy statement.