Can SingleFile Save a Webpage as PDF, or Only as HTML?
SingleFile saves webpages as self-contained HTML, not PDF. To make a PDF, use your browser’s print dialog and choose Save as PDF.
Short answer: SingleFile saves a webpage as one self-contained HTML file. PDF is not a documented SingleFile output format. To save a webpage as a PDF, open the browser’s Print dialog or print preview and choose a PDF destination when available. That print workflow is provided by the browser, separately from SingleFile.
Choose HTML when you want a webpage-style offline copy that includes resources such as images and styles. Choose PDF when you want a document for printing, sharing, or archiving in a fixed-page format. Neither format guarantees that a dynamic site will look or behave exactly as it does online.
1. What SingleFile saves
SingleFile captures a webpage and packages it into one HTML file, including resources such as CSS, images, fonts, and frames. Its command-line tool also saves a page and its resources into one HTML file. The project describes the extension as a way to capture a webpage and package it into a self-contained HTML file (SingleFile project; official FAQ).
That output is still HTML. A file extension or a browser’s ability to print a page does not mean SingleFile itself has created a PDF. For a PDF, use the browser’s print feature.
2. Save a webpage as PDF with your browser
- Open the webpage you want to save and wait for its important content to load.
- Open the browser’s Print dialog or print preview.
- Select a PDF destination, such as Save to PDF, if your browser and operating system offer one.
- Review the preview, adjust print settings if needed, then save the PDF.
Chrome on desktop
Use Ctrl+P on Windows or Linux, or Command+P on Mac. In the print preview, choose an available destination for saving as PDF, then save. See Google’s Chrome printing instructions.
Firefox
Open Print preview and select Save to PDF from the destination options where available. The menu and available destinations can vary by operating system and browser version. See Mozilla’s Firefox printing instructions.
Print output is controlled by the browser and its print settings. It may differ from the screen layout; check the preview rather than assuming the PDF will be an exact visual copy.
3. Choose HTML or PDF for your task
| Need | Better fit | What to expect |
|---|---|---|
| Keep a webpage-style offline capture | SingleFile HTML | Page resources are packaged into a single file, but some behavior or assets may not work offline. |
| Print, send, or archive a paginated document | Browser print to PDF | The browser lays the page out for printing; screen and print layouts can differ. |
| Preserve interactive behavior such as maps or carousels | Neither is guaranteed | SingleFile’s offline copy may not preserve interactions, and a PDF is a print-oriented document. |
4. SingleFile limitations to know
A self-contained HTML capture is useful for offline reading, but it is not necessarily a complete, working copy of a live site. According to the SingleFile FAQ:
- Scripts are removed by default because they can alter page rendering and may not work offline. The FAQ describes options for retaining scripts and raw page content.
- Interactive features, including dynamic maps and carousels, may not work properly in the saved file.
- Browser restrictions prevent extensions from saving some protected domains.
- Some sites require a Referer header to load images; the related setting is off by default for privacy reasons.
Treat the saved HTML as an offline capture, not a perfect interactive replica. If an image or other resource is missing, check the site’s loading requirements and SingleFile’s documented settings. If the page cannot be captured, the browser may restrict extension access on that domain.
5. Capture a screenshot or PDF with ScreenshotNeo
If your goal is an automated visual capture or a PDF from a URL, ScreenshotNeo is a website screenshot API and MCP server for developers. A single GET request can return a screenshot or PDF. This is a separate workflow from saving a SingleFile HTML archive; use SingleFile when you specifically need that self-contained HTML file.
For options and response details, 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.webpTo request a PDF, use the PDF options documented by ScreenshotNeo. ScreenshotNeo also supports full-page capture, element capture, viewport and device settings, PDF paper size, margins, landscape mode and page ranges. Its other options include custom CSS and JavaScript, wait conditions, request blocking, caching, bulk capture and asynchronous jobs. Every feature is available on every plan.
ScreenshotNeo accepts cookie and consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be turned off. It bills only clean shots: bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info and capture_pdf for AI agents using Claude, Cursor or another MCP client.
The free plan includes 1,000 shots per month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free. See the docs for the available parameters and output settings.
Sign up for 1,000 free screenshots a month, with no card required.
6. Troubleshooting
| Problem | Likely cause | What to do |
|---|---|---|
| Looking for a PDF option in SingleFile | SingleFile’s documented output is HTML. | Use the browser’s Print dialog and choose a PDF destination if available. |
| The PDF looks different from the webpage | Print layout and browser settings can change pagination and appearance. | Review print preview and adjust the available print settings before saving. |
| Saved HTML is missing images | A site may require a Referer header or may restrict resource loading. | Consult SingleFile’s FAQ and check its Referer setting; it is off by default for privacy. |
| Maps, carousels, or other controls do not work offline | Scripts are removed by default, and some dynamic features do not work properly in a saved copy. | Check SingleFile’s script and raw-content options, while expecting that some interactions may remain unavailable. |
| SingleFile cannot save a page | The browser may block extensions on a protected domain. | Try a page the browser allows extensions to access, or use the browser’s print workflow for a PDF where available. |
| No PDF destination appears | Available print destinations depend on browser, operating system, and version. | Check the browser’s print help for your platform and available destinations. |
7. FAQ
Does changing the saved file extension from .html to .pdf convert it?
No. Renaming a file does not convert its contents. Use the browser’s print-to-PDF workflow to produce a PDF.
Can I use SingleFile’s command-line tool to create a PDF?
The project describes its CLI as saving a page and its resources into one HTML file. PDF is not a documented output format; use a browser print workflow for PDF.
Which browsers support SingleFile?
The project lists extensions for Chrome, Firefox desktop and mobile, Microsoft Edge, Safari, Vivaldi, Brave, Waterfox, Yandex Browser, and Opera. Compatibility can change, so check the project’s current browser information.
Is the saved HTML the same as the original webpage?
It is a self-contained capture intended for offline use, not a guarantee that every script, resource, or interactive feature will behave as it did online.
