How to create a PDF of a long web page for client documentation

The simplest way to make a PDF of a long web page is to open it in a desktop browser, use Print, choose a PDF destination, and inspect the preview before saving. First let the page finish loading. If it reveals content as you scroll, scroll through the relevant sections and return to the top so they have a chance to load. Then print, adjust paper size, orientation, margins, and scale for readability, and check the saved PDF from beginning to end.

For client documentation, also record where the page came from and when you captured it. A PDF is a useful saved record, but browser print settings alone do not establish that it meets a client’s legal, regulatory, or retention requirements.

1. Prepare the page before printing

1. Open the exact page you need and confirm that you have access to its content.
2. Wait for the main content to load. If the page loads more material as you scroll, scroll down through the relevant content, pause as needed, then return to the beginning. This is a practical precaution; page behavior varies by site.
3. Decide whether the client needs the page’s original visual context, such as navigation, branding, or backgrounds, or mainly its readable text and tables. That choice affects whether a simplified print view is suitable.
4. Note the page title, source URL, and capture date for the file name or a cover note. Do not assume browser-added headers will identify the source URL.

2. Save to PDF in your browser

Microsoft Edge

Open Settings and more > Print, or use Ctrl+P on Windows or Command+P on macOS. Choose an available PDF destination in the print flow, review the preview, and save. Edge’s print dialog provides controls for orientation, paper size, page range, margins, scale, headers and footers, and background graphics. If the page has a cleaner reading view, Immersive Reader may be available; support varies by site. Microsoft Edge print instructions.

Mozilla Firefox

Open Menu > Print, choose Save to PDF in the destination dropdown, review the preview, and save. Firefox offers paper size, orientation, page range, scale, pages per sheet, margins, color, and optional headers, footers, and backgrounds. If offered, Simplified format can reduce clutter, but it changes the page presentation and cannot be combined with printed backgrounds. Firefox printing help.

Chrome and other browsers

Open the browser’s Print command—commonly Ctrl+P on Windows or Command+P on macOS—and select a PDF destination if available. Browser and operating system controls differ, so use the print preview to confirm the output before saving.

3. Choose settings for a readable client record

Setting	How to choose	Check in the preview
Paper size	Use the size expected by the client or your organization, such as Letter or A4.	Tables and text fit without excessive scaling.
Orientation	Use portrait for ordinary articles. Try landscape for wide tables or layouts.	Columns remain legible and are not clipped.
Margins	Keep enough margin for readable pages and any required annotations.	Text is not cut off at page edges.
Scale	Adjust to fit where useful, but favor readable text over forcing a wide page into a tiny font.	Body text is comfortable to read at normal zoom.
Headers and footers	Enable them if date or page numbers help identify the record. Add the URL and capture context separately when needed.	Headers do not obscure content; source information is present where required.
Background graphics	Enable when color or shaded elements carry meaning and the preview loses them.	Important labels, chart keys, or distinctions remain visible.
Page range	Use all pages unless the client only needs a specified section.	The first and last included pages match the requested scope.

Web content is paginated for paper, so it may break differently than it appears on screen. Chrome’s print documentation describes content being fragmented across printed pages and the use of CSS paged-media rules such as @page to set page size and margins. Browser-generated headers and footers can use print margins too. Chrome print CSS documentation.

4. Inspect and name the PDF

1. Review the preview from the first page through the last. Look for missing sections, blank or mostly blank pages, clipped columns, broken tables, and awkward page breaks.
2. Save the PDF, then reopen it. Check the beginning, middle, and end, plus any tables, links, or other details the client needs.
3. Use a descriptive filename that identifies the client, source, page, and capture date, following the client’s naming rules. For example: ClientName-example-com-page-title-2026-10-04.pdf.
4. Store and share the file according to the client’s access, retention, and confidentiality rules.

Edge can add the current date to the header and page number to the footer. Those details can help identify pages, but they do not by themselves establish the source URL, capture context, or compliance with a client’s recordkeeping standard. Confirm any formal evidence or regulated-documentation requirements with the client.

5. When the browser print view is not enough

