Free Online Tool
OG Image Resizer, Open Graph & Twitter Card
When someone shares your page on LinkedIn, Twitter, Slack, or iMessage, the platform fetches your og:image and crops it to fit its preview card. A wrong-sized image gets cut off or shows a thin letterbox. Set og:image to exactly 1200ร630 px and you control the preview everywhere. Drop your image here and download a correctly-sized JPG ready to set as your og:image.
The Open Graph og:image tag is used by Facebook, LinkedIn, Slack, Discord, WhatsApp, and most link-preview systems. Twitter/X uses its own twitter:image tag but accepts the same image when sized correctly.
Two presets: OG Image 1200ร630 px (universal) and Twitter Card 1200ร600 px (Twitter/X-specific).
Image resizing happens in your browser. Your design assets never leave your device until you deploy them to your server.
When not to use this tool
Per-platform card variants
Different platforms render OG images at different sizes (LinkedIn shows 1200ร627, Twitter shows 1200ร675). Generate platform-specific cards for each instead of one generic OG.
Text-heavy designs from Photoshop
Resizing rasterised text degrades sharpness. Export OG cards directly at 1200ร630 from the source app for crispest text.
OG images for already-deployed pages
Updating an OG image means re-scraping by Twitter / LinkedIn / Facebook, some platforms cache for days. Plan for the lag.
Technical details
The 1200ร630 standard
Facebook, LinkedIn, WhatsApp, Slack, all share-preview pipelines settled on 1.91:1 aspect ratio at 1200ร630 pixels. Twitter's "summary_large_image" card uses 1200ร675 (16:9), close but not identical. A single 1200ร630 image works on every platform; for Twitter specifically, you can ship a separate 1200ร675 variant if you want to control top/bottom cropping.
Safe area for text overlays
Different platforms crop slightly differently. To survive every crop, keep text within the central 1100ร580 area (~50px padding on all sides). Avoid corners. They're the most likely to be sliced by mobile previews.
PNG vs JPG for OG
For text-heavy OG images (call-to-action cards, quote pull-outs), PNG keeps text crisp. For photo-based OG images, JPG q85 saves 60%+ with no perceptible quality loss. Whichever you pick, keep total file size under 1 MB, some platforms reject larger.
Frequently Asked Questions
- What size should an OG image be?
- The standard og:image size is 1200ร630 px (approximately 1.91:1 ratio). This is the size Facebook, LinkedIn, Slack, and Discord use for link previews. Images smaller than 600ร315 may be displayed as small thumbnails instead of full-width cards.
- What is the difference between OG image and Twitter Card image?
- og:image is the standard Open Graph tag used by most platforms. Twitter/X has its own twitter:image meta tag and uses a slightly different aspect ratio (2:1 = 1200ร600 px). This tool provides both presets. Use 1200ร630 for og:image and 1200ร600 for twitter:image, or use the OG size for both, Twitter accepts it.
- What file format should an OG image be?
- JPG is the best choice for OG images. PNG files load slower and some platforms compress them further on their CDN anyway. WebP is not reliably supported in og:image crawlers. JPG at quality 85 keeps the file under 200 KB, which loads quickly when crawlers fetch it.
- Why does my OG image look wrong on Slack or Twitter?
- Each platform caches og:image the first time it sees a URL. If you change the image, the old version may still be shown. For Twitter, use the Twitter Card Validator to clear the cache. For LinkedIn, use the Post Inspector. For Facebook, use the Sharing Debugger to force a refresh.
- Should my OG image have text on it?
- Text on OG images improves click-through rate in link previews because users see context before clicking. Keep text within a safe inner zone, some platforms add a slight letterbox. This tool outputs at exactly 1200ร630, so your design margins are accurate.
- How many OG images do I need per page?
- One per page. Set a different og:image for each important page (homepage, blog posts, product pages). If all pages share one image, link previews look identical and users cannot tell pages apart before clicking.
- What is the minimum og:image size that still gets full-width previews?
- Facebook requires at least 600ร315 px for a full-width link preview. Below that, the image is shown as a small thumbnail to the left of the text. LinkedIn requires at least 1200ร627 px for full-width. Twitter requires at least 300ร157 px for Summary Large Image cards. Always use 1200ร630 px to cover all platforms.
- Does every blog post need its own og:image?
- Yes, ideally. When links are shared, a unique og:image signals that the content is distinct and increases click-through rates in social media feeds. A generic site-wide default image makes all shared links look identical. Most CMS platforms support per-post og:image fields: set one for every post you publish.