Social Media and Open Graph Image Sizes for 2026

Use a dependable link-preview baseline

For a general Open Graph link preview in 2026, 1200 × 630 pixels at roughly 1.91:1 remains a practical baseline. Meta recommends at least that size for high-resolution link shares and advises keeping close to 1.91:1 to limit cropping. Other consumers may crop, downsample, or ignore the image.

Open Graph defines metadata rather than one mandatory canvas size. Include an absolute HTTPS image URL and describe the asset with og:image, og:image:width, og:image:height, and og:image:alt. Keep title and essential branding away from the edges.

• General link preview: 1200 × 630 is the first asset to produce.
• X large-card variant: consider a separate 1200 × 675, 16:9 composition when that channel is important.
• Use JPG for photographic artwork or PNG where sharp flat graphics and transparency support are required.
• Verify current file-type and file-size limits in each publisher before launch because platform rules change.

Do not confuse link previews with native posts

An Open Graph image is fetched from a web page when its URL is shared. Native feed posts, profile images, ads, stories, reels, and video thumbnails use different placement rules. A common production set starts with square, portrait, landscape, and full-screen vertical canvases, then adapts them to the exact channels in the campaign.

• Square working canvas: 1080 × 1080 for placements that accept 1:1.
• Portrait feed working canvas: 1080 × 1350 for placements that accept 4:5.
• Full-screen vertical working canvas: 1080 × 1920 for placements that accept 9:16.
• These are production starting points, not promises that every platform surface will display every pixel.

Design for unpredictable crops

Interfaces can add rounded corners, overlays, badges, text, or responsive crops. Keep the subject, logo, and short headline inside a conservative central safe area. Avoid placing small text in the image when the page title can carry the message accessibly.

Prepare art-directed variants instead of mechanically cropping one master when the subject moves off-centre or text becomes unreadable. Preview on a small phone as well as a desktop.

• Leave breathing room on every edge.
• Use high contrast and a type size that survives thumbnail rendering.
• Keep text brief and repeat essential meaning in the page title or post copy.
• Check that the image still makes sense when cropped to square or shown as a small thumbnail.

Publish and test the metadata

Social crawlers cache aggressively and may not run client-side code. Render metadata in the initial HTML, make the image publicly fetchable without authentication, return the correct content type, and avoid blocking known crawlers unintentionally.

Use each platform’s preview or inspection tool before an important launch. After replacing an image, a new versioned URL is more dependable than relying on every cache to refresh immediately.

• Use canonical, absolute URLs for both the page and image.
• Provide og:title, og:description, og:url, and og:type alongside image fields.
• Add the appropriate X card metadata when X presentation matters.
• Test the deployed URL; a local preview cannot prove crawler access.
• Re-check official platform documentation during each campaign cycle.