Skip to main content
ViewportKit
ViewportKit

Turn a website sitemap into a screenshot run

Find the pages that matter, capture them across responsive viewports, and keep the result as reviewable visual evidence for a release.

Sitemap screenshot tool

Website screenshot capture that starts with the URLs you already maintain.

ViewportKit reads a public site’s robots.txt and sitemap references on the server, follows bounded sitemap indexes, and lets you choose the pages worth capturing. That means a visual QA run can begin with a real page inventory instead of a hand-built spreadsheet of links.

Scan a sitemap See full-page capture Compare browser and URL capture paths

From sitemap to review-ready screenshots

  1. 1

    Start with a site URL

    Enter the public website URL. ViewportKit looks for robots.txt and sitemap locations, then performs the scan through its bounded server-side discovery path.

  2. 2

    Select the pages and viewports

    Review discovered URLs, choose the pages to include, and run Desktop, Laptop, Tablet, or Mobile captures together instead of checking one breakpoint at a time.

  3. 3

    Save the visual record

    Keep the capture in a project with version history, before-and-after comparison, review tasks, share links, and ZIP or PDF export where your plan supports it.

Useful when a site has more than one important page

Release-wide visual QA

Capture the selected landing pages, product pages, and documentation routes together so a deploy review covers the site surface that changed.

Responsive checks in one run

Compare the same URL across desktop, laptop, tablet, and mobile viewports, including dark mode when the capture settings call for it.

Evidence a reviewer can use

Organize screenshots by page and device, then share a review link or export the run for a pull request, QA report, or client handoff.

Sitemap screenshot tool FAQ

Does ViewportKit capture every URL in a sitemap automatically?
No. The sitemap scan gives you a bounded, grouped list of discovered URLs. You choose the pages and viewports for the capture run, which keeps large sites controllable and the resulting evidence relevant.
Can I capture a single URL instead of a sitemap?
Yes. The main capture flow also accepts one URL or a direct URL list when a sitemap is unavailable or you already know the exact pages to review.
Can sitemap screenshots be compared after a deployment?
Yes. Save the run in a project, run it again after the change, and use the project’s version history and comparison workflow to inspect what moved.

Need one page instead? Start with the full-page screenshot workflow and add a sitemap when the release surface grows.