How Full Page Screenshots Work
A standard screenshot captures only what fits inside the browser viewport — typically 768 to 1080 pixels of height. A full page screenshot goes further: the browser scrolls down the page so lazy content loads, then captures the whole document height in one image.
Site-Shot uses a real Chromium browser to render the page, execute JavaScript, load lazy images, and then capture the fully rendered document from the first pixel to the last.
Screenshot a Whole Web Page Online, Without an Extension
Firefox and Microsoft Edge can capture a full page on their own, Chrome keeps the option in DevTools, an iPhone has Full Page in its screenshot editor, and many Android phones have Capture more or Scroll Capture. All of them capture a page that is open on your own device. This tool needs only the URL: the page renders in a browser on our server at the width you set, and the full website screenshot comes back as one image on any device, phone included. For the built-in methods step by step, see how to screenshot an entire web page.
When to Use Full Page Capture
- Landing page archiving — save a complete visual record of marketing pages before redesigns or A/B tests.
- Design review — save full page screenshots for designers and stakeholders without requiring them to visit the live site.
- Legal and compliance — capture entire terms of service, privacy policies, or product listings for evidence.
- Competitor analysis — document competitor pages in full for side-by-side comparison.
- SEO audits — visually inspect full page layout, content order, and above-the-fold elements.
Full Page Screenshot API
Automate full page captures with the Site-Shot API. Set full_size=1 in your API request to capture the entire document. Control the maximum height with the max_height parameter (up to 20,000 pixels; WebP up to 16,383 px).
Example API call:
https://api.site-shot.com/?url=https://example.com&userkey=YOUR_API_KEY&full_size=1&max_height=15000
Tips for Better Full Page Screenshots
- Enable No ads / No cookie to remove banners and overlays that clutter the capture.
- Use a wider viewport (1920 px) for desktop pages to avoid content reflow.
- Set a higher delay time in the API (
delay_time=3000) for pages with heavy lazy-loading. - Choose JPEG format for smaller file sizes when capturing very long, photo-heavy pages.
- Need a page behind your login? An online tool sees the public version, so capture it in your own browser: how to screenshot an entire web page in any browser or on a phone.
Let's Get In Touch
Questions about screenshots, API access, or integrations? Reach the team directly.