9 Things to Screenshot on Your Site Before Filming an Ad

Before filming an ad from your own website, screenshot nine specific things: the hero once every asset has finished loading, a product detail large enough to inspect, the complete pricing table, one specific proof section, the exact booking or checkout step, matching mobile and desktop views of your strongest section, a hover or interaction state, any empty state a new visitor might see, and a comparison or before-and-after element if the site has one. Each screenshot should show something a viewer can recognise and trust, not just fill a gap in the edit.

1. The hero, once every asset has finished loading

Screenshot the hero after the page has fully settled, not on first paint. Many sites swap in a placeholder image, load a webfont a beat late, or fade a headline into view, so a screenshot taken too early can capture a layout that no real visitor sees for more than a second. Load the page fresh, wait for images, fonts, and any hero animation to finish, then capture it. If the hero includes a background video, pause on the frame that best represents the product rather than a mid-transition blur. This screenshot usually opens the ad, so it has to match what a visitor actually experiences, not a loading state that only exists for a moment.

2. A product detail at a size someone could actually inspect

Do not screenshot the whole page and expect the product to read once it is cropped into a vertical frame. Zoom in on the specific detail that proves the offer: a material close-up, a dashboard reading, a menu item, or a feature panel, captured large enough that its text and edges stay legible once placed inside a 1080x1920 canvas. A full-page screenshot forces every element down to a small fraction of the frame, and the one detail that matters ends up too small to read. Capture the detail on its own, at the resolution it needs, and let the wider page provide context elsewhere in the edit rather than in this shot.

3. The pricing table, captured at its full width

Screenshot the entire pricing section in one image, with every tier and its price visible, rather than a partial capture that cuts off a column. Viewers use pricing to decide whether an offer is worth investigating further, so a cropped or half-visible price creates confusion instead of clarity. If the table is wider than a single screen, capture it in sections that can be reassembled, or capture it at a browser width where all tiers fit. Check that the currency, billing period, and any discount label are all visible in the same shot; a price shown without its period can misrepresent the actual offer once it appears on screen.

4. One proof section, chosen for what it actually says

Pick the review, case detail, or testimonial that names a specific outcome, not the one that simply says something is good. A screenshot of "great service, would recommend" proves less than one that mentions a number, a result, or a concrete detail, because a specific claim gives the viewer something to evaluate. Screenshot the proof section exactly as it appears on the live site: real name, real date, real context, since inventing or restaging a review is the kind of shortcut that makes an ad look fabricated the moment someone checks. If the site has several proof sections, choose the one most relevant to the hook you plan to open with, not simply the newest or the longest.

5. The exact screen where a visitor commits

Screenshot the actual moment of action: the calendar with an open slot showing, the cart summary just before payment, or the form with its final button visible. This differs from screenshotting the booking page in general, because the goal is to show the specific step a visitor completes, not the page that leads up to it. If that step is buried behind several clicks, or only works after filling in unrelated fields, the screenshot will expose the problem before the ad does, which is useful information in itself. A related checklist on signs a website isn't ready to become a video ad covers what to fix first if this step doesn't hold up.

6. The same section on both mobile and desktop

Capture your strongest section at both a mobile viewport and a desktop viewport, because many sites rearrange content between the two rather than simply scaling it down. A three-column feature layout on desktop might stack into a single column on mobile, changing what's visible without scrolling. Knowing both versions matters because a vertical ad usually needs a mobile-style crop, and starting from a layout that already stacks vertically is easier than forcing a wide desktop layout into a narrow frame. Take both screenshots at the browser's actual mobile width, not a shrunk desktop screenshot, since a genuine mobile layout often reveals or hides different elements than a resized one does.

7. A hover or interaction state, not just the resting page

Some of the most useful proof only appears on interaction: a dropdown menu, a tooltip explaining a feature, a filter panel, or a button's active state. Screenshot the page at rest only and you miss functionality that might be the actual reason to buy. Trigger the interaction manually, hold it, and capture it in that state. This matters most for products where the value sits in a specific piece of interface behaviour rather than a static layout, such as a live search result appearing or a price updating after a selection. Note which interaction you captured and why, so the editor can pair it with a line that explains what's happening on screen.

8. Any empty state a new visitor might actually see

An empty state is what a first-time user sees before they've added anything: an empty cart, a dashboard with no data yet, a blank search result. If your onboarding flow shows this screen to every new visitor, it's worth knowing what it looks like before deciding whether to include it in the ad. An empty state can undercut a promise, such as "see your results instantly", if it's the first thing shown, or it can genuinely help set expectations if the ad is honest about a setup step. Screenshot it either way, so the decision to include or avoid it is made deliberately rather than by accident.

9. A comparison or before-and-after element, captured at both ends

If the site has a slider, side-by-side comparison, or a toggle between two states, screenshot both endpoints separately rather than trying to capture the interactive element mid-drag. A slider frozen halfway usually looks broken rather than informative. Capture the "before" position, then the "after" position, each as a clean still, so an editor can recreate the reveal deliberately with proper timing instead of relying on one scrappy screenshot. If the comparison relies on hover or a click to switch state, note the exact trigger so the same view can be reproduced consistently later, rather than guessing at it after the fact.

None of this needs to be captured by hand every time. Paste a URL and sizzledraft has a headless browser capture the real site the way a visitor would see it, then builds the video from those actual screenshots rather than a redrawn guess. If you would rather see it than plan it, start from your own site.