How to Convert a Webpage to PDF from a URL in Windows

To save a webpage from a URL as a PDF in Windows, open it in Microsoft Edge or Google Chrome, press Ctrl+P, choose the PDF destination, review the print preview, and save. Edge and Chrome both document this browser print workflow. The exact PDF destination label can vary by browser version and system print options. Microsoft’s Edge print instructions and Google’s Chrome print instructions explain the available steps.

Save a webpage as PDF in Microsoft Edge

Open Edge and navigate to the webpage you want to save.
Press Ctrl+P, or open Settings and more and choose Print.
In the print preview, choose the PDF destination available on your system. If the destination is not shown in the first preview, use the option to open the system print dialog and look for a PDF printer.
Review the pages and layout settings, then choose Print or Save, depending on the destination.
Choose a folder and filename, then save the PDF.

Edge’s preview can provide controls for page range, margins, scale, headers and footers, and background graphics. The choices shown can depend on the current page and Edge version. Use the preview to confirm the resulting page count and layout before saving.

Make an Edge printout easier to read

For a text-focused result, try Edge’s Immersive Reader before printing when the page supports it. Microsoft notes that this feature is not available on every website. It can simplify the reading view, but check that headings, links, and other details you need remain present before saving.

Save a webpage as PDF in Google Chrome

Open Chrome on your Windows computer and navigate to the webpage.
Press Ctrl+P to open print preview.
In the destination selector, choose Save as PDF.
Review the preview and available layout options.
Choose Save, select a folder and filename, then save the PDF.

Chrome’s documented computer workflow uses Ctrl+P and the Save as PDF destination. If your system or browser presents a different print dialog, select an available PDF destination rather than a physical printer.

Choose settings that produce a readable PDF

Webpages are designed to scroll and adapt to screen width; a PDF divides that content into fixed pages. Inspect the preview before saving, especially for long articles, tables, navigation-heavy pages, and content with large images.

Page range: Save only the pages you need when the preview offers page selection.
Margins: Adjust margins if text is clipped or the page looks too crowded.
Scale: Reduce scale if wide content is cut off; avoid making text too small to read.
Headers and footers: Turn these off for a cleaner page when they add unwanted browser-generated details. Leave them on if printed page numbers or page details help.
Background graphics: Enable this option when the page’s colors or backgrounds carry useful information and the preview omits them.
Orientation: Use landscape for wide tables or diagrams if the print preview offers that setting.

Browser print output may differ from the live webpage because websites can use print-specific styles or load content as you scroll. If an important section is missing, scroll through the page first to let visible content load, then reopen print preview. For a simpler article layout, Edge Immersive Reader is an option on eligible sites.

Use Windows’ PDF printer when needed

If the browser preview does not show a direct save destination, check the system print dialog for a PDF printer, such as Microsoft Print to PDF where available. Select it as the printer and complete the print flow, then choose the output location if prompted. The exact labels depend on Windows and browser configuration. No physical printer is required when using a PDF destination.

Automate webpage-to-PDF capture from a URL

The browser steps above are appropriate for an occasional page. For repeatable captures, a script or screenshot API can request a URL and return a PDF. Automation is useful when you need to process many pages, control capture options consistently, or connect capture to an application. Make sure you have permission to access and archive the target pages.

ScreenshotNeo API: one request for a PDF

ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. Its API accepts a URL and returns a screenshot or PDF. See the ScreenshotNeo API documentation for the PDF parameters and response details. Replace the example URL with the page you need and supply your API key.

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

import requests

response = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={
        "access_key": "YOUR_API_KEY",
        "url": "https://stripe.com",
        "format": "pdf",
    },
    timeout=90,
)
response.raise_for_status()
with open("page.pdf", "wb") as pdf_file:
    pdf_file.write(response.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(`Capture failed: HTTP ${res.status}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('page.pdf', bytes));

These examples request PDF output with format=pdf. For protected pages, the API also supports custom headers, cookies, user agents, and Authorization; use only credentials you are authorized to use, and avoid putting secrets in URLs or logs. Other relevant capture controls include waiting for a selector, a delay or network idle; custom CSS and JavaScript; page ranges, paper size, margins and landscape PDF settings; and blocking requests or resource types. The parameter names used by other screenshot APIs also work to ease migration. Check the docs for exact parameter names and accepted values.

Practical PDF capture considerations

Dynamic pages: A page may need time or a specific selector to appear before capture. Choose an appropriate wait condition instead of assuming every site is ready immediately.
Long pages: Lazy-loaded images or sections may not appear until the page is scrolled or the capture option loads them. Check the resulting PDF for missing content.
Page layout: Use PDF paper size, margins, orientation, and page ranges when the default pagination does not fit your use case.
Failures and retries: Distinguish an HTTP/API error from a PDF document response. Check the response status and capture verdict before treating returned bytes as a valid PDF.
Cost: ScreenshotNeo bills only clean shots; bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing. Responses include X-Page-Verdict and X-Billed headers. Free includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Yearly billing gives two months free, and every feature is on every plan.

Or skip the browser setup

Send one request to ScreenshotNeo to create a PDF from a URL. Cookie banners are accepted like a visitor and more than 60 known consent platforms, newsletter popups, and chat widgets are removed before the shot; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are never billed. An MCP server lets AI agents, including Claude and Cursor, take screenshots. The free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000.

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

Read the API docs and ScreenshotNeo, then sign up for 1,000 free screenshots a month with no card.

Troubleshooting

Problem	Likely cause	What to try
The PDF option is missing	The browser opened a system print dialog or your available destinations differ.	Look for a PDF printer in the system dialog, such as Microsoft Print to PDF where available. In Chrome, use Save as PDF when it appears.
The preview is blank or does not finish	The page, browser, print component, or connection may be having trouble.	Retry, restart the browser, and test another website or online document. If another page prints, the original page may be the issue. Microsoft’s Edge print troubleshooting guide suggests checking the site or document, Edge, the printer driver, Windows, and connectivity or hardware.
Text or images are clipped	The page’s dimensions do not fit the chosen paper size, scale, or margins.	Adjust scale and margins, try landscape for wide content, and inspect the preview again.
Colors or backgrounds are absent	Background graphics may be disabled or omitted by the print styling.	Enable background graphics if the setting is available. Confirm the preview reflects the intended result.
Some content is missing	The page may load content dynamically, use print-specific styles, or defer images until scrolling.	Scroll the page to load more content and retry. In Edge, try Immersive Reader where available for a simpler text view.
An automated capture returns an error instead of a PDF	The request may have invalid parameters, missing authorization, or a page-load failure.	Check the API response status, key, URL encoding, and documented PDF parameter. Review `X-Page-Verdict` and `X-Billed` on ScreenshotNeo responses; allow an appropriate timeout and wait condition for dynamic pages.

Frequently asked questions

Can I convert a URL to PDF without installing software?

Yes. Edge or Chrome can open the URL and print to a PDF destination using the browser print workflow.

Does converting to PDF require a physical printer?

No. Choose a PDF destination such as Save as PDF or an available PDF printer.

Can I save only selected pages?

Yes, when the print preview offers a page-range control. Enter the pages you want before saving.

Why does the PDF look different from the website?

A webpage is reflowed for paper, and the site may apply print-specific styling. Use the preview to adjust layout and check whether the page has loaded all required content.