OG Image Checker

Verify your Open Graph images display perfectly on every platform

What are OG images?

Open Graph (OG) images are the preview images that appear when you share a link on social media, messaging apps, and collaboration tools. They're defined using the og:image meta tag in your page's HTML head section.

A properly configured OG image dramatically increases click-through rates. Studies show that posts with optimized preview images get 2-3x more engagement than those with broken or missing images. Yet many websites have misconfigured OG images — wrong dimensions, broken URLs, or missing tags entirely.

The most common issues include using relative URLs instead of absolute ones, serving images over HTTP instead of HTTPS, and using dimensions that get awkwardly cropped on specific platforms. Each social network has different size requirements: Twitter prefers 1200x628, Facebook uses 1200x630, LinkedIn wants 1200x627, and WhatsApp renders square 400x400 crops.

OG image size requirements by platform

PlatformRecommended SizeAspect Ratio
Twitter / X1200 x 628 px1.91:1
Facebook1200 x 630 px1.91:1
LinkedIn1200 x 627 px1.91:1
WhatsApp400 x 400 px1:1
Slack500 x 250 px2:1
Discord400 x 200 px2:1
Pinterest600 x 900 px2:3
Telegram1200 x 628 px1.91:1

Common OG image issues and how to fix them

1. OG image URL is relative, not absolute

Social media crawlers cannot resolve relative paths. Always use a full URL starting with https://.

<!-- Wrong -->
<meta property="og:image" content="/images/og.png" />

<!-- Correct -->
<meta property="og:image" content="https://example.com/images/og.png" />

2. Image dimensions not specified

Without og:image:width and og:image:height, platforms may not render the image until they fetch and measure it, causing blank previews on first share.

<meta property="og:image" content="https://example.com/og.png" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />

3. Image file too large

Facebook limits OG images to 8MB, but for fast loading, keep images under 1MB. Use JPEG at 80% quality for photos, PNG for graphics with text.

4. Image served over HTTP

Most platforms require HTTPS for OG images. Mixed content (HTTPS page with HTTP image) will cause the image to be blocked by browsers and crawlers.

Frequently Asked Questions

What is the best OG image size?

The recommended OG image size is 1200x630 pixels with a 1.91:1 aspect ratio. This works well across most platforms including Facebook, Twitter, LinkedIn, and Slack. For Pinterest, use 600x900 (2:3 portrait).

Why is my OG image not showing?

Common causes include: the og:image URL returns a 404, the image is served over HTTP instead of HTTPS, the image file is too large (keep under 5MB), the image URL is relative instead of absolute, or your server blocks crawlers via robots.txt or User-Agent filtering.

Does the OG image need to be on the same domain?

No, the og:image URL can point to any publicly accessible URL, including CDNs like Cloudinary, Imgix, or AWS S3. The key requirement is that the URL must be absolute (starting with https://) and publicly accessible without authentication.

How do I set an OG image in Next.js?

In Next.js App Router, export a metadata object from your page.tsx with openGraph.images. For example: export const metadata = { openGraph: { images: [{ url: 'https://example.com/og.png', width: 1200, height: 630 }] } }. You can also use the opengraph-image.tsx file convention to generate images dynamically.

What image formats work for OG images?

JPEG and PNG are universally supported. WebP works on most modern platforms but may not render on older WhatsApp clients. SVG is not supported. For best compatibility, use JPEG for photos and PNG for graphics with text.

How often do platforms refresh cached OG images?

Facebook caches OG images for about 24 hours. Twitter caches until you manually invalidate. LinkedIn caches for around 7 days. You can force a refresh on Facebook using the Sharing Debugger, and on Twitter using the Card Validator.

Related tools