Chrome Full Page Screenshot Without Extension (2026)

Sometimes you need a full page screenshot but can't — or don't want to — install a Chrome extension. Maybe you're on a locked-down corporate machine, using a shared computer, or just want a quick one-off capture.

Chrome actually has built-in ways to capture entire pages. None of them are perfect, but they work in a pinch. Here's every method available without installing anything.

Method 1: Chrome DevTools "Capture full size screenshot"

This is the closest Chrome gets to a native full page screenshot feature. It's hidden in DevTools, but it works.

Steps:

1. Open the page you want to capture.
2. Press F12 to open DevTools.
3. Press Ctrl+Shift+P (Cmd+Shift+P on Mac) to open the Command Menu.
4. Type screenshot and select "Capture full size screenshot".
5. Chrome saves a PNG to your Downloads folder.

What happens behind the scenes: Chrome resizes the internal rendering viewport to the full computed height of the page and takes a single snapshot. It does not actually scroll through the page.

The Problems

This method has real limitations that you should know about before relying on it:

Sticky headers repeat. Any element with position: fixed or position: sticky — navigation bars, cookie banners, floating chat widgets — appears multiple times throughout the image. There's no way to prevent this in DevTools.

Lazy-loaded images are blank. Modern websites load images only when they enter the viewport. Since DevTools doesn't scroll, these images never trigger. You'll see blank spaces or placeholder images where real content should be.

Dynamic content is missing. Single-page applications, infinite scroll feeds, and content that loads via JavaScript after user interaction won't appear in the capture.

Very long pages may fail. Chrome has memory limits. Pages over ~15,000 pixels tall may produce corrupted images, blank sections, or cause the tab to crash.

No editing. The PNG is saved directly to Downloads. No annotation, no cropping, no PDF export.

When It Works Well

DevTools full page capture is reliable for:

• Short, static HTML pages
• Documentation sites with simple layouts
• Pages without sticky navigation
• Quick one-off captures where quality doesn't matter

Method 2: Print to PDF

Chrome's Print dialog can save any page as a PDF, which technically captures the "full page."

Steps:

1. Press Ctrl+P (Cmd+P on Mac).
2. Change destination to "Save as PDF".
3. Adjust margins, scale, and layout if needed.
4. Check "Background graphics" if you want to preserve colors.
5. Click Save.

The Reality

Print to PDF doesn't produce a screenshot — it produces a reformatted document. The page is re-rendered using print stylesheets, which means:

• The visual layout changes (often dramatically)
• Responsive design is replaced by paper-width rendering
• Background colors and gradients may disappear
• Interactive elements (dropdowns, tabs, accordions) show only their default state
• The content is paginated — split across multiple pages
• Fixed-position elements may appear on every page

Best for: Text-heavy pages where you need the content, not the visual design. Academic articles, documentation, long-form text.

Not suitable for: Capturing the actual visual appearance of a webpage.

Method 3: DevTools Responsive Mode + Screenshot

A variation of Method 1 that gives you more control over the output dimensions.

Steps:

1. Open DevTools (F12).
2. Toggle Device Mode (Ctrl+Shift+M / Cmd+Shift+M).
3. Set a custom viewport width (e.g., 1280px).
4. Click the three-dot menu in the device toolbar.
5. Select "Capture full size screenshot".

This captures at the exact width you specify, which is useful for consistent screenshots across sessions. However, all the same limitations apply — sticky headers, lazy loading, and memory issues.

Method 4: Scroll and Stitch Manually

The brute-force approach: take multiple viewport screenshots and combine them in an image editor.

Steps:

1. Take a screenshot of the visible area (Ctrl+Shift+P → "Capture screenshot").
2. Scroll down by approximately one viewport height.
3. Take another screenshot, ensuring slight overlap with the previous one.
4. Repeat until you've covered the entire page.
5. Open all images in an editor (Paint, GIMP, Photoshop) and manually align them.

Reality check: This is painful. Alignment is never perfect, you'll spend 10-20 minutes on what should be a 2-second task, and the result often has visible seams. Not recommended for anything beyond desperation.

Method 5: Browser Console Script

For developers comfortable with JavaScript, you can use the Chrome console to automate scrolling and capture:

// This scrolls to the bottom to trigger lazy loading, then back to top
(async () => {
  const delay = ms => new Promise(r => setTimeout(r, ms));
  const height = document.body.scrollHeight;
  for (let i = 0; i < height; i += window.innerHeight) {
    window.scrollTo(0, i);
    await delay(500);
  }
  window.scrollTo(0, 0);
  console.log('Scroll complete — now use DevTools screenshot');
})();

Run this script, wait for it to finish, then use the DevTools "Capture full size screenshot" command. This forces lazy-loaded images to render before capture.

Limitations: This only solves the lazy-loading problem. Sticky headers still repeat, and you still have no editing tools.

Honest Comparison

The Extension Alternative

If you've read this far and the limitations sound frustrating, that's because they are. Chrome's built-in tools were designed for developers, not for everyday screenshot needs.

A full page screenshot extension solves all of these problems:

• Actually scrolls through the page (no blank lazy-loaded images)
• Detects and handles sticky headers automatically
• Opens every capture in a built-in editor with arrows, text, highlights
• Exports as PNG, PDF, or clipboard
• One click instead of 4+ steps

For occasional one-off captures, DevTools works. For anything regular, an extension saves hours of frustration.

Summary

You can take a full page screenshot in Chrome without an extension — DevTools is the most practical built-in option. But it comes with real limitations around sticky elements, lazy-loaded content, and lack of editing. For reliable, high-quality full page captures, an extension remains the better tool.