PageUnfold vs Chrome’s built-in print
| What happens | Chrome print / Save as PDF | PageUnfold |
|---|---|---|
| Long page | Split at paper boundaries | One continuous page by default |
| Sticky header | Can repeat or overlap content | Captured from the live layout once |
| Lazy-loaded images | May be absent before print layout runs | Scroll-and-settle preparation before capture |
| Signed-in page | Print CSS may hide or rearrange the live view | Uses the content already visible in the tab |
| Text | Usually searchable, but layout follows paper | Searchable vector text in a continuous document |
Four difficult page shapes are part of the release gate
Long tables
Rows remain in reading order on a single continuous PDF page instead of being divided by arbitrary page cuts.
Lazy-loaded pages
PageUnfold scans through the live document and waits for image loading and DOM changes to settle before rendering.
Multi-section layouts
Cards, grids and long report sections are captured from the browser’s current responsive layout.
Authenticated dark pages
The technical gate includes a signed-in-style dark fixture measuring more than 20,000 pixels, with searchable output and no forced watermark.
What “local” means. Core conversion does not upload the selected webpage to a conversion server. Chrome still grants the extension access to the tab you explicitly choose; account and diagnostic requests are documented in the privacy policy.
When to use a multi-page mode instead
If the final PDF must print onto physical A4 sheets, choose one of the explicit multi-page modes. PageUnfold does not silently turn the single-page command into a different product behavior.