How to Convert a Web Page to a PDF in Google Chrome

On a computer: open the page in Google Chrome, press Ctrl+P on Windows or Linux (or Command+P on Mac), choose Save as PDF, adjust the print settings, and save the file.

On Android: open the page, tap More > Share > Print, choose Save as PDF, select a location, and finish saving.

Chrome’s documented iPhone and iPad workflow uses Share > View more > Print with AirPrint; the cited Chrome Help instructions do not describe the same direct Save as PDF destination available on desktop and Android. See Chrome Help’s printing instructions for the current menu wording.

Save a web page as a PDF on Windows, Linux, or Mac

Open the page you want to convert in Chrome.
Open the print dialog with File > Print, Ctrl+P on Windows or Linux, or Command+P on Mac.
In the destination or printer list, select Save as PDF. The exact position and label can vary with your operating system’s print interface.
Set the options you need in the preview.
Click Save, choose a filename and folder, then confirm.

Useful print settings

Setting	When to use it
Pages	Save all pages or enter a range such as 1-3.
Layout	Use portrait for most articles and landscape for wide tables.
Paper size	Choose the paper size required by your reader or printer.
Margins	Use default margins for predictable output; reduce them when content is being clipped.
Scale	Lower the scale if a wide table or heading runs off the page.
Headers and footers	Turn them off when you do not want the page title, URL, date, or page numbers added.
Background graphics	Enable them when the page relies on colored panels or background images; the result depends on the page and print preview.

Save a web page as a PDF on Android

Open the page in Chrome.
Tap More (the three-dot menu), then Share, then Print.
In the printer area, choose Save as PDF.
Select where to store the file.
Tap Print to finish the save action.

Android’s available controls can vary by device and system version. If you do not see the destination immediately, open the printer selector and look for Save as PDF.

Chrome's print flow turns the rendered page into a PDF document.

What happens on iPhone and iPad?

Chrome’s documented iPhone and iPad route is Share > View more > Print, followed by AirPrint. The official instructions cited for this workflow do not promise a desktop-style Save as PDF choice. Your available PDF workflow therefore depends on the iOS or iPadOS print interface and installed apps. If you need a repeatable server-side PDF instead of a device print action, use the automation option below.

Saving to Google Drive

Chrome Help documents an optional Save to Google Drive destination. It may appear under See more and requires the Save to Google Drive extension. You can also save the PDF locally first and upload it through Drive for desktop or the Google Drive website. Neither Drive route is required to create a local PDF.

Why the PDF may look different from the page

Print previews apply print CSS, so navigation, animations, sticky elements, and interactive controls may disappear.
Long pages can split headings, tables, or cards across page boundaries.
Lazy-loaded images may not be present when the print preview is generated.
Fonts, background graphics, margins, and scaling depend on the page, browser, device, and operating system.
A page that requires login, a consent action, or JavaScript may not render the same way for every visitor.

Chrome’s general instructions explain how to create the PDF; they do not guarantee identical rendering for every website.

Automate PDF capture with ScreenshotNeo

For scheduled jobs, backend workflows, bulk URLs, or consistent browser settings, ScreenshotNeo provides a website capture API and MCP server. It supports PDF capture with paper size, margins, landscape mode, and page ranges, plus full-page capture, lazy-image loading, custom CSS and JavaScript, cookies, headers, authentication, waiting rules, and request blocking. The complete option list is in the ScreenshotNeo documentation.

cURL

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

Python

import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)

Node.js

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Use the PDF parameters documented for your capture in the API reference. The API also supports custom waits, selector capture, dark mode, device presets, geolocation, time zones, transparent backgrounds, caching, signed links, asynchronous jobs, signed webhooks, bulk capture of up to 100 URLs per call, and a usage API.

Or skip the browser setup

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the shot. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and response headers identify the page verdict and billing result. Its MCP server lets Claude, Cursor, and other MCP clients take screenshots or capture PDFs. The Free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000 screenshots.

Create a free ScreenshotNeo account.

Troubleshooting

Save as PDF is missing

On desktop, open the full system print dialog or check the destination list. On Android, enter the printer selector after opening Share > Print. On iPhone and iPad, Chrome’s documented path uses AirPrint rather than the same desktop destination.

Automated capture can clear common overlays before rendering the document.

The page is cut off

Try landscape layout, a larger paper size, smaller scale, or narrower margins. Wide tables often need landscape mode or a page range.

Images are missing

Wait for the page to finish loading before opening print preview. Some images are lazy-loaded or blocked by the page’s scripts. For automated capture, configure a selector wait, delay, or network-idle wait.

Complete the consent or login step before printing. For server-side capture, provide the required cookies, headers, user agent, or authorization in the API configuration.

The PDF contains an error page or is blank

Reload the page and verify that it works without an extension blocking scripts. For automation, inspect the response verdict and billing headers, then increase the timeout or wait for a page selector.

Performance, reliability, and cost considerations

For one-off documents, Chrome’s built-in print flow has no separate PDF service cost.
For repeated captures, reduce unnecessary work with a chosen viewport, targeted waits, request blocking, and a cache TTL where appropriate.
Use asynchronous jobs and signed webhooks when a capture should not block a request handler.
Bulk capture is available for up to 100 URLs per call.
ScreenshotNeo bills only clean shots; failed loads, bot checks, blank pages, timeouts, and cache hits cost nothing. Check the response headers before storing or retrying a result.

FAQ

Can I convert a web page to PDF without installing software?

Yes. Chrome includes the print-to-PDF workflow on computers and Android.

Does Save as PDF preserve the whole page?

It can produce multiple PDF pages, but exact page breaks and visual fidelity depend on the page and print settings.

Can Chrome save a PDF directly to Google Drive?

Yes, with the documented Save to Google Drive extension and destination. Saving locally and uploading is another supported route.

Can I automate this for many URLs?

Yes. A capture API such as ScreenshotNeo supports automated and bulk workflows, with PDF options documented in its API reference.