Learn the fastest way to make a full page screenshot in Chrome, plus better options for long pages, mobile captures, scheduled screenshots, and screenshot automation.
Learn what Puppeteer is, how it controls browsers, and how to use it for automation, testing, scraping, screenshots, PDFs, and performance workflows.
GuideStop running a browser, a parser, and a Markdown converter for every URL you process. One AllScreenshots request returns the screenshot, the main content, and the meta tags you need — billed as a single screenshot.
Developers, marketers, and founders use Allscreenshots to automate website captures. No credit card required to get started.
Chrome can capture a full page screenshot without installing an extension. The feature is built into Chrome DevTools, but it is hidden inside the command menu, so most people never find it.
This guide covers the fastest built-in method, the other screenshot commands Chrome gives you, common problems with long pages and lazy-loaded images, and when to switch from manual Chrome screenshots to an automated screenshot workflow.
To take a full page screenshot in Chrome:
Ctrl+Shift+I (Windows) or Cmd+Option+I (Mac) to open Developer ToolsCtrl+Shift+P (Windows) or Cmd+Shift+P (Mac)screenshotChrome saves a PNG of the entire scrollable page to your Downloads folder.
If the page uses lazy-loaded images, scroll to the bottom once before taking the screenshot, then run the full size screenshot command.
The screenshot feature is not a single keyboard shortcut. It is a DevTools command:
| Platform | Open DevTools | Open Command Menu |
|---|---|---|
| Windows | Ctrl+Shift+I | Ctrl+Shift+P |
| Linux | Ctrl+Shift+I | Ctrl+Shift+P |
| macOS | Cmd+Option+I | Cmd+Shift+P |
After the command menu opens, type screenshot and choose the screenshot mode you need.
Chrome offers several capture modes:
| Command | What it captures | Best for |
|---|---|---|
| Capture full size screenshot | The entire scrollable document | Full page screenshots |
| Capture screenshot | The visible viewport only | Quick above-the-fold captures |
| Capture area screenshot | A rectangle you draw manually | Cropping one region |
| Capture node screenshot | The selected DOM element | Components, cards, modals, headers |
Most people looking for a Chrome full page screenshot want Capture full size screenshot. If you only need a product card, pricing table, or hero section, select the element in the Elements panel first and use Capture node screenshot.
Element screenshots are useful when you do not want the entire page.
Ctrl+Shift+P or Cmd+Shift+PscreenshotChrome saves only the selected element. This works well for documentation, QA reports, design reviews, and bug tickets where a full page screenshot would include too much noise.
Chrome's built-in screenshot command is convenient, but it is not perfect. These are the most common problems.
Many sites load images only after the user scrolls. Chrome's full size screenshot command can capture the page before below-the-fold images have loaded.
Fix it by scrolling through the page first, waiting a moment, then capturing.
Sticky navigation bars, cookie banners, chat widgets, and fixed announcement bars can cover content in full page screenshots. Chrome captures the page as rendered, including fixed-position elements.
If the screenshot is for documentation or reporting, close overlays before capturing. For automated screenshots, use a tool that can block cookie banners and ads before rendering.
Chrome has practical limits for very tall screenshots. Extremely long pages can produce incomplete captures, blank sections, or huge PNG files that are hard to open.
For long pages, capture sections individually or use a screenshot API that handles full-page scrolling and stitching.
Browser-based apps such as Gmail, Google Docs, dashboards, and canvas-heavy tools may use internal scrolling containers instead of normal page scrolling. Chrome's full page command captures the document, not necessarily every scrollable panel inside the app.
Chrome extensions can make screenshots easier if you capture manually every day. They usually add a one-click button, annotation tools, cloud storage, or simple editing.
Use Chrome DevTools when:
Use an extension when:
Use an API when:
If you want Chrome screenshots programmatically, Puppeteer is the most direct option:
import puppeteer from 'puppeteer';
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.setViewport({ width: 1440, height: 900 });
await page.goto('https://example.com', { waitUntil: 'networkidle2' });
await page.screenshot({
path: 'full-page.png',
fullPage: true,
});
await browser.close();This is useful for local scripts, testing, scraping, and one-off automation. The trade-off is infrastructure: once you run this in production, you need to manage Chrome dependencies, memory usage, retries, timeouts, and browser cleanup.
For more details, see our Puppeteer browser automation guide.
Chrome's DevTools work for occasional screenshots, but if you need to capture screenshots regularly or at scale, a dedicated API is more practical.
AllScreenshots captures full-page screenshots without Chrome's height limitations:
curl -X POST 'https://api.allscreenshots.com/v1/screenshots' \
-H 'X-API-Key: your-api-key' \
-H 'Content-Type: application/json' \
-d '{"url": "https://example.com", "fullPage": true}' \
-o screenshot.pngThe API handles lazy-loaded images, blocks ads and cookie banners, supports desktop and mobile viewports, and works from any environment. No browser required.
Try it free with 100 screenshots per month.
Yes. Open DevTools, open the command menu, type screenshot, and choose Capture full size screenshot.
Chrome saves DevTools screenshots to your default Downloads folder unless your browser or operating system asks you where to save each file.
The page probably lazy-loads images. Scroll through the page first, wait for images to load, then run the full size screenshot command.
You can emulate a mobile viewport in DevTools before capturing. Open DevTools, toggle device emulation, choose a mobile viewport, then run Capture full size screenshot.
No. A screenshot is an image of the rendered page. A PDF uses Chrome's print rendering pipeline and can apply print-specific CSS. Use screenshots when you need the visual page exactly as it appears on screen.