The quickest way to screenshot all pages of a website is to use its XML sitemap: the sitemap lists every page the site wants search engines to find, so you can import it into a batch screenshot tool and capture each URL automatically. Find the sitemap (usually at /sitemap.xml), filter out pages you do not need, choose full-page or visible-area captures, and run the batch. This guide walks through each step and what to do when a site has no sitemap.
Step 1: Find the website's sitemap
Most sites built on a modern platform or content management system publish a sitemap automatically. Try these in order:
- Add
/sitemap.xmlto the domain, for examplehttps://example.com/sitemap.xml. - Try
/sitemap_index.xml, which many WordPress SEO plugins use. - Open
https://example.com/robots.txtand look for a line beginningSitemap:. It gives the exact address. - If it is your own site, check your site platform or SEO plugin settings, which usually show the sitemap address.
Sitemap index files
Larger sites split their sitemap into several smaller ones, listed in a sitemap index. Opening it shows links to files such as post-sitemap.xml, page-sitemap.xml and product-sitemap.xml. This is useful: you can pick just the section you need, for example only the pages and not hundreds of blog posts.
Step 2: Decide which pages you actually need
"All pages" can mean thousands of URLs on a store or blog. Before capturing, decide what the screenshots are for:
| Purpose | Pages to include |
|---|---|
| Redesign or migration record | Every page template: home, main pages, a sample of posts, products and categories |
| SEO or content audit | Main pages and top landing pages, plus anything flagged with an issue |
| Legal or compliance archive | Every page in the sitemap, on a fixed date |
| Client sign-off after launch | All pages and posts, but not tag, author or archive pages |
If the full list is large, open the sitemap URLs in a spreadsheet, filter by path (for example everything containing /blog/), and save the subset you want as a text or CSV file.
Step 3: Choose your capture settings
Full page or visible area
For a record of a whole site, choose full page: each page is saved from top to bottom as one tall image. For a quick visual index or thumbnails, the visible area at a desktop size is smaller and faster to review.
Screen sizes
One desktop width, such as 1920 pixels, is enough for many jobs. If mobile layout matters, add a phone width such as 390 pixels, and see our guide to screenshotting a website at different screen sizes.
Load delay
Give each page a few seconds after loading for images, fonts and scripts to finish. Sites with sliders, embedded videos or heavy scripts may need longer.
Format
PNG keeps text sharp and handles very tall pages. For a deliverable, a single multi-page PDF with one page per screenshot is often the tidiest thing to send a client.
Step 4: Import the sitemap and run the batch
In Bulk Captures, you can import a sitemap directly instead of copying URLs out of it:
- Choose the URL capture mode.
- Import the sitemap, or load the filtered TXT or CSV file you made in Step 2.
- Select full page or visible area, the viewport widths and the load delay.
- Set a naming pattern, for example
{domain}_{date}_{n}, so each file carries the site name and a running number. - Choose the output folder and format, then click Capture.
Bulk Captures visits each page in turn, waits for it to finish loading, saves the screenshot and retries any page that errors. Because there is no per-capture limit, a 400-page site is simply a longer run, not a bigger bill.
Be considerate with sites you do not own. Capturing hundreds of pages in a row is a lot of requests for a small server. A longer delay between pages spreads the load out, and you should respect any terms of use the site publishes.
What if the site has no sitemap?
Some small or older sites have none. You still have options:
- Use the navigation. For a site with 10 to 30 pages, copying links from the main menu and footer into a text file takes a few minutes.
- Use a site crawler. SEO crawling tools follow links from the home page and can export every URL they find to CSV, which you can then load as your list.
- Search the site. Searching
site:example.comin a search engine shows indexed pages, though not necessarily all of them.
Our guide on how to screenshot URLs from an Excel list covers cleaning up an exported list before you capture it.
Checking and organizing the results
After the run, sort the output folder by size. Tiny files are usually blank or error pages; very small full-page captures may be pages that redirected to a login or a 404 page. Rerun those individually with a longer delay.
Keep each run in its own folder named with the date, such as example.com_2026-10-05. If you capture the same site again after a redesign, you can compare the two folders page by page. If you need to send the whole set to a client, combining it into one document is covered in our guide on how to combine screenshots into one PDF.
Limits of sitemap-based capture
- Only public pages. Sitemaps list pages for search engines, so account areas, checkouts and pages behind a login will not be included or captured.
- Sitemaps can be out of date. Deleted pages may still be listed and show as 404s; new pages may be missing.
- Interactive states are not captured. Tabs, accordions and menus appear in their default state. Capture those by hand if they matter.
- Cookie banners appear. Each page is visited as a first-time visitor, so consent banners and pop-ups show as they would for a new visitor. For an honest record of the site, that is usually what you want, but note it in any report so readers are not surprised.
Within those limits, a sitemap is the most reliable way to get a complete, consistent set of screenshots of a site in one go.
Frequently asked questions
How do I find a website's sitemap?
Try adding /sitemap.xml or /sitemap_index.xml to the domain, or open /robots.txt, which often lists the sitemap address on a Sitemap: line.
What if the site has no sitemap?
Build a URL list by hand from the navigation menus, or export one from a site crawler, then load it as a text or CSV file.
Can I screenshot pages that need a login?
A sitemap only lists public pages, and a batch capture visits pages as a logged-out visitor. For pages behind a login, open them in your browser and use a window or scrolling capture instead.
