Conversion
What size should an og:image be
What 13x checks
This is rule conversion.og-image-size in the public registry: og:image is the right size. It runs on every audit, against the pages we actually fetched, and its result is derived from the response rather than estimated.
- Surface
- Conversion
- Score weight
- 5 of the readiness score
- Scope
- Reported as skipped when the page renders only with JavaScript
- Applies
- Only where the market or the page shape makes it relevant
Registry version 2026-07-30. Every rule is published, and the audit is deterministic — the same page produces the same finding every time.
The fix
The same text the audit hands you when this check fails on your own site.
The og:image is ×. Use 1200×630 (1.91:1).
That size works everywhere: Facebook, LinkedIn and Slack render it as a full-width card, and X uses it for summary_large_image. Below roughly 600×315 they all fall back to a small square thumbnail beside the text.
Design constraints that matter more than the pixel count:
- Platforms crop toward the centre, so keep text away from the edges — that is usually where the product name sits. - It is read at thumbnail size in a feed. Nothing smaller than about 40px tall is legible. - Keep it under 5 MB, or some crawlers give up and render no image.
Declare the dimensions too, so the card renders before the image downloads:
<meta property="og:image" content="https://example.com/og.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />Framework-specific versions
Where the change differs enough to be worth writing out separately.
Does your site have this problem?
13x checks this and 112 others against your live URL in about 30 seconds. No account, and every finding comes with the fix for your framework.
No signup. Results in 30 seconds.
More conversion checks
- Why every launch page needs an email captureThere is a way to capture an email
- Which analytics should I install before launchAnalytics is installed
- My page has no clear call to actionThere is a recognisable call to action
- Why I need error tracking before launchErrors are reported somewhere
- Why my site needs a contact routeThere is a way to make contact
- Should I show pricing on my websitePricing is stated or reachable