Bulk Captures
Windows 10 & 11 Buy license · $39.95
Workflows

How to Take Great Website Screenshots for Your Design Portfolio

Take website screenshots for your portfolio that show your work at its best: desktop and phone sizes, full page vs hero shots, formats and file sizes.

Updated 5 minute read The Bulk Captures team

The best website screenshots for a portfolio are taken at launch, at a clean desktop width such as 1920 or 1440 pixels, with a phone-width version alongside, and saved as PNG originals that you then export to WebP or JPG for your portfolio site. Use a "hero" capture of the top of the page as the main image, keep a full-page capture for anyone who wants to see the whole design, and capture every client site in one consistent batch so the set looks like a collection rather than a pile of mismatched images.

This guide covers when to capture, which sizes to choose, how to prepare each page, and how to keep originals and web-ready copies organized.

Capture at launch, not later

The most common portfolio regret is waiting. Client sites change: a new owner swaps the theme, an in-house team adds banners, or the business closes and the domain lapses. Capturing at launch gives you a permanent record of the work exactly as you delivered it.

  • Make the capture part of your launch checklist, right after the final sign-off.
  • Capture the key pages, not just the home page: an inner page, a product or service page, and any page with a design detail you are proud of.
  • Recapture your whole client list once or twice a year. Some sites will have changed; you keep both versions.

Check your contract before publishing client work. Most clients are happy to be featured, but some agreements restrict it, and work for unreleased products may be confidential.

Choose your sizes

Showing a design at desktop and phone sizes tells a prospective client you think about every screen. These widths cover what most portfolios need:

WidthUse in the portfolio
1920 pxLarge hero images and case study headers
1440 px or 1366 pxLaptop view; often looks more balanced than full HD for content-heavy sites
768 pxTablet view, useful for showing a layout adapting
390 pxPhone view, shown in a row or next to the desktop image

Capturing all widths in the same run keeps them consistent. Our guide to screenshotting a website at different screen sizes explains how viewport widths work and how display scaling affects them.

Hero shot or full page?

You will usually want both, used in different places.

Hero shots

A viewport capture shows what a visitor sees before scrolling. At 1920 by 1080 or 1440 by 900, it makes a clean, wide image for a portfolio grid or the top of a case study. It is also the shape people recognize, because it looks like a browser window.

Full-page captures

A full-page capture shows the whole design from header to footer as one tall image. It is the best way to show structure and rhythm, but it is too tall for a grid. Use it inside a case study, in a scrolling frame, or as a link for visitors who want to see everything.

Phone captures

Phone-width full-page captures are long and narrow. Crop them to the first two or three screens for display, and keep the full version as your original.

Prepare the page before capturing

A few minutes of preparation makes the difference between a record and a showcase.

  1. Dismiss or avoid cookie banners. A batch tool sees each page as a first-time visitor, so banners will appear. For hero shots of a single site, capture from a browser where you have already accepted them, or crop the banner out afterward.
  2. Wait for animations. Entrance animations and sliders can be caught halfway. A load delay of three to five seconds usually lets them settle.
  3. Check lazy-loaded images. In full-page captures, images lower down may not have loaded. See fixing full page screenshots with missing images if you see gaps.
  4. Use real content. If the site launched with placeholder text or stock images, consider waiting a few weeks for real content before your main capture.
  5. Avoid personal data. Do not capture logged-in dashboards or pages showing real customer details.

Formats and file sizes

Keep two versions of every screenshot: an archive original and a web-ready copy.

VersionFormatWhy
Archive originalPNGLossless, sharp text, safe to edit and re-export later
Portfolio imageWebPMuch smaller than PNG with sharp results; supported by current browsers
Portfolio image (alternative)JPG, high qualityWorks everywhere, good for photo-heavy designs
Client presentationMulti-page PDFOne file with every page, easy to email

Very tall full-page captures can exceed WebP's maximum height of 16,383 pixels, so keep long pages as PNG or JPG. For more on choosing formats and keeping files small, see our guide to reducing screenshot file size without losing quality.

Capturing all your client sites in one batch

If you have built a dozen or more sites, capturing them one at a time in a browser is slow and the results are inconsistent. Bulk Captures captures the whole list at once on your Windows PC:

  1. Paste your client URLs, or load them from a TXT or CSV file.
  2. Choose viewport for hero shots, or full page for complete designs. Run both if you want both.
  3. Select your widths, for example 1440 and 390, so desktop and phone versions are captured in the same run.
  4. Set a load delay of a few seconds for animations and fonts.
  5. Use a naming pattern with the domain and date, such as {domain}_{date}_{n}, so each file says which site and when.
  6. Save as PNG for the originals. Turn on resizing to a fixed width and thumbnails if you also want smaller copies for a portfolio grid.
  7. Click Capture.

Every site is captured at the same sizes, with the same delay, in the same format, which is exactly what makes a portfolio grid look polished. Running the same Bulk Captures batch again next year into a new dated folder gives you a second snapshot of every site without touching the first.

Presenting the screenshots

  • Be consistent. Use the same width and crop for every item in a grid. Mixed sizes look untidy even when the work is good.
  • Pair desktop and phone. A desktop hero next to a phone capture tells the responsive story in one glance.
  • Show detail with crops. A tight crop of a navigation menu, a pricing table or a form can say more than a whole page.
  • Add a subtle border or shadow if the design has a white background, so it does not merge into your page. See adding a border or drop shadow to screenshots.
  • Label each image with the client, the year and your role, so visitors know what they are looking at.

Keeping your archive organized

A simple folder structure saves hunting later: one folder per client, with sub-folders by year or project, and a web folder for exported copies. Never overwrite an original. If a site changes and you recapture it, keep both sets; the older one may be the version you want to show.

Frequently asked questions

Should portfolio screenshots be full page or just the top?

Use a hero shot of the top of the page as the main image, with a full-page capture available for anyone who wants to see the whole design.

What format should portfolio screenshots be?

WebP or high-quality JPG for images on your portfolio site, and PNG for your archived originals.

Why capture client sites now rather than later?

Client sites change or go offline. Capturing them at launch keeps a record of your work exactly as you delivered it.

Get three guides like this every month, plus software update notices.Subscribe →