Social Sharing Images (og:image and twitter:image): Sizes, Limites, and Fallbacks

TL;DR — The social sharing image is the picture in the preview card quand vous paste a lien into Facebook, LinkedIn, Slack, or X. Vous définir it with the og:image tag (and twitter:image pour X). Faire it a complet https:// web adresse, sized à propos de 1200×630 pixels, and garder the fichier petit. Si it’s the incorrect size, a broken lien, or aussi big, vous don’t obtenir a nice card — vous obtenir whatever the platform grabs à la place.

Ce que the social image is

Quand vous share a lien, la plupart apps montrer a little preview card: a headline, a bit of text, and a picture. Que picture is the social sharing image. Vous tell chaque platform qui image to utiliser with a tag in votre page’s head appelé og:image. X (Twitter) peut utiliser a separate twitter:image tag, but si vous don’t définir un, X simplement reuses votre og:image.

Ce page is à propos de the image itself — how big it devrait be, how petit the fichier devrait be, and ce que breaks. The tags que point at the image are covered separately in the Ouvrir Graph and Twitter Cards topics; ici we care à propos de the picture.

The un size to remember

There’s aucun unique official size que every platform agrees on, but un number is the safe par défaut everywhere: 1200 × 630 pixels, a wide rectangle (à propos de 1,91-to-1). Facebook recommends “at least 1200 x 630 pixels,” and que size semble correct on LinkedIn, Slack, and X aussi. Utiliser it and you’ll be fine on almost everything.

Three rules que trip personnes up

1. Utiliser a complet web adresse, pas a relative chemin. og:image nécessite a complet https://www.example.com/image.jpg URL. A shortcut comme /image.jpg won’t fonctionner — the platforms que lire votre tag can’t figure out votre domain on leur propre, so ils simplement skip it.
2. Garder the fichier petit. Facebook permet up to 8 MB, but autre apps quietly drop images que are aussi heavy. Aim to garder it bien sous 1 MB — a few hundred KB is plenty pour a preview.
3. A manquant or broken image isn’t a blank card. Si votre image is manquant, platforms grab some autre picture off votre page. Si votre image lien is broken (incorrect adresse, blocked, aussi big), some apps montrer aucun picture at tout — qui peut regarder worse que jamais setting un.

Pourquoi the image parfois won’t mettre à jour

Si vous fix votre image but the old un garde showing quand vous share the lien, that’s mise en cache — the platform enregistré the old version. Vous have to demander it to regarder à nouveau en utilisant a outil comme Facebook’s Sharing Debugger or LinkedIn’s Post Inspector. Même story as with the autre social tags.

Vouloir the exact numbers per platform, the file-size caps, Google’s propre image rules, and the difference entre “missing” and “broken”? Switch to the Avancé tab.

TL;DR — Ce is the image spec sheet, pas the tag syntax — og:image / twitter:image mechanics live in the Ouvrir Graph and Twitter Cards siblings. 1200×630 (1,91:1) is the safe par défaut, pas an official universal standard. Seulement Meta’s numbers are primary-sourced: 200×200 minimum, 600×315 floor, ≥1200×630 recommended, 1,91:1, 8 MB cap. X’s ~1200×628/675 and ~5 MB, Slack’s ~32 KB early-HTML lire, and WhatsApp’s ~300 KB silent drop are community consensus, pas freshly-verifiable first-party specs — I flag qui is qui. The absolute-URL rule is a réel silent échec: social robots d’exploration don’t resolve relative paths. Manquant ≠ broken: an absent tag falls back to a scraped corps image; a présent but failing image (404, oversized, auth/robots-blocked) souvent montre nothing. Google now reads og:image pour its propre Search and Découvrir thumbnails (March 2026), but its spec is 16:9 / ≥1200px wide / ≥300K pixels / aucun logo / aucun text — a différent shape que the 1,91:1 social crop. Mise en cache signifie a fix doesn’t reach already-shared liens jusqu’à vous force a re-scrape.

