Facebook image sizes for link previews
Last updated: September 20, 2026.
Size figures on this page are placeholders. They are not marked verified because we have not re-checked Facebook’s current documentation.
Facebook still decides how a shared URL looks in Feed, Groups and Messenger by reading Open Graph tags in the first HTML response. The picture is og:image. A dedicated 1200×630 file is easier to control than a random crop from the article. This page is a size and crop guide, not a full sharing manual. Pixel values in the table are placeholders we have not re-checked against Meta’s current documentation, so treat them as a working default until the verified badge appears. After you host a PNG or JPG, scrape the live URL in Sharing Debugger so cache does not keep an older file. Relative paths fail; use https.
Recommended Facebook size
| Platform | Image type | Recommended size | Aspect ratio | Max file size |
|---|---|---|---|---|
| Link preview | 1200 × 630 px | 1.91:1 | 8 MB |
Official page to re-check:https://developers.facebook.com/docs/sharing/webmasters/images/
How Facebook crops your image
Link previews are landscape. Facebook lays the image in a wide card and may letterbox or clip the edges if your file is a different ratio. Text that sits on the far left or right can disappear on a phone even when it looked fine on a desktop canvas. Keep the headline inside a comfortable inner margin — the safe-area overlay in the OG Image Generator is a guide for that, not a Facebook spec.
If you upload a square or portrait photo and tag it as og:image, Facebook will not preserve the full frame. It favors the center. Faces or logos in a corner are the first things to go. A 1.91:1 canvas with padding around the title is more predictable than tagging a story-format frame.
Replacing a file at the same URL often does nothing in Feed until you force a rescrape. Change the path or add a query string when the artwork changes, then run Sharing Debugger on the canonical page URL, not on the image URL alone.
Three common Facebook mistakes
Tagging a 1080×1920 story as og:image
Stories and Reels use a tall frame. A link preview does not. If you reuse that vertical file, Facebook crops through the middle and the title is gone. Export a separate landscape image for the URL you actually share.
Putting the og:image tag only in client-rendered HTML
The Facebook crawler does not wait for your React tree. If the meta tag is missing from View Source, the preview will be empty or guessed from some other image on the page.
Leaving a 3 MB PNG on a slow origin
Huge files fail quietly or get recoded. The table lists a maximum we still need to verify; in practice you want well under a megabyte for a title card. PNG is fine for type on a flat background. Switch to JPG if a photo background balloons the size.
What to put in the tags
og:image must be an absolute https URL that returns 200 to an anonymous GET. Add og:image:width and og:image:height to match the file you actually uploaded. og:title and og:description still control the text next to the picture; this site only builds the image.
Do not point og:image at a CDN URL that expires, a signed S3 link, or a path blocked by robots.txt. If the image host differs from the page host, make sure the file is publicly cacheable. After a domain move, scrape again — Facebook will otherwise keep the old preview.
Create a Facebook-sized OG image
Opens the generator with the Facebook size preset selected. Nothing is uploaded.