Why use SnapFetch
- Preserves layout and styling from the original page
- No account needed, and the file is gone from our servers within the hour
- Works with a single self-contained HTML file
How it works
- 1
Choose or drag in an .html or .htm file
- 2
We render it and export a PDF
- 3
Download your PDF
- 4
Files are deleted from our servers after 1 hour
When to use HTML to PDF
Good for saving a self-contained HTML document - an exported report, an invoice template, a saved article - as a fixed PDF. Rendering uses WeasyPrint, which honours CSS including print stylesheets and page-break rules. It is not a headless browser: it does not run JavaScript, so a page that builds its content client-side will come out empty.
Specifications & limits
- Accepted input
- HTML files (.html, .htm)
- Rendering engine
- WeasyPrint
- JavaScript
- Not executed - content generated by scripts will not appear
- CSS support
- Print stylesheets and @page rules including page breaks
- Maximum file size
- 20 MB per upload
- File retention
- Deleted from our servers 1 hour after upload
Troubleshooting
The PDF is blank or missing most of the page
The content is almost certainly rendered by JavaScript. Save a fully rendered copy of the page first, then convert that.
Images and styles are missing
Assets referenced by relative path are not uploaded with the file. Inline the CSS and embed images as data URIs.
The upload is rejected before anything happens
The file is over the 20 MB cap. Compress it first, or split a long PDF into smaller files and process them separately.
References
The published specification for the formats involved, and the open-source software that actually performs this conversion.
- WeasyPrint documentation
The rendering engine used for HTML-to-PDF, including its CSS support and limits.
Frequently asked questions
Only if they're referenced by a working URL the page can reach, or embedded directly in the file - a fully offline HTML file with only local references may render without them.