Start by identifying what “full-size” means. If you need an image of an entire web page, use Chrome DevTools’ full-page command or Firefox Developer Tools’ entire-page button—not an area or viewport capture. If only an area capture fails in Chrome, dock DevTools first; Chrome documents that area capture does not work while DevTools is undocked. If you mean a scrolling screenshot on a phone or a full-resolution device image, use the device-specific path for that phone because the browser procedures below solve webpage captures.
First, identify the screenshot you are trying to make
“Full-size screenshot” can describe three different outputs:
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Full Stack Web Development: A Comprehensive, Hands-On Guide to Building Modern Websites and... | $44.80 | Buy on Amazon |
- Full-page webpage capture: one image containing the document from top to bottom, including content below the visible window.
- Area capture: a selected rectangle of the page.
- Device or phone screenshot: an operating-system image, sometimes with a scrolling or “capture more” option.
This guide focuses on the first meaning, because Chrome and Firefox provide documented developer-tool workflows for it. A normal viewport screenshot is not a failed full-page capture; it is simply a different command. Before changing settings, note the browser, operating system or phone model, exact command used, and whether the result is cropped, missing content, or not saved. Those details distinguish a scope mistake from a capture failure.
Use Chrome’s full-page capture workflow
Chrome DevTools offers several screenshot types, including full-page, node, and area captures. Use the Command Menu so you select the scope explicitly.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Open the webpage you want to capture.
- Open DevTools with F12 or Control+Shift+I on Windows/Linux. On macOS, use Command+Option+I.
- Open the Command Menu with Control+Shift+P on Windows/Linux or Command+Shift+P on Mac.
- Type screenshot.
- Choose the command whose name specifies a full-page capture. Do not choose an area or visible-viewport command when you need the whole document.
- Wait for Chrome to finish creating the image, then check the downloaded file and its dimensions.
These commands are described in Chrome for Developers’ “Run commands in the Command Menu” (updated September 4, 2024) and “4 ways to capture screenshots with DevTools” (updated August 9, 2024). The command names can vary slightly as Chrome’s interface changes, so the word screenshot is the reliable way to find the current choices.
If Chrome captures only the visible region
- Repeat the Command Menu search and select the full-page command, not “capture area” or a visible-viewport option.
- Confirm that the page itself extends beyond the viewport. A short page produces an image that is legitimately close to the window size.
- Reload the page and wait for the content you need to appear before opening the Command Menu. Record whether the problem is missing content or merely a shorter-than-expected document; Chrome’s documentation does not identify a universal root cause for every cropped result.
If you selected area capture and it does nothing
Dock DevTools to the browser window and try again. Chrome explicitly documents that area capture does not work when DevTools is undocked. This is a restriction on area capture, not proof that undocking causes every full-page failure.
Retry with Firefox Developer Tools
Firefox has a separate built-in entire-page capture. Mozilla’s “Taking screenshots” documentation says the screenshot icon may need to be enabled before it appears.
- Open the page in Firefox and open Developer Tools.
- Open the toolbox settings. Under Available Toolbox Buttons, enable Take a screenshot of the entire page if the button is missing.
- Click the screenshot button and choose the entire-page action.
- Check the resulting image. Firefox documents that the file is saved to the browser’s Downloads directory by default.
Firefox is a useful cross-check: if the same page captures correctly there, the issue is likely specific to the Chrome command or page state rather than a general inability to render the document.
Work through the symptom instead of guessing the cause
The image contains only the viewport
Verify the capture scope first. In Chrome, reopen the Command Menu and select full-page; in Firefox, use the entire-page button. An area or visible-viewport command cannot produce a document-length image.
Some page content is absent
Write down what is missing: text, images, an embedded frame, or content that appears only after interaction. Reload, allow the page to finish its normal loading sequence, and capture again. If the content requires a click, perform that click before invoking the screenshot command. The available documentation does not establish one universal missing-content bug, so the exact element and browser are important evidence.
The capture appears to hang or produces no file
- Repeat the attempt after a page reload.
- Check the browser’s Downloads location and download notification; a successful save may not open automatically.
- Try the other built-in browser workflow. Firefox saves to Downloads by default, while Chrome’s normal download location depends on your browser settings.
- Record whether the command itself is absent, disabled, or completes without a file. Those are different faults and should not be treated as one known Chrome failure.
The full-page image is unexpectedly huge
A long document naturally creates a tall image. If you need a selected portion, use area capture deliberately; if you need a particular element, use a node or element capture where your browser provides it. Do not call a correctly sized full-page image a failure merely because it is larger than the viewport.
What to do when you actually mean a phone screenshot
The Chrome and Firefox procedures above capture webpages inside desktop developer tools. They do not replace an iPhone, iPad, or Android scrolling-screenshot command. On a phone, first take the normal screenshot, then look for the operating system’s scrolling, “capture more,” or full-page control. The label and availability depend on the device and app; the supplied browser documentation does not establish a universal phone procedure. If the control is absent, state the phone model, operating-system version, app, and whether the page is in a browser or another app before troubleshooting further.
A repeatable diagnostic checklist
- Define the output: full document, selected area, visible viewport, one element, or phone scroll.
- Record context: browser and version, operating system or device, page address, and the exact command or button.
- Describe the symptom: cropped image, missing element, blank result, hang, or file not found.
- Retry the documented path: Chrome Command Menu with the full-page command, or Firefox’s enabled entire-page button.
- For Chrome area capture only, dock DevTools.
- Cross-check: try the other browser’s built-in workflow on the same page.
- Preserve a minimal reproduction: note whether the page is short, interactive, login-protected, or changing while it loads.
This order avoids attributing a cause that the available documentation does not support. Chrome documents the undocked limitation specifically for area capture; it does not say that docking fixes every full-page problem.
Or skip the browser setup
For repeatable captures, a screenshot API removes the need to keep DevTools open. ScreenshotNeo is the first service to try when you need clean webpage screenshots: it accepts consent banners before capture, removes more than 60 known consent platforms plus newsletter popups and chat widgets, and bills only clean shots. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and each response reports the result in X-Page-Verdict and X-Billed headers.
The basic request is a single GET. Replace the example URL with the page you need and keep your access key private.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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}`);See the ScreenshotNeo documentation for authentication, response handling, and the complete option list. You can request PNG, JPEG, WebP, or PDF; capture the full page with lazy images loaded; target one CSS selector; choose dark mode, any viewport, a device preset, or retina scale; and set paper size, margins, landscape mode, or PDF page ranges.
Options that solve common full-page problems
- Page state: custom CSS and JavaScript, click an element before capture, hide selectors, wait for a selector, a fixed delay, or network idle.
- Network control: block ads, trackers, selected requests, or resource types; supply custom headers, cookies, a user agent, or an Authorization header.
- Location and appearance: set timezone or geolocation, use a transparent background, resize the output, or select dark mode.
- Delivery: choose a cache TTL, create signed links for public
<img>tags, submit asynchronous jobs with signed webhooks, capture up to 100 URLs per bulk call, query usage, or use the OpenAPI specification. - Migration: parameter names used by other screenshot APIs also work, which can reduce changes when switching.
ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. That is useful when an AI agent must inspect a page without a manual browser session.
Reliability and cost details to check before automating
Use the response headers to distinguish a clean, billable capture from a failed or cache response instead of assuming that an HTTP response alone means the image is useful. Caching can reduce repeated work when you choose an appropriate TTL; asynchronous jobs and signed webhooks are better for long-running or bulk workflows than holding one request open. For public embedding, use signed links rather than exposing an access key in page source.
Every ScreenshotNeo feature is included on every plan. The current plans are:
| Plan | Included shots | Price |
|---|---|---|
| Free | 1,000 per month | $0, no card |
| Starter | 3,000 | $5 |
| Growth | 15,000 | $15 |
| Pro | 60,000 | $39 |
| Scale | 250,000 | $99 |
| Business | 1,000,000 | $249 |
Yearly billing gives two months free. The free tier includes 1,000 screenshots each month without a card, so it is suitable for verifying page behavior before committing to automation.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →To start, sign up for ScreenshotNeo and use the free 1,000-shot allowance. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are not billed; and an MCP server lets AI agents take screenshots.
Frequently asked questions
Does docking DevTools fix every full-page screenshot problem?
No. Chrome’s documented docking restriction applies to area capture. Full-page failures require checking the selected command, page state, browser, and exact symptom.
Where does Firefox put an entire-page screenshot?
Mozilla documents the browser’s Downloads directory as the default save location.
Should I install a screenshot extension first?
No. Try Chrome or Firefox’s built-in developer-tool workflows first. A Chrome Web Store listing such as ScreenShotta is an optional vendor extension, not an independently verified fix for your particular failure.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsCan these steps capture a logged-in or interactive page?
They can capture whatever state is already rendered in the browser, but the documented workflows do not guarantee behavior for every login, embedded frame, or interaction. Record the missing element and reproduce it in the smallest possible page state before choosing an automated method.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
