What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a typical portrait Facebook feed image, use 1080 × 1350 pixels (4:5). A 1080 × 1080-pixel square (1:1) is a practical alternative when your design is naturally square or must work across several placements. These are working recommendations, not a verified universal Meta requirement for every organic post.
The correct dimensions depend on where Facebook will display the image: an organic feed upload, link preview, Story, Reel and advertisement use different shapes and cropping rules.
Facebook image sizes at a glance
| Placement | Common working size | Aspect ratio | What to know |
|---|---|---|---|
| Portrait organic feed image | 1080 × 1350 px | 4:5 | A commonly reported portrait recommendation from secondary guides; not verified as a universal official requirement. |
| Square feed image | 1080 × 1080 px | 1:1 | Useful when the composition is square or the same asset must fit multiple surfaces. |
| Landscape or link-preview image | 1200 × 630 px | About 1.91:1 | A common link-preview working size. A preview is fetched from page metadata such as og:image. |
| Story or Reel | 1080 × 1920 px | 9:16 | Vertical placement; feed dimensions should not be reused without checking the crop. |
| Feed image advertisement | 1440 × 1800 px | 4:5 | A reported advertising specification, not a requirement for an organic feed upload. |
These figures come from secondary references including Postproxy (August 11, 2026), RecurPost (updated September 24, 2026), Media Cheat Sheet (reviewed August 20, 2026) and Adship (published September 6, 2026). Facebook rendering can change by placement, device and product update, so confirm the current settings in the publishing or Ads flow before finalizing paid creative.
Which size should you choose?
Use 1080 × 1350 for a portrait feed post
The 4:5 canvas gives a portrait photo more vertical space in a scrolling feed than a square canvas. It suits people, products, posters and step-by-step graphics. Keep the subject and essential text away from the outer edges so a preview or device-specific crop cannot remove them.
#1 Best Overall
Use 1080 × 1080 when square is better
Square is a sensible choice for logos, product tiles, quotations and designs built around a centered composition. It can also simplify reuse across surfaces. It is not established by the cited sources that 1:1 performs better or worse than 4:5; choose based on composition and the placements you need.
Use 1200 × 630 for a link preview
When somebody shares a URL, Facebook generally builds the card from the page’s metadata rather than from an image you upload in the composer. Set the page’s og:image to a landscape image around 1200 × 630 pixels, then test the actual URL. This size should not be described as mandatory for every direct feed upload.
Use 1080 × 1920 for Stories and Reels
Stories and Reels occupy a full vertical screen. Design at 9:16 and leave breathing room at the top and bottom for interface controls, captions and account information. A 4:5 feed image placed into a 9:16 frame will normally require padding or cropping.
Treat ad specifications separately
The reported 1440 × 1800-pixel 4:5 value belongs to a feed-ad specification compilation. Paid placements have their own review and delivery rules. Do not present an ad specification as the required canvas for an organic post, and check the current Ads Manager placement guidance before exporting.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesHow to prepare an image that survives Facebook cropping
- Start with the placement. Decide whether the asset is for feed, a link card, Story, Reel or an ad before opening your design tool.
- Create the correct pixel canvas. Use 1080 × 1350 for a portrait feed recommendation, 1080 × 1080 for square, 1200 × 630 for a link-preview image or 1080 × 1920 for Story/Reel.
- Build a safe area. Keep faces, logos, prices and calls to action comfortably inside the edges. Do not rely on a precise crop boundary remaining identical on every device.
- Export a clean final file. Use the format and quality settings appropriate to your design tool, inspect the exported pixel dimensions, and avoid accidentally uploading a thumbnail or a low-resolution preview.
- Preview the real placement. Upload a draft or use the relevant publishing preview. For a link, inspect the page metadata and refresh the preview after changing the image.
- Check on a phone. Small text that looks readable on a large monitor may be unusable in a feed. Confirm that the focal point and text remain clear at typical mobile size.
Direct upload versus link-preview image
These workflows are often confused. A direct photo post uses the file selected in Facebook’s composer. A link preview is generated from the destination page, commonly using og:image, title and description metadata. Changing the image in your design app does nothing to an already cached link preview until Facebook fetches the updated metadata.
- Direct upload: choose a feed, Story or Reel canvas and upload that file.
- Link share: set and test the website’s preview image, then share the URL.
- Ad creative: follow the placement-specific Ads Manager specification rather than an organic-post recommendation.
Common mistakes and fixes
The image looks zoomed or clipped
Cause: the source ratio does not match the placement or important content sits near an edge. Fix: create a canvas for the intended placement, move essential elements inward and preview before publishing.
The link card shows an old image
Cause: Facebook has cached the page metadata. Fix: verify that og:image points to the new file, ensure it is publicly reachable, then retry the URL in the publishing flow. A changed filename or query string can help distinguish a new asset, but Facebook’s refresh behavior is not guaranteed to be immediate.
Text is unreadable on mobile
Cause: too much copy or type sized for a desktop canvas. Fix: shorten the message, increase type size, strengthen contrast and test at phone width.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteA Story or Reel has cut-off labels
Cause: content was designed for a feed ratio and then enlarged into 9:16. Fix: redesign on a 1080 × 1920 canvas and keep controls and captions clear of the top and bottom areas.
An ad is rejected or rendered differently
Cause: an organic-post convention was used for a paid placement, or the current placement has changed. Fix: inspect the exact placement in Ads Manager and export a separate version rather than assuming one file fits every placement.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Checking the rendered result without setting up a browser
If you publish a page containing an image or link-preview metadata and need a repeatable screenshot for QA, ScreenshotNeo can capture the rendered page through one request. It is separate from Facebook’s own upload and preview rules, so use it to inspect your page or documentation rather than to bypass Facebook’s composer.
Or skip the browser setup:
The API removes cookie banners, newsletter popups and chat widgets before the shot. Bot checks, blank pages and failed loads are not billed, and an MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 shots.
See the ScreenshotNeo documentation for parameters and response headers. The following examples capture a page that contains your image or preview metadata; replace the URL with your own publicly reachable page.
Best Value
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo supports PNG, JPEG, WebP and PDF output, with options such as full-page capture, a selected CSS element, custom viewport or device, dark mode, retina scale, custom CSS and JavaScript, waits, blocked resources and signed links. The response identifies whether the page was cleanly captured and whether it was billed. Create a free ScreenshotNeo account to get 1,000 shots each month without a card.
Reliability and cost considerations
- Keep separate source files for feed, link-preview and 9:16 placements; automatic resizing cannot preserve every composition.
- Use a consistent naming convention such as
campaign-feed-1080x1350.webpso the intended canvas is obvious before upload. - For link previews, test the public page from outside your local network. A private, blocked or slow image URL cannot be fetched reliably.
- Do not infer engagement from dimensions alone. The cited sources provide recommendations and specifications, not a controlled comparison of 4:5 versus 1:1 performance.
What is established—and what is not
The practical choices are clear: 1080 × 1350 for a common portrait feed canvas, 1080 × 1080 for square, 1200 × 630 for a common link-preview image and 1080 × 1920 for Stories and Reels. Secondary references disagree about how to describe organic-feed cropping, and no directly verified official Meta page establishing one universal organic-post canvas was identified. Treat the values as production conventions, then verify the current rendering in the placement where the image will appear.
Frequently Asked Questions
Is 1080 × 1350 an official Facebook requirement?
It is a commonly reported 4:5 working recommendation for a portrait feed image, not a verified universal official requirement for every organic post.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Can I use one image for feed, Stories and Reels?
You can, but the ratios differ. Prepare separate crops or layouts when important text or subjects would otherwise be cut off.
What size should a Facebook link-preview image be?
A common working size is 1200 × 630 pixels, using the page’s preview metadata such as og:image.
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.
