How to Save a Webpage as PDF When the Print Dialog Hangs

If a browser’s print preview hangs, first cancel it if it still responds, reopen the page, and retry. If it hangs again, test another page in the same browser, try the browser’s system print dialog, or save the page through another browser’s built-in PDF destination. You do not need a physical printer to save a webpage as a PDF.

Use this sequence to narrow down the cause: a failure on one page points toward that page’s content or print styles; a failure on every page in one browser points toward the browser or its print path; failures from other applications too suggest an operating-system, driver, device, or connection problem.

1. Recover the current print preview

1. Cancel the preview if its controls still respond. Return to the page and open Print again.
2. Retry once. A transient preview failure may clear on a new attempt.
3. Restart the browser if retrying does not work. In Edge, Microsoft specifically recommends retrying or closing Edge and starting a new session when preview fails. Save any other work first.
4. Check the destination. If Edge says “Print preview failed,” select another available printer or PDF destination if one is listed, then reopen the dialog.

If the entire browser is unresponsive, the cancel control may not work. Closing an unresponsive browser can lose unsaved work in other tabs, so use that only when necessary.

2. Check whether the problem is the page, browser, or system

1. Try printing a different webpage or online document in the same browser.
2. If that works, return to the original page. Its graphics, fonts, scripts, or print styles may be triggering the failure or making preview slow.
3. Try printing from another application. If that also fails, investigate the operating system, printer or PDF driver, device, and connectivity.
4. If another browser can save the original page as PDF, use it as a workaround. That result alone does not prove the first browser is defective; browsers may handle a page’s print content differently.

Microsoft notes that an Edge print issue can have several causes, including the document, browser, printer driver, operating system, connectivity, or hardware. A driver can also affect one application differently from another. Use the comparisons above to narrow the fault before changing system settings. Microsoft’s Edge print troubleshooting guide describes this diagnostic approach.

3. Use the browser’s built-in Save as PDF route

Browser labels and available destinations can vary by version and operating system. The core process is to open Print, choose a PDF destination, adjust the output settings, and save the resulting file.

Chrome on desktop

1. Open the page and press Ctrl+P on Windows or Linux, or Command+P on Mac.
2. In the print window, choose the PDF destination, such as Save as PDF.
3. Set the pages, layout, and other available options, then save the file.

Chrome also documents saving to Google Drive when the relevant extension is installed. You can instead save a PDF locally and upload it to Drive. See Chrome’s instructions for printing from Chrome.

Firefox

1. Open the menu and choose Print.
2. In the preview, choose Save to PDF from the Destination dropdown.
3. Review pages, orientation, margins, paper size, scale, and headers or footers, then save.

Firefox may offer a Simplified format. Use it when available if navigation, sidebars, or other page clutter makes the output hard to read. It is not offered for every page. See Mozilla’s guide to printing web pages in Firefox.

Microsoft Edge

1. Open the page and press Ctrl+P on Windows or Command+P on macOS. You can also right-click the page and choose Print.
2. Choose the PDF destination and adjust the available print settings.
3. Save the file.

For an alternate print path, choose Print using system dialog in Edge’s print interface. Microsoft lists Ctrl+Shift+P on Windows and Option+Command+P on macOS as direct shortcuts to the system dialog. If the command is not visible, look in the print interface’s additional options. See Microsoft’s Edge print instructions.

4. Try the system dialog or simplify the page

The system dialog provides a different route through the operating system. In Edge, open Print and choose Print using system dialog, or use the platform shortcut above. This can help determine whether the issue is specific to Edge’s own preview. It does not guarantee the system dialog will work if the underlying PDF destination or driver is unavailable.

If the original page’s layout appears to be the problem, try a cleaner reading view where available:

• Edge: Microsoft suggests Immersive Reader for eligible pages, then printing from that view.
• Firefox: Choose Simplified format when the preview offers it.

These modes can remove page clutter, but the PDF may not preserve the original visual design. If exact layout matters, first retry the normal page in another browser and compare the results.

