What a complete Lens capture file contains #
A complete Lens capture file contains: the winning CSS rules for the element you clicked, the losing rules with reasons, origin classification for every rule, the ancestor chain up to the body element, any competitor elements detected, capture context (URL, Viewport, browser, timestamp), and the correlation output. If you open the file and any of those sections appear empty or abbreviated, the capture was incomplete.
Common reasons a capture file is missing data #
The page was still loading when you clicked #
Lens reads the CSS state at the moment you click. If the page is mid-load, some stylesheets may not have applied yet, JavaScript-injected styles may not have run, and the computed CSS state won’t reflect the final rendered result. The capture file will contain whatever the browser had at that moment, which may be significantly less than the full picture.
Fix: wait for the page to fully load and any visible animations or transitions to settle. Then reactivate Lens and capture again.
The element is partially rendered by JavaScript #
Some elements only reach their final CSS state after JavaScript runs: a slider that positions itself after a transition, a sticky header that changes state after scrolling, a modal that applies its styles on open. If you capture the element before JavaScript has finished applying its styles, the capture reflects the pre-JavaScript state.
Fix: interact with the page to trigger the final state (scroll to trigger sticky behavior, open the modal, run the slider to the broken position), then capture while the element is in that state.
A Content Security Policy limited what Lens could read #
Some pages set a Content Security Policy that restricts what browser extensions can access. When a CSP limits Lens’s content script, the capture may complete but with a reduced data set. The popup will usually note when a CSP restriction affected the capture.
Lens captures what the browser makes available to content scripts. On pages with strict CSPs, some inline styles or dynamically injected rules may not be accessible. The capture file will contain what was readable, but it may not include everything needed for a definitive diagnosis.
The element is inside a cross-origin iframe #
If you clicked inside a cross-origin iframe, the capture file will contain no CSS data for that element. This is a browser security restriction that no extension can work around. See What Lens Can and Can’t Diagnose for a full explanation.
What to do with a partial capture file #
A partial capture file isn’t worthless. It contains whatever Lens was able to read, and a developer can often work with partial data more effectively than with a screenshot. When sharing a partial capture file with a developer, note that it’s incomplete and describe the conditions at the time of capture (mid-load, post-scroll, etc.). That context helps them interpret what’s missing.
If the capture is consistently incomplete on a specific page despite timing the capture correctly, contact support@loupelylens.com with the URL and a description of what you’re seeing. Some page configurations require Lens-side adjustments to capture correctly.