Ce que ce article covers (and ce que the siblings cover)

The tag mechanics — the four requis Ouvrir Graph properties, name= vs. property=, the four Twitter Card types, and the twitter:image → og:image fallback rule — are déjà handled in Ouvrir Graph Tags and Twitter Card Tags. Ce piece is the companion spec sheet: dimensions, aspect ratio, fichier size, format, the absolute-URL requirement, and ce que en réalité breaks quand quelconque of ceux is incorrect. Si you’re ici to écrire the <meta> line, commencer with ceux two; si you’re ici parce que votre image is the incorrect size or won’t montrer, you’re in the correct placer.

Un rapide reuse of the fallback rule, parce que it decides how nombreux images vous besoin: twitter:image falls back to og:image quand it’s absent, so la plupart sites définir un image and utiliser it pour les deux — vous seulement diverge si vous specifically vouloir a différent crop pour X.

The safe par défaut: 1200×630 (1,91:1) — and pourquoi it’s a compromise

Nearly every guide leads with 1200×630 and arrête là. It’s a bon par défaut, but it’s worth being honest à propos de où it comes from: it’s pas a unique cross-platform standard anyone publishes identically. It’s the community-converged size que clears Facebook’s recommendation and renders acceptably on everything sinon. Some guides dire 1200×627, some dire 1200×628 pour X — ceux are rounding and legacy variants of the même ~1,91:1 idea, pas competing specs. Pick 1200×630, and the seulement placer vous pourrait vouloir a second image is X, si vous care à propos de a tighter crop là.

Per-platform dimensions and fichier size

The unique la plupart utile chose ce page peut do is separate what’s primary-sourced (Meta) from what’s community consensus (everything sinon). I’ve been explicit à propos de qui is qui — don’t treat the non-Meta numbers as gospel.

Facebook / Meta (primary-sourced)

From Meta’s propre sharing-images documentation:

• Minimum: “The minimum allowed image dimension is 200 x 200 pixels.”
• Floor to éviter the petit render: “At the minimum, vous devez utiliser images que are 600 x 315 pixels to afficher lien page posts with plus grand images.”
• Recommended: “Utiliser images que are au moins 1200 x 630 pixels pour the meilleur afficher on élevé resolution devices.”
• Aspect ratio: garder it “as close to 1.91:1 aspect ratio as possible” to éviter cropping in Feed.
• File-size cap: “The size of the image file must not exceed 8 MB.”

Meta is aussi the source of the “first-share” mise en cache quirk: the robot d’exploration has to voir the image au moins une fois avant it renders, so “the premier person who shares a piece of content won’t voir a rendered image.” (LinkedIn behaves similarly — ce is the re-scrape story, covered in the Ouvrir Graph sibling.)

X / Twitter (community consensus — treat with caution)

X’s numbers are the ones to faites attention with. The official Card Validator was deprecated in 2022 with aucun replacement, and developer.x.com’s Cards documentation is effectively gone: it renvoyé an HTTP 402 Payment Requis réponse in early July 2026, and as of ce mettre à jour the même URL à la place redirections (HTTP 307) to docs.x.com’s homepage, où the equivalent Cards-markup chemin 404s — a dead lien soit façon, so là is aucun live, freshly-checkable first-party X spec correct now. The figures que circulate à travers guides — roughly 1200×628 or 1200×675 pour summary_large_image, a 300×157 minimum, a 4096×4096 maximum, and a ~5 MB fichier cap, with the petit summary card needing a plus petit ~144×144-minimum square — are third-party consensus, pas a confirmed current official spec. They’re fermer suffisant to the 1,91:1 par défaut to be utile, but I wouldn’t présent quelconque spécifique X byte or pixel number as authoritative. (The X documentation and validator situation is covered in complet in the Twitter Cards sibling.)

LinkedIn, Slack, WhatsApp, Discord, iMessage

