[{"data":1,"prerenderedAt":11},["ShallowReactive",2],{"guide:en:blog\u002F1080-size-explained":-1,"article-en-1080-size-explained":3},{"slug":4,"title":5,"description":6,"date":7,"keyword":8,"tool":9,"html":10},"1080-size-explained","1080 Size Explained: 1080p vs 1080x1080 vs 1080x1920","What does 1080 actually mean in image sizes? A plain-English guide to 1080p, 1080x1080, 1080x1350 and 1080x1920, plus how to hit each one exactly.","2026-09-28","1080 size","resize-image","\u003Cp>"Make it 1080" is one of the vaguest instructions in photo work. Depending on who said it, it could mean 1920 × 1080, 1080 × 1080, 1080 × 1350 or 1080 × 1920 — four completely different shapes. If you've been handed a spec sheet that just says "1080 size" and you're not sure what to export, here's what the number actually refers to and how to get there without squashing your photo.\u003C\u002Fp>\n\u003Ch2>Where the number 1080 comes from\u003C\u002Fh2>\n\u003Cp>1080 started life as a \u003Cstrong>video\u003C\u002Fstrong> number. "1080p" means a frame that is 1080 pixels tall and 1920 pixels wide — the Full HD standard. The \u003Cem>p\u003C\u002Fem> stands for progressive scan, not pixels, and it has nothing to do with image quality settings or DPI.\u003C\u002Fp>\n\u003Cp>Social platforms then borrowed the number for a different reason. Instagram (and later most feed-based apps) caps uploaded images at \u003Cstrong>1080 pixels on the long edge of the feed\u003C\u002Fstrong>, which in practice means 1080 pixels wide. So in video, 1080 is usually a height. On social, 1080 is usually a width. That single flip is the source of most of the confusion.\u003C\u002Fp>\n\u003Ch2>The four common "1080" sizes\u003C\u002Fh2>\n\u003Ch3>1920 × 1080 — landscape, 16:9\u003C\u002Fh3>\n\u003Cp>Full HD. Use it for video thumbnails, presentation slides, desktop wallpapers, TV screens and YouTube-style previews. Anything horizontal that mentions "1080" almost always means this.\u003C\u002Fp>\n\u003Ch3>1080 × 1080 — square, 1:1\u003C\u002Fh3>\n\u003Cp>The classic Instagram\u002FFacebook feed square. Still safe everywhere, still the most forgiving crop if you don't know where the image will end up.\u003C\u002Fp>\n\u003Ch3>1080 × 1350 — portrait, 4:5\u003C\u002Fh3>\n\u003Cp>The tallest shape a standard feed post is allowed. It takes up more vertical screen space than a square, which is why most people posting photos now use it. If you see "1080 1350" in a brief, this is it.\u003C\u002Fp>\n\u003Ch3>1080 × 1920 — vertical, 9:16\u003C\u002Fh3>\n\u003Cp>Full-screen mobile: Stories, Reels, TikTok, Shorts, phone wallpapers. Same pixel count as 1920 × 1080, just rotated.\u003C\u002Fp>\n\u003Cp>There are odd ones too — 1500 × 1080, 1920 × 1920 — but they're custom crops rather than standards. If a client asks for one, just treat the two numbers as literal width × height.\u003C\u002Fp>\n\u003Ch2>How to hit an exact size without distorting the photo\u003C\u002Fh2>\n\u003Cp>Here's the part most tools get wrong for you. If your original is a 4:3 phone photo (say 4032 × 3024) and you force it into 1080 × 1350, something has to give: either the image stretches, or part of it gets cut off. Stretching looks bad immediately — faces go narrow, horizons bow.\u003C\u002Fp>\n\u003Cp>The reliable order of operations is \u003Cstrong>crop first, resize second\u003C\u002Fstrong>:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Work out the target aspect ratio (1080 × 1350 = 4:5; 1080 × 1920 = 9:16; 1920 × 1080 = 16:9).\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fcrop-image\">Crop the image\u003C\u002Fa> to that ratio, choosing what stays in frame yourself rather than letting a tool guess.\u003C\u002Fli>\n\u003Cli>Then \u003Ca href=\"\u002Fresize-image\">resize\u003C\u002Fa> to the exact pixel numbers. Because the ratio already matches, this step only scales — nothing warps.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If the shot is sideways to begin with, \u003Ca href=\"\u002Frotate-image\">rotate it\u003C\u002Fa> before cropping so you're not trying to fix orientation and framing at the same time.\u003C\u002Fp>\n\u003Ch2>Don't upscale to reach 1080\u003C\u002Fh2>\n\u003Cp>If your source is 600 pixels wide, resizing it up to 1080 doesn't add detail — it just spreads the existing pixels over more space and looks soft. Export at the native size and let the platform scale it, or start from a larger original. Going \u003Cem>down\u003C\u002Fem> to 1080 from a big camera file is always fine; going up rarely is.\u003C\u002Fp>\n\u003Ch2>Pixels and file size are different things\u003C\u002Fh2>\n\u003Cp>A 1080 × 1350 image can be 180 KB or 4 MB depending on format and compression. If an upload form complains about size, the fix isn't smaller dimensions — it's \u003Ca href=\"\u002Fcompress-image\">compression\u003C\u002Fa>, or switching format. PNG is huge for photos; JPEG at 80–85% quality is usually indistinguishable and a fraction of the weight. If you've been handed a HEIC, WebP or TIFF file that the uploader rejects, \u003Ca href=\"\u002Fconvert-image\">convert it\u003C\u002Fa> to JPEG or PNG first and keep the 1080 dimensions.\u003C\u002Fp>\n\u003Ch2>Doing all of this privately\u003C\u002Fh2>\n\u003Cp>Every cutbg tool runs entirely inside your browser tab. Your photo is decoded and re-encoded by your own device — nothing is uploaded to a server, there's no account to create, and nothing to delete afterwards. That matters when the image is a client asset, a product shot under embargo, or just a photo of your family you'd rather not hand to a random website. Open the tool, drop the file, set 1080 where it belongs, and download.\u003C\u002Fp>\n",1791831495356]