Every major browser can save a webpage as a PDF using built-in print functionality, and for most purposes that is the quickest path. When the browser's output does not match what you need — print stylesheets applied, content clipped, background colours stripped — a dedicated converter that renders the page with a headless browser gives you more control and more consistent output.
The built-in browser method
In Chrome, Edge, Firefox, and Safari, File → Print → Save as PDF (or the equivalent in your OS print dialog) converts the currently-loaded page to a PDF. The result is what the page looks like when optimised for print — which often differs from the screen layout. Websites apply print stylesheets that hide navigation, shrink images, remove backgrounds, and reformat content to fit a letter or A4 page.
For articles, documentation pages, and text-heavy content, the print stylesheet often produces a cleaner output than the screen version. For visual pages — marketing sites, dashboards, portfolio pages with specific layouts — the print output can collapse columns, strip backgrounds, and look nothing like the page as displayed.
The main advantage of the browser method is that it works on any page you are already viewing, requires no additional tools, and includes dynamic content that was loaded after the page's initial render. It is the right choice for a quick capture of most text-based content.
When the browser output falls short
Print stylesheets are applied by the page's authors, not by the browser. A page whose authors have not written a print stylesheet — or whose print stylesheet removes too much content — produces poor output from the browser method. Common problems include: navigation bars taking up the first third of every page, background colours used as design elements stripped out entirely, multi-column layouts collapsing to a single column, and images with intrinsic sizing cropped to the page margin.
A headless browser converter renders the page the same way a real browser does, then converts the screen render to PDF rather than applying print formatting. What you see on screen is what appears in the PDF. This method is more reliable for visual pages, and it does not depend on the page's print stylesheet having been configured.
Using Filum's URL to PDF tool
Filum's URL to PDF tool takes a web address and returns a PDF of the rendered page. Enter the URL, press Convert, and the page is loaded in a headless Chromium browser on Filum's server, rendered at 1280px wide, and saved as a PDF. The tool handles JavaScript-rendered content — content loaded after the initial page response — because a headless browser runs the full JavaScript engine before capturing the output.
The tool works without a browser extension, without an account, and without installing any software. The PDF is generated from the live page at the moment you convert it, so the output reflects the page's current state. There is a processing delay of a few seconds while the page loads and renders; pages with heavy JavaScript may take longer.
This approach differs from iLovePDF and Smallpdf, both of which require a browser extension for webpage-to-PDF conversion. Filum handles it server-side using a headless browser, so no extension is needed — just the URL.
What the tool cannot capture
Pages that require authentication — behind a login — cannot be accessed by a headless browser with no session. If you need a PDF of a page that requires you to be logged in, the browser print method is the right approach: you are already authenticated, so the page renders in full.
Pages with content behind paywalls, geo-restrictions, or CAPTCHA challenges will either show the blocked version or fail to load, depending on how the restriction is implemented. The converter sees the same page that would be shown to an unauthenticated visitor from the server's location.
Infinite-scroll pages capture only the content that loads in the initial render. Content that appears when you scroll — loaded lazily as you reach the bottom — is not captured unless the headless browser has scrolled far enough to trigger those loads. For standard pages with defined content, this is not a problem. For social feeds and infinite-scroll content aggregators, the capture is bounded by the initial render.
Saving multiple pages
To capture multiple pages from the same site as a single PDF, the browser method with the Print all pages option in Chrome's print dialog is often the most practical approach for paginated content. For saving multiple separate URLs as individual PDFs, use Filum's URL tool once per page.
If you need to combine multiple webpage PDFs into a single document, use a PDF merge tool after capturing each page separately. Filum's merge tool accepts multiple PDFs and combines them in the order you specify.