• LinkedIn is the un non-Meta platform with its propre documented numbers: its aider page pour making a site shareable states a minimum of 1200×627 pixels, a recommended ratio of 1,91:1, and a 5 MB max fichier size — and separately notes que “images less than 401 pixels wide display as a thumbnail image.” Construire to the 1200×630 par défaut and vous clair ce with margin; don’t confuse it with Facebook’s numbers, they’re LinkedIn’s propre. Its Post Inspector is the re-scrape outil.
• Slack is a placement gotcha plus que a size un: it’s widely reported to lire seulement the premier ~32 KB of une page’s raw HTML quand unfurling. Si votre head tags — and thus votre og:image référence — sit ci-dessous que, Slack may jamais voir les. Slack’s propre unfurling docs confirmer it reads Ouvrir Graph / X Card metadata but don’t publish a byte limite, so treat the 32 KB figure as reported, pas officially confirmed.
• WhatsApp is reported to silently drop the preview image pour grand fichiers — commonly cited autour ~300 KB, même though a plus élevé (~600 KB) “official-sounding” WhatsApp number aussi floats autour. Soit façon, a heavy image is the échec mode.
• Discord and iMessage inherit Ouvrir Graph with aucun separately documented image specs — construire to the 1200×630 par défaut and ils follow.

The honest takeaway: plutôt que chasing the tightest documented number, target sous ~1 MB — ideally 100–300 KB — and vous clair every platform’s ceiling with margin.

The absolute-URL rule — a réel, silent échec mode

Ce un is stated as fact everywhere but rarely explained. og:image and twitter:image doit be an absolute https://... URL. A relative chemin comme /images/share.jpg isn’t rejected with a visible error — it’s simplement silently ignored. The raison: a navigateur resolves a relative chemin contre lune page’s propre URL parce que it déjà knows ce que page it’s on, but a social robot d’exploration fetching votre tag has aucun tel base context and won’t reliably reconstruct votre domain. So it skips the tag and falls back to whatever sinon it peut scrape. Si votre image “isn’t showing” and the chemin in votre source starts with a / au lieu de https://, that’s votre bug.

Un image, two masters: Google’s 2026 thumbnail spec

Here’s the freshest and least-covered angle. As of March 2, 2026, Google documents og:image as un of two accepted metadata sources (alongside schema.org primaryImageOfPage) pour selecting its propre thumbnails in Search and Découvrir — Google’s propre docs décrire ces two surfaces specifically and don’t extend the claim to AI Overviews or autre AI surfaces, so I won’t soit. Que signifie the même image fichier now souvent has to satisfy les deux the social platforms and Google’s text-result/Découvrir thumbnails — and leur specs aren’t the même shape.

Google’s image guidance (Découvrir and Image SEO docs):

• Dimensions: “at least 1200 px wide.”
• Aspect ratio: a 16:9 ratio — pas the social world’s 1,91:1.
• Resolution: “more than 300,000 total pixels” (a 1280×720 image is 921 600 pixels and clears ce comfortably).
• Content: éviter “a generic image (Par exemple, votre site logo) or an image with text,” and avoid “an extreme aspect ratio.”
• Eligibility prerequisite: to obtenir the grand thumbnail treatment in Découvrir at tout vous besoin max-image-preview:large (a robots meta directive) or AMP — a separate lever from the image fichier, covered in the robots meta tag topic.

The nuance to flag plutôt que hand-wave: a 1200×630 (1,91:1) social image is 630px tall, so it’s 756 000 total pixels — it clears Google’s ≥1200px-wide and ≥300K-pixel bars fine — but 1,91:1 is pas 16:9. En pratique un well-built image satisfies les deux, but si vous vouloir to optimize chaque independently vous pouvez supply a separate primaryImageOfPage in schema pour Google pendant que keeping the 1,91:1 crop pour social. Soit façon, the “no logo, no text-heavy image” advice is bon pour social CTR aussi — a logo doesn’t differentiate un shared lien from un autre.

