How to Save a Webpage as PDF After Archiving It with SingleFileZ in Chrome
Open the archived page in Chrome, print it to PDF, and check the result. Here’s how to fix local-file access problems and missing content.
To save a SingleFileZ archive as a PDF, open the saved archive in Chrome with the SingleFile extension installed and allowed to access local files. Once the archived page renders, open Chrome’s print dialog, choose Save as PDF, review the preview and page settings, then save. Open the PDF afterward and check that important text, images, and frames made it into the document.
What you need to know first
SingleFileZ saves a webpage as a self-extracting ZIP/HTML file. The project repository says SingleFileZ has been merged into SingleFile; to save this format in SingleFile, look under File format in the extension’s options. The SingleFileZ FAQ describes the common archive filename form as .zip.html. SingleFileZ project repository · SingleFileZ FAQ
For a local archive, Chrome’s extension filesystem restrictions matter: according to the FAQ, the extension needs permission to access saved pages from the local filesystem. JavaScript must also be enabled for saved pages to open. The exact labels in Chrome’s extension settings can vary by version.
Step-by-step: print the archive to PDF
- Install or confirm the SingleFile extension. If you are following older SingleFileZ instructions, note that the repository says it has been merged into SingleFile. In SingleFile options, choose the self-extracting format under File format when creating an archive.
- Allow local file access. In Chrome’s extension settings, enable access to local file URLs for SingleFile. Without this permission, an extension may be unable to open or process an archive stored on your computer.
- Open the archive in Chrome. Locate the saved file, often ending in
.zip.html, and open it in Chrome. Wait for the archived page to render. JavaScript must be enabled for saved pages to open, according to the project FAQ. - Open the print dialog. Press Ctrl+P on Windows or Linux, or Command+P on macOS. You can also use Chrome’s menu and choose Print.
- Choose the PDF destination. In the destination selector, choose Save as PDF.
- Review print settings and preview. Check the page breaks and whether important images and content appear. Adjust layout or margins if needed. The print preview is a useful check, but it does not guarantee that every dynamic element or frame will be preserved.
- Save and inspect the PDF. Choose Save, select a destination, and open the resulting PDF. Check important text, images, page breaks, and frame content before sharing or relying on it.
This uses Chrome’s standard print-to-PDF workflow. The available research did not find official Google documentation specific to printing a SingleFileZ archive, so inspect the generated file rather than assuming the conversion preserved every detail.
What can be preserved—and what to verify
SingleFileZ’s FAQ describes collecting page resources such as images, CSS, frame contents, and fonts. The result can depend on the archive’s settings: options that reduce file size or make saving faster may omit resources, including frames or deferred images. Printing then renders the archived page; it is not a guarantee that interactive behavior or every dynamic element will survive.
- Check large or important images, especially images that may have loaded only after scrolling.
- Inspect pages containing embedded frames, since frame content may be absent from the archive or PDF.
- Look for missing fonts, changed line wrapping, clipped content, and awkward page breaks.
- If a detail is essential, compare the PDF with the rendered archive before sharing it.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| The archive does not open or its page does not render in Chrome. | The extension is missing, cannot access local files, or JavaScript is disabled. | Confirm SingleFile is installed, allow it to access local file URLs in Chrome’s extension settings, and enable JavaScript. Then reopen the archive. |
| The archive opens, but some images or frames are missing. | The resources may not have been captured, or the archive settings may have omitted frames or deferred images. | Check the archive settings and the original page if available. Re-create the archive with the needed resources included, then print again. |
| The PDF has unexpected page breaks or clipped content. | Print layout and margins affect pagination and page width. | Review Chrome’s print preview, try a different layout or margins, and inspect the saved PDF before using it. |
| The page looks different in the PDF from the archive. | Printing creates a document rendering; interactive or dynamic page behavior is not guaranteed to carry over. | Use the archive for interactive inspection where possible. For the PDF, verify the information that matters and adjust print settings if appropriate. |
| Chrome cannot access the archive through the extension. | Chrome restricts extensions from accessing local files by default. | Enable local file access for the extension. The FAQ notes this filesystem restriction does not apply when a saved page is hosted on a server, though that is a different workflow from opening a local archive. |
Performance, reliability, and file size
Printing begins only after the archived page has rendered, so allow time for larger archives and pages with many resources. The final PDF depends on both what the archive contains and how Chrome lays it out for print. There is no source-backed guarantee that a particular archive setting, page, or browser version will preserve every resource; preview the page and inspect the saved PDF when fidelity matters.
For a smaller or faster archive, some capture settings may omit resources. That tradeoff can affect the later PDF, particularly for frames and deferred images. Keep the resources needed for the document you intend to produce, then check the output.
Or skip the browser setup
If you need a screenshot or PDF directly from a live page instead of converting an existing SingleFileZ archive, ScreenshotNeo is a website screenshot API and MCP server for developers. It can return a PNG, JPEG, WebP, or PDF. The API accepts a URL in one GET request; see the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.pdf
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com", "format": "pdf"},
timeout=90,
)
r.raise_for_status()
open("shot.pdf", "wb").write(r.content)
const q = new URLSearchParams({
access_key: 'YOUR_API_KEY',
url: 'https://stripe.com',
format: 'pdf'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`ScreenshotNeo returned ${res.status}`);
await Bun.write('shot.pdf', res);
- Cookie banners are accepted and removed before the shot, along with supported newsletter popups and chat widgets; each step can be turned off.
- Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Response headers report the page verdict and billing status.
- An MCP server provides
take_screenshot,get_page_info, andcapture_pdffor AI agents and MCP clients. - The free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000; every feature is on every plan.
Sign up for 1,000 free screenshots a month, with no card required.
FAQ
Is SingleFileZ still a separate extension?
The project repository says SingleFileZ has been merged into SingleFile. The self-extracting output setting is available under File format in SingleFile’s options.
Can I print the archive if it is hosted online?
The SingleFileZ FAQ says the local filesystem restriction does not apply to saved pages hosted on a server. This guide covers opening a local archive, which may require granting the extension local file access.
Will the PDF keep links and interactive controls?
The available sources do not guarantee that interactive behavior survives printing. Treat the PDF as a fixed rendering and check the output for the content you need.
Why check the PDF after saving?
Archive settings can omit resources, and print layout can change pagination. Opening the file is the way to confirm the document contains the material you intended to keep.


