Documentation
Learn how to configure capture schedules, timezones, trigger windows, and cloud storage — from first setup to production workflows.
Browse sections
Need help?
Contact SupportElement Screenshots
Element Screenshots let you capture a specific part of a page instead of the full viewport. This is ideal for monitoring banners, widgets, pricing blocks, or critical UI components.
Instead of capturing everything visible on the page, Element Screenshots isolate a single element and crop the final image to its exact bounds. You configure this with SelectorXPath and optional pre-capture actions.
What are Element Screenshots?
An Element Screenshot captures only the area occupied by the element matched by SelectorXPath. The browser loads the page, finds the target element, and then crops the screenshot to that element.
- • Captures a single component instead of the whole page
- • Crops precisely to the element’s bounding box
- • Useful when only a small section matters
- • Output is a standard image file
Supported fields
Element screenshots and pre-capture interactions are configured using these four fields in your Shot Schedule:
SelectorXPathTargets the element to capture (and/or focus). This is the primary field used for element screenshots.
SelectorClickClicks an element before capture (example: open a tab, expand a section, dismiss a modal).
SelectorHideHides matched elements before capture (example: sticky headers, chat widgets, cookie overlays).
SelectorHoverHovers over an element before capture (example: reveal dropdowns, tooltips, or hover-based menus).
Capture behavior
Element Screenshots follow this execution order:
- 1. Page loads using the selected Web Profile
- 2. Apply optional actions: Hide / Click / Hover (when configured)
- 3. Locate the target element using
SelectorXPath - 4. Compute the element’s bounding box
- 5. Capture and crop the screenshot to the target element
If the target element is missing (or changes dynamically), the job can fail based on how the page behaves and what the selector matches at runtime.
Common use cases
- • Monitor a pricing table without capturing the full page
- • Capture a hero banner or promotion tile
- • Track consent UI / cookie banner states
- • Compare a single UI widget over time