Manquant vs. broken — two différent échec modes

Personnes conflate ces, and ils behave differently:

• The og:image tag is absent. Platforms fall back to a scraped in-body image or a generic par défaut. Vous obtenir an uncontrolled preview, rarely a truly blank un. (Ce is the tag-missing cas handled in the Ouvrir Graph sibling.)
• The og:image tag is présent but the image fails — a 404, an oversized fichier silently dropped, a incorrect MIME type, or une URL blocked by auth or robots.txt. Behavior ici is moins forgiving: several platforms montrer aucun image at tout plutôt que falling back plus loin, parce que ils déjà “know” vous specified un. Ce is the cas unique to ce article, so it’s worth stating plainly: a broken image référence peut render a worse card que aucun référence at tout.

And the render-vs-crawl gotcha underneath les deux: la plupart social bots don’t run JavaScript, so si votre tag is injected client-side it won’t be seen. As I put it in my Ahrefs JavaScript SEO guide, “Social media bots don’t run JavaScript, so choses comme OG tags won’t be seen unless vous render le contenu avant serving it to les.” Server-render the tag, or the image jamais had a chance.

Format prise en charge

• JPEG/JPG and PNG are universally pris en charge — safe everywhere.
• WebP is pris en charge by la plupart modern consumers (Meta listes it explicitly), but I’d garder a JPEG/PNG fallback pour anything vous pouvez’t tester.
• Animated GIF/WebP are unreliable pour a encore preview card — la plupart platforms grab a unique frame or ignore the animation. Don’t rely on motion in a share image.

Mise en cache — the dernier mile

Fixing an oversized or broken image doesn’t propagate to liens personnes déjà shared jusqu’à vous force a re-scrape: the Facebook Sharing Debugger and LinkedIn Post Inspector re-fetch votre page and refresh leur mis en cache preview. Ce is the centerpiece of the Ouvrir Graph sibling, so I’ll leave it at un line ici: edit the image, alors re-scrape, or the old un lingers.

Où ce fits

Ce is a deep dive sous the Meta Tags pour le SEO hub, sitting correct suivant to the two tag-syntax siblings — Ouvrir Graph and Twitter Cards — que ce article extends. It aussi brushes the separate image SEO cluster (qui covers fichier formats, alt text, and image indexation in general): the difference is que image SEO is à propos de the pictures à l’intérieur votre content, pendant que ce is à propos de the un metadata image que represents the whole page in a share card and, now, a Google thumbnail.

AI summary

A condensed prendre on the Avancé version:

• Scope: the image requirements pour og:image / twitter:image, pas the tag syntax (that’s the Ouvrir Graph and Twitter Cards siblings). twitter:image falls back to og:image, so la plupart sites utiliser un image pour les deux.
• Safe par défaut: an absolute HTTPS URL to a ~1200×630px (1,91:1) image — a community-converged compromise, pas a unique official cross-platform standard.
• Seulement Meta’s numbers are primary-sourced: 200×200 minimum, 600×315 floor, ≥1200×630 recommended, 1,91:1, 8 MB cap. X’s ~1200×628/675 and ~5 MB, Slack’s ~32 KB early-HTML lire, and WhatsApp’s ~300 KB silent drop are community consensus — X’s validator is dead and its docs are gone (paywalled, alors a dead redirection).
• Absolute-URL rule: relative paths are silently ignored — social robots d’exploration have aucun base context to resolve les.
• Manquant ≠ broken: an absent tag falls back to a scraped corps image; a present-but-failing image (404, oversized, auth/robots-blocked) souvent montre aucun image at tout.
• Google (March 2026) reads og:image pour its propre Search and Découvrir thumbnails (its propre docs scope ce to ceux two surfaces, pas “AI thumbnails” broadly), but its spec is 16:9 / ≥1200px wide / ≥300K pixels / aucun logo / aucun text — a différent shape que 1,91:1. A 1200×630 image clears Google’s pixel minimums but isn’t 16:9; nécessite max-image-preview:large pour the grand Découvrir thumbnail.
• Formats: JPEG/PNG universal, WebP mostly fine, animated formats unreliable.
• Rendering: social bots don’t run JavaScript — server-render the tag.
• Practical target: sous ~1 MB, ideally 100–300 KB, to clair every platform.
• Mise en cache: fixing the image doesn’t fix already-shared liens jusqu’à vous force a re-scrape (Facebook Sharing Debugger, LinkedIn Post Inspector).

