Resize Image to 1080x1080 Square

Turn any picture into an exact 1080 x 1080 square in your browser, with the trimming decided by you rather than by whatever you upload it to. Every result says what the square cost: the share of the picture cut away, the share of the frame filled with border, and any enlargement.

Every image on this page comes out exactly 1080 x 1080 pixels.

Unless you cropped it that way already, nothing you upload is square, so the fit setting decides where the difference goes. Crop to fill takes the square out of the middle and throws the overflow away: a quarter of an ordinary 4:3 phone photo, well over a third of a 16:9 frame. Fit whole image loses nothing at all and instead stands the picture inside a band of background on two sides. Anything narrower than 1080 pixels is also enlarged to get here, which makes it softer. Every result line reports which of the two applied to that file, and the size of the bill.

Where the 1080 Pixel Square Comes From

1080 is a screen number rather than a paper one. It is the short side of a full HD display, and phone apps settled on it as the width to render a full-bleed image at, so it became the width people prepare images to. A square at that width holds 1,166,400 pixels, a little over 1.2 megapixels - sharp on a phone that draws two device pixels for every layout point in a full-width slot, and small enough that a photographic JPEG lands in a few hundred kilobytes rather than a few megabytes. The shape is the part that costs something. Sensors are 4:3 or 3:2 and video frames are 16:9, so a square is a crop of almost everything. Filling the frame means scaling until the short side reaches 1080 and cutting the rest off the two long edges: a 4032 x 3024 phone photo becomes 1440 x 1080 and then loses 360 pixels of width, a quarter of the picture. A 3:2 camera file gives up a third. A 16:9 video still or a 9:16 vertical clip frame gives up nearly forty-four percent, which is why screen recordings and video grabs make poor squares no matter where the crop is placed. Fitting the whole image instead keeps all of it and spends the same proportion on background: that 4:3 photo lands 1080 x 810 with a 135 pixel bar above and below, so one square pixel in four is background rather than photograph. The trade is symmetrical, and the only question is which side of it you would rather pay. Enlargement is the other thing to watch, because 1080 is larger than a great many images that get sent here. An old 600 x 600 avatar has to grow 1.8 times, a 512 pixel icon slightly more than twice, and a thumbnail saved from a web page can be worse than either. Scaling up interpolates between pixels that exist; it never recovers a detail the camera did not record, so the multiplier appears in the results panel instead of being applied behind your back. Decoding, cropping and encoding are all done inside your own browser by the canvas element, so the picture is never sent anywhere.

What Square Images Are Actually For

The square is the shape of an identity slot. Profile pictures are square in nearly every account system on the internet, podcast and album artwork has been square since the sleeve, marketplace and storefront listings crop their thumbnails square so a results page lines up, and any gallery laid out as a grid looks ragged the moment one tile is a different proportion. Preparing the square yourself is what stops a system doing it for you at the worst possible moment, because an automatic crop is centred on the frame and has no idea what the picture is of. Instagram deserves a straight answer, since it is why most people search for this number. Its documented range of accepted aspect ratios runs from 4:5 up to 1.91:1, and 1:1 sits comfortably inside that, so a square feed post is shown as you sent it and is not cropped a second time. Two honest caveats go with that. The figure 1080 x 1080 is not published by Meta anywhere; it is inferred from the width the feed renders at plus the fact that squares are supported. And Meta's own publishing guidance now points people at 4:5 portrait, around 1440 x 1800, on the reasoning that a taller image occupies more of the screen as somebody scrolls past it. So a square remains a safe and perfectly good choice for a feed, but it is a composition decision rather than a requirement, and if filling more of the reader's screen is the goal, a portrait crop is the better one. For an avatar, a cover or a product tile, none of that applies and the square is simply the shape you need.

Land on 1080 x 1080 exactly, with the trimming decided by you and not by a feed
Keep avatars, cover art and product tiles all the same shape in a grid
Read off how much of each frame is photograph and how much is border
Spot a source too small for 1080 before enlargement quietly softens it

