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.
GuideThe fastest onboarding form is the one your users don't have to fill out. Here's how to derive the entire signup form — company name, industry, logo, colors — from one URL field, and how to wire it into three common product categories.
Developers, marketers, and founders use Allscreenshots to automate website captures. No credit card required to get started.
Chrome can make a full page screenshot without an extension. The feature is built into DevTools, but it is hidden behind the command menu, so it is easy to miss if you only use the normal browser toolbar.
This guide shows the built-in Chrome method, what to do when it fails on long or dynamic pages, and when it makes sense to use AllScreenshots screenshot automation instead of taking screenshots by hand.
To make a full page screenshot in Chrome in 2026:
Ctrl+Shift+I on Windows or Linux, or Cmd+Option+I on macOSCtrl+Shift+P on Windows or Linux, or Cmd+Shift+P on macOSscreenshotChrome saves a PNG file to your Downloads folder. The image contains the full scrollable page, not just the part currently visible on screen.
If images are missing, scroll to the bottom of the page once, wait for lazy-loaded content to appear, then run Capture full size screenshot again.
There is no single Chrome shortcut that immediately captures the full page. The shortcut opens the DevTools command menu, then you choose the screenshot command.
| Platform | Open DevTools | Open command menu | Command to choose |
|---|---|---|---|
| Windows | Ctrl+Shift+I | Ctrl+Shift+P | Capture full size screenshot |
| Linux | Ctrl+Shift+I | Ctrl+Shift+P | Capture full size screenshot |
| macOS | Cmd+Option+I | Cmd+Shift+P | Capture full size screenshot |
If DevTools is already open, you can skip the first shortcut and go straight to the command menu.
Load the URL in Chrome and wait until the page appears stable. If the page uses animations, dashboards, charts, or lazy-loaded images, give it a few extra seconds before opening DevTools.
Use Ctrl+Shift+I on Windows or Linux, or Cmd+Option+I on macOS. DevTools can be docked to the side, bottom, or a separate window. The docking position does not matter for the screenshot.
Use Ctrl+Shift+P on Windows or Linux, or Cmd+Shift+P on macOS. This opens the same kind of command palette you may know from VS Code.
Type screenshot. Chrome will show several screenshot commands.
Select Capture full size screenshot. Chrome renders the full scrollable document and downloads a PNG.
Chrome DevTools includes more than one screenshot command. Choose the one that matches the job.
| Chrome command | Captures | Use it for |
|---|---|---|
| Capture full size screenshot | The whole scrollable document | Full page screenshots, landing pages, articles, docs |
| Capture screenshot | The current viewport only | Above-the-fold checks and quick bug reports |
| Capture area screenshot | A rectangle you draw | Cropping a specific visible section |
| Capture node screenshot | The selected DOM element | Components, pricing cards, modals, headers |
For most "Chrome full page screenshot" searches, Capture full size screenshot is the right choice.
If you only care about the first viewport, try the free above-the-fold checker. It is more useful than a raw Chrome viewport screenshot when you need to inspect what appears before a user scrolls.
Chrome can also capture a mobile-sized full page screenshot:
Ctrl+Shift+M / Cmd+Shift+MThis is useful for checking responsive layouts, but it is still a manual workflow. If you need desktop, tablet, mobile, light mode, and dark mode screenshots repeatedly, use AllScreenshots screenshot automation or the visual regression testing workflow so each viewport is captured consistently.
Chrome's built-in screenshot feature is convenient, but it captures what Chrome can render at that moment. Modern websites often make that harder than it sounds.
Many pages do not load below-the-fold images until the user scrolls. Chrome's full page capture may finish before those images are requested.
Fix it manually by scrolling through the page before capturing. For automated captures, AllScreenshots' full-page screenshot capture uses smart scrolling to load lazy content before the final image is created.
Consent banners, chat widgets, newsletter popups, and ads are part of the rendered page. Chrome does not remove them before taking the screenshot.
For clean output, close overlays manually before capture. If you need repeatable captures, AllScreenshots blocks ads and cookie banners by default for new captures, as described in ad and cookie blocking now default.
Fixed headers, sticky footers, and floating toolbars can cover content while Chrome stitches the full page image. This is especially common on marketing pages and ecommerce sites.
When the screenshot is evidence or documentation, review the output carefully. For compliance use cases, pair full-page capture with scheduled records through compliance and auditing screenshots.
Extremely tall pages can produce very large PNG files. Chrome may clip content, create blank regions, or download a file that is awkward to preview and share.
If the page is very long, capture meaningful sections separately or use a screenshot service that handles the scrolling and rendering pipeline for you.
Apps like dashboards, editors, inboxes, project tools, and analytics pages often scroll inside a panel instead of the whole document. Chrome's full size screenshot captures the document, not every nested scroll container.
For those cases, use Capture node screenshot on the specific panel, or automate a purpose-built workflow with custom selectors.
The best method depends on how often you take screenshots and what you need to do with the result.
| Method | Best for | Limitations |
|---|---|---|
| Chrome DevTools | Occasional full page screenshots | Manual, hidden UI, inconsistent on complex pages |
| Chrome extensions | Frequent manual capture and annotation | Requires installation, often browser-specific |
| Puppeteer or Playwright | Developer scripts and tests | You manage Chrome, dependencies, memory, retries, and hosting |
| AllScreenshots | Repeatable screenshots, batches, schedules, APIs, clean output | Requires an API call or dashboard workflow |
Use Chrome DevTools when you need one quick PNG.
Use AllScreenshots when you need the same capture to work again tomorrow, from CI, on a schedule, across many URLs, or with clean defaults for ads and cookie banners.
If you want to automate Chrome yourself, Puppeteer can create a full page screenshot:
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: 'chrome-full-page.png',
fullPage: true,
});
await browser.close();This works well for local scripts and controlled pages. In production, you also need to manage Chrome versions, Linux dependencies, timeouts, crashes, resource limits, retries, proxy behavior, and storage.
For more context, read our Puppeteer browser automation guide and website screenshots from the command line.
AllScreenshots gives you a Chrome-rendered full page screenshot without running Chrome yourself:
curl -X POST 'https://api.allscreenshots.com/v1/screenshot' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"url": "https://example.com",
"fullPage": true,
"viewport": {
"width": 1440,
"height": 900
},
"format": "png"
}'Use the API when you need:
You can also connect screenshot capture to tools your team already uses, including Zapier, Make, Airtable, Google Sheets, and Notion.
If you are replacing a manual Chrome screenshot workflow, these are the most useful AllScreenshots features to start with:
| Need | Feature |
|---|---|
| Capture a whole page | Full-page screenshot capture |
| Remove popups and visual clutter | Default ad and cookie blocking |
| Run captures on a cadence | Scheduled screenshots |
| Check UI changes after deploys | Visual regression testing |
| Capture many URLs | Screenshot automation |
| Archive pages for proof | Compliance and auditing |
| Monitor competitors | Website monitoring |
| Save a document version | HTML to PDF |
Yes. Open DevTools, open the command menu, type screenshot, and choose Capture full size screenshot.
Chrome usually saves DevTools screenshots to your Downloads folder. If your browser or operating system asks where to save downloads, choose the folder when prompted.
The page may be too tall, too dynamic, or using rendering patterns that Chrome's DevTools screenshot command does not handle well. Try scrolling through the page first, closing overlays, reducing the viewport height, or capturing sections separately.
Chrome desktop can emulate a mobile viewport in DevTools and then capture a full size screenshot. Open the device toolbar, choose a mobile preset, refresh the page, then run Capture full size screenshot.
No. A screenshot captures the screen rendering as an image. A PDF uses print rendering, pagination, and print CSS. Use HTML to PDF when you need a document, and use screenshots when you need an image of the rendered page.
For local scripts, Puppeteer or Playwright works. For production workflows, scheduled captures, CI/CD, batches, clean output, and retries, use AllScreenshots screenshot automation.