Full Page Screenshot vs Viewport Screenshot — What's the Difference?
Understand the difference between full page screenshots and viewport screenshots. Learn when to use each type, how they work technically, and how to capture both with the Site-Shot API.
Apr 3, 2026
When you capture a website screenshot, there are two fundamentally different approaches: viewport screenshots and full page screenshots. Understanding the difference helps you choose the right method for your use case.
What Is a Viewport Screenshot?
A viewport screenshot captures exactly what fits inside the browser window at a given size — the visible portion of the page without scrolling. If the page is longer than the viewport height, everything below the fold is excluded.
Example: A 1280×1024 viewport screenshot of a blog post would capture the header, navigation, and the first few paragraphs — but not the rest of the article.
When to use viewport screenshots:
- Link previews and thumbnails — you only need the "above the fold" content to give users a visual hint of what the page looks like.
- Performance monitoring — capturing just the initial viewport is faster and produces smaller images.
- Consistent dimensions — every screenshot has the exact same width and height, making them easy to display in grids or comparison views.
- Social media cards — Open Graph and Twitter Card images work best with fixed dimensions.
What Is a Full Page Screenshot?
A full page screenshot captures the entire document from top to bottom. The browser scrolls through the whole page, rendering lazy-loaded images and scroll-triggered content, then stitches everything into one tall image.
Example: A full page screenshot of that same blog post would capture the header, the entire article body, all inline images, the comments section, and the footer — potentially producing an image thousands of pixels tall.
When to use full page screenshots:
- Archiving and compliance — you need a complete visual record of the page as it appeared at a specific point in time.
- Design review — stakeholders want to see the entire page layout, not just what fits on one screen.
- Competitor analysis — capture the full landing page, pricing table, or product listing for side-by-side comparison.
- SEO audits — inspect the full content structure, heading hierarchy, and internal linking.
Technical Differences
| Aspect | Viewport | Full Page |
|---|---|---|
| Height | Fixed (e.g. 1024 px) | Variable (up to 20,000 px) |
| File size | Smaller, predictable | Larger, varies with page length |
| Render time | Faster | Slower (must scroll and stitch) |
| Lazy-loaded content | Not captured | Captured (scroll triggers loading) |
| Sticky headers | Captured once | May appear multiple times |
| Infinite scroll | Only initial content | Content loaded during scroll |
How to Capture Each Type with Site-Shot
Viewport screenshot (default)
https://api.site-shot.com/?url=https://example.com&userkey=YOUR_API_KEY&width=1280&height=1024
The width and height parameters define the viewport size. The screenshot captures exactly that rectangle.
Full page screenshot
https://api.site-shot.com/?url=https://example.com&userkey=YOUR_API_KEY&width=1280&full_size=1&max_height=15000
Set full_size=1 to enable full page capture. The max_height parameter (up to 20,000 px) limits how far down the page the screenshot goes.
Online tool
On the Site-Shot homepage, check the full-size checkbox in the Browser options panel to switch between viewport and full page capture. Or use the dedicated full page screenshot tool.
Which Should You Choose?
For most automated workflows, start with viewport screenshots. They're faster, produce smaller files, and work well for link previews, monitoring, and visual regression testing.
Switch to full page screenshots when you need to capture content below the fold — for archiving, design documentation, or when the important content is further down the page.
You can also combine both: use viewport screenshots for quick thumbnails and trigger a full page capture on demand when a user wants to see the complete page.