Troubleshooting
Image could not be fetched
Our API could not download the image from its URL, and the extension's bounded retry with bytes failed too. Usually a login-walled or short-lived URL.
Updated
How images are normally checked
The extension sends the image's URL; our API fetches the file (up to 8 MB), reads its metadata and runs the provenance checks. If the fetch fails, the API answers with a "fetch failed" result rather than an error, and the extension retries once by reading up to 4 MB of the image with the page's own credentials and sending the bytes. Only when both paths fail does the card say "Image could not be fetched".
Why a fetch fails
- The image is behind a login or is served only to the page's session, so our server cannot reach it.
- The URL is short-lived or signed and expired between the page load and the check.
- The host blocks server fetches, or the file is larger than the limits.
- The image is a
data:orblob:URL; those never go through the API and are read directly by the extension, so this message means the local read failed.
What still ran
Writing-pattern analysis for any text in the post, and, where the image is same-origin, an in-page provenance read. The detector rows list what ran and what was skipped.
What you can do
Scroll away and back to trigger a fresh check with a fresh URL. If it always fails on one site that you think should work, report it with the page address.