If the page is cluttered, try Edge Immersive Reader or Firefox Simplified format when available, then compare the output with the original to ensure the client-relevant material remains. Simplified views can remove navigation and other clutter, but can also alter the presentation; they may not be available for every site. If visual fidelity matters, retain the ordinary print view and adjust its settings instead.

For a page you develop, print-specific CSS can control paper layout. Chrome documents the @page rule for page size and margins and the paged-media model for splitting content into pages. This is useful for building a better print view, but it does not guarantee a third-party page will print exactly as it appears on screen.

Chrome’s chrome.pageCapture extension API saves a tab as MHTML, which packages a page and its resources; it is an archive format, not a PDF-print workflow. Use the browser’s print-to-PDF flow when the required deliverable is PDF. Chrome pageCapture API documentation.

6. Troubleshooting

Problem	Likely cause	What to try
Some sections are missing	Content had not loaded, or the site only reveals it as you scroll.	Wait for loading, scroll through the relevant page content, return to the top, and reopen the print preview.
A table or column is clipped	The page is wider than the selected paper layout.	Try landscape, a suitable paper size, or a less restrictive scale. Check legibility after scaling.
Text is too small	Scale is shrinking a wide layout to fit.	Increase scale and use landscape or accept a multi-page table where possible. Do not prioritize fitting everything onto one page over readable text.
Large blank areas or awkward breaks	The page’s print styles or content layout divide poorly across pages.	Inspect the full preview, adjust scale or margins, and consider a simplified view if it preserves required content.
Colors, charts, or shaded labels disappear	Background printing is disabled or the print view omits those elements.	Enable background graphics if available and review the result. If color carries meaning, verify that it remains clear in the saved PDF.
Navigation or popups dominate the document	The site is presenting screen-oriented content in its print view.	Try a browser’s reading or simplified format if available, then verify that useful context and content have not been removed.
The browser does not offer Save to PDF	The destination depends on the browser and operating system.	Check the system print dialog or available PDF destination. The exact options vary by platform.
The file exists but is incomplete or corrupted	The save may have been interrupted, or the preview was not checked through the final page.	Reopen the file, inspect beginning, middle, and end, and repeat the print flow if pages are missing.

7. Performance, reliability, and recordkeeping

For an ordinary web page, browser Print-to-PDF is a direct workflow and avoids setting up a browser automation script. The time-consuming part is often waiting for dynamic content and reviewing a long preview. Print layout depends on the page’s own styles, browser, and chosen settings, so a saved PDF should be checked rather than assumed to match the screen.

For repeatable client work, use a consistent filename and capture-context note, save to an approved location, and verify important pages and tables before sharing. If the client needs formal evidence, a specific accessibility format, or a retention standard, agree on those requirements first; the browser help sources describe printing controls, not certification or compliance.

Or skip the browser setup

ScreenshotNeo can create a PDF from one API request. The example requests a PDF for a long page; replace the URL with the page you are authorized to capture. See the ScreenshotNeo API documentation for request options.

curl -G "https://api.screenshotneo.com/v1/shot" \
  -d access_key=YOUR_API_KEY \
  --data-urlencode url=https://stripe.com \
  -d format=pdf \
  -o client-page.pdf

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com", "format": "pdf"},
    timeout=90,
)
r.raise_for_status()
with open("client-page.pdf", "wb") as f:
    f.write(r.content)

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://stripe.com',
  format: 'pdf'
});
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`ScreenshotNeo request failed: ${res.status}`);
await Bun.write('client-page.pdf', res);

ScreenshotNeo removes cookie banners, newsletter popups, and chat widgets before the capture. Bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Create a free account and get 1,000 screenshots a month with no card.

FAQ

Can a browser PDF prove exactly what a page showed at a particular time?

A saved PDF records the output you captured, but browser print controls alone do not establish authenticity or satisfy a formal evidence standard. Ask the client what context and handling they require.

Should I print the simplified version?

Use it when readability matters more than the original site presentation, and compare it with the page to ensure it retains the content the client needs.

Does Chrome’s pageCapture API create a PDF?

No. The documented extension API saves a tab as MHTML. Use the browser’s print workflow for a PDF.