OG Image Size Guide: Every Platform's Dimensions

The standard OG image size is 1200 x 630 pixels — that single dimension works on Facebook, LinkedIn, Slack, and Discord. Twitter cards crop to a 2:1 ratio (1200 x 600). Generate a perfectly sized image free with our OG image generator; the per-platform breakdown is below.

The 1200x630 standard: why it exists

The 1200 x 630 pixel dimension is the universal Open Graph standard because it renders at a 1.91:1 aspect ratio — the exact ratio Facebook's link preview cards were designed around when the Open Graph protocol launched in 2010. At 1200 pixels wide, the image stays sharp on retina and high-DPI displays, where a 600-pixel-wide image would look soft; the 630-pixel height fills the card without cropping on Facebook, LinkedIn, Slack, Discord, and most messaging apps. Facebook's crawler accepts images as small as 200 x 200, but anything under 600 x 315 renders as a small thumbnail beside the text instead of the large banner card — a massive downgrade in click appeal. The practical rule: always design at exactly 1200 x 630, export as PNG for graphics with text or JPEG for photographic images, and keep the file under 8MB for Facebook (under 5MB for X and LinkedIn, which enforce stricter limits). Our OG image generator exports at exactly these dimensions so you never have to think about it. For the meta tags that reference the image, see how to generate Open Graph meta tags.

Platform-by-platform dimensions

While 1200 x 630 is the safe universal size, each platform has its own quirks worth knowing. Facebook displays 1200 x 630 natively and requires a minimum of 600 x 315 for the large card; images under 8MB are accepted. LinkedIn also uses 1200 x 630 and caps files at 5MB — oversized files silently fail to render, which is the most common cause of 'my LinkedIn preview is blank.' X (Twitter) with a summary_large_image card displays at a 2:1 ratio (1200 x 600 visible), cropping roughly 15 pixels off the top and bottom of a 1200 x 630 image — keep critical text away from the edges. Slack unfurls 1200 x 630 beautifully but caches aggressively, so updated images can take hours to refresh. Discord renders the standard size inline in chat. WhatsApp is the outlier: it crops link previews to roughly 400 x 400 square-ish, so the center of your image carries the whole message there. iMessage shows a wide banner similar to Facebook. The design implication: compose for 1200 x 630, keep all text and logos inside a central safe zone, and test the actual share on each platform that matters to you. Our Markdown to HTML converter can help you build the test pages for preview checks.

Safe zones: where to put text and logos

The biggest OG design mistake is treating the full 1200 x 630 canvas as usable — it is not. X crops about 15 pixels from top and bottom, WhatsApp crops the sides heavily, and various apps round the corners of the card. The professional approach is a central safe zone: keep all text, logos, and critical visuals inside the middle 1000 x 500 pixels, leaving roughly 100 pixels of padding on every side as sacrificial margin. Backgrounds, gradients, and decorative patterns can bleed to the full edge — only the meaningful content needs protection. Text sizing matters too: at 1200 x 630, body text below 48 pixels becomes unreadable when the card renders at 500 pixels wide on mobile, so headlines should run 72 to 120 pixels and supporting text no smaller than 48. Limit on-image text to a headline plus one short subline — the card already shows your page title and description beside or below the image, so repeating them wastes the visual. High contrast is non-negotiable: white text on a dark overlay survives every platform's compression, while thin gray text on a light photo dissolves into mush. For headline brevity discipline, our meta description guide teaches the same tight-copy skills, and our word counter keeps on-image text lean.

File format, size, and compression

Format choice affects both quality and whether the image renders at all. PNG is the right choice for graphics with text, logos, and flat colors — it is lossless, so headline edges stay crisp through every platform's recompression. JPEG suits photographic OG images, where its smaller file size matters more than pixel-perfect edges; export at 80 to 85% quality for the best size-to-sharpness trade. WebP is tempting but has inconsistent support across social crawlers — some platforms ignore it entirely, so avoid it for OG images despite the smaller files. SVG is never acceptable as an og:image; crawlers require raster formats. File size limits are hard ceilings: 8MB on Facebook, 5MB on X and LinkedIn — exceed them and the preview silently shows nothing, with no error message to debug. Aim for 200 to 500KB, which loads instantly and survives every limit with headroom. Also mind the URL: og:image must be an absolute HTTPS URL — relative paths fail on every platform — and the image must be publicly accessible without login. Changing the image later requires re-scraping through each platform's debugger because of aggressive caching. Our OG image generator handles dimensions, format, and compression automatically.

Common sizing mistakes to avoid

Five sizing errors account for most broken OG previews. One: designing at the wrong aspect ratio — a 1080 x 1080 square or 1920 x 1080 video frame gets center-cropped unpredictably by the 1.91:1 card. Two: text in the crop zone — headlines running edge to edge lose their first and last words on X's 2:1 crop. Three: files over the platform limit — a 12MB PNG renders nowhere and tells you nothing about why. Four: forgetting og:image:width and og:image:height meta tags — without them, some crawlers guess the dimensions wrong and render a squished or thumbnail card; always declare 1200 and 630 explicitly. Five: testing only on desktop — more than half of social traffic is mobile, where the card renders at half the width and small text vanishes. The fix for all five is a checklist: 1200 x 630 canvas, safe-zone composition, sub-500KB export, absolute HTTPS URL, width/height tags declared, and a live share test on mobile for each target platform. For the full mistake catalog, see common OG image mistakes, and for the Twitter-specific differences, OG image vs Twitter card breaks down exactly what changes between the two.