OG Image Checker

Verify your Open Graph image server-side: format, 1200x630 dimensions, 1.

Visual Studio Release Diff Regression Check Staging Check SEO Checker URL Debugger llms.txt Hreflang OG Image Social Meta JSON-LD Schema Markup Social Preview SERP Preview Robots.txt

OG Image Checker

Paste the URL of your Open Graph image and SerpCraft verifies it server-side: correct format, 1200×630 dimensions, 1.91:1 aspect ratio, and file size — exactly how Facebook, X, and LinkedIn will fetch it. Browsers can't do this reliably on their own (CORS), so this check actually reads the image bytes.

Fetched server-side (no CORS limits). Limited to 30 checks per hour per IP. Results cached 24h.

Tip: paste the exact URL from your og:image meta tag to make sure Facebook and X will render it correctly.

An Open Graph image checker that verifies your og:image server-side: whether it loads, its real format, its exact pixel dimensions, its aspect ratio, and its file size. Facebook, X, LinkedIn, and Slack all fetch your image independently — if it fails any of these checks, your link renders as a bare URL. This is the one check browsers cannot do on their own.

What breaks a social preview (and what does not)

Social platforms fetch the og:image URL, download the bytes, and validate them: correct format, minimum dimensions, and reasonable file size. Common failure modes are a 404 or redirect loop, a WebP image old scrapers refuse, a 600x300 image that gets upscaled into blur, and a 12 MB image that times out the fetch. The checker tests exactly these conditions, the same way the platforms do.

Why this cannot be a browser-only tool

A browser checking an image on another domain hits CORS: it can load the image to display it, but it cannot read its bytes, dimensions, or file size. Every image checker that claims to do this client-side is guessing from the DOM, which fails for most real-world images. SerpCraft fetches the image server-side and parses the actual header bytes — the same method Facebook's scraper uses.

The 1200x630 rule, explained

Facebook and LinkedIn recommend 1200x630 pixels (a 1.91:1 ratio) — large enough to look sharp on retina screens, with a ratio that fits their crop. Twitter prefers 1200x675 for its own card. Any image at least 600x315 will render, but platforms upscale it, and upscaling is where images get blurry. The checker reports your dimensions, your ratio, and the recommended thresholds.

Formats and sizes that actually work

JPG, PNG, and WebP are the safe choices for og:image. GIF and BMP render inconsistently across platforms, and SVG is not supported by most scrapers at all. File size matters too: Facebook's crawler has historically struggled with very large images, and every platform gives up after a few seconds. Under 2 MB is the safe zone; the checker flags anything above.

Frequently Asked Questions

More SEO Tools

Visual SEO Studio

Interactive visual SEO workspace

Release Diff

Compare staging vs production URLs

SEO Regression Checker

Catch SEO drops between releases

Staging SEO Checker

Compare staging vs production

Fixing a known problem?

Why Does Google Show the Wrong Meta Description?Your OG Image Is Not Showing When You Share a Link Canonical and noindex on the Same Page: a Signal Conflict Schema Passes Validation but Google Shows No Rich Results Google Sees Different HTML Than Your Browser Does