Can You Screenshot Multiple Pages at Once?

Yes, with an important distinction. A full-page or scrolling screenshot captures content below the visible screen on one webpage. It does not automatically combine several different URLs or separate document pages. For multiple distinct pages, capture each page separately or export the source as a paginated PDF.

Choose the output first:

What you need	Best output	Why
One webpage from top to bottom	Full-page screenshot	Produces one tall image or long-page capture.
Several separate URLs or screens	Individual screenshots or a batch job	Each page remains a separate, addressable file.
A document with logical pages	Print or export to PDF	Preserves pagination, margins, and print structure.

What “multiple pages” can mean

The phrase usually describes one of two jobs:

1. One long page: A webpage extends below the viewport, and you want a single image containing the whole page.
2. Several pages: You need screenshots of different URLs, routes, app screens, or pages in a document.

These workflows have different limits. A scrolling capture follows one page’s document, while a collection of screenshots requires a separate navigation and capture for every page. An extremely tall image can also be difficult to view, print, or share; a PDF is often better for a document that already has page breaks.

Capture one entire webpage on iPhone

Apple’s iPhone guide documents a Full Page option after taking a screenshot, using a Safari webpage as the example. The exact controls depend on the iPhone model:

1. Open the webpage in Safari and wait for the content you need to load.
2. Take a screenshot. On Face ID models, press the side button and volume-up button together. On models with a Home button, press the side button and Home button together.
3. Tap the screenshot thumbnail before it disappears.
4. Select Full Page.
5. Review the long preview, crop or mark it up if needed, then use the available save or share control on your iOS version.

This is intended for one scrollable webpage. It does not create a set of screenshots for several URLs. Save or export options can vary by iOS release, so check the preview and share sheet on the target device.

Capture several distinct pages

For separate pages, use a repeatable capture list:

1. Make a list of URLs or application routes.
2. Open one page at a time and wait for its content to settle.
3. Capture the page using the normal or full-page mode that matches the page.
4. Name each file with an index and a useful identifier, such as 01-home.png or 02-pricing.png.
5. Review the set for redirects, login screens, cookie dialogs, and pages that did not finish loading.

For a document, use the application’s print or export command when preserving page boundaries matters. Review print preview, page ranges, paper size, margins, and page breaks before saving the PDF.

Desktop browser options

Desktop browser interfaces vary by version. Chrome and Edge developer tools commonly expose a full-size screenshot command, and browser extensions can provide scrolling capture. Treat the labels and locations as version-dependent:

1. Open the page in the browser and allow important content to load.
2. Open developer tools and look for the command that captures a full-size screenshot, or use the browser’s installed full-page capture feature.
3. For several pages, repeat the operation after navigating to each URL.
4. Check the resulting dimensions and file names. A page with a nested scroll container may not behave like a page whose document itself scrolls.

Dynamic pages can change while you capture them. Sticky headers, animations, lazy images, consent dialogs, and internal scrolling panels can all affect the result. If a browser command omits content, wait longer, scroll through the page first, or use a PDF/export workflow.

Android scrolling screenshots

Some Android phones show a Scroll, Capture more, or similar action after a screenshot. Availability and wording depend on Android version and manufacturer:

1. Take a normal screenshot.
2. Look for the scrolling or capture-more control in the screenshot toolbar.
3. Extend the capture through the required content and save it.

These controls are not universal. If the option is missing, use the browser’s full-page feature, capture the page in sections, or export the source as a PDF.

When a PDF is better than one tall image

Use PDF when the source is already paginated or the result will be printed. PDF keeps page boundaries and can support paper size, margins, landscape orientation, and page ranges. A tall image is better for visual reference to one webpage; a PDF is usually easier to search, print, and distribute as a document.

Automate multiple pages with a screenshot API

For recurring captures, automation removes manual navigation. A typical workflow is:

1. Store the URL list and any required authentication data securely.
2. Submit one capture per URL, or use a bulk endpoint when the service supports it.
3. Wait for each response or asynchronous job.
4. Persist the returned image or PDF with a deterministic name.
5. Record status, redirects, and failures so an incomplete batch can be retried.

Account for pages that require login, consent, a custom user agent, a specific timezone, geolocation, or JavaScript interactions. Also decide whether you need a full-page image, a selected element, or a PDF before starting the batch.

Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request returns a PNG, JPEG, WebP, or PDF. It supports full-page capture with lazy images loaded, element capture by CSS selector, PDF paper size and page ranges, custom CSS and JavaScript, clicks, selector or network-idle waits, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, resizing, caching, signed links, asynchronous jobs, webhooks, bulk capture of up to 100 URLs per call, and a usage API. See the ScreenshotNeo API documentation for the available options.

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

To capture several pages, run the request once per URL or use ScreenshotNeo’s bulk capture capability. For a paginated result, request PDF output and set the document options described in the docs. The MCP server also provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.

Reliability, performance, and cost notes

• Wait for the right state: Use a selector wait, delay, or network-idle wait when content is rendered asynchronously.
• Reduce unnecessary work: Block ads, trackers, or selected resource types when they are not part of the page you need.
• Control repeat captures: Choose a cache TTL for pages that do not change often. Use signed links when a public image tag needs temporary access.
• Protect private pages: Pass custom headers, cookies, user-agent values, or Authorization only through a secure server-side workflow.
• Plan batches: Capture independent URLs concurrently within your own rate and resource limits, then retry only failed items.
• Understand billing: ScreenshotNeo bills only clean shots. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and each response reports the result with X-Page-Verdict and X-Billed headers.
• Choose a plan: 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 included on every plan.

Troubleshooting

Problem	Likely cause	Fix
The result contains only the visible screen	Full-page mode was not selected, or the page uses a nested scroll area.	Enable the browser’s full-page option, scroll the internal panel separately, or capture the relevant element.
Several URLs appear as one unexpected image	The workflow treated separate pages as one document.	Capture each URL separately or export the source document to a paginated PDF.
Images or sections are missing	Lazy loading or JavaScript had not completed.	Wait for a selector, add a delay, use network-idle waiting, or scroll the page before capture.
A cookie banner, popup, or chat widget covers content	The page’s consent or promotional UI remained active.	Dismiss it manually, hide the selector, or use ScreenshotNeo, which removes known consent platforms, newsletter popups, and chat widgets before capture.
The output is blank or shows a bot check	The destination blocked automated browsing or failed to load.	Check the URL, authentication, headers, and user agent. With ScreenshotNeo, inspect X-Page-Verdict; these failed results are not billed.
The image is too tall or hard to share	A long webpage was forced into one image.	Capture sections, select an element, or use PDF with page ranges and margins.
Files from a batch are hard to identify	Outputs were saved without stable names.	Use an index plus URL slug, and store the original URL and capture timestamp with each file.

FAQ

Can one screenshot contain several different websites?

Not as a normal full-page capture. Capture each URL separately, then assemble the files or create a PDF if that format suits the result.

Does a full-page screenshot include content below the fold?

It can, when the browser or capture service supports scrolling capture and the content is part of the page document.

Should I use PNG, JPEG, WebP, or PDF?

Use PNG for lossless UI detail, JPEG for smaller photographic images, WebP for a compact modern image, and PDF when page structure or printing matters.

Can I capture pages that require authentication?

Yes, when the browser or service can access the session. Keep cookies, headers, and authorization data on a trusted server and verify that the captured page is the intended account.

What is the simplest automated option?

Use one API request per URL, or a bulk capture feature when available. ScreenshotNeo’s free plan includes 1,000 screenshots per month with no card, and you can sign up free.