Skip to content

Open Graph Image Validator

Free and no obligation. A real reply from me, not a bot.

Prefer Saad Raza SEO on Google Add this site as a preferred source and Google will show more of my SEO and AI search guides when you search.

Add saadrazaseo.com as a preferred source on Google
Free tool

Our server checks the public URL you enter. Results are not stored.

Loading the tool...

To check the image that appears when a page is shared, paste its URL into the free Open Graph Image Validator above. It finds the og:image and twitter:image tags, then downloads each image and checks the URL, the HTTP status, the real file type, the file size, the pixel dimensions and the aspect ratio. It also checks whether the declared width and height match the file. It shows a preview cropped to the 1.91:1 shape used for large link cards, and it checks up to 10 pages at once.

Last updated: 6 November 2026. Written by Saad Raza.

Key takeaways

  • Use a 1200 × 630 px JPG or PNG for og:image. That 1.91:1 shape shows in full on Facebook, LinkedIn, WhatsApp and Slack, and close to full on X.
  • The image URL must be absolute (starting with https://) and must return 200 with an image content type. A broken image means no image in the share.
  • Facebook rejects images over 8 MB and X rejects card images over 5 MB, but 100 to 300 KB is a sensible target.
  • Write Open Graph tags with property="og:image", not name=. Some networks accept both; the protocol specifies property.
  • Networks cache previews, so after a fix you need to refresh the cache in each network’s debugging tool.

What the Open Graph image does

When someone pastes your link into a social network or messaging app, the app fetches the page and reads its Open Graph tags to build a preview card: a title, a description and an image. X reads its own Twitter card tags first and falls back to Open Graph. The image is the largest part of the card, so a missing, broken or badly cropped image makes a share look unfinished and gets fewer clicks.

Open Graph images do not affect Google rankings directly, but they shape how your content travels, and every share is a chance to earn a visit or a link. The social share preview tool shows how a card looks; this validator checks that the image itself will actually load and fit.

How to use the Open Graph Image Validator

  1. Paste one page URL, or up to 10 with one per line. Mix page types, such as the home page, a blog post and a product, because templates often set images differently.
  2. Run the check. Our server loads each page, reads its tags, then downloads each image once.
  3. Read the summary table: pass, check or fix, the image URL, its size and type, and the twitter:card value.
  4. Look at the crop preview for each page. Anything outside the frame will be cut off in a large link card.
  5. Fix the tags or the image, then refresh the preview in the Facebook Sharing Debugger and LinkedIn Post Inspector.

What the validator checks

CheckPassWarning or fail
Tag presentog:image foundNo og:image (fail)
URLAbsolute https URLRelative URL (fail), http:// (warning)
Tag syntaxproperty="og:..."name="og:..." (warning)
Status200404, 403, 5xx or an HTML page instead of an image (fail)
File typeJPG, PNG, WebP or GIFSVG or an unusual type
File sizeUnder 1 MBOver 5 MB (X limit), over 8 MB (Facebook limit)
DimensionsAt least 600 × 315, ideally 1200 × 630Under 600 × 315 (small thumbnail), under 200 × 200 (fail)
RatioAbout 1.91:1 or 2:1Square or other shapes that get cropped
Declared sizeog:image:width and height match the fileMismatch (warning)
Supporting tagsog:title, og:url, og:image:alt, twitter:cardMissing (information)

A worked example with real pages

I ran the four example pages through the validator on 6 November 2026.

  • github.com passed. Its og:image is a 1200 × 630 JPEG of about 124 KB, a 1.90:1 ratio, with og:image:alt and twitter:card set to summary_large_image.
  • MDN Web Docs got two warnings. Its Open Graph tags are written with name= instead of property=, and the image is a 1024 × 1024 square PNG, which large cards crop top and bottom. Its twitter:card is summary, so X shows a small square thumbnail, which suits a square logo.
  • My own SEO tools page got a warning too. It uses a 1512 × 1512 square photo as its share image, and has no og:image:alt. The fix is a 1200 × 630 version of the image.
  • example.com failed because it has no og:image at all, so each network chooses an image or shows none.

That spread is typical. Big sites usually get the basics right but still ship square images and unusual tag syntax, and small sites often have no share image set for most pages.

How to fix the common problems

  • No og:image: in WordPress, Yoast and Rank Math add Open Graph tags automatically. Set a default image in the plugin’s social settings and a specific image for important pages. On other platforms, add the tag to the page head.
  • Wrong shape: create a 1200 × 630 version. Keep text and faces inside the middle, because some apps crop further. The image resizer can crop to exact dimensions.
  • File too large: run it through the image compressor. A JPG at 80 percent quality is rarely distinguishable in a preview.
  • Image returns 403: hotlink protection or a firewall may block social crawlers. Allow facebookexternalhit, LinkedInBot, Twitterbot and WhatsApp in your firewall or CDN rules.
  • Declared size mismatch: update og:image:width and og:image:height, or remove them. Facebook uses them to render the first share before it has downloaded the file.

While you are improving how pages look when shared, it is worth checking how they look in Google too, with the SERP snippet preview and the meta tag generator.

Limits

The validator reads the HTML our server receives. Tags added by JavaScript after the page loads are not seen, and most social crawlers do not run JavaScript either, so tags must be in the server HTML. Each network has its own rules and changes them from time to time, so the thresholds here are the published minimums and common recommendations, not a guarantee of how every app will render. The crop preview loads the image in your browser. Up to 10 pages are checked per run; each page and each image counts as one check towards the fair-use limit.

Questions about the Open Graph Image Validator

What size should an Open Graph image be?

1200 × 630 pixels, which is a 1.91:1 ratio. It displays as a large card on Facebook, LinkedIn and most messaging apps. Images under 600 × 315 pixels show as a small thumbnail instead.

Why is the wrong image showing when I share my page?

Either the og:image tag points to a different image, it is missing so the network picked one, or the network has cached an old preview. Check the tag here, then refresh the cache in the Facebook Sharing Debugger or LinkedIn Post Inspector.

Do I need a separate twitter:image?

No. X uses og:image when there is no twitter:image. Add twitter:card set to summary_large_image if you want the large image layout on X.

Can I use a WebP or SVG image?

WebP works on most major networks, but JPG and PNG are the safest. SVG is not supported for share images, so convert it to PNG.

Does the Open Graph image help SEO?

Not as a Google ranking factor. It improves how links to your page look on social networks and in chat apps, which can bring more clicks, shares and, over time, links.

If you want every template’s social and search snippets set up properly, my on-page optimisation service covers titles, descriptions and share tags, and you can ask for a free audit. You can also browse the other free on-page SEO tools.

Got your results? Let’s turn them into a plan

Tools show the issues. I will tell you which ones matter most and how to fix them.

Your details are only used to reply to your request. No spam.

Grow my trafficCall