Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
An Open Graph image debugger helps you see what a social platform can read from a page and diagnose why a shared link shows the wrong image, no image, or an outdated preview. Start by checking the page’s Open Graph tags and whether its image URL is accessible to a crawler; then use the relevant platform debugger to inspect that platform’s scrape and preview. A debugger can reveal the problem, but the fix usually belongs in your page metadata, image delivery, or cache—not in the debugger itself.
What an Open Graph image debugger checks
Open Graph (OG) metadata describes a web page to services that create link previews. The tags belong in the document’s <head>. The Open Graph protocol identifies four basic properties: og:title, og:type, og:image, and og:url. The image debugger workflow is to inspect those values, see which image URL the crawler encounters, and compare that evidence with the platform’s preview.
og:image is a URL representing the page’s object. It is not an image upload or a setting inside the debugger. If it points to the wrong file, the platform may produce the wrong preview even if the correct image appears prominently on the page itself.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What the debugger can and cannot tell you
- It can help expose metadata values and a platform’s interpretation of a page when that platform provides a debugger.
- It can help separate a tag or image-delivery problem from a preview that may be using an earlier scrape.
- It does not automatically repair your HTML, guarantee that every platform will choose the same image, or ensure that an already-shared post changes immediately.
Inspect the page before requesting another scrape
- Open the page’s source. Use your browser’s view-source option or developer tools to inspect the HTML returned for the public page. Find the
<head>and search forog:. - Check the four basic properties. Confirm that title, type, image, and URL tags exist and describe the page you intend to share. In particular, copy the value of
og:imageand verify that it is the intended image URL. - Open the image URL directly. Check that it resolves to the expected image for a visitor without requiring a login or an interactive browser session. A URL that looks correct in a logged-in admin view may not be available to a platform crawler.
- Review the image’s structured metadata. Where useful, include
og:image:type,og:image:width, andog:image:height. The protocol says a page specifyingog:imageshould also specifyog:image:alt; write alternative text that describes the image rather than using it as a caption. - Look for duplicates and ordering. If more than one
og:imagetag exists, inspect their order and determine why each is present. The protocol gives the first value preference when properties conflict, but individual consumers may have their own selection behavior. - Use the platform’s debugger. Run the page through the relevant platform tool, inspect what it reports, and request a fresh scrape if that capability is available. Recheck the rendered preview after correcting the page or image delivery issue.
Understand the tags that determine image selection
| Property | What to verify |
|---|---|
og:title |
The title value is present and belongs to the page being shared. |
og:type |
The page declares the type of object represented. |
og:image |
The URL identifies the intended representative image and is available to the crawler. |
og:url |
The canonical object URL is the one you expect the platform to associate with the preview. |
og:image:type |
When included, the MIME type describes the image resource. |
og:image:width and og:image:height |
When included, the values describe the image’s pixel dimensions. |
og:image:alt |
Describe what is in the image; the protocol recommends providing this when an image is specified. |
Do not treat a debugger preview as proof that every service will make an identical choice. Duplicate image values and platform-specific behavior can lead consumers to interpret the same page differently.
#1 Best Overall
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Use the platform-specific debugger for the share in question
When the preview is wrong on one service, use that service’s own debugger if one is available. The Open Graph protocol’s resource list identifies Facebook Object Debugger as Facebook’s official parser and debugger. Search for the official tool from Facebook rather than relying on a third-party page that may show a different scrape. Interface labels, access requirements, and current capabilities can change; verify those details in the platform’s current tool.
A platform debugger is useful because it lets you inspect that platform’s scrape rather than infer its behavior from another service’s preview. The essential comparison is between the tags and image URL available to the crawler and what the platform reports. If the debugger sees the intended tags but shows an older preview, the issue may be stale cached data. If it cannot retrieve the intended image or reads different tags from your browser, investigate delivery, redirects, server responses, or crawler access before repeatedly requesting a scrape.
Fix common Open Graph image problems
No image in preview
- Check whether
og:imageis present in the returned page HTML, not only added later by client-side code. - Confirm the tag contains an image URL and not a relative path that resolves differently than intended.
- Open the URL without a logged-in session and confirm it returns the image rather than an error, redirect loop, or HTML page.
- Check whether the page or image delivery system blocks the crawler. A browser screenshot alone cannot establish that the platform’s crawler can retrieve the resource.
The wrong image appears
- Compare the exact
og:imageURL in the source with the image shown in the preview. - Find duplicate
og:imagetags and inspect their document order. The first value has protocol-level preference when values conflict, although platform behavior can differ. - Check whether your content-management system emits page-specific metadata or reuses a site-wide default.
The preview shows an old image
First confirm that the current page source points to the new image and that the image URL serves the new file. Then use the platform debugger to inspect or request a fresh scrape if the tool offers that action. Re-scraping is not a promise that every existing post or downstream cache will update instantly; timing and behavior depend on the service.
Recommended Free Tools
The debugger and browser appear to disagree
Compare the HTML available to an unauthenticated visitor with what the debugger reports. Differences can result from server-side variations, redirects, access controls, or metadata inserted only after browser scripts run. Inspect the response delivered at the public URL and the final image destination rather than relying only on the page as rendered in your own session.
Rank #3
Image dimensions and formats: avoid assumptions
The Open Graph protocol defines structured image metadata such as MIME type, width, height, and alternative text. It does not establish in the material cited here a current universal Facebook image-size, file-size, or format threshold. Requirements and recommendations can vary by platform and change over time, so do not treat a commonly repeated dimension as a current Meta guarantee without checking Meta’s current official guidance.
Use a screenshot to inspect the rendered page, not to replace the debugger
A screenshot can help you see whether a page visually loads as expected, but it does not reveal which metadata a social crawler reads or prove that the crawler can fetch the image. ScreenshotNeo is a website screenshot API and MCP server for developers; it can capture a page for visual inspection, while the page’s tags and the platform debugger remain the right tools for OG diagnosis. See ScreenshotNeo.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Or skip the browser setup
One GET request can capture the page as an image; replace YOUR_API_KEY and the example URL with your own. See the ScreenshotNeo API documentation for request options.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers indicate the page verdict and billing status. Its MCP server gives AI agents tools to take screenshots, get page information, and capture PDFs. The free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan to try a capture.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Practical limits and troubleshooting checklist
- Metadata looks right, but the preview is not: inspect the platform’s scrape and consider whether its preview may be cached; do not assume an immediate refresh for every existing share.
- The image opens for you but not for the crawler: test the public image URL without a logged-in browser, then investigate access restrictions and redirects.
- More than one image is declared: review tag order and remove unintended duplicates where possible; protocol ordering does not guarantee identical selection across all consumers.
- Image quality or acceptance is in doubt: consult current first-party platform requirements. The protocol properties alone do not settle each platform’s current size or format thresholds.
- You are debugging a visual layout issue: use a screenshot as a visual aid, but separately inspect source metadata and the platform’s own scrape.
Frequently Asked Questions
Is a website screenshot enough to validate an Open Graph image?
No. A screenshot shows rendered appearance; it does not establish what metadata a social platform read or whether its crawler fetched the image.
Does the Open Graph protocol specify exact current Facebook image dimensions?
The protocol information covered here defines image metadata fields, but it does not establish a current Facebook dimension threshold. Check Meta’s current official guidance for platform-specific requirements.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Will requesting a new scrape update every old link post immediately?
That is not guaranteed. A fresh scrape can help diagnose or refresh a platform’s stored preview, but existing posts and downstream caches may behave differently.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
