Social Media Image Sizes in 2026: The Complete Cheat Sheet

Image dimensions are one of those details that quietly decide whether an automated post looks professional or looks broken. The same image that renders beautifully on LinkedIn can arrive on Instagram with the top of someone’s head cropped off, or appear on X as a letterboxed strip with grey bars on either side. This guide covers the sizes that actually matter in 2026, why automated posts are especially vulnerable to cropping problems, and the practical approach that lets one well-made image work across every platform you distribute to.

Why This Matters More for Automated Posts

When you post manually, you see the crop preview before publishing and can adjust. Automation removes that checkpoint by design — that’s the point of it. An image pulled from your RSS feed goes out to Facebook, X, LinkedIn, and Pinterest simultaneously, and each platform applies its own crop rules without asking. If your source image doesn’t survive those crops, you find out afterward, usually from the post that already went to your entire audience.

The fix isn’t to abandon automation or to produce a separate image per platform for every post. It’s to understand which ratio each platform crops toward and to design source images that degrade gracefully when cropped.

The Two Ratios That Cover Most Situations

Before the full table, here’s the shortcut that solves the majority of cases:

• 1200×630 (1.91:1 landscape) — the standard for link preview cards on Facebook, LinkedIn, and X. If your automation posts links to blog articles, this is your primary size.
• 1080×1080 (1:1 square) — the safest universal format for native image posts, because it renders acceptably on nearly every platform without severe cropping.

If you produce nothing else, produce these two. Everything below is refinement.

The Complete 2026 Size Reference

Treat these as targets rather than absolute law. Platforms adjust rendering periodically, and the ratios above are far more stable than the exact pixel counts — a 1600×840 image and a 1200×630 image both sit at 1.91:1 and will crop identically.

Ratio Beats Resolution

The most useful mental shift: platforms crop based on aspect ratio, then scale to whatever resolution they serve. A 2400×1260 image and a 1200×630 image are the same shape and get treated identically, with the larger one simply downscaled. What causes visible damage is a ratio mismatch — feeding a 1:1 square into a slot that wants 1.91:1 means roughly the top and bottom thirds get discarded, and if that’s where your headline text sits, it’s gone.

So the practical rule is: get the ratio right first, then make sure resolution is high enough to look sharp on a high-density display. Doubling the recommended dimensions is a reasonable habit; going far beyond that mostly adds file size without visible benefit.

The Safe Zone Concept

Because different platforms crop the same image slightly differently, professional social designers work with a “safe zone” — the central region of the image that survives every crop. In practice:

• Keep headline text, logos, faces, and any critical detail within the central 80% of the frame.
• Treat the outer 10% on each edge as expendable — background, texture, or gradient only.
• Never place text that runs edge to edge; it will be clipped somewhere.
• Avoid putting a logo in a corner if that image will be used in multiple ratios. Corners are the first thing cropping removes.

Design once with a generous safe zone, and a single image can serve a 1.91:1 card, a 1:1 square, and a 4:5 portrait crop without any version looking broken.

File Size, Format, and Compression

Dimensions are only half the story. Three technical constraints regularly break otherwise-correct images in automated posting:

Format. JPEG and PNG are universally supported. Use JPEG for photographs and PNG for graphics with flat colour, sharp edges, or transparency. WebP support remains inconsistent across social crawlers, and SVG is not supported as a preview or post image on the major platforms — a feed whose images are SVG will consistently produce imageless posts.

File size. Aim for well under 1 MB. Very large files risk timing out when a platform’s crawler fetches them, which produces the same visible result as having no image at all. Compression to around 80% JPEG quality is usually indistinguishable from the original at feed size.

Accessibility. A publicly reachable HTTPS URL is required. Images behind a login, on a staging domain, or protected by hotlink rules that block unfamiliar user agents will fail silently for every platform crawler.

How Automated Posts Pick an Image

Understanding the chain helps you control the outcome. For a typical RSS-driven automated post, the image comes from one of these sources, roughly in this order of precedence:

1. An explicit image field in the RSS item itself — commonly an <enclosure> element or a <media:thumbnail> tag.
2. The first image found inside the item’s content, if the feed carries full HTML content.
3. The og:image tag on the destination page, which is what the platform itself uses when rendering a link preview card.

This is why two posts from the same site can show different images: one may be a native image post using the feed’s enclosure, while another is a link post where the platform ignored the feed entirely and read the page’s Open Graph tag. If your card images look wrong specifically on link posts, the fix belongs on the page rather than in the feed.

Tools like PostRSS pass through whatever image the feed provides for the formats that support it, which means the quality and shape of what gets posted is largely determined upstream — by the images you attach to your source content in the first place.

A Practical Workflow for Automated Distribution

Producing platform-specific images for every post defeats the purpose of automation. This workflow keeps the effort low:

