To make website thumbnail images from a list of URLs, capture each page at a normal desktop viewport (1920 by 1080 or 1366 by 768), then scale the image down to your thumbnail width, typically 300 to 600 pixels, and save it as WebP or JPG. Capturing at full size and shrinking afterward gives a thumbnail that looks like the real site, while capturing at a tiny width gives you the site's mobile layout instead. A batch tool can do both steps for the whole list at once, saving the full-size capture and the thumbnail side by side.
This guide explains how to choose the capture size and thumbnail size, what to do about pop-ups and slow pages, and how to name the files so they drop straight into a directory, gallery or link list.
Where website thumbnails are used
- Directories and listings: a preview image for each listed business or resource.
- Portfolios: a grid of client sites. Our guide to website screenshots for a portfolio covers the full-size side of this.
- Link pages and resource lists: a visual cue next to each link.
- Internal tools and reports: a quick visual reference beside each site in a spreadsheet or dashboard.
- Presentations: a slide showing a market's websites at a glance.
Capture size vs thumbnail size
There are two different sizes involved, and mixing them up is the most common mistake.
The capture size (viewport)
This is the browser window size the page is rendered at. It decides which layout the site shows. At 1920 or 1366 pixels wide, you get the desktop layout people recognize. At 390 pixels, you get the phone layout.
The thumbnail size
This is the size of the final image file. You get it by scaling the capture down. A 1920 by 1080 capture scaled to 480 pixels wide becomes 480 by 270, the same shape, just smaller.
Do not set the viewport to 400 pixels to make a "small" screenshot. Most sites switch to their mobile layout at that width, so your thumbnail will show a phone design stretched into a tiny desktop-shaped frame.
Common thumbnail sizes
There is no single standard, but these sizes work well for most uses. All keep the 16:9 shape of a 1920 by 1080 capture.
| Thumbnail width | Resulting size | Good for |
|---|---|---|
| 240 px | 240 × 135 | Small icons beside links, dense tables |
| 320 px | 320 × 180 | Directory listings, sidebars |
| 480 px | 480 × 270 | Gallery grids, cards |
| 640 px | 640 × 360 | Larger cards, high-density screens at 320 px display size |
For sharp results on high-resolution screens, save the thumbnail at twice the size it will be displayed and let the browser scale it. A thumbnail shown at 320 pixels wide looks crisper if the file is 640 pixels wide.
Viewport, not full page
For thumbnails, capture the visible area rather than the whole page. A full-page capture of a long site might be 1920 by 8000 pixels; shrunk to 320 pixels wide, it becomes a thin strip where nothing is recognizable. The top of the page, with the logo, navigation and hero image, is what people recognize at a glance.
If you want a taller thumbnail, for example a 4:3 or square card, capture the viewport at a taller size such as 1440 by 1080, or crop the top of a full-page capture to the shape you need.
Format and file size
Thumbnails are small, so file size matters more than perfect quality:
- WebP gives the smallest files with good sharpness and is supported by current browsers. It is the best default for thumbnails on the web.
- JPG at a quality around 80 is a safe choice that works everywhere.
- PNG is unnecessary for thumbnails and produces much larger files. Keep it for full-size originals.
For more on balancing quality and size, see reducing screenshot file size without losing quality, and for a deeper look at scaling images, our guide on resizing screenshots in bulk.
Making thumbnails from a URL list, step by step
Bulk Captures can capture the whole list and create thumbnails in the same run:
- Choose the URL capture mode and paste your URLs, load a TXT or CSV file, or import a sitemap.
- Choose visible area rather than full page.
- Set the viewport to 1920 (or 1366 if you prefer a slightly closer view of the content).
- Set a load delay of a few seconds so hero images and fonts are in place.
- Turn on thumbnails and set the thumbnail width. The full-size capture is saved alongside it.
- Choose the format, for example WebP for the web.
- Set a naming pattern such as
{domain}or{domain}_{n}so each file is named after its site. - Click Capture.
Naming each thumbnail after its domain makes it easy to match images to listings: a directory entry for example.com simply uses example.com.webp. If the list contains several pages from the same domain, include the counter to keep the names unique.
Dealing with pop-ups, banners and slow pages
- Cookie banners often cover the bottom of the viewport. At thumbnail size they are usually a thin strip, but if they cover too much, crop the full-size capture before scaling or capture those sites manually.
- Newsletter pop-ups may appear after a few seconds. A shorter delay sometimes captures the page before they open.
- Slow sites may show blank areas or loading spinners. Increase the delay and rerun just those URLs.
- Sites that block automated visits may return an error page. Sort the folder by size; error pages tend to be unusually small.
Keeping thumbnails up to date
Websites change, and a directory full of outdated thumbnails looks neglected. Rerun the same list in Bulk Captures every few months into a new dated folder, then replace the old images. Because the file names come from the domain, the new thumbnails can simply overwrite the old ones in your site's image folder, while the dated originals stay in your archive.
Before replacing them, glance through the new set at Extra large icon size in File Explorer. A site that has closed, moved or started showing a parked domain page is easy to spot at that size, and it is a good prompt to update or remove the listing itself.
Frequently asked questions
What size should website thumbnails be?
It depends on where they appear, but 300 to 600 pixels wide is common for directories and galleries. Capture at a desktop width and scale down.
Should a website thumbnail show the full page?
Usually not. A thumbnail of the top of the page at a desktop viewport is easier to recognize than a tall, narrow full-page image.
Can I keep full-size images as well as thumbnails?
Yes. Bulk Captures can save thumbnails alongside the full-size captures in the same run.
