Social Media Specs

Facebook Specs

Facebook is the platform where the accepted range is widest and the rendered result is least predictable, because the same post can appear in feed, in Marketplace, in a Reel surface and inside Messenger. I build to the ratios below and let Facebook crop from there. The link preview section is the part most teams get wrong.

Image placements
PlacementAspect ratioRecommended pixelsNotes
Feed image1.91:11200 x 630Also the safe size for shared links
Feed image, square1:11080 x 1080More vertical space on mobile
Stories9:161080 x 1920Keep copy inside the safe area
Reels cover9:161080 x 1920Cropped to 1:1 on the profile grid
Page profile photo1:1170 x 170 displayedUpload larger, it is downsized
Page cover photoRoughly 2.7:1820 x 312 on desktopCrops hard on mobile
Event cover1.91:11200 x 628Text sits over the lower third
Video placements
PlacementAspect ratioResolutionLength guidance
Feed video1:1 or 4:51080 x 1350Sound off by default, caption it
Reels9:161080 x 1920Short form, up to 90 seconds is typical
Stories video9:161080 x 1920Splits into 15 second cards
In stream video16:91920 x 1080Longer form, monetisable surface
Text limits and link preview fields
FieldLimit or requirementWhat actually shows
Post textVery long, over 60,000 charactersAround 250 before 'See more'
Page short description255 charactersShown in the About panel
Link preview titlePulled from og:titleAround 60 to 70 characters
Link preview descriptionPulled from og:descriptionOften truncated near 100 characters
Link preview imageog:image, at least 1200 x 630Under 600 x 315 renders as a small thumb

Notes

The single highest leverage Facebook fix is not creative, it is the og:image on your own site. If the shared image is under 600 pixels wide, Facebook renders a small square thumbnail next to a line of text instead of a full width card, and click through collapses. Set og:image at 1200 x 630 and force a re-scrape in the Sharing Debugger after any change, because Facebook caches the old preview aggressively.

Design assuming sound is off and the crop is unknown. Feed, Reels and Stories all serve the same asset in different frames, so put the message in the middle 60 percent of the canvas and burn in captions rather than relying on auto captions.

Page cover photos are the worst asset in social because desktop and mobile crop differently from the same file. Keep any logo or copy inside a central region roughly 820 x 312 and accept that the outer edges will be lost on one device or the other.

Facebook changes these values without announcing them, and Meta frequently tests new crops in the app before documenting them. Confirm against the Meta Ads Guide and the Sharing Debugger before a large production run.

Frequently asked questions

Why does my shared link show the wrong image?

Facebook cached an earlier scrape. Run the URL through the Sharing Debugger and click Scrape Again. If it still picks the wrong asset, your page is likely exposing more than one og:image tag or an image below the minimum size.

Should I still post native video rather than a YouTube link?

Yes, if reach is the goal. Native uploads autoplay in feed and a YouTube link does not, which is most of the distribution difference. Post the link separately when the goal is watch time on YouTube itself.

Do square or vertical images perform better in feed?

Vertical formats take more screen on mobile, which is where nearly all the impressions are. I default to 4:5 for image posts and only use 1.91:1 when the asset is a shared link that needs a matching preview.

Official sources

Platforms change specifications without notice. Check the primary documentation before a launch that depends on an exact value.

Read next

You might also like

Ranked by how closely each page overlaps with this one, using a similarity model over the whole library.

More Social Media Specs