Confirm the exact result
- Check the target URL, including its path and query string.
- Compare the capture timestamp with the time the page changed.
- Check any
cachedindicator in the API response and whether your application reused a previous stored URL. - Download the result again without relying on an image viewer or browser’s previously opened file.
Check the target’s own cache
A CDN or service worker can serve older content to a new visitor. Your signed-in browser can also show a different page version from a signed-out capture. Compare a clean browser session and avoid assuming that every stale image originated in the screenshot service.
Ask support to trace the request
Send the request ID, actual capture timestamp, full public URL, and response metadata. Describe which part of the image is outdated and when you expected it to change.
Documentation
Related support articles
Fix a blank or incomplete screenshot
Check page readiness, selectors, client-side rendering, and blocking options.
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.
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]