# Why 1080×1080 Is the Wrong Default for Every Platform

A size without a source label is a rumor with a table. "Instagram post: 1080 × 1080" gets repeated in a hundred charts, and it is not even wrong in the narrow sense — a square post is a real thing. But it is the wrong default, because it collapses three different questions into one number: what shape does the slot want, what did the platform actually publish, and what did creators merely converge on?

This post is about that collapse. The [Social Media Image Sizes 2026 guide](https://toolkitloop.com/social-media-image-sizes) I built keeps those questions apart on purpose: every row carries a source label — official recommended, official ad asset spec, or common creator preset — and a last-checked date. The label matters more than the pixels, because the pixels are only correct inside the claim the label makes.

## The table, with labels attached

Official figures were last checked September 11, 2026 against platform Help and developer documentation; preset figures come from current cross-platform guides checked September 9, 2026.

| Platform | Placement | Size | Ratio | Source status |
|---|---|---|---|---|
| X | Profile photo | 400 × 400 | 1:1 | Official recommended |
| X | Header image | 1500 × 500 | 3:1 | Official recommended |
| LinkedIn | Personal background / cover | 1584 × 396 | 4:1 | Official recommended |
| LinkedIn | Page logo | 400 × 400 | 1:1 | Official recommended |
| LinkedIn | Page cover image | 1512 × 256 | 5.91:1 | Official recommended |
| LinkedIn | URL post preview image | 1200 × 627 | 1.91:1 | Official recommended |
| LinkedIn | Organic photo post | 1080 px wide | 3:1 to 4:5 | Official width / ratio guidance |
| Pinterest | Standard image Pin | 1000 × 1500 | 2:3 | Official recommended |
| YouTube | Channel banner | 2560 × 1440 | 16:9 | Official recommended |
| YouTube | Custom video thumbnail | 3840 × 2160 | 16:9 | Official recommended |
| YouTube | Custom Shorts thumbnail | 2160 × 3840 | 9:16 | Official recommended |
| TikTok | Vertical image / carousel asset | 720 × 1280 | 9:16 | Official ad asset spec |
| TikTok | Square image / carousel asset | 640 × 640 | 1:1 | Official ad asset spec |
| TikTok | Landscape image / carousel asset | 1200 × 628 | 1.91:1 | Official ad asset spec |
| Instagram | Feed portrait export preset | 1080 × 1350 | 4:5 | Common creator preset |
| Instagram | Story / Reel export preset | 1080 × 1920 | 9:16 | Common preset + official ratio guidance |
| Facebook | Feed / link export preset | 1200 × 630 | 1.91:1 | Common creator preset |
| Facebook | Story / Reel export preset | 1080 × 1920 | 9:16 | Common preset + official ratio guidance |
| Threads | Feed portrait export preset | 1080 × 1350 | 4:5 | Common creator preset |
| Bluesky | Post landscape export preset | 1200 × 675 | 16:9 | Common creator preset |

Read the right-hand column before the numbers. It is the only column that tells you how much to trust the row.

## 1200 × 627 vs 1200 × 630: the same ratio, different pixels

The most instructive pair in the table is also the smallest difference: LinkedIn's URL preview is 1200 × 627, Facebook's link preset is 1200 × 630. Same 1.91:1 ratio, three pixels apart. A single shared export means one of the two platforms rescales your image, and rescaling is where rendered text goes soft.

This is the kind of detail a label-free chart hides. "1200 × 630 for link previews" is the standard advice, and it is wrong for LinkedIn by three pixels — wrong in a way that only matters if you render text at exactly the target size, which is exactly what a careful designer does. The fix is boring and total: export each placement separately. The ratio is the shape; the pixel count is the contract with one specific slot.

The TikTok rows teach the opposite lesson. 720 × 1280, 640 × 640, and 1200 × 628 are documented, official numbers — from TikTok Ads Manager. They are ad asset specs, not universal organic-post rules. A chart that lists them without the "ad spec" qualifier invites you to treat an advertising constraint as a law of the platform. Labels prevent that category error.

And then there is Threads: no simple first-party pixel table was available in this review. The honest entry is a 1080 × 1350 creator preset with the gap stated openly, not an invented official number. A guide that admits its gaps is more useful than one that fills them silently.

## Safe areas are geometry, not taste

Two placements in the table are really safe-area problems wearing size labels.

YouTube's channel banner is 2560 × 1440, but the safe area at the minimum 2048 × 1152 size is 1235 × 338. That is the rectangle that survives across TV, desktop, and mobile. Everything outside it is decoration that some screens will never show. Designing a banner to the full 2560 × 1440 canvas is designing a message for an audience that may not exist.

X's header is the same problem in miniature: 1500 × 500, with X's own Help article warning that top and bottom cropping can occur. The mitigation is positional, not dimensional — keep faces and text in the vertical middle, because the crop is vertical.

Pinterest adds a third variant: the standard Pin is 1000 × 1500 at 2:3, and taller Pins can be cut off in feeds. Here the ratio itself is the ceiling. Going taller does not buy visibility; it buys truncation.

## Ratios are the API

Twenty rows, four shapes: 1:1 for squares and avatars, 4:5 for portrait feeds, 9:16 for full-screen vertical, 16:9/1.91:1 for landscape and link previews. If you build any tooling around sizes — an export script, a validation check, a CMS preset — model the ratio, not the pixel count. The pixel count is the resolution you render a shape at; the ratio is the shape itself.

```javascript
// The whole calculation: height from width and a [w, h] ratio.
function sizeFor(width, [w, h]) {
  return { width, height: Math.round((width * h) / w) };
}

sizeFor(1080, [4, 5]);   // { width: 1080, height: 1350 } — Instagram / Threads portrait
sizeFor(1080, [9, 16]);  // { width: 1080, height: 1920 } — story / Reel / Shorts
sizeFor(1200, [16, 9]);  // { width: 1200, height: 675 }  — Bluesky landscape

// Validation, not vibes: does this file actually fit the slot?
function fits(file, [w, h]) {
  return Math.abs(file.width / file.height - w / h) < 0.005;
}
fits({ width: 1080, height: 1080 }, [4, 5]); // false — a square is not a portrait
```

A `fits` check that returns false means the platform will crop or pad, and the only open question is where it cuts. "Close enough" is not a strategy when the shapes differ — a 1:1 file in a 4:5 slot is not approximately right, it is a different geometry.

## Fit, Crop, Pad are three different contracts

Once the size is right, the treatment is the last decision, and the three options are not interchangeable. **Fit** keeps the entire source inside the target box. **Crop to fill** makes the exact canvas by cutting edges. **Pad to fit** keeps the full source and adds space around it. Resizing changes dimensions; compression is a separate operation that reduces file weight. If text sits near an edge, Pad or Fit — never Crop to fill.

I built [ToolkitLoop Image Resizer](https://toolkitloop.com/image-resizer) for this step: type the target dimensions, pick Fit, Crop to fill, or Pad to fit, and download. It runs entirely in your browser, no upload, no account. (Disclosure: I built ToolkitLoop, and the size guide and the resizer are my own tools.)

## The default worth keeping

1080 × 1080 is not a bad size. It is a bad default — a square that pretends to be universal. The better default is a question asked before every export: which slot is this for, what did the platform actually publish for it, and what happens to the edges? The table above answers the first two. The third is yours to decide, deliberately, before the platform decides it for you.

Do you export every placement exactly, or ship one master file and accept the crop? And which platform's crop has bitten you hardest — the X header, the YouTube safe area, or something I have not listed?
