ViewportKit

Full-page screenshots for every page you ship

Capture complete websites across responsive viewports, preserve a versioned visual record, and give reviewers evidence they can inspect without recreating your browser session.

Full-page screenshot tool

A screenshot is more useful when it is a repeatable workflow.

Browser screenshots are quick to make and easy to lose. ViewportKit turns a full-page capture into a project: discover the right URLs, capture the necessary viewports, compare a later run, assign feedback, and export a record for the people who need it.

Start a capture View plans

Follow the visual regression checklist

What a full-page screenshot workflow should cover

Capture the complete page

Start from one URL or discover a site from its sitemap. ViewportKit scrolls the page, includes lazy-loaded sections, and keeps each capture in a named project.

Check the breakpoints that matter

Run desktop, laptop, tablet, and mobile captures together so a responsive regression is evidence, not a browser-tab anecdote.

Keep a visual history

Save a run, capture again after a release, then compare versions and leave review tasks on the exact screenshot that changed.

Share the result in the format the work needs

Use review links for feedback, ZIP files for handoff, PDF for a client report, or AI-ready Smart Cut segments for a visual review workflow.

Choose the capture path that matches the page

Public website screenshot capture

Paste a URL or let ViewportKit discover pages from sitemap.xml and robots.txt. Select the pages and viewports to capture, then keep the result with the release it documents.

Capture a public site

Authenticated, localhost, and staging screenshots

When a cloud screenshot service cannot reach the page, use the Chrome extension from the browser session that already has access. Capture local development, staging behind a VPN, or signed-in product screens.

See the Chrome extension

Visual QA with an AI coding assistant

Connect the MCP server when your team wants an assistant to capture a page during a coding conversation, inspect a versioned image, and help turn a visual mismatch into an actionable change.

Explore MCP capture

Full-page screenshot FAQ

What is a full-page screenshot?: A full-page screenshot captures the scrollable document, rather than only the visible browser viewport. It is useful for reviewing long landing pages, checking content changes, and keeping visual evidence of a release.
Can I capture a whole website instead of one page?: Yes. ViewportKit can start from sitemap and robots.txt discovery or from a manual URL list, then capture the selected pages across multiple device viewports in one project.
Can a full-page screenshot include a page behind login?: Use the ViewportKit Chrome extension for pages your open browser session can see, including authenticated, localhost, and staging environments. The web app remains the place to organize projects, comparisons, and recurring captures.
How do I compare screenshots after a deployment?: Keep the before and after captures in a project. ViewportKit provides versioned history, side-by-side comparison, review tasks, and export options so the evidence can travel with a pull request, bug report, or client review.