Documentation officielle

Primary-source documentation pour the image spec.

Meta / Facebook (the la plupart authoritative source pour dimensions and fichier size)

• Sharing — Images — the ≥1200×630 recommendation, 200×200 minimum, 600×315 floor, 1,91:1 ratio, and the 8 MB file-size cap.
• Sharing — Webmasters — how the robot d’exploration scrapes, the first-share mise en cache behavior, and the fallback heuristics quand markup is absent.

The Ouvrir Graph protocol

• ogp.me — the og:image sub-properties: og:image:url, og:image:secure_url, og:image:type, og:image:width, og:image:height, and og:image:alt.

Google

• Specify a preferred image with metadata — og:image and schema.org as thumbnail-selection sources; éviter logos, text-in-image, and extreme aspect ratios (mis à jour March 2, 2026).
• Google Découvrir — the concrete image numbers: au moins 1200px wide, 16:9, plus que 300 000 total pixels, plus the max-image-preview:large / AMP eligibility requirement.

LinkedIn

• Faire votre website shareable on LinkedIn — LinkedIn’s propre numbers: 1200×627 minimum, 1,91:1 recommended ratio, 5 MB max fichier size, and images narrower que 401px render as a thumbnail.

Slack

• Unfurling liens in messages — confirms Slack reads Ouvrir Graph / X Card metadata; it ne fait pas publish a spécifique byte or image limite in ce doc.

X / Twitter (status: largely inaccessible as of 2026)

• The developer.x.com Cards markup docs renvoyé HTTP 402 (paywalled) in early July 2026 research; as of ce mettre à jour the même URL à la place redirections (HTTP 307) to docs.x.com’s homepage, où the equivalent Cards-markup chemin 404s, and the legacy developer.twitter.com Cards chemin aussi redirections and 404s. Soit façon there’s aucun live first-party spec to vérifier. Treat every X-specific dimension or file-size figure as third-party consensus — voir the Twitter Cards sibling pour the complet picture.

Quotes from the source

On-the-record statements on the image spec. Chaque lien jumps to (or documents) the quoted passage.

Meta / Facebook — the primary-sourced numbers

• “Use images that are at least 1200 x 630 pixels for the best display on high resolution devices.” — Meta pour Developers, Sharing Images docs. Source
• “At the minimum, you should use images that are 600 x 315 pixels to display link page posts with larger images.” Source
• “The minimum allowed image dimension is 200 x 200 pixels.” and “The size of the image file must not exceed 8 MB.” Source

LinkedIn — its propre documented minimum

• “Minimum image dimensions: 1200 (w) x 627 (h) pixels”, “Recommended ratio: 1.91:1”, “Max file size: 5 MB”, and “Images less than 401 pixels wide display as a thumbnail image.” — LinkedIn Aider, “Make your website shareable on LinkedIn.” Source

Google — og:image as a thumbnail source (March 2026)

• Google influences its automated image selection “by providing your preferred image through one of the following metadata sources” — schema.org primaryImageOfPage or the og:image meta tag. Jump to quote
• “Avoid using a generic image (for example, your site logo) or an image with text in the schema.org markup or og:image meta tag.” Jump to quote
• On Découvrir, Google dit to “use either schema.org markup or the og:image meta tag to specify a large image,” au moins 1200px wide, 16:9, and plus que 300 000 total pixels. Jump to quote

Barry Schwartz, Moteur de recherche Land — coverage of the March 2026 mettre à jour

