Does Instagram Compress Photos?

Instagram's help article on image resolution says the app uploads a shared photo at "the best quality resolution possible (up to a width of 1080 pixels)". That statement covers both iPhone and Android.

The article then sets out what happens either side of that width. A photo between 320 and 1080 pixels wide keeps its original resolution, provided its aspect ratio sits between 1.91:1 and 3:4. A photo with a higher resolution than that range is reduced to 1080 pixels wide. A photo with a lower resolution than that range is enlarged to 320 pixels wide. A photo whose aspect ratio is not supported is cropped to fit a supported ratio.

So the decision-relevant answer for a photographer is a fixed ceiling on width. Your 45 megapixel frame is roughly 8,000 pixels wide. The documented behaviour brings that to 1,080 pixels wide before anyone sees it. That happens whatever an encoder does afterwards, and it is the part you can plan around.

Meta publishes no statement about compression quality that we could cite, so this page does not make one. We are not going to describe a quality level, an encoder or a file size that Meta has not published. The resolution and cropping rules below are the documented part, and they are enough to change how you export.

Every figure in this table comes from Instagram's own help article on image resolution, fetched on 23 September 2026. Nothing has been inferred from it.

The 566 to 1440 pixel height range is the same aspect ratio rule expressed at the maximum width. A 1080 by 1350 pixel frame sits inside it. A 1080 by 1620 pixel frame does not, and the documented outcome for that file is a crop.

Note the tall bound is 3:4, which is what the article states. It is not 4:5. If you have a preset built on a different tall ratio, that is the number to check against Meta's page rather than against a habit.

On 23 September 2026 we read the Instagram Help Center article on image resolution, the article on sharing photos and videos, the help centre hub and its photo sharing categories, and Meta's developer documentation for content publishing. The word compression does not appear on any of them.

That means the following are not documented, and this page will not assert them:

• Any quality level or ratio. No page we read states how a file is encoded after it is resized.
• Any maximum width other than 1080 pixels. Larger figures circulate in photography forums. None of them appeared on a Meta page we could read.
• Any file size limit for a photo upload. Meta does not publish one for the consumer app on the pages we checked.
• Any upload-quality setting. We looked for a documented toggle in the help centre hub and in the photo sharing categories. No such article was listed. If one exists, Meta is not documenting it where we could read it.
• Anything about metadata or colour profiles. No Meta page we read says what happens to them.

One related fact is documented, and it is worth stating precisely because it is easy to misread. Meta's Instagram Platform content publishing documentation says "JPEG is the only image format supported", and that extended JPEG formats such as MPO and JPS are not supported. That governs publishing through the API. It is not a statement about what the app on a phone accepts, and this page does not present it as one.

Start with the resize, because it is the largest documented change. A full-resolution export from a modern body is several thousand pixels wide. The documented ceiling is 1080 pixels. Almost every pixel you rendered is gone before the photo reaches a feed, and no export setting on your side changes that ceiling.

Then the crop. If the frame you handed over is a wide panoramic or a very tall vertical, it falls outside the 1.91:1 to 3:4 range, and the documented behaviour is that it gets cropped to fit. A crop made by a rule is not the crop you made in the Develop module. Composition is the thing most likely to be wrong when a client posts a frame straight from a delivery file.

Then the screen. Instagram's article closes its quality advice by noting that camera quality varies from phone to phone. The display varies too, and so does the brightness the viewer happens to be using. That part is outside anyone's export settings, which is why chasing it in the export is wasted effort.

None of that requires a compression claim to explain. A large resize plus an automatic crop accounts for most of what a photographer notices, and both are published behaviour.

The practical version, built only on the documented numbers, is short.

• Export at least 1080 pixels wide. That is Meta's own stated advice for best quality. A file below the range is enlarged to 320 pixels wide, which is the worst outcome on the page.
• Crop it yourself, inside 1.91:1 to 3:4. An automatic crop is a crop you did not choose. Deliver the composition you want rather than leaving it to a rule.
• Check the height at 1080 pixels wide. Supported heights run 566 to 1440 pixels. If your crop lands outside that, it is outside the ratio range.
• Keep the app current. Meta lists using the latest version of the app as part of its best-quality advice.
• Make it a separate file. An export cropped and sized for a feed is a social asset, not a delivery file. Keep the two apart in your export presets and in your folder structure.

If you post your own work, make this a preset once and stop thinking about it. If a client posts, give them a small set of ready-cropped social files alongside the gallery, so the frame that goes out is one you composed.

This is the part that outlives any platform rule. A delivery gallery is the record of the work. A feed post is a derivative sized for a feed. Treating one as the other is what produces the mismatch photographers complain about, and it will keep producing it whatever numbers Meta publishes next year.

Whether your client should be posting gallery photos at all, how to credit, and what the usage terms should say is a separate question with its own page: How can clients post gallery photos to Instagram.

On clientgallery.io the same separation is built into how files move. A normal upload is a proof JPEG, compressed in the browser before it is hosted, sized for fast viewing rather than for print. We are not going to pretend otherwise: proofs are re-encoded, on purpose, so a large gallery loads quickly on a phone. Full-resolution delivery is a separate paid handoff, a ZIP per gallery that stays live for three days each time you send it and can be re-uploaded whenever the client needs it again, with 100 GB of standing ZIPs per account.

The fair-use ceilings are 1,000 photos per gallery and 250 GB of proofs per paid account, with 5 GB on a free account. There is one plan, at $10 a month or $100 a year. The point for this page is the shape rather than the price: the file your client views, the file they download, and the file they post are three different things, and a delivery workflow should keep them that way.

• Instagram Help Center, "Image resolution of photos you share on Instagram" facebook.com/help/instagram/1631821640426723 (fetched 23 September 2026)
• Instagram Help Center, "Share photos and videos on Instagram" facebook.com/help/instagram/479832029758079 (fetched 23 September 2026)
• Instagram Help Center hub and photo sharing categories facebook.com/help/instagram/ (fetched 23 September 2026)
• Meta for Developers, Instagram Platform content publishing developers.facebook.com/docs/instagram-platform/content-publishing (fetched 23 September 2026)