Check whether the target loads
Open the exact URL in a signed-out browser. A page that requires a login, a location-specific session, or a consent action may differ from what the capture browser can see. Compare a viewport capture before attempting a full-page capture.
Wait for the content you need
Set waitFor to a stable CSS selector for the visible content. Use waitUntil: "load" when the page needs resource loading, and add a small delay if its application renders after loading. networkidle can be unsuitable for pages with continuously active connections.
{
"url": "https://example.com",
"waitUntil": "load",
"waitFor": "main",
"delay": 1000
}Remove conflicting options
Temporarily disable ad, cookie-banner, and popup blocking to see whether those options affect required page resources or layout. Check custom CSS, hidden selectors, and any element selector. Report both the result and the expected view with the exact capture settings.
Documentation
Related support articles
Fix a cut-off full-page capture
Check scrollable content, capture height, sticky elements, and full-page mode.
Fix missing images, fonts, or styles
Identify late-loading resources, blocked requests, and differences from your own browser.
Remove cookie banners and popups
Use blocking settings and selectors without removing page content you need.
Need help with this issue?
Email support with this article, your request or capture ID, and the result you expected. Remove credentials and private information first.
Email [email protected]