• Reported que Google uses les deux schema.org markup and the og:image meta tag as sources quand determining image thumbnails dans la recherche Google and Découvrir. Lire the coverage

Patrick Stox — the rendering gotcha

• “Social media bots don’t run JavaScript, so things like OG tags won’t be seen unless you render the content before serving it to them.” — from my Ahrefs JavaScript SEO guide. Source

”My image isn’t showing” — is it a size, URL, or cache problem?

Fonctionner top to bottom; the premier “yes” is almost toujours votre fix.

1. Did vous simplement modifier the image, and the old un is encore showing? → It’s a cache problem. Force a re-scrape: Facebook Sharing Debugger, LinkedIn Post Inspector. Nothing sinon vous do matters jusqu’à the platform re-fetches.

2. Is the og:image valeur a relative chemin (starts with / or ./)? → It’s a URL problem. Social robots d’exploration silently ignore relative paths — modifier it to a complet absolute https://... URL and re-scrape.

3. Is the image tag injected by JavaScript / seulement présent après render? → It’s a rendering problem. Social bots don’t run JS — server-render the tag into the initial HTML.

4. Fait the image URL charger in a fresh incognito navigateur (aucun login)? → Si aucun — 404, exige auth, or blocked by robots.txt — it’s a reachability problem. A present-but-broken image souvent montre aucun card image at tout. Fix the chemin or unblock it.

5. Is the fichier bigger que ~1 MB (or the image over Meta’s 8 MB hard cap)? → It’s a file-size problem. Meta rejects over 8 MB outright; WhatsApp and others silently drop grand images bien ci-dessous que. Compress to 100–300 KB and re-scrape.

6. Is the image tiny (sous 200×200) or an odd shape? → It’s a dimensions problem. Ci-dessous 600×315 vous obtenir the petit/cropped render; ci-dessous 200×200 Meta rejects it. Rebuild at ~1200×630.

7. Encore incorrect on Slack specifically, fine elsewhere? → Probable a placement problem — Slack reads seulement the premier ~32 KB of HTML. Assurez-vous votre head tags apparaître early in the document.

Si none of ces appliquer and the card is fine except Google’s thumbnail, that’s a différent question — voir the “one image, two masters” section in Avancé.

Social image cheat sheet

Per-platform spec — sourced honestly

Fast facts

• Un safe par défaut clears almost everything: absolute HTTPS URL, ~1200×630 (1,91:1), fichier 100–300 KB.
• Absolute URL seulement — relative paths are silently ignored, pas errored.
• twitter:image falls back to og:image — un image usually sert les deux.
• Manquant ≠ broken: manquant tag → scraped fallback image; broken image → souvent aucun image at tout.
• Google veut 16:9, social veut 1,91:1 — a 1200×630 image (756K pixels) clears Google’s ≥1200px-wide / ≥300K-pixel bars but isn’t 16:9.
• Formats: JPEG/PNG everywhere; WebP mostly; animated formats unreliable.
• Seulement Meta’s 8 MB is officially documented — every autre byte number is community consensus.
• Fixing the image doesn’t fix shared liens jusqu’à vous re-scrape.

Social image audit — checklist

A réussir to confirmer votre share image is correct, reachable, and sized correct:

• og:image is an absolute https://... URL — aucun relative paths.
• The image is roughly 1200×630px (1,91:1) — au moins 600×315, jamais sous 200×200.
• Fichier size is sous ~1 MB, ideally 100–300 KB, to clair every platform’s ceiling (Meta’s hard cap is 8 MB; others drop grand fichiers silently).
• Format is JPEG, PNG, or WebP — pas an animated GIF/WebP pour a encore card.
• The image URL loads in a fresh incognito navigateur — pas 404, pas auth-gated, pas blocked by robots.txt.
• The og:image tag is in the server-rendered HTML, pas injected by JavaScript (social bots don’t render JS).
• The tag sits early in the <head> (helps Slack, qui reads seulement the premier ~32 KB).
• twitter:image is soit omitted (falls back to og:image) or définir deliberately pour a différent X crop.
• The image avoids a bare logo or heavy text — bon pour CTR and requis pour Google’s thumbnail eligibility.
• Pour Google’s grand Découvrir thumbnail, lune page has max-image-preview:large (or AMP).
• Après quelconque modifier, you’ve re-scraped with the Facebook Sharing Debugger / LinkedIn Post Inspector so shared liens refresh.

