Full-Page Screenshot
What a full-page screenshot is, how it differs from viewport and scrolling captures, and when to use one.
A full-page screenshot captures the entire scrollable height of a web page in one image, not only the part visible in the browser window. A long landing page can produce an image several thousand pixels tall.
There are two common methods. The browser can render the whole document height in one pass, which DevTools and automation libraries support. Or a tool can scroll the page one viewport at a time and stitch the pieces together.
Both methods run into the same page behaviors: sticky headers, images that load only when scrolled into view, infinite scroll and animations that change between frames.
Full-page screenshot vs viewport and scrolling screenshots
| Type | Height | How it is made |
|---|---|---|
| Viewport | One screen | Captures what is visible now |
| Full-page | Whole document | Renders or stitches the full page |
| Scrolling | Whole scrolled area | Scrolls any window or panel and stitches |
A full-page capture is specific to web pages. A scrolling capture can also cover app panels, chat threads and documents.
Where full-page screenshots are used
- Design reviews and handoff, where the whole layout matters.
- Archiving a page before a redesign or for records.
- QA checks for layout breaks far below the fold.
- Portfolio and case study images.
How full-page screenshots are created
In Temposhot Website Capture, set Area to Full page. Choose a Wait condition (Load, DOM content loaded or Network idle) and add a delay of 0-60 seconds if content arrives late. Output can be JPEG, PNG or WebP.
For a single page in Chrome 116+, the Temposhot Full Page Screenshot extension scrolls the active page, stitches the viewports at Retina resolution locally and downloads one PNG.
Common mistakes with full-page screenshots
- Capturing before lazy-loaded images appear, which leaves blank areas.
- Repeated sticky headers or chat buttons in a stitched image.
- Very tall images that some viewers and upload forms reject.
- Using JPEG for long pages with small text.
Taking the same screenshots again and again?
Capture full pages for a whole URL list with website screenshot automation.
Common questions
Why is part of my full-page screenshot blank?
The page probably loads images on scroll. Use Network idle or a longer delay.
Can I split a tall capture into pages?
Yes. Split Image cuts a tall image into parts.
Sources
Related resources
- Website Capture options: area, wait and format settings.
- Stitch Screenshots: join separate captures into one image.
Taking the same screenshots again and again?
Temposhot captures a screen, window or area on a timer and exports the set as a PDF, images, ZIP or MP4. The free browser tools fix single images.
Related resources
Related terms
- Scrolling ScreenshotWhat a scrolling screenshot is, how it differs from a full-page screenshot, and when to use one.
- Viewport ScreenshotWhat a viewport screenshot is, how it differs from full-page capture, and when it's the right choice.
- Screenshot StitchingHow screenshot stitching combines overlapping captures into one image, vs native full-page capture, and common pitfalls.
- Lazy LoadingHow lazy loading works, why it affects screenshot capture, and techniques for detecting and handling lazy-loaded content.
- Batch ScreenshotWhat batch screenshots are, how they differ from single captures, and where teams use them.
- Screen CaptureWhat screen capture means, the different capture methods, and how to choose the right one.
- Screenshot AutomationWhat screenshot automation is, how it differs from manual capture and screen recording, and where teams use it.