How to Save a Full-Page Screenshot as PDF or PNG

A full-page screenshot captures content below the visible viewport. Saving it as a PNG and saving it as a PDF are separate operations: a browser workflow that downloads one format does not automatically provide the other.

For a PNG image on desktop, Firefox documents a built-in Save full page capture. For a PDF on an iPhone, Safari’s documented full-page screenshot flow saves to Files as a PDF. Microsoft Edge documents full-page capture and saving to files, but the cited page does not specify the exported extension.

Choose the route that matches your output

Route	Full-page capture	Format explicitly documented	Best fit
Firefox desktop	Yes	Image download; Mozilla’s example filename ends in `.png`	PNG image without installing an extension
Microsoft Edge	Yes	Save to files; extension not specified	Full-page capture with optional markup
iPhone screenshot	Yes	PDF to Files	PDF of a Safari page
Firefox for iOS	Yes	Save as PDF	PDF from Firefox on iPhone
ScreenshotNeo API	Yes	PNG, JPEG, WebP or PDF	Repeatable or automated captures

Save a full-page screenshot as PNG in Firefox desktop

Open the webpage in Firefox.
Right-click an empty part of the page and choose Take Screenshot. You can also use Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on macOS.
Select Save full page.
Download the image. Mozilla’s documented example uses the .png extension.

Firefox also offers visible-area and selected-region captures. Use those when you do not need content below the viewport. Menu names and shortcuts can change between Firefox releases, so check the current interface if the command is missing.

When Firefox’s full-page image is not what you need

If the page uses lazy-loaded content, scroll through it first so content is present before capture.
If a fixed header repeats over every section, inspect the result and crop it in an image editor if necessary.
For a document that must paginate or print cleanly, use a PDF workflow instead of treating a very tall PNG as a document.

Capture and save a full webpage in Microsoft Edge

Open the page in Edge.
Press Ctrl+Shift+S, or open the right-click menu and choose Screenshot.
Choose Capture full page.
Use the overlay to annotate if needed, then save the capture to files.

Microsoft also documents selected-area capture and markup. The feature page warns that availability and functionality can vary by device type, market and browser version. It does not identify the saved image’s file extension, so verify the format after saving rather than assuming it is PNG.

Save a full-page webpage as PDF on iPhone

In Safari, open the webpage.
Take a screenshot. On iPhones with Face ID, press and release the Side and Volume Up buttons together. On an iPhone with a Home button, press and release Home and Side together.
Tap the screenshot preview.
Tap Full Page.
Choose Save PDF to Files, select a folder and tap Save.

Apple documents this route for content beyond the screen, including an entire webpage in Safari. The documented export is PDF; it is not a PNG save path. Button combinations depend on the iPhone model.

Save a full-page webpage as PDF in Firefox for iOS

Open the webpage in Firefox for iOS.
Take a screenshot with the iPhone’s hardware buttons.
Open the screenshot preview and select Full Page.
Tap Done, then choose Save as PDF.

Mozilla’s guide for Firefox on iOS is older than Apple’s current iOS guide. Confirm the labels in the versions installed on your device before following a team procedure.

PNG versus PDF: which should you use?

PNG: best when another tool needs an image, when you want pixel-level editing, or when you need a single raster asset. A very long page can create a large image and large memory footprint.
PDF: best for sharing, printing, archiving or adding document metadata. Pagination, margins and selectable text depend on the capture workflow.

Do not rename a PNG to .pdf or a PDF to .png; the container and encoding remain unchanged. Use a workflow that explicitly exports the format you need.

Optional browser extension

A third-party extension can add full-page capture and advertise PNG and PDF export. Before installing one, verify its currently supported browsers, permissions, privacy terms, whether processing happens locally or remotely, export limits and price. The cited store listing establishes that such an extension is available, but does not establish affiliate availability or those details for every version.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a clean PNG, JPEG, WebP or PDF, with full-page capture available. See the ScreenshotNeo documentation for the complete parameter list.

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}`);

Adapt the URL and output handling to request the format and options your job needs. ScreenshotNeo can accept cookie and consent banners like a visitor, remove more than 60 known consent platforms plus newsletter popups and chat widgets, and lets you turn each cleanup step off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing; response headers identify the page verdict and whether the request was billed. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.

You also get full-page capture with lazy images loaded, CSS-element capture, dark mode, device presets or custom viewports, retina scale, PDF paper size, margins, landscape mode and page ranges. Other controls include custom CSS and JavaScript, clicks before capture, selector hiding, waits, ad/tracker/request blocking, headers, cookies, user agent, Authorization, timezone, geolocation, transparent backgrounds, resizing, caching with a chosen TTL, signed links, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, a usage API and an OpenAPI specification.

There are 1,000 free screenshots each month with no card. Paid plans start at $5 for 3,000 screenshots, and every feature is available on every plan. Create a free ScreenshotNeo account.

Troubleshooting

Symptom	Likely cause	Fix
The capture stops at the visible viewport	The visible-area mode was selected.	Choose Firefox’s Save full page, Edge’s Capture full page or the device’s Full Page option.
The output format is wrong	Full-page capture and file format were treated as the same feature.	Use Firefox for the documented PNG image path or iPhone/Firefox for iOS for the documented PDF path. Confirm an Edge file’s extension after saving.
Images or sections are missing	Lazy loading has not run before capture.	Scroll through the page first, or use an API option that loads lazy images before a full-page capture.
A consent banner, popup or chat bubble covers content	The page rendered visitor-facing overlays.	Dismiss overlays before a manual capture. ScreenshotNeo can accept the consent banner and remove supported consent platforms, newsletter popups and chat widgets before capture.
The browser command is unavailable	Browser version, device, market or interface differences.	Update the browser and check its current Screenshot help. Edge specifically notes that availability can vary.
The page is blank or times out in an automated capture	The target failed to load, is blocked or requires more time.	Check the URL and access requirements, then use waits, headers, cookies, user agent or request blocking as appropriate. ScreenshotNeo reports verdict and billing headers for each response.

Performance, reliability and cost considerations

Very long pages: a single PNG becomes taller and larger as content grows. A PDF can be easier to distribute, but pagination may differ from the screen layout.
Dynamic content: capture after the page reaches the needed state. For automation, wait for a selector, a delay or network idle and hide or click elements when required.
Repeat jobs: caching with a chosen TTL can avoid unnecessary recaptures. Signed links, asynchronous jobs and webhooks help when a capture should be consumed later.
Billing: ScreenshotNeo bills only clean shots. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and the response states the verdict and billing result.
Capacity: bulk capture supports up to 100 URLs per call. Use the usage API to monitor consumption and choose a plan that matches volume.

FAQ

Can I save a full-page screenshot as both PDF and PNG?

Yes, but make two exports or use a tool that explicitly supports both formats. The documented Firefox desktop route is an image download, while Apple’s iPhone route is PDF to Files.

Does an iPhone full-page screenshot create a PNG?

The documented iPhone Full Page workflow saves a PDF to Files. It should not be described as a PNG export.

Does Edge guarantee PNG output?

The cited Edge page documents full-page capture and saving to files but does not name the file extension. Check the saved file or use a route with an explicitly documented format.

Do I need a physical accessory?

No. Firefox, Edge and iPhone use built-in software. An extension or API is optional.

Can an API capture only one part of a page?

ScreenshotNeo supports capturing one element by CSS selector as well as full-page capture, so you can choose the page region that matters.