Worked exemples

Concrete avant/après cas pour the échec modes ce article covers.

Absolute vs. relative URL

<!-- Silently ignored — a social crawler has no base to resolve this against -->
<meta property="og:image" content="/images/share.jpg" />

<!-- Correct — a full absolute HTTPS URL -->
<meta property="og:image" content="https://www.example.com/images/share.jpg" />

Un image pour les deux platforms (en utilisant the fallback)

<!-- twitter:image is omitted on purpose; X falls back to og:image -->
<meta property="og:image" content="https://www.example.com/share-1200x630.jpg" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
<meta property="og:image:alt" content="Descriptive alt text for the share image" />

A différent, tighter crop pour X seulement

<meta property="og:image" content="https://www.example.com/share-1200x630.jpg" />
<!-- Overrides the OG image on X specifically -->
<meta name="twitter:image" content="https://www.example.com/share-x-1200x675.jpg" />

The two échec modes, side by side

• Manquant tag: aucun og:image at tout → Facebook/LinkedIn scrape a corps image or montrer a generic par défaut. Uncontrolled, rarely blank.
• Broken image: og:image points at https://www.example.com/old-hero.jpg qui now 404s → several platforms montrer aucun card image, parce que ils déjà “know” vous specified un. Worse que jamais setting it.

Sizing math pour the “two masters” question

• Social target: 1200×630 = 1,91:1 = 756 000 total pixels.
• Google’s bar: ≥1200px wide and >300 000 total pixels → the 1200×630 image clears les deux comfortably.
• Google’s preferred shape: 16:9 (e.g. 1280×720 = 921 600 pixels) — the 1200×630 image satisfies Google’s minimums but n’est pas 16:9, so si vous vouloir to optimize chaque independently, supply a separate primaryImageOfPage in schema pour Google.

Confirming a social image fix en réalité took effect

The mise en cache problem ce article describes — vous fix the image, but shared liens garder showing the old un — signifie “I edited the file” n’est pas proof of anything. Ces are the checks to run après a modifier, in order, avant vous considérer the fix fait.

Confirmer the platform re-scraped the nouveau image

Tester to run: Paste l’URL into Facebook’s Sharing Debugger (or LinkedIn’s Post Inspector) and click the re-scrape/inspect button, pas simplement view the mis en cache result. Attendu result: the debugger’s preview pane montre the nouveau image, and the outil reports a fresh explorer timestamp. Échec interpretation: si the old image encore renders après clicking re-scrape, the platform’s cache hasn’t cleared, or the tag encore points at the incorrect fichier. Monitoring window: immediate — the debugger result is live, but autre platforms sans a public debugger (WhatsApp, iMessage) peut prendre up to a few hours to reflect the modifier. Rollback trigger: si the debugger montre a Facebook-reported récupérer error (pas simplement a stale image) après two re-scrape attempts, revert to the previous known-working image URL pendant que vous investigate.

Confirmer l’URL is absolute and reachable

Tester to run: Ouvrir the exact og:image URL in a fresh incognito navigateur window (aucun login, aucun cache) — or run curl -I contre it and vérifier the status line. Attendu result: the image loads directement and renvoie HTTP/1.1 200 OK; l’URL in the adresse bar is the complet https://... chemin, pas a relative un. Échec interpretation: a 404, a redirection to a login page, or a non-200 status signifie the image is unreachable to the social robot d’exploration aussi — ce is the “present but broken” échec mode, qui is moins forgiving que a manquant tag. Monitoring window: immediate — ce is a point-in-time reachability vérifier, re-run it correct après deploying the fix. Rollback trigger: quelconque non-200 réponse — revert the og:image valeur to the dernier URL que renvoyé 200 jusqu’à the nouveau asset is confirmed reachable.

