Use a 1200 × 630 pixel canvas (about 1.91:1) as a practical starting point for one Open Graph image shared across services. It is a broad-compatibility recommendation, not a universal Open Graph rule. File-size limits belong to the platform fetching your preview: for example, LinkedIn’s sharing module requires at least 1200 × 627 pixels, recommends a 1.91:1 ratio, accepts JPG, PNG, or GIF, and caps the image at 5 MB. Other services can impose different dimensions, formats, or byte limits.
Open Graph size has two separate meanings
Developers often ask for “the OG image size” as if the Open Graph Protocol defines one file limit. It does not. The protocol defines og:image as an image URL representing the object; it does not establish one pixel dimension or byte cap for every social network.
The platform that retrieves your page decides whether it can download, decode, crop, and display that image. Therefore, design the asset and metadata separately:
- Canvas dimensions and composition: the pixel width, height, aspect ratio, and safe placement of text or logos.
- Transport and encoding: the file format, compression, byte size, HTTP response, and whether the crawler supports the format.
A technically valid og:image can still produce a missing or poorly cropped preview when a destination has stricter requirements.
#1 Best Overall
Recommended dimensions and file-size targets
Start with 1200 × 630 pixels
A current cross-platform design guide recommends 1200 × 630 pixels, approximately 1.91:1, for a shared image. Treat that as a starting canvas rather than a guarantee. Keep important content away from every edge: previews may crop differently on timelines, cards, mobile screens, and messaging apps.
LinkedIn’s documented sharing requirement
LinkedIn’s sharing help specifies a minimum of 1200 × 627 pixels and recommends a 1.91:1 ratio. Its sharing module accepts JPG, PNG, or GIF and has a 5 MB maximum. These requirements apply to the sharing module, not automatically to every LinkedIn advertising placement. If LinkedIn is a priority destination, export an asset that meets those values or create a LinkedIn-specific variant.
Why there is no universal maximum
Secondary cross-platform references report different ceilings, including 8 MB for Facebook, 5 MB for X and LinkedIn, and a smaller target for WhatsApp. Those figures can change and are not a substitute for each platform’s current first-party documentation. A verified official X limit was not established here, so do not present a secondary number as X’s authoritative current policy.
| Source or destination | Dimensions or ratio | Maximum size | Formats or evidence |
|---|---|---|---|
| Open Graph Protocol | No universal dimension stated | No universal byte cap stated | Defines og:image as an image URL representing the object |
| General cross-platform starting point | 1200 × 630; about 1.91:1 | Varies by destination | Secondary design guidance; verify current platform rules |
| LinkedIn sharing module | Minimum 1200 × 627; 1.91:1 recommended | 5 MB | JPG, PNG, or GIF; official LinkedIn help |
| X | Not stated here | Not stated here | Confirm current first-party requirements before publishing |
Choose a format based on the artwork
Photographic or gradient-heavy images
Lossy JPEG, WebP, or AVIF can substantially reduce bytes at a comparable visual quality. The best choice depends on the destination’s decoder and the image’s details. Examine faces, gradients, small type, and dark areas at the size a social card actually displays.
Text, logos, and sharp graphics
Strong edges expose ringing, halos, and color bleeding. A higher-quality JPEG, lossless PNG, or a modern format with carefully inspected settings may be better than aggressively reducing quality. PNG is not automatically smaller: a photographic PNG is often much larger than a JPEG or WebP.
AVIF and compatibility
AVIF can be much smaller than JPEG, PNG, GIF, or WebP at comparable quality, according to web.dev’s AVIF guidance. That advantage matters only when the service fetching the preview can decode AVIF. If support is uncertain, use a broadly supported fallback or maintain a platform-specific asset. A smaller file in an unsupported format is not an optimization; it is a broken preview.
A repeatable optimization workflow
- Compose at 1200 × 630. Put the title, logo, and subject inside a generous central safe area. Do not rely on pixels at the extreme top, bottom, or sides.
- List the destinations. Identify where the URL will be shared, then check each service’s current official minimum dimensions, maximum bytes, and accepted formats. Record requirements for the specific product surface, such as a sharing module versus an advertisement.
- Export candidates. Produce a high-quality JPEG or WebP for photos, and compare PNG or a carefully tuned modern format for crisp graphics. If you test AVIF, keep a fallback until support is confirmed.
- Compress iteratively. Lower quality or remove metadata in small steps. Stop at the smallest file that still looks correct in a real preview and stays below every verified limit.
- Inspect at preview scale. Check text legibility, logo edges, gradients, faces, and transparent areas. A file that looks excellent at full resolution can fail when reduced to a small card.
- Validate delivery. Return the correct
Content-Type, allow the crawler to fetch the URL without authentication, avoid accidental redirects, and ensure the final response is the intended image rather than an HTML error page.
Metadata and implementation checks
Place an absolute image URL in your page’s head:
<meta property="og:image" content="https://example.com/images/article-og.jpg">
Serve the image over HTTPS with a stable URL. Confirm that your server sends an image media type such as image/jpeg, image/png, image/webp, or image/avif matching the bytes. Do not confuse an HTTP 200 response with a valid image: a consent page, login screen, bot challenge, or framework error can also return 200 while preview crawlers cannot render it.
When you maintain multiple variants, give each one a clear purpose (for example, a broad fallback and a destination-specific file). Update cache-busting URLs when the artwork changes, because social crawlers can retain an earlier response.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Performance, reliability, and cost considerations
Bandwidth and latency
Every preview fetch consumes bandwidth and time. A smaller file generally reaches the crawler faster, but excessive compression creates visible defects and can undermine click-through. Measure the delivered file, not just the source export; CDN transformations, metadata, and content negotiation can change the final bytes.
Caching
Use long-lived caching for immutable, versioned image URLs. If you replace an image at the same URL, a platform may continue showing the previous card until its cache expires. Version the filename or query strategy you control, then update og:image.
One asset versus several
One 1200 × 630 file simplifies publishing and usually works broadly. Separate assets make sense when a high-value destination has a materially different minimum, crop, or format policy. Keep the message and branding consistent while adjusting composition for that service.
Troubleshooting common failures
The preview is blank
Fetch the image URL as an unauthenticated client and inspect the status, redirects, final URL, and Content-Type. Replace HTML error pages, blocked hotlink responses, expired signed URLs, and robots or firewall rules that prevent crawler access.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchThe image is cropped badly
Recompose with more edge padding and test the actual 1.91:1 crop. Keep faces, headlines, and logos near the center. A 1200 × 630 source can still be cropped by a destination’s card design.
The file exceeds a platform limit
Check the limit for the exact destination surface, then re-export from the original at a lower quality or a more suitable format. Remove unnecessary metadata and compare the rendered result after each change. Do not simply rename a file extension; the encoded bytes must match the declared type.
AVIF or WebP does not render
Assume decoder support is the issue until the platform confirms otherwise. Publish a broadly supported JPEG or PNG fallback for that destination, or use a platform-specific URL.
LinkedIn shows an old image
Verify that the page now references the new absolute URL and that the URL returns the new bytes. Because preview services cache fetches, changing the asset URL is often more dependable than overwriting the same file.
Or skip the browser setup
ScreenshotNeo can capture the rendered page while handling the browser work. Its clean-shot steps accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in headers. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
One request returns PNG, JPEG, WebP, or PDF:
Read the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is included on every plan. Create a free ScreenshotNeo account.
Practical decision checklist
- Use 1200 × 630 as the initial shared canvas.
- Confirm each destination’s current requirements instead of assuming a universal cap.
- Keep critical content inside a safe area.
- Choose JPEG, WebP, AVIF, or PNG according to image content and decoder support.
- Compress until the visual result is right and the file is below every verified limit.
- Test the public URL, response type, redirects, and cache behavior.
Frequently Asked Questions
Does the Open Graph Protocol require 1200 × 630 pixels?
No. The protocol defines the image URL property but does not set one universal dimension or byte limit. The 1200 × 630 canvas is practical cross-platform guidance.
Is 5 MB the maximum size for every social network?
No. LinkedIn documents a 5 MB maximum for its sharing module. Other destinations can publish different limits, and those policies can change.
Should every OG image be JPEG?
No. JPEG, WebP, and AVIF can suit photographs, while PNG or a higher-quality export may preserve sharp text and logos better. Confirm that the destination supports the chosen format.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why can a 200 response still produce no social preview?
The response may contain HTML, a bot challenge, a consent page, or another non-image payload. Check the final response body and Content-Type, not only the HTTP status.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
