Open Graph Preview Checker: Check Share Image Dimensions
Check whether your website preview image uses a clean Open Graph card size before adding it to a page, blog post, landing page, or product page.
Preview card
Website share image
Keep important text away from the outer edges.
AI answer card
Quick answer
- Best size
- 1200 x 630 px
- Best ratio
- About 1.91:1
- Use when
- Use this checker before adding an image to og:image metadata for a website, blog post, landing page, or product page.
- Avoid
- Avoid tiny source images, wrong-ratio exports, or placing text and logos near the outer preview edges.
- Check with
- Open Graph Preview Checker
- Last checked
- August 9, 2026
- Source boundary
- This page checks the image file locally; it does not crawl live URLs or validate website metadata tags.
Open Graph preview action path
Treat this page as the pre-publish route for website share cards. A working preview needs a clean image file, readable card composition, deployed metadata, crawler access, and cache refresh; checking only the dimensions is not enough when the shared URL is blank or stale.
Check the exported share image
Check image file
Start with the final 1200 x 630 or larger 1.91:1 image file before editing page metadata or refreshing preview caches.
Preview the card composition
Preview card
Use the local card preview to confirm the title, description, site name, and image framing still read like a share card.
Publish the metadata layer
Open metadata guide
Move to the Open Graph image guide when the file is ready and the page needs og:image, width, height, alt text, and Twitter Card fields.
Route stale or inconsistent previews
Debug preview
Use the troubleshooting route when Facebook, LinkedIn, Slack, X, or chat apps show a blank, old, cropped, or different card.
Open Graph metadata workflow gate
Use this gate before publishing a share card. The local checker only proves the image file shape; a live Open Graph preview also depends on absolute metadata URLs, crawler access, and platform cache refresh.
| Gate | What to check | Pass means | Route |
|---|---|---|---|
| Local image file | Confirm the exported image is 1200 x 630 or a larger 1.91:1 source before editing page tags. | The file can become the og:image source. | Check image |
| Absolute og:image URL | Use a full https image URL in page metadata, not a relative path or a logged-in asset URL. | Social crawlers can resolve the preview asset. | Open metadata guide |
| Public crawler access | Make sure the image URL returns 200, loads without authentication, and is not blocked by robots or hotlink rules. | The card can be fetched by Facebook, LinkedIn, X, Slack, and messaging crawlers. | Check public image |
| Platform cache refresh | After deployment, refresh or re-scrape the URL when a platform keeps showing an old image. | The live shared URL displays the current preview card. | Refresh checklist |
Live preview evidence-to-fix matrix
Use this matrix when the image file looks correct locally but the shared URL still renders a blank, stale, cropped, inconsistent, or wrong-surface preview. It keeps image fixes separate from metadata, crawler access, platform cache, and asset routing problems.
| Live preview evidence | Likely layer | Decision before fixing | Next route |
|---|---|---|---|
| Local file is 1200 x 630, but the shared URL is blank | Metadata or crawler access | Do not redesign the image first. Confirm the live page has absolute og:image metadata and that the image URL returns 200 publicly. | Check metadata setup |
| New image is deployed, but an old card still appears | Platform preview cache | Keep the image file if it passes. Verify the HTML points to the new asset, then refresh or re-scrape platform previews. | Route cache issue |
| Image passes locally, but text crops in the social card | Card composition | Move logo, title, product, or UI details toward the center and re-export a dedicated share-card image. | Preview card crop |
| A wide banner or header is being reused as og:image | Wrong asset type | Route the original wide image to the banner checker and export a separate 1200 x 630 Open Graph card. | Check banner asset |
| Facebook, LinkedIn, Slack, or X shows a different result | Platform-specific parser or cache | Confirm one canonical URL and one public image candidate, then validate platform behavior after the local image passes. | Route social preview |
| The preview image URL is a screenshot, thumbnail, or compressed download | Source file quality | Find the original export and run generic file facts before publishing the asset in page metadata. | Check source file |
Check the image file before metadata work
Open Graph previews start with a source image. If that image is too small, the wrong shape, or exported from a compressed preview, the URL debugger cannot fix the visual result.
Use this page for the file-level check, then use the full Open Graph image size guide for metadata, source, and update notes.
Open Graph checker search intent map
Use this page for the image-file part of link preview work. After the file passes the size check, open the guide for metadata tags, cache refresh, and platform-specific preview notes.
| Search query | What this page answers | Next action |
|---|---|---|
| open graph preview checker | Use the local checker on this page to test whether a preview image fits the common 1200 x 630 Open Graph card target. | Check OG image |
| open graph image checker | Check the preview file dimensions before adding it to og:image metadata or refreshing social preview caches. | Run image check |
| og image checker | Check the exported image dimensions first, then review the Open Graph image size guide for metadata and cache refresh steps. | Open Graph image guide |
| facebook share image checker | Use the 1200 x 630 file check before setting a Facebook or Meta share image, then keep text away from crop-prone edges. | Share image size guide |
| link preview image checker | Use this page when a landing page, blog post, or product page needs a clean card image before publishing. | Preview card layout |
| website preview image checker | Use this page when a site, article, landing page, or product page needs a share-card image before publishing. | Preview card |
| twitter card image size checker | Start with the same 1.91:1 source image check, then verify platform-specific metadata after publishing. | Social image sizes hub |
| social card preview checker | Use this when the same image will appear as a Facebook, LinkedIn, X, Slack, or messaging app preview card. | Route share card |
| og metadata checker | Start with the image file check here, then move to the Open Graph guide for og:image, title, description, and cache-refresh checks. | Metadata checklist |
| link preview debugger | Use this page for the preview image file, then verify live metadata and platform cache when the URL card is blank or stale. | Debug preview layer |
| social preview cache checker | If the file passes but the card still shows an old image, treat the issue as metadata deployment or platform cache refresh. | Check cache layer |
Image checker vs metadata debugger
This checker covers the image-file step. It does not replace a URL debugger: after the file passes, update page metadata and refresh platform caches to verify the live card.
| Step | Use when | Output |
|---|---|---|
| Check the preview image file | You have an exported share image and need to confirm 1200 x 630 or another 1.91:1 source size. | File-level image evidence before metadata work. |
| Update page metadata | The image file is ready but the page still needs og:image, title, description, or Twitter Card tags. | A page that points to the correct preview asset. |
| Refresh platform previews | The page metadata is updated but Facebook, LinkedIn, X, Slack, or another platform still shows an old card. | A verified live preview after cache refresh. |
How to find this Open Graph checker from ImageSizeKit
Open Graph Preview Checker is the file-level route for website share-card images. It is linked from the global desktop navigation, homepage router, social media image hub, Open Graph image guide, and general image size checker so crawlers and users can reach it before metadata debugging.
| Discovery route | Use when | Open |
|---|---|---|
| Global desktop navigation | Use the OG Checker link in the desktop header when you need a website share-card file check. | Open route |
| Homepage tool router | Start here when the image may be a social preview, banner, thumbnail, or generic upload asset. | Open route |
| Social Media Image Sizes hub | Use this route when the preview image belongs to a broader social image workflow. | Open route |
| Open Graph Image Size guide | Use this route when the file passes and you need metadata, cache, and publishing guidance. | Open route |
| Image Size Checker | Use this route when you first need raw width, height, ratio, file size, and format for any exported image. | Open route |
How this Open Graph preview checker is different
Use this checker when the image file itself needs to be tested before page metadata, crawler access, or platform cache debugging. It separates the local file preview from the Open Graph image size guide, the generic image checker, and platform cache debuggers.
| Differentiation point | Why this checker is distinct | Recommended next step |
|---|---|---|
| File-level preview check | This checker starts with the exported image file and verifies 1200 x 630, 1.91:1 shape, file readiness, and visual card framing before metadata work begins. | Keep Open Graph guide and checker pages routing source-image checks here before users debug a live URL. |
| Not the Open Graph image size guide | The guide explains target dimensions, og:image fields, source notes, and cache workflow. This page provides the local checker and preview card tool for the image itself. | Use /open-graph-image-size/ for publishing guidance, then return here when the file needs another local check. |
| Not a generic image checker | The generic checker routes many asset types. This page narrows the result to website share cards, social link previews, and Open Graph-specific failure layers. | Route broad file checks from /image-size-checker/ here only when the final destination is a website share card. |
| Not a platform cache debugger | A passing file check cannot prove Facebook, LinkedIn, Slack, X, or chat apps have refreshed the live page preview. | After the local image passes, verify absolute metadata URLs, crawler access, and platform cache refresh separately. |
Check Open Graph image dimensions
Upload a website preview image and compare it against 1200 x 630 or a larger 1.91:1 source image.
Drop an exported image here or choose a file.
The check runs locally in your browser and compares the file to this page's target sizes.
Start with an Open Graph preview image: 1200 x 630. Press Check sample to see the result path, then upload the final file for exact file-size evidence.
Canonical Open Graph checker result action map
Use this short action map immediately after the local file check. It routes the most common Open Graph checker results into the canonical next step before users spend time on metadata, cache refresh, or a redesign.
File matches 1200 x 630
Publish OG metadata
Keep this as the canonical share-card source, then publish absolute og:image metadata and record the live preview check.
File is 1.91:1 but larger
Preview card crop
Use it as a high-resolution source if key text stays readable after card downscaling.
File is close but too small
Check source facts
Re-export before cache debugging; stale preview tools cannot repair a source image that will look soft.
File is too wide or banner-shaped
Route banner asset
Route the asset as a banner or header first, then export a separate 1200 x 630 website share card.
File passes but live URL is blank or stale
Run publish gate
Treat the problem as metadata, crawler access, canonical URL, or platform cache before redesigning the image.
Build a share card preview
Draft the visible Open Graph card text and image together before you update page metadata or refresh platform preview caches.
imagesizekit.com
ImageSizeKit: Image Size Tools
Check image dimensions, aspect ratio, and upload readiness before publishing.
Open Graph publish readiness checker
Check the live-preview layers before you share the URL
Use this local checklist after the image-dimension check. It separates the file, metadata, crawler access, and platform cache layers so a good image file is not mistaken for a verified live card.
0 of 4 layers checked
0% complete
Start with the image file, then confirm metadata, public access, and cache refresh.
Next layer: Image file passes the 1200 x 630 or 1.91:1 check
Live URL preview evidence package
After the image file and publish-readiness checks, package the evidence for the person fixing the live URL. Include image file evidence, live page metadata, crawler access proof, preview cache action, wrong-surface routing, and the approval record so the team knows whether to redesign the image, update HTML, fix access, or refresh platform previews.
| Package part | Include in the note | Why it matters | Next route |
|---|---|---|---|
| Image file evidence | Final file name, width, height, ratio, file size, format, and whether the image passed the 1200 x 630 or larger 1.91:1 local check. | Designer or SEO owner can verify the actual source asset before page metadata or cache debugging begins. | Check image file |
| Live page metadata | Canonical page URL, absolute og:image URL, og:title, og:description, image width and height fields, and Twitter Card fields if used. | Developer can confirm the HTML points to the intended public preview asset instead of a stale or relative image path. | Review metadata |
| Crawler access proof | Page status, image URL status, no-login access, no robots or hotlink block, and one public image candidate for the card. | Prevents redesigning a good image when the real failure is crawler access or private asset hosting. | Route crawler issue |
| Preview cache action | Which platform still shows an old, blank, cropped, or different card and whether the URL was re-scraped after deploy. | Keeps Facebook, LinkedIn, Slack, X, and chat-app preview issues separate from local image-size problems. | Run publish gate |
| Wrong-surface routing | Whether the checked file is actually a banner, social image, thumbnail, or generic source file that should not be used as og:image. | Routes wide headers and reused campaign assets before they become badly cropped link preview cards. | Route asset type |
| Approval record | A copied line with file result, metadata status, crawler access, cache action, owner, and final live preview status. | Gives the publishing owner a durable record for why the URL preview is ready, blocked, stale, or returned for a fix. | Record readiness |
Open Graph platform preview acceptance record
Use this acceptance record after the live URL evidence package is prepared. It verifies the final og:image file, live page metadata, crawler access, platform preview cache, and wrong-surface escape route before a URL is approved for sharing.
| Acceptance gate | Proof to keep | Accept when | Validate |
|---|---|---|---|
| Final og:image file identity | Final file name, 1200 x 630 or larger 1.91:1 dimensions, file size, format, public image URL, and whether this is the exact asset referenced by metadata. | The checked image file is the deployed og:image candidate, not a screenshot, resized CMS thumbnail, banner export, or chat-preview download. | Check final image |
| Live page metadata match | Canonical page URL, absolute og:image URL, og:title, og:description, image width and height, and Twitter Card fields when used. | The live HTML points to the same image that passed the local file check and does not rely on a stale, relative, private, or fallback image URL. | Review metadata |
| Crawler access acceptance | The page and image URL return public 200 responses without login, private storage, robots blocking, redirect loops, or hotlink restrictions. | A social crawler can fetch both the page metadata and image asset without needing browser session state or internal network access. | Check crawler layer |
| Platform preview cache proof | Facebook, LinkedIn, Slack, X-style, chat-app, or internal preview evidence after the page metadata and image URL changed. | The platform preview has been refreshed or re-scraped after deploy and no longer shows a blank, stale, cropped, or wrong image card. | Run publish gate |
| Wrong-surface escape route | A note when the image is actually a banner, hero image, social post, product photo, YouTube thumbnail, or compressed proxy asset. | Wrong-surface assets are routed to the social, banner, product, or generic checker instead of being forced into an Open Graph card. | Route wrong surface |
Open Graph preview failure to repair coverage map
Use this coverage map when the local image passes but the live URL preview is still blank, stale, cropped, soft, or using the wrong visual. It routes each preview failure to the repair page that can keep the evidence and produce a usable share-card fix.
| Preview signal | Likely failure layer | Repair record to keep | Repair route |
|---|---|---|---|
| Blank card after the image file passes | Missing, relative, private, or blocked og:image metadata on the live page | Keep the passing file evidence, then repair absolute metadata, image width and height, alt text, and public image URL fields. | Repair OG metadata |
| Old image still appears after deployment | Platform cache or stale preview parser result | Record the live page URL, deployed og:image URL, platform showing the stale card, and the refresh or re-scrape action. | Run publish gate |
| Share image crops like a banner | A wide header, hero image, or profile cover was forced into a 1.91:1 link-preview card | Route the wide asset to banner review, then export a separate 1200 x 630 Open Graph image for the page URL. | Check banner source |
| Preview card uses a social post or vertical cover | A feed, Story, Reel cover, Shorts cover, or campaign social image is being reused as og:image | Use the social checker to identify the source surface, then create a dedicated website share card instead of reusing the social file. | Route social source |
| Preview image is soft or compressed | The og:image URL points to a screenshot, CMS thumbnail, chat download, or compressed proxy asset | Find the original export, check file facts, then replace the metadata URL with the high-quality public asset. | Check source file |
| LinkedIn, Facebook, Slack, or X crop differently | One Open Graph file is being treated as if every platform renders identical card crops | Confirm the central safe content and compare with platform-specific social image guidance before approving the live URL. | Compare social crops |
| Product or marketplace URL preview looks wrong | A product photo, Etsy listing image, Shopify image, or seller cover is being used without share-card composition | Keep product detail evidence, then decide whether the asset belongs to ecommerce image review or a dedicated website preview card. | Review product image |
| Video thumbnail is reused as the page preview | A YouTube-style thumbnail is being used for a page card without checking Open Graph readability and metadata behavior | Confirm whether the 16:9 file should remain a thumbnail, become a website share card, or be re-exported as 1200 x 630. | Check thumbnail source |
Open Graph launch decision log
Use this log after the live URL evidence package is prepared. The preview workflow should end with one operational decision: share the URL, re-export the image, repair metadata, fix crawler access, refresh platform previews, or route a wrong-surface asset before publishing.
| Launch decision | Use when | Record before handoff | Next route |
|---|---|---|---|
| Ready to share | The image file passes, live metadata points to the intended public og:image, crawlers can fetch it, and the preview cache has been refreshed. | Page URL, og:image URL, file dimensions, metadata owner, crawler status, cache refresh status, and approval owner. | Run final share checklist |
| Return image for re-export | The image is too small, wrong ratio, cropped badly, unreadable after downscaling, or exported from a banner/header artboard. | Failed image fact, replacement target, source artwork owner, crop note, and whether the file should route to banner or social image guidance. | Recheck image file |
| Fix metadata before sharing | The image file is correct, but the live page has missing, relative, stale, or mismatched og:image, og:title, or og:description fields. | Canonical page URL, expected metadata fields, deployed HTML owner, and the exact tag that needs repair. | Fix OG metadata |
| Fix crawler access | The browser can load the page or image, but social crawlers see a blank card, blocked asset, private URL, redirect problem, or non-200 response. | Page status, image status, access blocker, robots or hotlink note, and the owner who can make the asset public. | Route crawler issue |
| Refresh platform previews | The deployed HTML is correct, but Facebook, LinkedIn, Slack, X, chat apps, or other previews still show an old or inconsistent card. | Platform name, stale card evidence, cache refresh action, re-scrape time, and final preview screenshot. | Refresh preview cache |
| Route wrong-surface asset | The checked file is actually a banner, website hero, thumbnail, product image, social post, or compressed proxy instead of a dedicated 1.91:1 share card. | Wrong surface reason, replacement route, required export, owner, and the page URL that should receive the corrected share image. | Route asset type |
What to do after the OG image check
A passing file-level check means the image is a good candidate. You still need to place it in metadata, refresh platform caches, and confirm the preview after publishing.
If the file is correct but the shared URL is blank, stale, or missing a card image, open the Open Graph Image Size guide for the og:image, width, height, alt text, and cache-refresh checklist.
| Checker result | Meaning | Next action |
|---|---|---|
| 1200 x 630 match | Good default Open Graph card source | Open guide |
| 1.91:1 larger source | Good high-detail source before platform resizing | Open guide |
| Wrong ratio | The preview can crop or letterbox unpredictably | Open guide |
| Image too small | The preview may look soft after social platform resizing | Open guide |
| Metadata not updated | The file is ready, but the page still needs og:image tags | Open guide |
How to act on Open Graph checker status
Treat the local checker status as a publishing decision. A passing file can move into metadata work; a close or failed file should be fixed before you spend time refreshing Facebook, LinkedIn, X, Slack, or chat previews.
| Checker status | What it means | Publishing decision |
|---|---|---|
| Fits target | The image matches 1200 x 630 exactly, or it is a larger 1.91:1 source that can survive platform resizing. | Use it as the og:image source, then verify metadata and preview cache after deployment. |
| Close shape | The aspect ratio is close to the Open Graph card shape, but the file is smaller than the selected target. | Re-export from a larger canvas before publishing if text, UI details, or product edges need to stay sharp. |
| Needs resize | The image does not match the expected 1.91:1 shape, so platforms may crop, letterbox, or choose another preview. | Resize or crop toward 1200 x 630, then rerun the local check before touching metadata. |
| Metadata/cache issue | The image file is ready, but the live URL still shows a blank, stale, or wrong share card. | Move to the Open Graph image guide and debug og:image, absolute image URL, crawler access, and preview cache. |
Open Graph preview failure diagnosis card
Open Graph failures usually sit in one of three layers: the image file, the page metadata, or the platform preview cache. Use this diagnosis card before deciding whether to redesign the image, update page metadata, route the asset to a different image checker, or refresh the social preview.
| Checker result | Likely cause | Fix before publishing | Next route |
|---|---|---|---|
| Image passes size check, but preview does not change | The page or platform may still be using cached Open Graph metadata or an older image URL. | Confirm the deployed page uses the new image URL, then refresh platform previews after publishing. | Metadata and cache guide |
| Image file is correct, but social card is blank | The page may be missing an absolute og:image URL, the image URL may return an error, or crawlers may be blocked. | Check that og:image points to a public 1200 x 630 image URL that returns 200 without login or robots blocking. | Check image file first |
| Preview crops text or logo | The image can be the right 1.91:1 ratio while important text sits too close to crop-prone edges. | Move key text, logo, and product details toward the center before exporting the share image again. | Review social sizes |
| The preview asset is actually a banner | A YouTube, LinkedIn, Facebook, or site header banner is wider than an Open Graph link preview card. | Route wide header artwork to the banner checker and export a separate 1200 x 630 share-card image. | Open banner checker |
| Different apps show different card images | Facebook, LinkedIn, Slack, X, and chat apps can cache previews separately or read different metadata fields. | Confirm one public 1200 x 630 source image, then route the asset through the social image checker before refreshing each platform. | Route social image |
Open Graph preview failure decision matrix
A broken URL preview is not always an image-size problem. Use this matrix to separate source file dimensions, HTML metadata, crawler access, cache, canonical or redirect behavior, and wrong-surface reuse before publishing.
| Preview result | Likely cause | Decision before publishing | Route |
|---|---|---|---|
| Blank preview card | The page may be missing og:image metadata, the crawler cannot access the image, or the image URL is blocked. | Check the live URL preview first, then confirm the og:image size and metadata. | Check OG image size |
| Old image still appears | The platform cache may still hold an older card even after the image file changed. | Verify the page metadata, then refresh cache in the platform debugger after the new image is crawlable. | Preview again |
| Image is cropped badly | The source image may not match the 1200 x 630 / 1.91:1 card shape or important content is near the edge. | Use the Open Graph size guide or banner checker depending on whether the file is a share card or wide header. | Fix OG crop |
| Image looks fine locally but wrong when shared | The local file can be correct while HTML metadata, canonical URL, redirect behavior, or crawler access is wrong. | Treat this as a deployed-page preview problem, not a raw dimension problem. | Check source file first |
| Wide banner used as share card | A LinkedIn, YouTube, Facebook, or site header export is being reused as a 1200 x 630 social card. | Route wide headers to the banner checker and only use the OG guide for actual website share cards. | Check banner route |
| Social platform shows different crops | LinkedIn, Facebook, X-style shares, chat apps, and site embeds can crop or cache the same image differently. | Use the social checker when the image is shared across multiple platforms instead of one Open Graph target. | Route social image |
Open Graph preview result priority matrix
Use this after the deployed URL is reachable and the local image file has been checked. Fix the first broken layer before redesigning the card, because many preview failures come from metadata, crawler access, cache, or wrong-surface reuse rather than the artwork itself.
| Preview result | Fix first | Why it matters | Next check |
|---|---|---|---|
| Card is blank | Public og:image URL | A blank card usually means the crawler cannot read the image URL or page metadata, even if the source file dimensions are correct. | Check OG image setup |
| Old card still appears | Preview cache and image URL version | If deployed HTML is correct, Facebook, LinkedIn, Slack, X, or chat apps may still hold a stale preview cache. | Debug stale preview |
| Wrong image appears | Single canonical image candidate | Multiple page images, fallback metadata, redirects, or reused templates can cause a platform to select another asset. | Review OG metadata |
| Image crops like a banner | Separate 1.91:1 Open Graph card | Wide headers, covers, and banners do not map cleanly to social link-preview cards. | Route wide asset |
| Image is right but text is unreadable | Source dimensions and center text scale | Small text can fail after platform downscaling even when the file matches 1200 x 630. | Check source file first |
| LinkedIn differs from Facebook | Platform-specific preview validation | Different crawlers can use different caches, dimensions, fallback fields, and crop behavior for the same URL. | Route social preview |
Open Graph preview verification priority matrix
Use this order when a link preview still looks wrong after the image file passes. It keeps the workflow focused on the highest-impact checks first: public metadata, crawler access, dimensions, preview refresh, asset type, and platform-specific behavior.
| Priority | Check | Failure signal | First fix | Route |
|---|---|---|---|---|
| P0 | Confirm public preview metadata | The checker file passes, but the shared URL has no title, description, or image candidate. | Deploy absolute og:title, og:description, and og:image metadata before testing platform cards. | Review OG guide |
| P0 | Verify crawler access to the page and image | A browser can load the image, but social cards stay blank or use a fallback image. | Make the page and og:image URL public, fetchable, and free from login, private, robots, or hotlink blocks. | Route debug layer |
| P1 | Check dimensions before recaching | The preview appears, but it crops, blurs, or hides important text after platform resizing. | Use a 1200 x 630-style 1.91:1 source, then confirm the exported file dimensions locally. | Read file facts first |
| P1 | Refresh previews after metadata changes | The old title or old image still appears after the new metadata has been deployed. | Recheck the URL after deployment and use platform preview tools where available. | Use pre-upload gate |
| P2 | Separate share cards from banners | A wide header, cover, or channel banner is being forced into an Open Graph card. | Route wide artwork through the banner checker and export a dedicated website share-card image. | Check banner route |
| P2 | Compare platform-specific preview behavior | LinkedIn, Facebook, Slack, X, or messaging apps crop or select different images from the same page. | Use the social image hub after the generic Open Graph card passes the local file check. | Open social hub |
Image file vs page metadata vs platform cache
A local image check cannot prove that a deployed URL will render the right card. Treat publish readiness as a four-layer check: file dimensions, metadata, public crawlability, and platform cache refresh.
| Layer | Check | Failure signal |
|---|---|---|
| Image file | The exported asset is 1200 x 630 or a larger 1.91:1 source image. | The checker flags wrong ratio, small source size, or soft text. |
| Page metadata | The live page uses absolute og:image, og:title, og:description, and Twitter Card tags. | A URL debugger shows missing metadata, a relative image path, or an old title. |
| Public crawlability | The image URL returns 200, loads without login, and is not blocked from social crawlers. | The social card is blank even though the local file dimensions are correct. |
| Platform cache | Facebook, LinkedIn, X, Slack, and chat apps have refreshed their preview cache after deployment. | The same URL keeps showing an old image after the page metadata has changed. |
Open Graph preview checklist
- Use a 1200 x 630 or larger 1.91:1 source image.
- Keep text, logo, and product details away from the outer edges.
- Compress the image without blurring text or UI lines.
- Use the image in your og:image metadata after the file passes the size check.
- Refresh platform preview caches after updating the page.
- Pair this checker with the full Open Graph image size guide.
- Use the Open Graph publish readiness checker before sharing the live URL.
Public Open Graph preview workflow reference
For a citable share-card workflow map, use the public reference that connects local image-file checks with Open Graph metadata, crawler access, cache refresh, and social preview troubleshooting.
External workflow
Open Graph preview checker public workflow reference
Opens the self-owned workflow asset for share-card image checks and AI citation context.
Open Graph preview checker FAQ
What size should an Open Graph preview image be?
A practical default is 1200 x 630 pixels, about a 1.91:1 ratio. Use the platform-specific guide for additional metadata and crop notes.
Does this checker validate my website metadata?
No. This page checks the image file dimensions locally. It does not crawl your URL or validate og:image tags yet.
Why does my preview image crop even at the right size?
Different platforms can crop thumbnails, round corners, or compress previews. Keep text and logos away from the outer edges.