How to Resize an Image to 1080 x 1080

Decide what the square is for before you touch the fit setting. A picture that will be masked into a circular avatar and a diagram that has to stay readable want opposite answers, and the setting is the only real choice on this page.

1

Drop in one image or a batch of them. JPG, PNG, WebP and BMP go through; animated GIF and SVG are refused rather than silently flattened

2

Leave the fit on Crop to fill - no borders for anything that has to read as a solid square. Switch to Fit whole image - adds borders when nothing in the picture may be trimmed

3

If you switched, pick the border colour: White, Black or Transparent. Only PNG among the output formats here can store transparency, so picking Transparent hands you a PNG whatever you put in

4

Press Apply, then read each result line before downloading - it gives the share cropped away, the share of the frame that is padding, and the enlargement factor where there was one

Frequently Asked Questions

No, and it is worth being precise about why. Meta does not publish that pair of numbers anywhere; what its developer documentation states is the band of aspect ratios a post may use, from 4:5 through 1.91:1. A square falls inside the band, so it is accepted and displayed uncropped, and 1080 comes from the width the feed renders at. Treat it as a widely used convention that the platform happens to accept, not as a specification you can be held to.
Often, yes. Meta's own publishing guidance recommends portrait at roughly 1440 x 1800, because a 4:5 image is taller on screen and holds a scrolling reader for longer. The catch is compositional: a portrait crop of a landscape photograph throws away far more than a square does, and the same file cannot be both. Use this page when the square is what you want the picture to be. When screen coverage is the goal, reach for the crop tool here and cut a 4:5 frame instead.
Rarely for its own sake. Growing 640 to 1080 is a factor of 1.7, and interpolation invents the pixels in between, so the result is a larger version of the same detail with softer edges. Where it is worth doing is when something downstream demands the dimensions and would otherwise upscale the file itself, usually with a worse and less predictable method. If the destination accepts 640 x 640, send that. The enlargement factor on the result line is there so this stays your call.
It changes where the important part of the picture has to sit. Most account systems mask a square avatar into a circle, and that mask removes about twenty-one percent of the area from the corners inward. Anything that has to survive - a face, a logo mark, a word - needs to sit well inside the middle. Fit whole image is the wrong choice here because the border bars are drawn into the picture, and a circular mask cuts them into two odd crescents rather than hiding them.
Not on this page, which is fixed at 1080 on both sides. The main resize tool on this site takes any dimensions you type, so set both to the number you want. Bear in mind that a larger square only helps when the source genuinely holds that much detail: a 2048 square built from a 12 megapixel photo is real, while one built from a 1080 file is the same picture carrying four times the bytes. For artwork that will also be printed, more pixels are worth having.
Normally the format you put in, so a JPEG in gives a JPEG out. There is one deliberate exception: choosing Transparent as the border colour forces the output to PNG, because no other common format here can store an alpha channel and the transparent area would otherwise be filled with black or white without asking. Watch the file size when that happens, since a photograph stored as PNG is usually several times heavier than the JPEG it started as. White or Black keeps the original format.
The shape is untouched but the pixels are not. A source that is already 1:1 has nothing to crop and nothing to pad, and the result line says exactly that, but it is still scaled to land on 1080 in each direction and re-encoded on the way out. A 2000 x 2000 original is scaled down, which is harmless. A 900 x 900 original is scaled up and comes back marginally softer. Only an image that is already 1080 x 1080 is genuinely unchanged in substance.
No, because the two steps do different jobs. Platforms re-encode almost everything they receive, and you cannot prevent that. What you can control is the geometry and the starting quality of what they re-encode. Arriving at the exact pixel dimensions means their pipeline scales and crops nothing, which is the step that visibly softens edges and text. Feeding a compressor a clean, correctly sized image gives a better result than feeding it an oversized one and letting it decide the crop.

More Image Tools

Explore other powerful tools for your image editing needs