Upload an image at the wrong size and the platform decides what happens next — usually a clumsy crop that cuts off a face, a stretch that softens the detail, or a re-encode that leaves the whole thing looking muddy. Getting the size right before the upload is the only way to keep control of how the image actually appears.
Two things changed in 2026, and both matter. First, the feed went vertical: Meta now prioritises 4:5 portrait posts over the old 1:1 square, and Instagram's profile grid moved to a taller 3:4 shape, so designing at 1080×1440 fills more of the grid than a square ever did. Second, the format rules loosened — WebP is now accepted on most major platforms, though JPEG remains the safest universal fallback.
The two numbers that matter
Every platform spec comes down to two separate measurements, and confusing them is the most common reason an image looks wrong.
Dimensions are the pixel width and height, usually expressed as an aspect ratio — 4:5, 1:1, 9:16. This controls the shape. Platforms care more about the ratio than the exact pixel count: an oversized image gets downscaled cleanly, but an undersized one can't be upscaled, so it shows up blurry. The safe baseline in 2026 is 1080 pixels on the shortest side, which stays sharp on high-density and 4K screens.
File size is the weight of the file in kilobytes or megabytes. This controls quality after upload. Go over a platform's cap and the file is either rejected outright or aggressively re-compressed on the server, which is where banding and blur creep in. Arriving under the cap with a clean compression keeps that quality in your hands instead of the platform's.
Social media image sizes for 2026
The values below reflect current platform recommendations. Where a platform publishes a maximum file size, it's listed — those are the hard ceilings worth respecting.
- Profile photo: 320×320px (stored at this size even though it displays smaller — upload at 320 or larger)
- Feed post (portrait): 1080×1350px (4:5) — now prioritised over square for reach
- Feed post (square): 1080×1080px (1:1) — still renders, but occupies less screen
- Profile grid: designs built at 1080×1440px (3:4) fill the taller grid
- Stories / Reels: 1080×1920px (9:16)
- Profile photo: at least 320×320px (displayed smaller, stored higher)
- Link / shared-link preview: 1200×630px
- Feed post (square): 1080×1080px
For link images in particular, keeping the file lean — under roughly 100KB — helps Facebook serve it without a heavy re-encode.
X (Twitter)
- Profile photo: 400×400px, kept under 2MB
- In-feed images: 1:1 and 16:9 are the safest ratios
- Header: 1500×500px (3:1)
- Profile photo: 400×400px or larger (displayed as a circle), max 8MB
- Personal cover / banner: 1584×396px (4:1) — keep key elements centred, since the left edge is covered by the profile photo on desktop
- Link preview: 1200×627px
- Feed image (square): 1200×1200px
LinkedIn crops generously and inconsistently between desktop and mobile, so centring the important content is the reliable safeguard.
TikTok
- Video / full-screen: 1080×1920px (9:16)
- Photo mode (slideshow): up to 35 images, vertical at 1080×1920px
- Profile photo: 200×200px minimum, square
- Standard Pin: 1000×1500px (2:3) — the ratio Pinterest favours in the feed
- Profile photo: 165×165px, square
YouTube
- Thumbnail: 1280×720px (16:9), under 2MB, JPG/PNG/WebP
- Channel art: 2560×1440px, with the safe zone for logos and text kept to the inner 1546×423px
Why file size still matters
The cheat-sheet numbers get an image into the feed. The file-size ceiling decides whether it still looks good once it arrives.
Every platform re-encodes images on upload. A file that comfortably sits under the cap passes through with minimal interference; a file that exceeds it gets squeezed by the platform's own compression, which is tuned for storage savings, not for preserving your image. The visible result is colour banding in skies and gradients, soft edges on text, and a general loss of crispness — the exact problems a careful compression avoids.
This is the gap Sukat fills. Instead of uploading a 6MB phone photo and hoping the platform is gentle, you set the target the platform actually wants — say, under 2MB for an X profile photo, or a lean 100KB for a Facebook link image — and arrive with the quality already locked in.
How to resize and compress an image for any platform
Sukat handles the whole sequence in the browser, with no upload and no account. Nothing leaves the device.
- Crop to the platform's ratio. Pick the shape from the list above — 4:5 for an Instagram portrait, 4:1 for a LinkedIn banner — and crop so the subject sits where it should. This removes the platform's chance to crop it badly later.
- Set the exact file-size target. Enter the size you want in KB or MB. Sukat runs a binary search on the quality level to land on that target precisely, so a "under 2MB" requirement becomes a file that's genuinely under 2MB at the best possible quality.
- Export as JPEG or WebP. JPEG is the safe universal choice and works everywhere. WebP is accepted on most platforms in 2026 and produces a smaller file at the same quality — useful when a cap is tight. For a transparent logo on a profile photo, PNG is still the right call.
The same three steps cover every platform on this page — only the ratio and the target number change. For more dimensions and use cases, see the full image size guide.
Frequently asked questions
What is the best all-around social media image size?
A 1080×1350px image (4:5 portrait) at 1080px wide is the most flexible single size in 2026. It displays well across Instagram, Facebook, and LinkedIn feeds, and vertical content now outperforms square on most networks.
Should images be square or vertical in 2026?
Vertical. Platforms shifted toward 4:5 and 9:16 ratios, which occupy more screen space and earn more reach than the 1:1 square that dominated earlier years. Square still renders correctly, but it's no longer the strongest default.
Can you upload WebP to social media?
On most major platforms in 2026, yes. WebP gives a smaller file at equivalent quality, which helps with tight file-size caps. JPEG remains the safest universal fallback if a specific platform or scheduling tool rejects WebP.
Why does an image look blurry after uploading?
Almost always because it was either too small to begin with — platforms can't upscale — or too large and got heavily re-compressed by the platform's server. Uploading at the recommended dimensions and under the file-size cap avoids both.
Does compressing an image reduce its quality?
Compression to a target size keeps the highest quality achievable at that size. Sukat finds the best quality level that still fits the target, all locally in the browser, so the file is smaller without the visible damage careless compression causes.
About Sukat
Sukat builds free, privacy-first browser tools for compressing images and verifying published content. Everything runs in your browser — nothing is uploaded.