5. Troubleshoot common errors

Symptom	Likely scope	What to try
Preview spins or freezes on one page	Page content, graphics, fonts, scripts, or print styles	Cancel and retry; test another page; use another browser’s PDF destination; try a simplified reading view if offered.
Preview fails on every page in Edge	Edge’s preview path, destination, or a system component	Retry or restart Edge; choose another available printer or PDF destination; try Print using system dialog. Microsoft also lists a missing built-in PDF viewer among possible reasons Edge may fail to show preview.
The system dialog opens, but no PDF destination appears	Operating-system PDF destination or installed printer configuration	Return to the browser’s built-in Save as PDF destination or try another browser. If other apps also cannot print, investigate the system’s printer and PDF setup.
Other applications also cannot print	Operating system, driver, hardware, or connectivity	Check whether the destination is available and connected; investigate the printer or PDF driver and system-level print setup.
PDF saves, but content is missing or looks different	Page print layout or browser-specific rendering	Review page range, scale, margins, and orientation; try another browser; use Simplified format or Immersive Reader if available and acceptable.
Retrying does not change the failure	Persistent page or browser/system issue	Compare another page, another application, and another browser to identify which layer is common to the failure.

Browser support instructions describe diagnostic steps, not guaranteed fixes. Avoid concluding that a printer driver is faulty from a single failed page or browser.

6. Preserve long or complex pages reliably

• Choose the output before saving. Confirm destination, page range, paper size, orientation, scale, margins, and headers or footers in the preview.
• Check long pages in sections. If a page has lazy-loaded content or infinite scrolling, move through it first so the content you need has a chance to load. Browser print output can still differ from the live page.
• Keep a second copy when the record matters. Save the PDF and verify that it opens and contains the expected pages before closing the source page.
• Do not assume a visual match. Print CSS and browser rendering can omit interactive elements or reflow the layout. If a clean reading copy is more useful than a faithful visual copy, try the simplified view.

7. Or skip the browser setup

If browser print preview keeps failing, ScreenshotNeo can capture a page as a PDF through one API request. It is a website screenshot API and MCP server for developers. This route renders the page independently of your local browser print dialog.

For the API options and configuration, see the ScreenshotNeo documentation.

cURL

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

Python

import requests

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

Node.js

const q = new URLSearchParams({
  access_key: 'YOUR_API_KEY',
  url: 'https://example.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}`);
const bytes = new Uint8Array(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('page.pdf', bytes));

Replace https://example.com with the page you need and YOUR_API_KEY with your key. ScreenshotNeo accepts cookie or consent banners as a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000, and every feature is on every plan.

Sign up for 1,000 free screenshots a month, with no card required.

8. Performance, reliability, and cost

The built-in browser route has no API usage fee, but it depends on the page, browser preview, and local print path working. A complex page may take longer to render or may fail only in one browser. Testing a second page and a second application helps avoid spending time changing the wrong component.

An API route adds a per-request service and requires an API key, but it avoids configuring a local browser print dialog. ScreenshotNeo’s billing rules mean bot checks, blank pages, timeouts, failed loads, and cache hits are not billed; check the response’s X-Page-Verdict and X-Billed headers to see the reported outcome. Free usage is 1,000 shots per month; paid tiers range from $5 for 3,000 to $249 for 1,000,000, with two months free on yearly billing. These are service plan prices, not a claim that API capture is always faster than browser printing.

FAQ

Can I save a webpage as a PDF without printing it?

Yes. Choose a PDF destination such as Save as PDF or Save to PDF in the browser print workflow. No physical printer is needed.

Will switching browsers prove which one is broken?

No. A second browser is a useful comparison and workaround, but different browsers can render the same page differently.

Will a simplified reader view preserve the page’s design?

Usually its purpose is to reduce clutter, so use it when readability matters more than matching the original layout. Availability depends on the page and browser.

What should I try if only one site hangs?

Retry the page, compare it with another browser, and use a simplified reading view if available. That helps distinguish page-specific print behavior from a browser-wide issue.