Auto-check OGP recommended sizes for each platform

Page Summary

The OGP Image Size Checker tells you at a glance whether an uploaded image meets the recommended size for X (formerly Twitter), Facebook, LINE, note, WordPress, Instagram, YouTube, and more. Pass / warn / fail are shown visually for each platform.

  • 8 platforms: Check the recommended sizes for major social platforms in one go
  • 3-tier verdict: Pass / warn / fail icons make it intuitive
  • Aspect previews: See how it looks in each aspect-ratio frame
  • Privacy: Images are never sent to a server
ADVERTISEMENT

OGP Image Size Checker

How to Use

1
Upload an Image
Drop or select the OGP image you want to check
2
Review the Results
See the pass / warn / fail verdict per platform
3
Check the Previews
Verify how it actually appears in each aspect ratio

🔒 Images are processed in your browser and never uploaded or stored on a server

Click or drag & drop an image to upload

Supports JPG, PNG, WebP
Uploaded image preview

Per-Platform Verdict

Platform Recommended Size Minimum Size Ratio Result

Aspect Ratio Preview

ADVERTISEMENT

Frequently Asked Questions (FAQ)

What is OGP (Open Graph Protocol)?

OGP is a metadata standard originally created by Facebook that lets URLs shared on social media display the right title, description, and image. It is supported by X (formerly Twitter), LINE, Slack, and most major social and messaging apps.

Recommended Sizes per Platform

X (Twitter) / Facebook: 1200×630 px (ratio 1.91:1) is standard, with a minimum of 600×314 px.
LINE: 1200×628 px recommended.
note: 1280×670 px (16:9) recommended.
Instagram (landscape): 1080×566 px.
Instagram (square): 1080×1080 px.
YouTube thumbnails: 1280×720 px (16:9) recommended; minimum 640×360 px.

How to Set OGP Image Tags in HTML

Place the OGP image inside the <head> like this:
<meta property="og:image" content="https://example.com/ogp.png">
For X (Twitter), also include <meta name="twitter:card" content="summary_large_image"> and <meta name="twitter:image" content="https://example.com/ogp.png">.

Practical Limits and What This Tool Cannot Do

OGP tag inspection relies on parsing the HTML meta elements, but actual social-media display depends on each platform's crawler and renderer. OGP tags rendered dynamically via JavaScript (SPAs/CSR) often aren't picked up — server-side rendering or static HTML is recommended. Display sizes, aspect ratios, and crop behavior may also change without notice, so this tool's output may not perfectly match real social previews.

Real-world Q&A

Q: My OGP image isn't showing — just a gray frame. Common causes: relative image URL, non-HTTPS URL, or image too small (Facebook minimum 200×200 px). Always specify og:image as an absolute URL (https://...). Q: My Twitter card isn't displaying. Make sure the twitter:card meta tag is set, validate via the Twitter Card Validator (cards-dev.twitter.com/validator), and remember the first crawl on a domain can take up to several hours.

Trends in OGP and Social Metadata

Facebook introduced OGP in 2010, and today it is supported by LINE, Slack, Discord, and many others. In practice, pairing it with X's Twitter Card meta tags is the de facto standard. Since 2024, video-thumbnail OGP (og:video), JSON-LD integration, and metadata consumed by AI chatbots have all grown in importance. Webmaster tools like Google Search Console and Bing Webmaster Tools have also been adding stronger OGP validation.