1. Create one master image at 1200×630 for each piece of content, designed with the central safe zone in mind.
2. Set it as both the featured image and the og:image on the source page, so link cards and feed-based posts agree.
3. If you distribute to Pinterest, produce one additional 1000×1500 vertical version — Pinterest’s ratio is different enough that a landscape image genuinely underperforms there.
4. If you distribute to Instagram, a 1080×1080 square version is worth the extra minute, since a 1.91:1 image in a square slot loses a lot of frame.
5. Reuse the template. Build the master as a reusable design template with a text slot and an image slot, and producing each new one becomes a two-minute task rather than a design project.

Common Sizing Mistakes

Using the blog’s inline image as the social image. Article images are often wide and short, or tall and narrow, because they’re designed to sit in a text column. Neither shape survives social cropping well.

Text too small to read at feed size. A preview card in a mobile feed may render only a couple of hundred pixels wide. Text that looks fine on your monitor at full size can be unreadable there — a good check is to shrink the image to 350 pixels wide and see whether the headline still reads.

Relying on transparency. A PNG with a transparent background composites against whatever colour the platform uses, which differs between light and dark mode. A logo that looks clean on white can vanish on a dark background. Always give social images an explicit background.

Ignoring dark mode. A large share of users browse in dark mode. Images with near-white backgrounds glare in a dark feed; images with very dark backgrounds can look like empty space. Mid-tone or clearly branded backgrounds are safer.

Assuming the platform will letterbox rather than crop. Most platforms crop to fill rather than shrink to fit. Extra margin around your content is not protection; it just means more of your actual content sits closer to the crop line.

Vertical vs Landscape: Which Should You Default To?

This has shifted meaningfully over the past few years. Landscape used to be the safe default because feeds were viewed on desktop and link cards dominated. Mobile consumption changed that calculation: on a phone screen, a 4:5 portrait image occupies roughly 60% more vertical space than a 1.91:1 landscape image, which means it stays in view longer as someone scrolls and simply has more opportunity to register.

The practical split for automated distribution: use landscape 1.91:1 when you’re posting a link and the platform will render a preview card anyway, because that’s the shape the card slot expects. Use portrait 4:5 when you’re posting a native image with the link in the caption, since you control the shape and vertical space works in your favour. Square 1:1 sits between the two and is the right choice when a single image has to serve several destinations and you’d rather not manage variants at all.

Logos, Watermarks, and Brand Consistency

Automated distribution multiplies whatever you do — consistently good or consistently sloppy. A few habits that pay off at volume:

• Place the logo inside the safe zone, not tucked into a corner where cropping removes it. Slightly inset from an edge, or integrated into a coloured band, survives every ratio.
• Keep it small. On a card rendered a few hundred pixels wide, a large logo eats space that the headline needs. Recognition doesn’t require size; consistency does.
• Use a consistent accent colour. When someone scrolls past three of your posts in a week, a repeated colour treatment does more for recall than the logo itself.
• Avoid watermarking photos across the middle. It reads as stock-image protection rather than branding, and it damages the image at exactly the point the eye lands.

Do Image Dimensions Affect Reach?

Not directly — no major platform ranks content by image dimensions. The effect is indirect and behavioural: a correctly-sized image occupies more vertical space in the feed, reads more clearly at a glance, and looks credible rather than careless. Portrait and square formats in particular take up more screen real estate on mobile than landscape, which is a meaningful advantage when most feeds are consumed on phones. That translates into attention, and attention is what the ranking systems actually measure.

Frequently Asked Questions

What is the safest single image size for social media?

1200×630 for link preview cards, and 1080×1080 if you’re posting native images and want one file that works nearly everywhere. Between them, those two cover most automated distribution.

Why does my image get cropped differently on each platform?

Each platform crops toward its own preferred aspect ratio rather than displaying your image as-is. Keeping important content within the central 80% of the frame means every crop still contains what matters.

Should I make a separate image for every platform?

Usually not. One well-designed 1200×630 master covers link cards across Facebook, LinkedIn, and X. Add a vertical version only if Pinterest or Instagram is a meaningful channel for you.

Can I use WebP images for social posts?

It’s risky. WebP support across social crawlers is inconsistent, and an unsupported format produces a post with no image at all. JPEG and PNG remain the reliable choices.

Does a bigger image file give better quality?

Only up to a point. Platforms recompress uploads anyway, and very large files risk fetch timeouts. Roughly double the recommended dimensions, compressed to under 1 MB, is the sweet spot.

Why does my automated post have no image at all?

The usual causes are an image URL that isn’t publicly reachable, a relative rather than absolute URL, an unsupported format such as SVG, or a feed item with no image field and a destination page with no og:image tag.

Does image size affect SEO?

Social image dimensions are not a search ranking factor. File size does affect page speed, which matters for SEO — but that’s about the images on your page, not the ones in your social posts.

The Bottom Line

Get the aspect ratio right and most sizing problems disappear. Build one 1200×630 master image per piece of content with your key elements inside the central safe zone, save it as a compressed JPEG or PNG on a publicly reachable HTTPS URL, and set it as both your featured image and your og:image. Add a vertical variant only for the platforms that genuinely reward it. That single habit means every automated post you publish from then on arrives looking deliberate, whichever platform it lands on.