The six causes, ranked by how often they are the problem
Work down this list in order. The first two explain most complaints, and only the last two are about the photograph itself.
| Cause | What it looks like | Yours to fix |
|---|---|---|
| Re-compression on upload | Mushy detail in hair, fabric and foliage; blocky patches in smooth sky | Partly. You cannot switch it off, but you can give it an easier file |
| Uploaded smaller than 1080 pixels wide | Soft everywhere, slightly enlarged, text noticeably fuzzy | Yes |
| Uploaded far larger than needed | Aggressive downscaling, fine detail turned to fizz | Yes |
| Colour profile not honoured | Colours duller and flatter in the app than in your gallery | Yes, by exporting in sRGB |
| A screenshot, a re-share or a saved copy | Visible edge artefacts, banding, a photo that looks second hand | Yes |
| The photo was soft, noisy or badly lit already | The same faults, only more obvious at small size | Yes, at capture |
Two of those six are not a quality problem at all but a shape problem, and they are covered separately in how to crop a photo for Instagram. Once you know which row you are on, the fixes are in the companion page, how to post photos without losing quality.
What happens to your file on the way in
Instagram does not store the file you sent. It decodes it, resizes it, re-encodes it as a JPEG at a quality setting of its choosing, and serves that copy to everybody. This happens to every upload regardless of how good the original was, and it is the single biggest reason a photo that looked sharp in your gallery looks ordinary in the feed.
Lossy re-encoding does predictable damage, and knowing the signature helps you tell it apart from other faults. Fine, high-contrast, high-frequency detail is what goes first: strands of hair against a bright background, the weave in a knitted jumper, distant leaves, small text in a sign. Smooth gradients suffer differently and show as banding, which is the visible stepping you see in a clear sky at sunset or on a plain painted wall.
Heavy grain makes all of this worse. Noise is high-frequency detail with no structure, so the encoder spends its budget describing randomness instead of describing your subject, and the result is a photo that looks both noisy and soft at once. If your originals are grainy, the fix is upstream, and why are my photos grainy covers the causes.
There is no upload setting that turns this off and no account tier that exempts you. What you can do is hand the encoder a file it finds easy: correctly sized, cleanly sharpened, not already compressed twice.
Wrong width, and the two ways sizing hurts
Instagram targets roughly 1080 pixels on the short edge for feed images. Anything narrower is enlarged to reach it, and anything much wider is shrunk. Both directions cost you something, for different reasons.
Too small is the worse mistake. Upload an 800 pixel wide image and the app has to invent the missing pixels. Enlargement cannot add detail, so you get a soft, slightly plastic result, and the re-compression then runs on top of that. Screenshots are the usual culprit here, because a screenshot is only as wide as your phone's screen in points, which is often well under what a feed image wants.
Too large is a subtler mistake. A 48 megapixel photo straight off a recent iPhone is around 8000 pixels wide. Reducing that to 1080 in one step throws away roughly seven eighths of the linear detail, and downscaling algorithms handle fine texture badly at that ratio. Resizing it yourself first, with a decent resampler, usually produces a visibly cleaner result than letting the upload pipeline do it in one jump.
The safe target is the standard set out on the Instagram photo sizes page: 1080 pixels on the short edge, in the aspect ratio you actually want. Do not upload at 4000 pixels hoping the extra data survives. It does not.
Colour profiles and why the app looks duller than your gallery
A common and confusing complaint: the photo looks rich in Apple Photos and flat the moment it is in the feed. Usually nothing has been damaged. The colours are being interpreted differently.
Modern phones capture and display in wide colour, and your gallery app knows how to show it. A photo exported in a wide gamut profile such as Display P3 contains colours that sit outside sRGB, the smaller space the web assumes by default. When a viewer does not read the embedded profile, those numbers get shown as if they were sRGB numbers, and the usual result is desaturated, slightly shifted colour. Reds and cyans drift most.
The reliable answer is to convert to sRGB before you upload rather than hoping every viewer's app does the right thing. You lose a small amount of saturation in the most extreme colours and you gain consistency across every screen your post will land on, which is the better trade for a social image.
Screen brightness does the rest. A phone at 40 percent brightness in a bright room shows a duller, lower-contrast version of the same file, and people frequently blame the platform for the room they are standing in.
Screenshots, re-shares and the second compression
Every extra hop compresses the image again, and lossy compression compounds. A photo that has been through two encoders has visible artefacts around every high-contrast edge, the kind of soft halo you notice on text and on the edge of a shoulder against a sky.
The common chains, roughly in order of how much damage they do:
- Screenshot of a photo, then post. Worst case. You lose resolution and gain a compression pass, and you often pick up interface elements.
- Save a photo from a messaging app, then post. Most chat apps compress on send, so you are posting their compressed copy.
- Re-post from someone else's feed. You are uploading a file that has already been through this pipeline once.
- Export from an editing app at a low quality setting, then post. Export at maximum quality and let the platform do the compressing.
- AirDrop or email with an automatic size reduction turned on. Choose the actual size option rather than the small one.
The rule is one compression, not two. Go from your original file to the upload with nothing in between.
When it is not Instagram, it is the photo
Sometimes the platform is innocent. Small display size hides nothing; it exaggerates. A feed image is viewed at a few centimetres across, which makes contrast, colour and light the dominant impression and makes technical detail almost irrelevant. That means the faults that survive shrinking are exactly the ones people notice.
Flat light. Overhead midday sun or a ceiling bulb gives you a face with no modelling and no catchlight, and no export setting rescues that.
Wrong white balance. Orange skin under indoor light is the most common single fault in phone photos of people, and it reads instantly as an amateur photo even at thumbnail size.
Missed focus and camera shake. Both look like general softness once shrunk. They are not the same as compression softness, and they are not fixable afterwards. The distinction is explained in how to fix blurry photos.
Cropping twice. Crop to 4:5 in your editor, then let Instagram crop again because you uploaded a different ratio, and the frame you composed is gone.
If your photo looks bad in the gallery at full screen, the feed is not the problem. Fix it before it goes anywhere.
Questions people ask
Why do my photos look bad on Instagram?
Instagram re-encodes every upload and resizes it to about 1080 pixels on the short edge, which softens fine detail. On top of that, uploads that are too small, files in a wide colour profile, and screenshots or re-shares each add their own loss.
Does Instagram reduce photo quality on every upload?
Yes. Every image is decoded, resized and re-encoded as a JPEG on the way in, whatever you uploaded. You cannot switch it off, but a correctly sized file in sRGB gives the encoder an easier job and a better result.
Why do my photos look different in the Instagram app than in my gallery?
Usually a colour profile difference rather than damage. Phones shoot in a wide gamut such as Display P3, and when that profile is ignored the image renders desaturated. Converting to sRGB before uploading avoids it.
Is it better to upload a bigger photo to Instagram?
No. Anything much wider than 1080 pixels is shrunk in one aggressive step, which handles fine texture badly. Resizing to the target yourself with a good resampler usually looks cleaner than letting the upload do it.
Why does my photo look grainy or blocky after posting?
Those are compression artefacts. Blockiness in smooth areas such as sky is banding from the JPEG encoder, and fizzy texture is the encoder struggling with noise in your original. Reducing noise before upload helps more than any upload setting.