PC 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 & 11Outdated 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 matchSome links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
On desktop Chrome, you can capture an entire webpage without installing anything: open DevTools with Ctrl+Shift+I (Windows/Linux) or Cmd+Option+I (macOS), open the Command Menu with Ctrl+Shift+P or Cmd+Shift+P, search for Capture full size screenshot, and select it. Chrome renders content below the visible viewport and downloads one image to your configured Downloads location.
This guide explains the built-in workflow, custom viewport sizes, element and area captures, dynamic-page limitations, troubleshooting, and when an extension or an API is a better fit.
As an Amazon Associate I earn from qualifying purchases.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →How do I take a full-page screenshot in Chrome?
The reliable built-in method is DevTools’ Capture full size screenshot command. It is intended for desktop Chrome and captures the page, including content that is not currently visible on screen.
- Open the page. Navigate to the URL you want to save and wait for the initial layout to appear.
- Open DevTools. Press Ctrl+Shift+I on Windows or Linux, or Cmd+Option+I on macOS. You can also right-click the page and choose Inspect.
- Open the Command Menu. Press Ctrl+Shift+P (Windows/Linux) or Cmd+Shift+P (macOS).
- Search for the capture command. Type
screenshot. Select Capture full size screenshot, not the similarly named visible-viewport command. - Find the file. Chrome downloads the image to the browser’s configured Downloads folder. If you do not see it immediately, check Chrome’s download history and the folder selected in Settings.
Chrome’s DevTools documentation describes the command this way: “To capture a screenshot of the whole page including the content that isn’t currently visible in the viewport, select Capture a full size screenshot from the same menu.”
#1 Best Overall
- SLIM. LIGHTWEIGHT. READY TO GO: The all-new slim design is perfect for busy lives on the go.
- SKILLFULLY DESIGNED. MILITARY TOUGH: Built with premium craftsmanship to withstand the occasional drop or ding.
- ALL-DAY, ALL-IN-ONE CHARGING: Power through your school day – and beyond – with a long-lasting 12-hour battery.¹
- 3X FASTER THAN THE PREVIOUS GENERATION OF WIFI: Crush your schoolwork in record time with Wi-Fi that’s three times faster than the previous generation of Wi-Fi.
- YOUR PHONE AND CHROMEBOOK WORK BETTER TOGETHER: Easily transfer files between devices, and control your phone right from your Chromebook.
What if the command does not appear?
Click once inside the DevTools panel before opening the Command Menu. The menu searches the active DevTools context, so a click in the webpage itself can leave the wrong context focused. Reopen the menu, type screenshot, and look for the full-size option.
What should I expect after selecting it?
Chrome creates an image of the rendered document rather than a picture of your monitor. Browser tabs, the address bar, bookmarks bar, and DevTools controls are not part of the webpage image. The output can be much taller than your screen, so open it in an image viewer that can zoom or fit a long image to the window.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What is the difference between Chrome’s screenshot commands?
The command names describe how much of the page Chrome captures. Choose the scope before you save so you do not mistake a viewport image for a complete page.
| Command | What it captures | When to use it |
|---|---|---|
| Capture screenshot | The currently visible viewport | A bug report, a single screen, or a visual state that fits on screen |
| Capture full size screenshot | The full rendered page, including content below the fold | Long landing pages, documentation, receipts, and complete-page archives |
| Capture area screenshot | A rectangle you select in the page | A precise region without capturing the entire document |
| Capture node screenshot | A selected DOM element, including an element larger than the viewport | One chart, card, table, article, or component |
Chrome for Developers presents these as four related techniques: screenshot an element, screenshot a node larger than the screen, capture a mobile version with a device frame, and capture a full page. The full-size command is the one that answers “how do I screenshot an entire webpage?”
How do I capture a full page at a custom width or height?
Use DevTools’ Device Toolbar when the screenshot must match a phone, tablet, or exact viewport rather than your normal browser window. The page is re-rendered at the emulated dimensions before Chrome takes the full-size image.
- Open DevTools and click the Toggle device toolbar button, or press Ctrl+Shift+M (Windows/Linux) or Cmd+Shift+M (macOS).
- Choose a device preset from the toolbar, or enter a custom width and height. A preset such as an iPad Pro is useful when you need a practical tablet viewport; custom values are better for a fixed design specification.
- Confirm that the page has reflowed at the selected width. Resize-sensitive menus, columns, and images may change when the viewport changes.
- Open the Device Toolbar’s three-dot menu.
- Choose Capture full size screenshot. The resulting file is saved to the default Downloads folder unless you have changed Chrome’s download location.
Changing the viewport affects layout, breakpoints, and sometimes which content is loaded. Record the width, height, device preset, and device-pixel-ratio setting if the image will be used for a visual regression or design handoff.
Can I make a retina-style capture?
Device emulation can represent a device’s pixel density, but the exact pixel dimensions of the downloaded file depend on the emulated settings and the page. If you need a repeatable high-resolution asset, note the device scale setting alongside the viewport and compare the resulting pixel dimensions after capture.
Rank #2
- FOR HOME, WORK, & SCHOOL – With an Intel processor, 14-inch display, custom-tuned stereo speakers, and long battery life, this Chromebook laptop lets you knock out any assignment or binge-watch your favorite shows..Voltage:5.0 volts
- HD DISPLAY, PORTABLE DESIGN – See every bit of detail on this micro-edge, anti-glare, 14-inch HD (1366 x 768) display (1); easily take this thin and lightweight laptop PC from room to room, on trips, or in a backpack.
- ALL-DAY PERFORMANCE – Reliably tackle all your assignments at once with the quad-core, Intel Celeron N4120—the perfect processor for performance, power consumption, and value (2).
- 4K READY – Smoothly stream 4K content and play your favorite next-gen games with Intel UHD Graphics 600 (3) (4).
- MEMORY AND STORAGE – Enjoy a boost to your system’s performance with 4 GB of RAM while saving more of your favorite memories with 64 GB of reliable flash-based eMMC storage (5).
How do I capture only an element or a selected area?
Full-page capture is excessive when you need one component. DevTools can capture a selected DOM node or a rectangular area instead.
Capture a DOM node
- Open DevTools and use the element picker to select the component in the page.
- In the Elements panel, right-click the highlighted node.
- Choose the screenshot option for the node. Chrome can capture a node that extends beyond the current viewport.
This approach is useful for a long article element, a table, or a single card because unrelated navigation and page chrome are excluded.
Capture an area
- Open the Command Menu and search for
screenshot. - Select Capture area screenshot.
- Drag over the rectangle you want to save and release.
Area capture is faster for a small region, but it does not include content outside the rectangle and is not a substitute for a document-length image.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why is content missing from my full-page screenshot?
Chrome captures the page state it can render at capture time. Dynamic applications can behave differently from static documents, especially when content appears only after scrolling, a click, a login transition, or another interaction.
Lazy-loaded images have not appeared
Some pages request images only when an element approaches the viewport. A full-size command may therefore produce blank image slots or placeholders if the page never triggered those requests. Scroll through the page once, wait for images to finish loading, and then run the capture again. If the page requires an explicit “Load more” action, activate it before capturing.
Content appears after a click or hover
Menus, accordions, tab panels, cookie dialogs, and hover cards may remain closed in the captured state. Perform the interaction first, verify the desired content is visible, and then invoke the full-size command. Chrome does not infer which hidden states you want.
An application returns only the visible window
Some web apps manage their own scrolling inside a fixed container rather than using the document’s scroll height. In that case, Chrome may capture the outer page but not every item in the app’s internal scroller. Select the relevant node for a component-level capture, or use the app’s export function if it provides one.
Rank #3
- Storage: 16GB Flash Memory
- OS: Chrome OS
- Screen Size: 11.6"
Fonts or media are still loading
Wait until the layout has settled before opening DevTools’ command. A late webfont can change line breaks and page height, while unfinished media can leave empty space. Taking a second capture after the page stabilizes often produces a different, more complete result.
How do I troubleshoot a failed or wrong capture?
- Wrong command selected: If the image ends at the bottom of your screen, repeat the process and choose Capture full size screenshot, not Capture screenshot.
- Command Menu is empty: Click inside DevTools, reopen the menu, and search for
screenshot. Keep DevTools open while selecting the command. - Download cannot be found: Check Chrome’s configured Downloads folder and the browser’s download history. A managed computer may redirect downloads to another location.
- Page layout is too wide or narrow: Close Device Toolbar or set the intended custom width before capturing. A responsive breakpoint can radically change the document.
- Images are blank: Scroll through the page, wait for network activity and image placeholders to finish, then capture again. Expand required sections first.
- Only an app panel is incomplete: Look for an internal scroll container. Capture the specific node or use an application export because the document-level command may not see the panel’s off-screen items.
- Capture looks different from the live page: Check whether a consent banner, chat widget, personalization layer, or logged-in state changed between viewing and capture. Reproduce the intended state in the tab immediately before taking the image.
Should I use a full-page screenshot extension?
An extension can reduce the number of DevTools steps and may offer a direct PNG or PDF workflow, but it adds a third-party component to your browser. Compare the practical trade-offs rather than assuming an extension will solve dynamic-page problems automatically.
| Consideration | Chrome DevTools | Full-page extension |
|---|---|---|
| Setup time | Already included in desktop Chrome; requires opening DevTools and the Command Menu | Usually one toolbar click after installation |
| Viewport control | Device Toolbar supports presets and custom dimensions | Depends on the extension; verify its viewport controls |
| Dynamic or embedded content | Captures the current rendered state and can miss interaction-dependent content | May use its own scrolling and stitching logic; behavior still varies by site |
| Output | Built-in image capture commands | Some extensions provide image and PDF downloads |
| Permissions | Uses Chrome’s built-in developer tools | Review the extension’s requested permissions and publisher before installing |
| Maintenance | Tracks the Chrome installation you already use | Third-party compatibility and store listing details can change |
What about GoFullPage?
The Chrome Web Store listing for GoFullPage – Full Page Screen Capture says it captures the current page, requests no extra permissions, and opens a result tab where you can download an image or PDF. The listing displayed 4.9 stars from 84.3K ratings and 11,000,000 users when accessed on October 25, 2026; store figures are dynamic and should be checked again before relying on them. Treat those numbers as listing information, not as a guarantee that every site will capture correctly.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
ScreenshotNeo is a website screenshot API and MCP server for developers. One GET request returns a PNG, JPEG, WebP, or PDF, so you can capture a URL from a script or an AI agent without opening Chrome.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →It is useful when you need repeatable captures, authenticated pages, or a pipeline rather than a one-off manual image. Full-page capture loads lazy images; you can also select one element by CSS selector, set a device preset or any viewport, use retina scale, wait for a selector, delay, or network idle, inject CSS or JavaScript, click an element before capture, hide selectors, block ads or selected requests, and supply headers, cookies, a user agent, or Authorization. PDF paper size, margins, landscape mode, and page ranges are available as well.
For larger workflows, ScreenshotNeo supports caching with a chosen TTL, signed links for public image tags, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API, and an OpenAPI specification. Its parameter names are compatible with those used by other screenshot APIs, which can simplify a migration.
cURL
See the ScreenshotNeo documentation for the complete parameter reference. This request saves a WebP response locally:
Rank #4
- Intel Celeron N4120: 4 Cores & Threads, 1.1GHz Base Clock, Up to 2.6GHz Boost Clock, 4MB Cache, Intel UHD Graphics 600. The perfect combination of performance, power consumption, and value helps your device handle multitasking smoothly and reliably with four processing cores to divide up the work.
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}`);ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before the shot; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response reports the page verdict and billing status in X-Page-Verdict and X-Billed headers. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
The Free plan includes 1,000 shots per month without a card. Paid plans start at $5 for 3,000 shots, and every feature is available on every plan. Create a free ScreenshotNeo account to try the API.
Which capture method should I choose?
| Your need | Best starting point | Reason |
|---|---|---|
| One complete page on a desktop | DevTools full-size capture | No installation and direct control over the current tab |
| A phone or tablet layout | Device Toolbar plus full-size capture | Lets you set a preset or exact viewport before rendering |
| One chart, card, or long component | Node capture | Avoids unrelated page content |
| A small rectangular region | Area capture | Fastest way to isolate a visible section |
| Repeated, scripted, or multi-URL captures | ScreenshotNeo | API, bulk jobs, waits, cleanup of common overlays, and MCP support |
| One-click PNG or PDF from the browser | A vetted full-page extension | Convenient when you accept third-party permissions and site-specific behavior |
What are the practical reliability and cost considerations?
Chrome’s built-in workflow has no separate screenshot charge because it is part of the browser, but it is manual and tied to the state of one open tab. It is ideal for occasional captures and for inspecting exactly what a user sees. It does not provide a documented success verdict or a billing distinction for failed pages.
An extension can be convenient, but you must maintain it and evaluate its permissions. Dynamic pages remain the main variable: neither a toolbar command nor an extension can guarantee content that the page has not rendered or that requires an interaction you did not perform.
An API introduces account and request-management work, but it is better suited to scheduled archives, visual testing, documentation builds, and AI workflows. ScreenshotNeo’s response headers distinguish clean captures from bot checks, blank pages, timeouts, failed loads, and cache hits, so you can handle those outcomes in code instead of silently storing a broken image.
What should I check before sharing a full-page screenshot?
- Confirm that the URL and viewport are the intended ones.
- Check the top, middle, and bottom of the image for missing lazy-loaded assets.
- Look for consent dialogs, chat bubbles, newsletter forms, or personal data that should not be distributed.
- Verify that interactions such as accordions and tabs are in the state you intend to show.
- Open the downloaded file at 100% zoom to check text legibility and unexpected clipping.
- Keep a note of the capture date, Chrome version, viewport, and page state when the image is evidence for a bug or design review.
Frequently Asked Questions
Will Chrome include an accordion section that is closed?
Usually not. Open the accordion, tab, or disclosure control first and wait for its contents to render; the full-size command captures the state currently present in the document.
Can I capture a page while I am signed in?
Yes, the DevTools command operates on the page already open in your tab, so it can capture the rendered state available to that session. Review the image for account details or other private data before sharing it.
Does the screenshot include Chrome’s address bar and tabs?
No. The result is a webpage image, not a picture of the browser window. If you need browser chrome visible, use an operating-system screen capture instead of DevTools’ page screenshot.
Can I automate full-page captures without controlling a desktop browser?
Yes. A screenshot API can accept URLs from scripts, wait for page conditions, and return an image or PDF. ScreenshotNeo also exposes MCP tools for AI clients and reports whether a response was billed.
Recommended Free Tools
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.