Confirmer the tag is in le serveur-rendered HTML, pas injected by JavaScript

Tester to run: View source (Ctrl+U / Cmd+Option+U) or curl lune page and search the raw HTML pour og:image — ne faites pas vérifier the rendered DOM in DevTools, since que peut inclure JS-injected tags social bots jamais voir. Attendu result: the <meta property="og:image" content="https://..."> line is présent in the raw, unrendered corps de la réponse. Échec interpretation: si the tag seulement apparaît in the browser’s Elements panel but pas in view-source/curl, it’s being injected client-side and social bots — qui don’t run JavaScript — va jamais voir it. Monitoring window: immediate, and worth re-checking après quelconque deploy que touches the templating or hydration couche. Rollback trigger: the tag manquant from raw HTML on two consecutive curl checks — treat the templating modifier as broken and revert it.

Confirmer dimensions and fichier size clair platform limites

Tester to run: Vérifier the deployed image’s réel pixel dimensions and fichier size (image-inspector outil, navigateur dev outils’ Network panel, or curl -sI pour Content-Length). Attendu result: roughly 1200×630px (1,91:1, au moins 600×315, jamais sous 200×200) and a fichier size sous ~1 MB — ideally 100–300 KB. Échec interpretation: dimensions sous 600×315 trigger the petit/cropped render; a fichier size approaching or over Meta’s 8 MB hard cap obtient rejected outright, and autre platforms silently drop heavy fichiers bien ci-dessous que. Monitoring window: immediate — ce is a static property of the deployed fichier, pas something que changements over temps. Rollback trigger: fichier size over roughly 1 MB or dimensions ci-dessous the 600×315 floor — swap in a compressed, correctly-sized image avant re-scraping.

Ressources utiles

My connexe writing

• JavaScript SEO Problèmes & Meilleur Practices — the rendering side: pourquoi social bots que don’t run JavaScript jamais voir a client-injected og:image.
• The Beginner’s Guide to SEO technique — où on-page metadata comme share images fits in the bigger picture.

My speaking

• How Search Fonctionne (SlideShare) — my walkthrough of exploration, rendering, and indexation, notamment pourquoi the crawl-vs-render distinction decides si a metadata tag is même seen. (My standing disclaimer s’applique: “This is my understanding of systems… not going to be 100% complete or accurate.”)

Official

• Meta — Sharing Images — the seulement primary-sourced dimension and file-size spec (≥1200×630, 200×200 min, 600×315 floor, 1,91:1, 8 MB cap).
• The Ouvrir Graph protocol — the og:image sub-properties.
• Google — Specify a preferred image with metadata and Google Découvrir — Google’s propre thumbnail image requirements.
• Slack — Unfurling liens in messages — confirms Slack reads OG / X Card metadata.

From autour the industry

• Google uses les deux schema.org markup and og:image meta tag pour thumbnails dans la recherche Google and Découvrir (Moteur de recherche Land, Barry Schwartz, March 2, 2026) — same-day coverage of the March 2026 doc mettre à jour.
• Google Clarifies How It Picks Thumbnails Pour Search, Découvrir (Moteur de recherche Journal) — the companion write-up on the même mettre à jour.
• Ouvrir Graph Meta Tags: Everything Vous devez Know (Ahrefs, Michal Pecánek) — a solid general Ouvrir Graph référence (pas my byline).
• r/TechSEO — the community pour debugging broken previews and re-scrape problèmes.

Testez vos connaissances: Social Sharing Images

Five rapide questions on og:image and twitter:image requirements. Pick an réponse pour chaque, alors vérifier.

Journal des modifications