Chrome on Mac can capture an entire webpage—not just the part currently visible—without an extension. Open DevTools with Command+Option+I, turn on Device mode, open the viewport toolbar’s More options menu, and choose Capture a full size screenshot.
What Chrome’s full-page capture does
Capture a full size screenshot renders the page from its top through the bottom, including content outside the current viewport. It is different from Capture screenshot, which saves only the visible viewport.
Chrome for Developers describes the command this way: “To capture a screenshot of the whole page including the content that isn’t visible in the viewport, select Capture a full size screenshot from the same menu.” The command is built into DevTools, so this workflow does not require an extension, paid software, or a separate device.
Before you start
- Use the desktop version of Google Chrome on macOS.
- Open the exact page you want to save and wait for its initial content to appear.
- Keep DevTools docked to the browser window if you plan to use the area-capture command later; area capture is not available when DevTools is undocked.
- If the page requires an account, sign in before opening DevTools. The screenshot reflects the page state Chrome can currently see.
Step-by-step: capture the entire page
-
Open the target page
Navigate to the webpage in Chrome. If the page changes after an interaction, perform that interaction first so the desired state is present when you capture it.
Recommended Free Tools
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy. -
Open DevTools
Press Command+Option+I. You can also use Chrome’s three-dot menu and choose More Tools > Developer Tools.
-
Enter Device mode
In the DevTools action bar, click Toggle device toolbar. This opens the device-mode viewport above or beside the page. Device mode simulates a mobile viewport on your Mac; it does not run the site on a physical phone.
-
Open the screenshot menu
In the device-mode viewport toolbar, open More options. The menu is part of the viewport controls, not Chrome’s main three-dot browser menu.
-
Choose the full-page command
Select Capture a full size screenshot. Chrome captures content above and below the visible viewport and downloads the resulting image. For only the currently visible area, select Capture screenshot instead.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Choose the right capture command
| Command | What it captures | Where to find it | Best use |
|---|---|---|---|
| Capture a full size screenshot | The page from top to bottom, including content outside the viewport | Device mode > More options | Documentation, audits, archives, and sharing a complete page |
| Capture screenshot | Only the current visible viewport | Device mode > More options | A desktop or simulated-device screen state |
| Capture area screenshot | A rectangle you select by dragging | Command Menu | A specific region rather than the full page |
Do not confuse Capture area screenshot with full-page capture. Area capture is a selection tool: open the Command Menu, search for “screenshot,” choose the area command, and drag across the portion of the page you want. On a Mac, the Command Menu opens with Command+Shift+P. The documented area workflow does not work while DevTools is undocked.
Device mode: what it changes
Device mode gives you a controllable viewport for testing responsive layouts. You can select a simulated device and inspect how the page fits that viewport before capturing it. The simulation happens inside Chrome on your computer; it is not evidence of how the page behaves on a particular physical handset, operating-system build, or mobile network.
For a desktop-style full-page image, choose a wide viewport before using the full-size command. For a mobile-layout image, select the desired device preset or set a custom viewport, then capture. The full-size command follows the viewport and page state you have configured.
Long, interactive, and changing pages
Let the page reach the state you need
A full-size command captures what Chrome can render at that moment. Wait for the page’s main content to appear, dismiss any overlays that obscure the content, and expand sections you want represented before taking the shot.
Check content that appears after interaction
If an accordion, tab, menu, or consent dialog controls what is visible, set that control first. A screenshot is a record of the current page state; it does not replace the actions needed to reveal content.
Expect larger files for larger pages
A very long or media-heavy page can produce a tall, large image. If the result is difficult to inspect or share, use the page’s print or PDF workflow for a document-oriented copy, or capture a selected region instead. Chrome’s full-size command itself does not provide a page-range selector.
Troubleshooting Chrome’s full-page screenshot
The shortcut does nothing
Make sure Chrome is the active application and press Command+Option+I again. If keyboard shortcuts are intercepted by another utility, open the three-dot menu and use More Tools > Developer Tools.
You cannot find “Toggle device toolbar”
Look in the DevTools action bar. If the window is narrow, some controls may be hidden behind the action bar’s overflow menu. Widen the DevTools pane and look for the device-shaped toolbar control.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11There is no “Capture a full size screenshot” option
The command appears in Device mode’s viewport-toolbar menu. Confirm that Device mode is enabled, then open More options in that toolbar—not the browser’s main menu. If you are looking at the Command Menu, search for “screenshot”; the area command there is a different feature.
The image contains only the visible viewport
You probably selected Capture screenshot. Repeat the process and choose Capture a full size screenshot. The two commands are adjacent but have different scopes.
The page looks like a phone layout
That is expected when Device mode is using a mobile preset or narrow viewport. Select a wider preset or enter a custom desktop-sized viewport, then capture again. Remember that Device mode is a simulation, not a physical mobile device.
Area capture will not start
Dock DevTools to the browser window. The documented Capture area screenshot workflow does not operate while DevTools is undocked.
Parts of the page are missing
Check whether those parts require a click, a tab change, scrolling-triggered loading, or a login. Perform the required action and wait for the content to appear before starting the capture. If the page still fails to render, the problem is with the page state or loading process rather than the screenshot menu.
The download is unwieldy
Use viewport capture for a single screen, area capture for a specific section, or a PDF/print workflow for a document that needs pagination. The full-size command intentionally produces one continuous page image.
Automation and repeatable captures
DevTools is convenient for an occasional capture, but repeating the same steps across many URLs requires a browser-automation setup or an API. Chrome’s documented menu workflow does not establish an official batch-capture command, webhook system, or usage endpoint. For a programmatic request, an HTTP screenshot API avoids opening DevTools for each page.
Or skip the browser setup
ScreenshotNeo returns a webpage screenshot or PDF from one request. Its cleanup steps accept cookie and consent banners before capture and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and each response identifies the result with X-Page-Verdict and X-Billed headers.
Start with the API documentation at screenshotneo.com/docs/. Replace the example URL with the page you need.
Best Value
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,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const data = Buffer.from(await res.arrayBuffer());
await Bun.write('shot.webp', data);The service supports PNG, JPEG, WebP, and PDF output. Relevant capture controls include full-page rendering with lazy images loaded, a single element selected by CSS selector, dark mode, 12 device presets or any custom viewport, retina scale, PDF paper size, margins, landscape mode and page ranges, HTML/CSS-to-image conversion, custom CSS and JavaScript, clicking an element before capture, hiding selectors, waiting for a selector, delay, or network idle, blocking ads, trackers, requests, or resource types, custom headers, cookies, user agent and Authorization, timezone and geolocation, transparent backgrounds, image resizing, user-selected cache TTLs, signed links for public <img> tags, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.
ScreenshotNeo also provides an MCP server for AI agents, including Claude, Cursor, and other MCP clients. Its tools are take_screenshot, get_page_info, and capture_pdf.
ScreenshotNeo plans and billing
| Plan | Included screenshots per month | Monthly price |
|---|---|---|
| Free | 1,000 | $0; no card required |
| Starter | 3,000 | $5 |
| Growth | 15,000 | $15 |
| Pro | 60,000 | $39 |
| Scale | 250,000 | $99 |
| Business | 1,000,000 | $249 |
Every feature is available on every plan. Yearly billing provides two months free. The free tier includes 1,000 screenshots each month with no card, and paid plans start at $5 for 3,000 screenshots.
Free tools Windows power users keep installed
One-click scans. No signup required.
To create an account, use the free ScreenshotNeo sign-up. You get 1,000 screenshots a month without adding a card; paid plans begin at $5 for 3,000.
Chrome DevTools versus an API
| Need | Chrome DevTools | ScreenshotNeo |
|---|---|---|
| One manual capture | Fast, built in, and free | Requires an API key and request |
| Many URLs | Manual repetition | Bulk capture supports up to 100 URLs per call |
| Consent and chat cleanup | You handle the page state yourself | Known consent platforms, newsletter popups, and chat widgets can be removed before capture |
| Failure billing | No service charge, but no API verdict | Failed loads, bot checks, blank pages, timeouts, and cache hits are not billed |
| AI-agent workflow | No MCP server in this workflow | MCP tools include take_screenshot, get_page_info, and capture_pdf |
History and current workflow
Chrome’s full-page DevTools capability was highlighted in the Chrome 59 release notes as a way to capture from the top to the bottom of a page. The current workflow is the Device mode toolbar path described above; menu placement can change as Chrome evolves, so rely on the command names rather than an old screenshot of the interface.
Frequently Asked Questions
When did Chrome first highlight full-page DevTools capture?
Chrome 59 release notes highlighted the ability to capture a page from its top to its bottom. The current command is still exposed through Device mode’s More options menu.
Is Chrome’s Device mode the same as testing on a real phone?
No. Device mode simulates a mobile viewport on your Mac. It does not run the page on a physical handset or reproduce every hardware, operating-system, or network condition.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteQuick 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.
