How to Take a Screenshot Larger Than Your Screen
Capture webpages and scrollable apps beyond the visible screen on Firefox, Edge, Android, iPhone, or with ScreenshotNeo.
To capture content larger than your screen, use a full-page or scrolling screenshot tool. For webpages, Firefox and Edge can capture the entire page in one image. Android and iPhone offer scrolling or Full Page capture on supported screens. For desktop applications that do not support native capture, use a scrolling-capture utility or export a PDF when a tall bitmap is not the best format.
First identify two things: your platform and whether you are capturing a webpage or an app window. Browser full-page tools are designed for webpages; support for desktop applications varies by app and capture utility.
Choose the right method
| Target | Best first option | Output | Limit |
|---|---|---|---|
| Webpage in Firefox | Take Screenshot → Save full page | Tall image or clipboard image | Designed for browser pages |
| Webpage in Edge | Screenshot → Capture full page | Image with optional markup | Designed for browser pages |
| Scrollable Android app | Scrolling screenshot / Capture more | Extended image | Android 12+ on most scrollable screens |
| Safari webpage on iPhone | Screenshot → Full Page | Image or PDF in Files | Full Page appears only where supported |
| Unsupported desktop app | Scrolling-capture utility | Tall image | Compatibility depends on the app and utility |
| Long document for printing or search | PDF export | Paginated, searchable document | Not a single tall bitmap |
Firefox: save a full webpage
- Open the webpage in Firefox.
- Right-click an empty area of the page and choose Take Screenshot. You can also press Ctrl+Shift+S on Windows or Linux, or Command+Shift+S on macOS.
- Select Save full page.
- Choose Download to save the image, or Copy to place it on the clipboard.
Firefox can also capture a selected region, an automatically highlighted page element, or only the visible area. Full-page capture is the option that extends beyond the current viewport. Mozilla says the feature collects interaction events such as using Copy or Save full page, but not the URL or details of the image captured. See Mozilla’s Firefox screenshot guide.
Microsoft Edge: capture the entire webpage
- Open the page in Edge.
- Press Ctrl+Shift+S, or open the browser’s Screenshot tool.
- Choose Capture full page.
- Review the result, add drawing or markup if needed, then copy or save it.
Edge’s tool is intended for webpage capture, including content below the visible screen. Details are in Microsoft’s Screenshot Tool documentation.
Android: take a scrolling screenshot
Google documents scrolling screenshots on devices running Android 12 and later on most screens that allow scrolling. The exact buttons differ by manufacturer.
- Open the screen you want to capture.
- Take a normal screenshot using your phone’s hardware-button or system gesture.
- When the preview appears, tap the scrolling, Capture more, or similarly named control if it is offered.
- Extend the selected area to include the content you need, then save.
The option is not guaranteed for every app, handset, or screen. If it does not appear, check the device manufacturer’s support instructions. On Xiaomi devices, the documented workflow is to take a screenshot, tap Scroll, let the page continue or choose the endpoint, tap DONE, and save. Xiaomi notes that Gallery Editor permissions may be needed to view and save the result; those button names are not universal Android controls. See Google Android Help and Xiaomi’s scrolling screenshot instructions.
iPhone: use Full Page capture
- Take a screenshot by quickly pressing the side button and volume-up button together. On an iPhone with a Home button, press the side button and Home button together.
- Tap the screenshot thumbnail to open the editing controls.
- Choose Full Page when it is available.
- Crop or annotate if needed.
- Save the result to Photos, or save the full-page capture as a PDF to Files.
Apple’s example is a complete webpage in Safari. Full Page is shown only for content that supports it. Read Apple’s iPhone screenshot guide.
Capturing a desktop app or an unsupported window
Native browser commands may fail when the target is a desktop application, a canvas, a virtualized list, or a page that changes while you scroll. A scrolling-capture utility can stitch several viewport captures together, but support is application-specific.
- Make the application window larger before starting.
- Keep the window at a stable zoom level and avoid moving the pointer over content that triggers hover changes.
- Try another browser when the target is a website and the first browser cannot detect the page boundaries.
- Check the utility’s supported applications and operating systems. TechSmith documents scrolling-capture troubleshooting for Snagit, while Zight documents a macOS workflow that currently works in Chrome as other applications are expanded.
Sources: TechSmith scrolling-capture troubleshooting and Zight’s long-page capture guidance.
When a PDF is better than one tall image
Choose a PDF when the result will be printed, searched, shared as a document, or read page by page. A single very tall bitmap can be difficult to open, zoom, annotate, or print. On iPhone, Apple’s Full Page workflow can save the capture as a PDF to Files. For webpages, the browser’s print dialog can also produce a paginated document when the page supports printing.
Quality checklist before saving
- Confirm that the page or app has finished loading.
- Scroll once through lazy-loaded sections if the capture tool does not load them automatically.
- Close menus, hover tooltips, chat panels, and temporary notifications.
- Use a consistent zoom level and window width.
- Check the bottom of the result for clipped content or a repeated section.
- For sensitive pages, verify that account details and private data are not included.
- Use PDF when a tall image would exceed your editor’s memory or become hard to navigate.
Troubleshooting common failures
| Symptom | Likely cause | Fix |
|---|---|---|
| No full-page option | The browser, app, or screen does not expose a scrollable document | Try the page in Firefox or Edge, use the platform’s scrolling control, or use a utility that supports the application. |
| Only the visible viewport is saved | Visible-area mode was selected | Choose Save full page, Capture full page, Full Page, or Capture more. |
| Bottom sections are blank | Lazy-loaded content did not render before capture | Scroll through the page first, wait for images to load, then capture again. |
| Sections repeat or seams are visible | Content moved while the tool stitched scroll positions | Stop animations, close sticky overlays, maximize the window, and retry at a stable zoom. |
| Capture stops partway through | The app blocks scrolling capture, the page is unusually long, or the utility hit a limit | Capture in smaller sections, export a PDF, or use a tool with documented support for that app. |
| Android scrolling control is missing | The device or app does not support extended capture | Update the device if possible, try another screen, or follow the manufacturer’s instructions. |
| iPhone Full Page is missing | The current app or content does not support it | Open the content in Safari when appropriate, or save separate screenshots/PDF pages. |
| File is too large to open | A very tall bitmap consumes substantial memory | Resize or compress it, split it into sections, or use a PDF. |
Performance, reliability, and file-size considerations
Full-page capture takes longer than a viewport screenshot because the tool must render or scroll additional content. Pages with video, animations, ads, infinite scroll, or network-loaded images are more likely to change during capture. For repeatable results, use a fixed viewport, wait for the page to settle, disable motion where possible, and capture at the same zoom and device scale each time.
Very long pages produce large image files. PNG preserves sharp text and transparency but is often larger; JPEG is smaller for photographic content; WebP can reduce size when your workflow supports it. If you need searchable text, selectable content, or predictable printing, use a PDF instead of increasing the bitmap dimensions indefinitely.
Or skip the browser setup
ScreenshotNeo captures a webpage with one API request and can return PNG, JPEG, WebP, or PDF. It supports full-page capture with lazy images loaded, element capture by CSS selector, custom viewport and device presets, retina scale, waits for selectors, delays or network idle, custom CSS and JavaScript, cookies and headers, blocking rules, resizing, caching, signed links, asynchronous jobs, bulk capture, and PDF options. See the ScreenshotNeo API documentation for request parameters.
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}`);Cookie banners, newsletter popups, and chat widgets are removed before the shot. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and the response identifies the page verdict and billing result with X-Page-Verdict and X-Billed headers. ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots each month with no card; paid plans start at $5 for 3,000 shots.
Create a free ScreenshotNeo account and start with 1,000 screenshots a month at no charge.
FAQ
Can I capture an entire webpage as one image?
Yes. Use Firefox Save full page, Edge Capture full page, or an API such as ScreenshotNeo. For very long pages, a PDF or several sections may be easier to use.
Why does scrolling capture work in a browser but not my app?
Browser tools know the page’s document structure. Desktop apps may render custom canvases, virtualized lists, or protected surfaces that do not expose one scrollable document.
Is a scrolling screenshot the same as a screen recording?
No. A scrolling screenshot is a still image assembled from content beyond the visible viewport. A screen recording preserves motion over time.
What should I use for a page that keeps loading more items?
Stop loading at a defined point, capture a bounded section, or use a capture API that can wait for a selector or network idle and then save a deterministic result.
How do I avoid capturing private information?
Review the page before saving, sign out when possible, hide sensitive selectors, and store the resulting image or PDF with the same access controls as the source.
