How to Screenshot a Webpage on an Apple Device
Learn how to capture a visible screen or an entire Safari webpage on iPhone, iPad, and Mac, plus an automated API option.
Short answer: On iPhone or iPad, take a Safari screenshot, tap the thumbnail, choose Full Page, then save or share it. On Mac, Apple’s Screenshot tools capture the full display, a window, or a selected area; Apple’s documented Mac workflow does not include a full-page webpage mode.
Choose the capture you need
| Device | Visible screen | Entire webpage below the fold | Typical output |
|---|---|---|---|
| iPhone | Yes | Yes, in Safari with Full Page | Image in Photos; full-page captures can be saved or shared from the preview |
| iPad | Yes | Yes, in Safari with Full Page | Image in Photos or PDF in Files |
| Mac | Full screen, window, or selected area | Not documented in Apple’s Screenshot instructions | File on the desktop by default, or another location you choose |
Apple documents full-page Safari capture on iPhone in its iPhone screenshot guide and on iPad in its iPad screenshot guide. The Mac Screenshot guide covers screen, window, and selection capture.
How to screenshot an entire webpage on iPhone
- Open the page in Safari and wait for the content you need to load. Scroll once if you want to trigger lazy-loaded sections before capturing.
- On an iPhone without a Home button, quickly press and release the Side button and Volume Up button together. On a model with a Home button, press and release Side and Home together.
- Tap the screenshot thumbnail that appears in the lower-left corner.
- At the top of the editor, tap Full Page. Safari displays a scrollable preview extending beyond the visible screen.
- Drag the preview to inspect the whole page. Use the crop controls if you only need part of it.
- Use the share or save controls shown by iOS. The regular screenshot is available in Photos; full-page captures may be shared or saved in the format offered by your iOS version.
Apple specifically uses an entire Safari webpage as the example for the Full Page option. If Full Page is missing, you are probably in an app or browser view that does not expose the full-page document, or the page has not finished loading.
Alternative iPhone input methods
Apple also supports screenshots through Siri and AssistiveTouch. On supported iPhone models, you can assign a screenshot action to Back Tap. These methods still produce the same thumbnail workflow, so choose Full Page after the capture.
How to screenshot an entire webpage on iPad
- Open the webpage in Safari and allow images and interactive sections to load.
- On an iPad without a Home button, quickly press and release the Top button and either Volume button together. On an iPad with a Home button, press and release Top and Home together.
- Tap the screenshot thumbnail.
- Choose Full Page to extend the capture beyond the display.
- Review the long preview and crop it if necessary.
- Choose the save destination. Apple documents saving an image to Photos or saving a full-page capture as a PDF to Files.
You can also start a screenshot with Siri or AssistiveTouch. With a compatible Apple Pencil, swipe diagonally upward from either bottom corner to capture the screen, then select Full Page.
How to screenshot a webpage on Mac
Mac’s built-in tools are designed for the screen, a window, or a selected rectangle. Apple’s cited instructions do not promise a Safari full-page webpage capture below the visible area.
- Open the page in your browser and arrange the window.
- Press Shift-Command-5 to open the Screenshot toolbar.
- Choose Capture Entire Screen, Capture Selected Window, or Capture Selected Portion.
- For direct shortcuts, press Shift-Command-3 for the whole screen or Shift-Command-4 for a selected area. After Shift-Command-4, press Space to capture a window.
- Open Options in the Screenshot toolbar to set a timer, choose a save location, or include the pointer.
Shortcut captures go to the desktop by default. Hold Control while using a capture shortcut to copy the result to the clipboard instead. On supported Macs running macOS Tahoe 26 or later, Apple documents SDR/PNG and HDR/HEIF capture choices. Some protected windows, including Apple TV playback, may refuse window capture.
Getting a true full-page capture on Mac
If you need content below the fold on a Mac, the documented Apple Screenshot controls are not enough by themselves. You can use a browser or developer tool that supports page capture, print the page to PDF, or automate a browser. Each approach has tradeoffs:
| Approach | Good for | Common limitation |
|---|---|---|
| Browser full-page tool | One-off captures while developing | Behavior varies by browser and page |
| Print to PDF | Archival documents and readable text | Print CSS can change layout; it is not always a visual screenshot |
| Browser automation | Repeatable workflows and authenticated pages | You must maintain browser binaries, waits, cookies, and rendering code |
| Screenshot API | Server-side jobs, CI, bulk URLs, and apps | Requires an API key and network request |
Make the capture complete and readable
- Wait for lazy content: scroll through the page once on a device, or use a tool that waits for a selector, a delay, or network idle.
- Check consent overlays: cookie dialogs, newsletter forms, and chat bubbles can cover important content. Dismiss them before capturing manually.
- Use the right scope: Full Page captures the document; a screen or selected area captures only what is visible.
- Review the bottom: sticky footers, clipped cards, and unloaded images are easiest to spot at the end of a long preview.
- Choose PDF for documents: On iPad, PDF in Files is often easier to search and share than a very tall image.
- Respect access controls: Do not capture pages or media you are not authorized to access.
Or skip the browser setup
ScreenshotNeo returns a PNG, JPEG, WebP, or PDF from one GET request. Its capture flow accepts cookie and consent banners like a visitor, then removes more than 60 known consent platforms plus newsletter popups and chat widgets before the shot. Each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response reports the result in X-Page-Verdict and X-Billed headers.
See the ScreenshotNeo API documentation for the complete parameter list. This runnable example captures a webpage as WebP:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport 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)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Relevant options include full-page capture with lazy images loaded, CSS-selector element capture, dark mode, 12 device presets or a custom viewport, retina scale, PDF paper size and margins, custom CSS and JavaScript, clicks before capture, hidden selectors, waits, ad/tracker/request blocking, custom headers and cookies, user-agent and Authorization headers, timezone and geolocation, transparent backgrounds, resizing, caching with a TTL you choose, signed image links, asynchronous jobs with signed webhooks, bulk capture for up to 100 URLs per call, and a usage API. ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
There are 1,000 free shots each month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free, and every feature is available on every plan. Create a free ScreenshotNeo account.
Troubleshooting
| Problem | Likely cause | Fix |
|---|---|---|
| No screenshot thumbnail appears | The button combination was held too long or pressed out of sequence | Press and release the required buttons quickly and together; check the model-specific combination. |
| Full Page is unavailable on iPhone or iPad | The content is not in a supported Safari full-page document view | Open the URL directly in Safari, wait for loading to finish, and take the screenshot again. |
| The long capture stops early | Only the visible screen was captured, or the page did not expose additional document content | Select Full Page from the thumbnail and verify the scrollable preview before saving. |
| Images are blank or missing | Lazy loading, a slow connection, or blocked third-party resources | Wait longer, scroll through the page, reload, or use an automated capture with a selector or network-idle wait. |
| Mac capture contains only the viewport | Mac Screenshot captures the screen or window, not a documented full webpage | Use a browser page-capture workflow, print to PDF, browser automation, or ScreenshotNeo. |
| A Mac window will not capture | The app protects its content | Capture an allowed area or use the app’s own export feature; Apple lists Apple TV as an example of protected content. |
| ScreenshotNeo returns a bot-check or blank-page verdict | The target site blocked automation or failed to render | Inspect X-Page-Verdict; adjust headers, cookies, user-agent, waits, or authentication. These failed results are not billed. |
| ScreenshotNeo request times out | The page is slow, blocked, or waiting on resources | Use a longer client timeout, block unnecessary resource types, wait for a specific selector, or capture a simpler route. |
Performance, reliability, and cost notes
- Device captures: Long pages require more preview space and storage. Review the bottom of the capture before sharing, especially when the page contains lazy images or sticky elements.
- Mac workflows: Screen capture is immediate, but it cannot reliably represent content that has not been rendered below the viewport.
- Automated captures: Deterministic waits, fixed viewport and device settings, explicit cookies, and request blocking reduce layout variation and speed up repeated jobs.
- Caching: ScreenshotNeo lets you choose a cache TTL. Reusing an unchanged capture can reduce latency and usage.
- Billing: Only clean shots are billed. Cache hits, failed loads, timeouts, blank pages, and bot checks do not consume paid shots, with the outcome exposed in response headers.
- Scaling: Use asynchronous jobs and signed webhooks for slow pages, and bulk capture for up to 100 URLs per call. Check the usage API before large runs.
FAQ
Can I screenshot an entire webpage from an iPhone?
Yes. In Safari, take a screenshot, tap its thumbnail, choose Full Page, then save or share the result.
Does iPad save a full webpage as an image?
It can save an image to Photos, and Apple also documents saving a full-page capture as a PDF to Files.
Does Shift-Command-3 capture an entire webpage on Mac?
No. It captures the entire Mac display. Apple’s documented Mac controls do not provide a full-page webpage mode.
What is the best format for a very long page?
Use an image when visual fidelity matters and a PDF when the result needs document-style sharing, printing, or filing.
Can I automate Apple-device-style webpage screenshots?
Yes. A browser automation library or ScreenshotNeo can render a URL with a chosen viewport, waits, cookies, headers, and output format without operating a physical Apple device.
