How to Save Multiple Tabs at Once with SingleFile
Save a chosen group, all unpinned tabs, or every open tab as separate HTML files with SingleFile. Follow the steps, shortcuts, settings, and fixes.
To save multiple tabs at once with SingleFile, select the tabs you want in your browser, then click the SingleFile toolbar button. For a larger group, open the SingleFile context menu and choose to save selected tabs, unpinned tabs, or all tabs. SingleFile saves each page as its own HTML file.
Save a selected group of tabs
- Wait for the pages you want to archive to finish loading. SingleFile recommends saving a page after it has fully loaded.
- Select the tabs. In browsers that support multi-tab selection, use the browser’s tab-selection controls to select the tabs you want together.
- Click the SingleFile toolbar button. It saves the selected tabs as individual HTML files.
- Check the browser’s configured downloads folder for the files. The browser download folder is the documented default destination.
If you do not see the SingleFile button, open the browser’s extensions menu and pin SingleFile to the toolbar. The exact toolbar and tab-selection gestures depend on the browser.
Save unpinned tabs or all tabs
When you want to save a set too large or inconvenient to select individually, use SingleFile’s context menu. Right-click the SingleFile toolbar button or a webpage, then choose the batch action matching your intent:
- Selected tabs: Save the tabs you selected in the browser.
- Unpinned tabs: Save the unpinned tabs in the relevant browser window.
- All tabs: Save every tab in the relevant browser window.
Check the scope in the menu before starting a large batch. Selected tabs are best for a deliberate hand-picked group; unpinned tabs are useful for a working set; all tabs are appropriate when you intend to archive the whole window.
Shortcut, auto-save, and destinations
Keyboard shortcut
SingleFile documents Ctrl+Shift+Y for saving the current tab or selected tabs. You can change the shortcut in your browser’s extension shortcut settings. On Firefox, if text is selected on the page, that shortcut may save only the selected content. A custom keyboard shortcut command saves the entire page.
Auto-save
Auto-save is an optional ongoing behavior, separate from a one-time batch. The context menu can enable it for the current tab, unpinned tabs, or all tabs. SingleFile saves a page after it loads, or before it unloads if it has not yet been saved. Choose the scope carefully if you have many tabs open.
Where files go
By default, look in the download folder configured in the browser. If you changed SingleFile’s destination options, check that destination instead. Firefox’s extension listing describes optional upload destinations such as Google Drive, Dropbox, GitHub, and WebDAV; these need configuration and are not the default local save behavior.
What gets saved, and what can be incomplete
SingleFile stores each captured page as a single HTML file. It aims to bundle page resources into that file, which makes it convenient to keep or move an offline copy. It cannot guarantee a perfect archive of every page element: browser security may prevent saving image representations of some canvas elements or snapshots of some video elements. Certain browser-internal and Mozilla pages are also restricted.
If SingleFile shows a blocked indicator or a saved page is incomplete, consult the project’s known-issues and troubleshooting guidance. This is especially relevant for browser-internal URLs, canvas-based graphics, and video content.
Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| The saved files are not in the folder you expected. | The browser controls the default download folder, or a destination option was changed. | Check browser download settings and SingleFile’s destination options. Also check the browser’s downloads list for the exact file location. |
| Only one page or selected text was saved. | The tabs may not have been selected together, or Firefox interpreted the shortcut as a selected-content save. | Confirm the browser’s selected-tab state before clicking the toolbar button. On Firefox, clear the page text selection and use the documented shortcut, or use a custom shortcut command for a full-page save. |
| A page is missing images, canvas artwork, or video content. | Browser security can restrict capture of some canvas and video representations. | Review SingleFile’s known issues and troubleshooting guidance. Some content may not be available to the extension for archiving. |
| The browser reports a page as blocked. | Some internal browser and Mozilla pages cannot be saved because of browser security restrictions. | Use SingleFile on an ordinary web page. Internal pages may not be archivable. |
| A page looks unfinished in the saved copy. | The page may not have finished loading when capture started, or some dynamic content may not have been available to capture. | Wait for loading to complete, then save again. Verify the online page itself contains the content before treating its absence as a SingleFile issue. |
| A batch is taking a while or you started the wrong set. | Many pages or complex pages take time to process, or the chosen batch scope is broader than intended. | For a one-time batch, click the SingleFile button during processing to interrupt the save. Next time, select only the intended tabs or choose the narrower context-menu scope. |
Performance, reliability, and storage
Batch time depends on the number and complexity of pages and whether they have finished loading. Let pages settle before starting, and consider saving very large groups in smaller batches so it is easier to locate or retry an individual file. SingleFile’s documented output is one HTML file per page, so the number of resulting files tracks the number of saved tabs. File sizes vary with the page resources included.
For reliability, verify that representative files open offline and contain the content you need, especially if the archive matters. Browser restrictions and page-specific content can leave elements out. Keep a separate backup if the saved pages are important; the extension’s default local download is not itself a backup strategy.
Or skip the browser setup
SingleFile is for archiving pages as HTML. If your goal is screenshot images or PDFs of websites, ScreenshotNeo provides a website screenshot API and MCP server. A single GET request returns a PNG, JPEG, WebP, or PDF; it does not create SingleFile-style HTML archives.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options and formats. 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. Learn about ScreenshotNeo, then sign up for 1,000 free screenshots a month, no card required.
FAQ
Does SingleFile create one file containing all the tabs?
No. It saves each captured page as an individual HTML file.
Can I save tabs automatically as they load?
Yes. Auto-save can be enabled for the current tab, unpinned tabs, or all tabs. It is an optional continuing setting, not required for a manual batch.
Which browsers support SingleFile?
The project lists Chrome, Firefox desktop and mobile, Chromium-based Edge, Vivaldi, Brave, Waterfox, Yandex Browser, and Opera. The Firefox listing also identifies Firefox for Android support. Browser capabilities and menus can vary.
Can I upload saved pages to cloud storage?
Optional destinations such as Google Drive, Dropbox, GitHub, and WebDAV are described in the Firefox listing and require configuration. Local browser downloads are the default behavior.
References: SingleFile project documentation and README; SingleFile on Firefox Add-ons.
