Full page, scrolling and normal screenshots: the differences
Short answer
A normal screenshot captures the visible window. A scrolling screenshot describes the method: scroll, photograph each screenful, join them. A full page screenshot describes the result: one image containing the entire document. On desktop the last two usually mean the same thing, because scrolling is how a full page capture is produced.
Updated 21 May 2026Written by the Full Page Screenshot team
The three at a glance
| Normal | Scrolling | Full page | |
|---|---|---|---|
| What it captures | The visible window | A range you scroll through | The whole document |
| Produced by | One frame grab | Many frames, joined | Many frames, joined |
| Available without software | Yes, every OS | On phones, yes | Chrome DevTools |
| Fails when | Content is below the fold | Content is virtualised | Page is taller than the image limit |
| Typical use | Error dialogs, quick shares | Chat threads on a phone | Whole page records |
Why the terms blur
The confusion is understandable, because two of the three describe different aspects of one thing. "Scrolling screenshot" is how it is made. "Full page screenshot" is what comes out. A tool that advertises both is not offering two features.
The distinction becomes real when you cannot reach the end. A full page capture promises the whole document; a scrolling capture only promises the range you covered. Capturing the first 200 messages of a chat thread is a scrolling screenshot but not a full page one, because there is no full page — the same reason an infinite feed has no complete capture.
A fourth term worth knowing
- Viewport screenshot
- What a developer usually means by a normal screenshot: the browser's content area, without the operating system window frame, tabs or address bar. It is what automated testing tools produce by default.
- Element screenshot
- A capture of one element's bounding box. Available in Chrome DevTools by right-clicking a node in the Elements panel and choosing Capture node screenshot. Useful for isolating a component.
Why the distinction matters in practice
Two people asking for a screenshot of the same page often want different things, and the terms are how the misunderstanding survives. Someone asking a developer for a screenshot of the checkout page usually means the whole flow. The developer, working from habit, sends the viewport.
It matters in the other direction too. A full page capture of a dashboard produces an image nobody can read at a glance, when a viewport screenshot of the one broken chart would have been immediately useful. The whole page is not automatically the better answer; it is the better answer when the context around the thing is part of the point.
The practical rule: capture the whole page when you are recording a state, and capture the viewport when you are pointing at a detail. If you are unsure which you are doing, capture the whole page and crop it — you cannot crop back in.
Where each is produced
None of these require software beyond what you already have.
- Normal screenshot, Windows
- Win + Shift + S
- Normal screenshot, macOS
- Cmd + Shift + 4
- Full page, Chrome desktop
- F12, Ctrl+Shift+P, capture full size screenshot
- Full page, Firefox desktop
- Right-click, Take Screenshot, Save full page
- Scrolling, Android
- Screenshot, then Capture more
- Scrolling, iOS Safari
- Screenshot, then Full Page tab
- Element only, Chrome
- DevTools Elements panel, Capture node screenshot
Frequently asked questions
Is a scrolling screenshot the same as a full page screenshot?
On desktop, usually. One describes the technique and the other the outcome. They diverge when the page has no reachable end.
Do phones take full page screenshots?
They take scrolling screenshots. Android offers Capture more after a screenshot; iOS offers a Full Page tab in Safari. Both scroll and join.
Which type should I use for a bug report?
Full page. The cause of a visual bug is frequently outside the crop that shows the symptom.
Capture your first full page screenshot
Free, no account, and nothing leaves your computer.
Keep reading
Scrolling screenshots: what they are and how they work
What a scrolling screenshot is, how scroll-and-stitch capture produces one seamless image, and why joins are visible in some tools and not others.
Full page screenshot: capture an entire webpage in one image
Take a full page screenshot of any webpage, including everything below the fold. Automatic scrolling, sticky header handling, PNG, JPG and PDF export.
Built-in browser capture versus an extension
Chrome can capture a full page without an extension. Where the built-in tool is enough, where it fails, and what an extension adds.
Full page capture
The capture engine: measuring the document, pinning the page, photographing each screenful and joining them without seams.