Clip to element: monitor only the page section you care about
Full-page screenshots on e-commerce pages produce too much noise to be useful
In our price monitoring experiment on Amazon, we captured full product pages and ran into a recurring issue. Geolocation banners, delivery modals, and recommendation blocks kept shifting the layout between captures, and visual diff was showing 20%+ changes on pages where the price hadn't moved at all.
We covered this in detail in our article on layout shifts in price monitoring and suggested two workarounds — hide selectors to remove unstable elements, and running captures more frequently at the start to map out which blocks "float" between renders. Both help, but neither solves the problem completely, because the core issue is that complex e-commerce pages simply have too many moving parts.
A delivery banner might render as a modal on one capture and as an inline bar on the next. The "featured offers" block appears and disappears. Recommendations change with every visit. All of this lands in the screenshot and pollutes the diff — even after you've hidden some elements with hide selectors. You end up playing whack-a-mole with noisy elements, and new ones keep appearing faster than you can add selectors for them.
The fix: capture only the element you actually care about
So we added a setting called Clip to element. Instead of capturing the entire page, you specify a CSS selector for a specific element, and the screenshot crops exactly to its boundaries. Only that block makes it into the image — no header, no banners, no footer, no sidebars, no recommendation blocks. Everything that generated noise in full-page or viewport captures simply isn't part of the screenshot anymore.

How to find the right CSS selector: a real eBay example
Let's say you want to track the right panel on an eBay product page — the one with the price, condition, quantity, and the Buy It Now button. Open DevTools (F12 in Chrome), hover over that panel, and look at its CSS class. In this case it's .right-summary-panel-container.

Paste that selector into the "Clip to element" field when creating or editing a monitor. On the next capture, the screenshot shows only the right panel — no image gallery on the left, no eBay header, no recommendations at the bottom. Just the price block and its immediate context.

Now visual diff compares only this block. If the price changes from $3,750 to $3,500, the diff highlights the change right in the price zone — without noise from banners and layout shifts elsewhere on the page. The number of false positives drops sharply because the elements that "float" between captures simply aren't in the comparison zone anymore.
Clip to element vs hide selectors: two approaches to the same problem
Hide selectors remove individual elements from the page before capture — cookie banners, modals, ad blocks. That works when there are a few known problem elements and you can list them all. But on pages like Amazon or eBay, there can be a dozen "noisy" blocks, and hiding each one individually gets tedious. New blocks can appear at any time, and you're constantly updating your selector list.
Clip to element approaches the problem from the other direction. Instead of "remove everything unwanted," you say "show only what I need." One selector — and the screenshot contains only the price block, or the product card, or the specs table. Everything outside the selected element doesn't make it into the screenshot or the diff. It's a fundamentally different strategy: subtraction (hiding things you don't want) versus selection (keeping only what you do want).
In practice, the two approaches combine well. You can use clip to element to crop to the right block and still add a hide selector to remove a popup that appears inside that block — a cookie banner overlay or a "sign in for better prices" prompt that renders on top of the element you're clipping to. We described the full process of finding selectors and configuring hide rules in our guide on dismissing popups before capture.
Other use cases where clipping to a specific element makes sense
Price monitoring is the most obvious case, but the same logic applies anywhere you need to watch a specific part of a page without the noise from everything around it.
Tracking the pricing table on a SaaS pricing page is a natural fit — clip to the pricing grid and ignore the hero section, testimonials, and FAQ that surround it. Monitoring legal blocks on Terms of Service pages works the same way, especially when the legal text sits inside a wrapper element while the rest of the page has dynamic navigation and footer content. Checking product availability on marketplace listings benefits from clipping to the buy-box or stock status element — you don't need the entire product page to know whether an item is in stock. And keeping an eye on specific sections of a competitor's landing page — say, just the hero section or just the testimonials block — lets you track one part of the page with precision instead of getting noise from everything else.
The smaller the screenshot area, the more precise the diff and the less noise in your alerts. If you've been getting too many false positives from full-page captures, clipping to the element you actually care about is probably the simplest fix available — one selector, and the problem goes away.
You can try this on the free plan — up to 3 URLs. The "Clip to element" field is available when adding a new monitor or editing an existing one.
Start archiving websites today
Free plan includes 3 websites with daily captures. No credit card required.
Create free account
Vitalii Holben