Open Graph Image Size: Dimensions, Safe Zones, and Export Checks
Prepare Open Graph image dimensions for website previews, Facebook shares, LinkedIn posts, Slack, Discord, and social cards.
Last checked: August 9, 2026. Sources: Open Graph protocol, Meta for Developers: images in link shares, LinkedIn Help: URL post image ratio. ImageSizeKit is independent and is not affiliated with Web and social previews.
Keep preview text large and central so social apps can crop or downscale without losing the message.
AI answer card
Quick answer
- Best size
- 1200 x 630
- Best ratio
- 1.91:1
- Use when
- Use 1200 x 630 pixels as the practical default Open Graph image size for most website link previews. Meta recommends images at least 1200 x 630 pixels for best display on high-resolution devices.
- Avoid
- The preview is readable in the design file but unreadable in feeds.
- Check with
- Check exported OG image first
- Last checked
- August 9, 2026
- Source boundary
- Based on the listed Web and social previews source links and ImageSizeKit local checks. ImageSizeKit is independent and is not affiliated with Web and social previews.
Canonical result routing
Canonical Open Graph image result action map
Use this map after checking an Open Graph image or deployed URL. Match the result to the next repair route before sharing the page, so source-file, metadata, crawler, cache, and wrong-surface problems stay separate.
Source image matches 1200 x 630
Check source file
Keep the source image only after checking file facts, readable center text, and 1.91:1 preview-card intent.
Metadata is missing or mismatched
Preview metadata
Preview the deployed URL and fix og:image, width, height, title, description, canonical URL, and Twitter card fields.
Crawler access is blocked
Check crawler access
Confirm the page URL and image URL are public HTTPS resources before refreshing social previews or redesigning the image.
Preview cache shows an old image
Debug stale preview
Record the platform cache state, refresh the preview tool, and use a fresh image URL when the old card remains cached.
Asset is actually a banner or product image
Route wrong surface
Route the file away from Open Graph and create a dedicated preview card only if the final job is a website share image.
OG image size action path
Use this path when you need to move from a size recommendation to a file that is actually ready to publish. Confirm the target dimensions, check the exported file, fix crop-sensitive details, then route reused artwork before uploading it to Web and social previews.
Confirm the target size
Review specs
Use the og image size specs before opening a design tool so the canvas, ratio, safe zone, and source guidance match the final Web and social previews surface.
Check the exported file
Check export
Upload the final export in the local checker and confirm width, height, ratio, file size, and nearest workflow before publishing.
Fix crop-sensitive details
Fix readiness
Use the checker result and checklist to repair edge text, tiny labels, soft exports, wrong ratios, and reused artwork before upload.
Route reused artwork
Route reuse
Open the social image hub when the same creative may also be a banner, vertical cover, Open Graph card, marketplace image, or thumbnail-like file.
Check OG image size dimensions
Upload your exported og image size image and compare it against the target sizes on this page before publishing.
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 og image size: 1200 x 630. Press Check sample to see the result path, then upload the final file for exact file-size evidence.
OG image size checker result action priority matrix
Use this matrix after checking the exported file. It turns the checker result into the next action before you upload, resize, or reuse the same image on another platform.
| Priority | Checker result | Fix first | Why it matters | Next route |
|---|---|---|---|---|
| P0 | Matches the og image size target | Review crop-sensitive content before upload | A matching canvas still needs the final platform crop, text placement, subject framing, and upload context checked before publishing. | Review this guide |
| P0 | Checker reads a different publishing surface | Route the file before resizing | A wide banner, vertical cover, square product photo, thumbnail, or Open Graph card can look close while belonging to a different workflow. | Route social image |
| P1 | Ratio is close but the file is smaller than the target | Re-export from a larger source canvas | Small but correctly shaped images often upload successfully and still look soft, blurry, or weak after platform resizing. | Check exported OG image first |
| P1 | Aspect ratio is wrong | Calculate a clean replacement size | Cropping by eye can hide important text, products, faces, or brand marks; calculate the target ratio before exporting again. | Calculate ratio |
| P2 | The same creative will be reused elsewhere | Split platform-specific exports | One file rarely works cleanly across feed posts, stories, banners, link previews, marketplace cards, and thumbnails. | Compare platform sizes |
OG image size search intent router
Search results often mix size guides, reusable templates, platform-specific crop rules, and exported-file checks. Use this route map to choose the next ImageSizeKit page by the problem you are actually solving.
| Query or task | What the user likely needs | Best route |
|---|---|---|
| open graph image size | Find the current og image size dimensions, ratio, crop notes, and export checks. | OG image size |
| open graph image size template | Start from a reusable layout or safe-area planning route before designing the final asset. | Image size templates |
| open graph image size checker | Verify the exported file dimensions, ratio, type, and publishing readiness before upload. | Check exported OG image first |
| social media image sizes | Compare this asset with adjacent social, banner, cover, thumbnail, product, or Open Graph image sizes. | Social Media Image Sizes |
Design-to-upload route
A size guide answers what to design. A checker confirms what you exported. Keep those steps connected so the final file, platform crop, and preview metadata are all checked before publishing.
| Stage | Use it for | Next page |
|---|---|---|
| Choose the platform asset | Confirm that this page matches the actual Web and social previews placement before choosing dimensions. | Compare social sizes |
| Plan from a template | Open template routes when you need guide layers, source files, or safe-area planning before design. | Open templates |
| Check the exported file | Upload the exported image locally and confirm width, height, ratio, format, and file size. | Check exported OG image first |
| Preview the deployed URL | After publishing metadata, use the Open Graph checker to separate image problems from page metadata or cache issues. | Open Graph preview checker |
OG image size specs
| Field | Value | How to use it |
|---|---|---|
| Recommended practical size | 1200 x 630 px | Strong default for Facebook-style link previews and many social preview workflows. |
| Aspect ratio | 1.91:1 | LinkedIn Help lists 1.91:1 for custom images used with URL posts. |
| Open Graph image tag | og:image | The Open Graph protocol requires an image URL to represent the object. |
| Structured width and height | og:image:width / og:image:height | Optional structured properties that help parsers understand the preview image dimensions. |
| Meta link-share file size | 8 MB max | Meta's link-share image documentation says the image file must not exceed 8 MB. |
Pre-upload checklist
Use this checklist after exporting the image and before publishing it to the platform or website.
- Create the image at 1200 x 630 pixels unless a platform-specific preview requires another size.
- Use a clear subject and large headline text.
- Set og:image to an absolute HTTPS image URL.
- Add og:image:width and og:image:height when your CMS allows it.
- Add useful og:image:alt text for accessibility and crawler context.
- Confirm the exported file in the Image Size Checker upload area before you attach it to page metadata.
- Open the Open Graph Preview Checker after deployment to separate image-size problems from metadata or cache problems.
- Test the final URL after deployment because preview caches can lag behind image changes.
Open Graph guide and preview checker handoff loop
Use this loop when a 1200 x 630 source image, page metadata, crawler access, and live social preview all need to agree before the URL is shared.
| Workflow step | Use this page for | Use the preview checker for | Next route |
|---|---|---|---|
| Source image decision | Choose 1200 x 630 or a larger 1.91:1 export, keep text central, and confirm the image is a link-preview card. | Check the same file in a realistic card preview before it is attached to live metadata. | Check source image |
| Metadata deployment | Prepare the og:image, width, height, alt, title, description, canonical URL, and Twitter Card handoff. | Verify the deployed URL exposes the expected card instead of a draft, fallback, or stale asset. | Preview deployed URL |
| Crawler access check | Confirm the page and image should be public, HTTPS, canonical, and free from login or private CDN assumptions. | Separate browser-visible images from images that social crawlers can actually fetch. | Check OG preview |
| Cache refresh decision | Record whether the image URL changed, which platform preview needs refresh, and whether the old card may remain cached. | Preview the live URL again after deployment and cache refresh before sharing campaign links. | Refresh preview |
| Wrong-surface route | Decide whether the file is truly an Open Graph share card or a reused banner, profile header, cover, thumbnail, or product image. | Route files that pass size checks but fail preview intent to the matching checker or platform guide. | Route reused asset |
Open Graph image source-to-preview answer matrix
Use this matrix when a website thumbnail, social share image, or og:image query needs a concrete route from source-file dimensions to deployed metadata and final link preview behavior.
| Checker evidence | What it answers | Publishing decision | Next route |
|---|---|---|---|
| 1200 x 630 source file | The exported file is close to the practical Open Graph source size for website thumbnails, link previews, and social share cards. | Use it as og:image only after width, height, file size, ratio, and central text readability pass. | Check source file |
| og:image metadata fields | The deployed page should expose an absolute HTTPS image plus optional width, height, type, and alt fields that crawlers can read. | Use the source file after the page metadata is deployed, public, canonical, and not blocked by redirects or auth. | Preview deployed URL |
| Website thumbnail intent | Queries such as website thumbnail size, link preview image size, and social share image size usually need a page preview image, not a profile banner. | Keep this route as the canonical Open Graph size guide, then preview the live URL before sharing it. | Check OG preview |
| LinkedIn or Facebook share mismatch | If a 1200 x 630 file crops, disappears, or shows stale art, the issue may be metadata, cache, crawler access, or platform-specific preview handling. | Separate image-size checks from deployed preview-cache checks before changing the design file again. | Route social preview |
| Wide banner reused as share card | A website hero, LinkedIn banner, YouTube channel banner, or Facebook cover can be too wide even when it looks like a strong preview image. | Export a dedicated 1200 x 630 source instead of reusing header artwork for the Open Graph card. | Check banner asset |
Open Graph image publish readiness decision card
Use this card before sharing a URL when the source file, og:image metadata, public crawler access, URL canonicalization, or platform preview cache may still block the final social card.
| Publish state | Preview risk | Fix before sharing | Next route |
|---|---|---|---|
| Source image is ready but not checked | The design looks like a share card, but the exported file may be the wrong ratio, too small, too compressed, or full of tiny text. | Check the actual exported file first, then use it as the og:image source only after the dimensions and ratio pass. | Check source file |
| Metadata is ready but the URL is not deployed | A local preview or CMS draft can look correct while the public HTML still lacks absolute og:image, title, description, width, or height fields. | Deploy the page, inspect the live HTML, then preview the public URL rather than a draft or localhost URL. | Preview deployed URL |
| Public crawler access is uncertain | Social crawlers may be blocked by auth, cookies, hotlink protection, robots settings, redirects, or a private CDN even when the image opens in your browser. | Confirm both the page URL and image URL return public 200 responses before refreshing platform previews. | Check OG preview |
| Platform preview still shows the old image | The exported image and metadata may be correct, but Facebook, LinkedIn, Slack, Discord, or message apps can keep stale cached card data. | Use a fresh image URL when possible, then refresh or wait for platform cache after deployment. | Debug stale card |
| Wide banner is being reused as an OG card | LinkedIn banners, YouTube channel art, Facebook covers, and website headers are not the same job as a 1.91:1 link preview card. | Create a separate 1200 x 630-style export, or route the file through the banner checker if it is really a header asset. | Route wide asset |
Open Graph metadata field checklist
Use this table after the image file is ready. The 1200 x 630 export is only one layer; the deployed page also needs metadata that social crawlers can read.
| Field | What it controls | Failure signal | Check with |
|---|---|---|---|
| og:image | The absolute HTTPS image URL that represents the page in social previews. | The preview is blank, uses a random image, or keeps showing an old asset. | Check image file first |
| og:image:width and og:image:height | Structured dimensions that help crawlers understand the image before rendering the card. | Preview parsers resize slowly, crop unexpectedly, or guess dimensions. | Calculate ratio |
| og:title and og:description | The text shown beside or below the preview image in link cards. | The image is correct but the card headline or description is stale. | Preview card |
| twitter:card and Twitter image fields | Fallback metadata used by X/Twitter-style cards and some social parsers. | The URL looks good in one app but shows a small or missing card in another. | Open social checker |
Open Graph publishing decision sequence
Use this sequence before sharing a live URL. It turns a 1200 x 630 image-size recommendation into a publishing gate for metadata, crawler access, canonical URLs, redirects, and preview cache refresh.
| Publishing gate | Pass condition | Failure signal | Next route |
|---|---|---|---|
| File is the right Open Graph source | The image is 1200 x 630 or a larger 1.91:1 source, with readable center text and no fragile edge details. | The card crops, letterboxes, or turns soft after platform resizing. | Check source file first |
| Page exposes one public og:image | The deployed HTML points to one absolute HTTPS image URL that returns 200 without login, cookies, or blocked crawler access. | The preview is blank, a fallback image appears, or a social app chooses the wrong asset. | Preview deployed URL |
| Metadata dimensions match the asset | og:image:width and og:image:height match the final exported file when your CMS or framework supports those fields. | Parsers guess the dimensions, render slowly, or crop the preview unexpectedly. | Calculate 1.91:1 |
| Canonical and redirects resolve cleanly | The shared URL, canonical URL, redirects, and final HTML all point crawlers to the same page and intended preview image. | The URL works in a browser but shared cards show stale metadata or another page's image. | Check preview workflow |
| Preview cache is refreshed after deploy | After metadata changes are live, the platform preview is re-scraped or allowed to refresh with the new image URL. | The old card keeps appearing even though the deployed HTML is correct. | Debug stale card |
| Asset is not a banner or profile header | The image is a website link-preview card, not a LinkedIn profile banner, YouTube channel art, or Facebook cover photo. | A wide header is forced into a 1.91:1 social card and loses important content. | Route wide asset |
Open Graph metadata-to-preview handoff package
Use this package after preparing a 1200 x 630 Open Graph image. It turns the guide into a developer, SEO, CMS, or client handoff record for file checks, metadata fields, public access, cache refresh, and final preview approval.
| Handoff part | Include in the note | Why it matters | Next route |
|---|---|---|---|
| Source image proof | Final file name, 1200 x 630 or larger 1.91:1 dimensions, ratio, file size, format, and center-safe text note. | The developer or CMS owner can confirm the real file before attaching it to og:image metadata. | Check source file |
| Metadata field set | Absolute og:image URL, og:image:width, og:image:height, og:image:alt, og:title, og:description, canonical URL, and Twitter Card fields when used. | The preview checker can separate image-size problems from missing or stale page metadata. | Preview deployed URL |
| Public crawler access | Page URL and image URL return public 200 responses without login, private CDN restrictions, hotlink blocking, or robots conflicts. | A correct image can still produce a blank card when social crawlers cannot fetch the page or image. | Check OG preview |
| Cache refresh action | Which platform needs a re-scrape or cache refresh after the deployed HTML and image URL changed. | Facebook, LinkedIn, Slack, Discord, X-style cards, and messaging apps can each hold stale preview data. | Use publish gate |
| Wrong-surface guard | Confirm the asset is an Open Graph card, not a LinkedIn banner, YouTube channel art, Facebook cover, product photo, or generic social post. | Wide banners and square product images often look acceptable in a design tool but crop badly as link previews. | Route social asset |
| Final preview approval | Record the checked file, deployed URL, metadata status, crawler access result, cache action, owner, and live preview status. | The publishing owner gets a durable proof that the URL preview is ready, blocked, stale, or returned for a fix. | Open preview checker |
Open Graph final preview acceptance record
Use this record when the source image, deployed metadata, crawler access, cache refresh, and platform preview all need one final publish decision before a URL is shared.
| Acceptance gate | Ready when | Return for repair when | Next route |
|---|---|---|---|
| Source file proof is attached | The final image file name, 1200 x 630 or larger 1.91:1 dimensions, ratio, format, file size, and readable center-text note are recorded. | Only the design canvas, CMS thumbnail, or old export is referenced, so the real og:image file is not proven. | Check source file |
| Deployed metadata matches the asset | The live HTML exposes the intended absolute HTTPS og:image URL plus matching width, height, alt, title, description, canonical URL, and Twitter Card fields when used. | The file is correct locally, but the deployed page still points to stale, missing, relative, or mismatched metadata. | Preview deployed URL |
| Crawler access is public | Both the page URL and image URL return public 200 responses without login, private CDN restrictions, hotlink protection, redirect traps, or robots conflicts. | The preview works for a logged-in browser but fails for social crawlers, unfurl bots, or messaging previews. | Check crawler access |
| Preview cache action is recorded | The handoff names whether the image URL changed, which platform cache needs refresh, and whether a re-scrape or waiting period is required. | The live metadata is fixed, but Facebook, LinkedIn, Slack, Discord, X-style cards, or message apps still show the old preview. | Refresh preview |
| Destination preview is approved | The intended destination preview shows the correct image, title, description, page URL, and readable card content after deployment. | The source file and metadata pass, but the platform preview crops, softens, substitutes, or hides the intended card. | Open preview checker |
| Cross-surface reuse is ruled out | The asset is confirmed as a link-preview card, not a LinkedIn banner, YouTube channel art, Facebook cover, product photo, or generic social post. | A wide banner, square product image, or vertical cover is forced into Open Graph metadata and loses important content. | Route social asset |
Open Graph image priority matrix
When a website needs social preview images, prioritize the Open Graph asset that changes brand recognition, click clarity, product trust, tool comprehension, or cross-platform reuse first.
| Page goal | Prioritize this image | Why it matters first | Next check |
|---|---|---|---|
| Homepage brand preview | Brand-level 1200 x 630 card | The homepage card should identify the site, product category, and core utility before users click from social or AI-cited surfaces. | Preview deployed URL |
| Article or guide share clarity | Topic-specific guide card | A guide page needs a clear topic card, not a generic logo image that hides the query intent. | Check source file first |
| Product or marketplace page trust | Product-specific share card | Product pages often need a separate 1.91:1 card rather than reusing square catalog or marketplace listing images. | Compare product image |
| Tool page comprehension | Tool-result or workflow card | A tool page card should show the task outcome clearly, then the deployed metadata should point to that exact public image. | Check OG preview |
| Cross-platform image reuse | Separate OG card export | A YouTube banner, LinkedIn header, Facebook cover, or Instagram post should not be reused as an Open Graph card without a 1.91:1 check. | Route wide asset |
Open Graph page type image selection matrix
Choose the Open Graph image by page type before exporting. A homepage, article, tool page, product page, comparison page, and downloadable template should not all reuse the same generic 1200 x 630 card.
| Page type | Best OG image concept | Selection rule | Next route |
|---|---|---|---|
| Homepage or brand entry | Brand promise plus primary tool category | Show ImageSizeKit, the image-size utility category, and the core outcome instead of a decorative hero crop. | Preview homepage card |
| Guide or tutorial page | Topic-specific answer card | Use the exact query topic, size, ratio, or failure symptom so the shared card explains why the page is useful. | Check source image first |
| Interactive checker page | Tool workflow or result card | Show the checker action, expected output, and privacy boundary instead of a static size table. | Check OG preview |
| Product or marketplace page | Product trust or listing-quality card | Use a 1.91:1 product-context card rather than reusing square catalog, Shopify, Etsy, or marketplace listing images. | Compare product image |
| Comparison or decision page | Two-option or decision-rule card | Make the choice visible in the card, such as JPG versus PNG, banner versus OG image, or thumbnail versus Shorts cover. | Route social image |
| Template or downloadable asset | Template preview card | Show the template canvas, safe area, or downloadable asset state, then verify it is not accidentally a banner header. | Check template route |
Open Graph platform preview acceptance matrix
After the 1200 x 630 image and metadata are ready, validate the shared URL by destination. Facebook, LinkedIn, Slack, Discord, X-style cards, and private messaging apps can each expose a different preview failure.
| Destination | Acceptance signal | Common failure | Next route |
|---|---|---|---|
| Facebook-style link share | The card uses the intended 1200 x 630 image, title, description, and public HTTPS URL. | The image is blank, too small, stale, or blocked by crawler access. | Preview deployed URL |
| LinkedIn URL post | The post preview uses the Open Graph card image instead of a profile or Page banner crop. | A LinkedIn banner or company cover is reused and crops like a header, not a link card. | Compare LinkedIn banner |
| Slack unfurl | The link expands with the intended image and readable text in a compact message preview. | Small text, redirects, blocked image URLs, or stale metadata make the unfurl weak or blank. | Check OG preview |
| Discord embed | The embed shows the intended card image without fragile edge text or confusing fallback artwork. | The page exposes multiple image candidates or the exported card has too much small text. | Check image file first |
| X-style summary card | The card still has a recognizable subject and headline when the app applies its own card format. | Only Open Graph tags are checked while twitter:card fields or image fallbacks remain stale. | Run social checker |
| Private messaging preview | The preview works from the public URL after redirects, canonical handling, and cache refresh. | The browser view works, but message previews keep an old image or choose a fallback asset. | Check publishing sequence |
Open Graph image failure diagnosis card
Use this diagnosis card when the image is 1200 x 630 but the final shared URL still renders a blank, stale, cropped, or wrong social card.
| Result | Likely cause | Fix before publishing | Next route |
|---|---|---|---|
| 1200 x 630 file is ready but card is blank | The page may not expose an absolute og:image URL, or the image URL may return an error to crawlers. | Confirm the image URL is public, HTTPS, returns 200, and is referenced by deployed page metadata. | Open OG checker |
| og:image uses a relative or private URL | The preview parser cannot resolve a relative path, logged-in media URL, localhost asset, or blocked CDN image. | Use one absolute public HTTPS image URL that returns 200 without cookies, auth, or robots blocking. | Check image file first |
| Crawler is blocked even though the image opens in your browser | Hotlink rules, robots settings, auth headers, or CDN protections can allow a human browser while blocking social crawlers. | Test the public image URL and page URL separately before refreshing the platform preview cache. | Preview deployed URL |
| LinkedIn share crops like a banner | A LinkedIn profile or Page banner was reused as a URL post image. | Create a separate 1.91:1 Open Graph image instead of reusing a wide LinkedIn header. | Compare LinkedIn banner |
| Image looks sharp locally but soft in social apps | The image may be over-compressed, too small before resizing, or full of tiny text. | Export a clean 1200 x 630 or larger 1.91:1 source with large text and fewer details. | Run image check first |
| Social app chooses a different image from the page | The page may expose multiple image candidates, stale metadata, or a CMS fallback image before the intended og:image. | Keep one canonical Open Graph image for the page, update metadata, and re-check the deployed URL preview. | Check OG preview |
| Old preview keeps appearing after deploy | The platform cache still holds previous page metadata or the old image URL. | Change the image URL when possible, then refresh platform previews after deployment. | Preview workflow |
Open Graph image workflow bridge
Use this bridge to route ImageSizeKit wide-image, social checker, LinkedIn, and preview-checker pages into the canonical 1200 x 630 Open Graph image guide.
| Workflow source | Entry role | Why it should link here | Next route |
|---|---|---|---|
| YouTube Banner Safe Area | Wide-image comparison entry | Wide-image users often ask whether one banner can become a link preview; this route clarifies that OG cards need a separate 1.91:1 file. | Compare OG image |
| Social Media Image Checker | Cross-platform checker entry | The checker routes broad social, poster, Linktree, and website share image files to this dedicated Open Graph size guide. | Check social file |
| Open Graph Preview Checker | Metadata preview entry | After the 1200 x 630 image is ready, the preview checker verifies og:image metadata, crawler access, and cache behavior. | Preview deployed URL |
| LinkedIn Banner Size | LinkedIn placement comparison | LinkedIn banner queries can be confused with LinkedIn URL post preview images; this route separates profile/Page banners from OG cards. | Separate LinkedIn banner |
Common mistakes
| Mistake | Symptom | Fix |
|---|---|---|
| Small text | The preview is readable in the design file but unreadable in feeds. | Use fewer words and larger type inside the center of the image. |
| Missing dimensions | Preview parsers guess the image size or load slowly. | Add og:image:width and og:image:height when possible. |
| Relative image URL | Social crawlers cannot fetch the image consistently. | Use an absolute HTTPS URL for og:image. |
| Stale preview cache | The old image still appears after you update the page. | Use platform debuggers or wait for cache refresh after changing OG images. |
| Correct image, wrong page metadata | The 1200 x 630 file is ready, but social apps still show the wrong card. | Check the deployed URL with an Open Graph preview tool after verifying the image dimensions. |
OG image size FAQ
What is the best Open Graph image size?
Use 1200 x 630 pixels as the practical default. It matches Meta's high-resolution link-share recommendation and aligns with the common 1.91:1 preview ratio.
Does the Open Graph protocol require a specific image size?
The Open Graph protocol requires og:image but does not define one universal pixel size. It supports structured properties such as og:image:width and og:image:height.
Should I add og:image:width and og:image:height?
Yes, when your site or CMS supports it. The Open Graph protocol lists these as optional structured properties for image metadata.
Why does my OG image look different on different platforms?
Different apps can crop, pad, cache, resize, or choose among multiple images differently. Start with 1200 x 630, keep important content centered, and test the deployed URL.
Should I check the image file or the page URL first?
Check the image file first. Confirm that the export is 1200 x 630 and close to 1.91:1, then test the deployed page URL to verify og:image metadata and platform cache behavior.
Is Open Graph image size the same as a social media banner size?
No. Open Graph images are link preview cards, usually around 1.91:1. Banner images are wide profile or page headers and should be checked with a banner-size workflow.
Related image tools
Social Media Image Sizes
Browse Instagram, Facebook, LinkedIn, Open Graph, Etsy, and Shopify image size guides.
Open ->Image Size Checker
Start in the upload area and confirm that your exported preview image is 1200 x 630 and close to 1.91:1.
Open ->Open Graph Preview Checker
Check a website share image workflow after deployment and separate image dimensions from metadata issues.
Open ->Social Media Image Checker
Route an exported social image to Open Graph, banner, cover, profile, or product image guidance.
Open ->Banner Size Checker
Use this when the image is a wide header or cover asset, not a link preview card.
Open ->LinkedIn Banner Size
Compare LinkedIn profile/Page banners with URL post image previews.
Open ->Aspect Ratio Calculator
Calculate alternate 1.91:1 preview sizes for retina and compressed exports.
Open ->Public workflow references
These public workflow references support this ImageSizeKit page with crawlable routing notes outside the main site. Use them to connect the platform-specific guide with the broader checker and workflow entity.
Sources and update history
August 9, 2026: Added the Open Graph final preview acceptance record for source-file proof, deployed metadata, public crawler access, preview cache action, destination preview approval, and cross-surface reuse boundaries. August 9, 2026: Added the Open Graph guide and preview checker handoff loop to connect source-image decisions, metadata deployment, crawler access, cache refresh, and wrong-surface routing between the guide and the preview checker. August 8, 2026: Refreshed the Open Graph image checker with sample-dimension checks for the 1200 x 630 source file, clearer source-file to metadata to preview routing, and a crawlable answer matrix for website thumbnail, social share card, link preview image, and og:image checks. August 3, 2026: Added the Open Graph image publish readiness decision card for source-file checks, deployed metadata, public crawler access, platform preview cache, and banner-versus-card misrouting. August 1, 2026: Routed Open Graph source-file checks directly to the Image Size Checker upload anchor before preview debugging. August 1, 2026: Added the Open Graph platform preview acceptance matrix for Facebook-style link shares, LinkedIn URL posts, Slack unfurls, Discord embeds, X-style cards, and private messaging previews. August 1, 2026: Added the Open Graph page type image selection matrix for homepage, guide, checker, product, comparison, and template page cards. August 1, 2026: Added the Open Graph image priority matrix for homepage brand previews, guide share clarity, product page trust, tool page comprehension, and cross-platform image reuse. August 1, 2026: Added the Open Graph publishing decision sequence for file checks, public og:image metadata, structured dimensions, canonical and redirect handling, preview cache refresh, and banner-vs-card routing. August 1, 2026: Added the Open Graph image failure diagnosis card for blank cards, relative/private og:image URLs, crawler blocking, wrong-image selection, soft previews, and stale cache. August 1, 2026: Updated the Open Graph image workflow bridge with routes from wide-image pages, social checker workflows, LinkedIn banner queries, and the Open Graph preview checker. July 16, 2026: Added metadata field checks, publish diagnostics, LinkedIn URL post routing, and cache-failure decisions for Open Graph image workflows. July 16, 2026: Reinforced local file checks, preview-cache boundaries, and related routes for Open Graph image workflows. July 8, 2026: Added as a cross-platform preview-image page using Open Graph protocol, Meta link-share image guidance, and LinkedIn URL post image guidance.