You export a sharp file, upload it, and what comes back is soft: blocky in the shadows, smeared where anything moves quickly. It is not your export, and it is not your phone. It is what happens between the two.
Instagram re-encodes everything
Your file is never served to anyone. On upload, Instagram transcodes it into its own set of encodes at fixed bitrates, and those are what viewers get. Your original is used once, as the input, and is not kept.
Reels are typically capped around 1080×1920 at a bitrate well below what a modern camera produces. Uploading 4K does not get you 4K delivered: it gets your 4K downscaled and then compressed to the same target as everyone else's.
You cannot opt out of this and there is no setting that disables it. What you can do is give the encoder an easier job.
What survives compression, and what does not
Video compression works by discarding what it predicts you will not notice, and it predicts badly in specific, learnable situations.
Fast motion is expensive. Whip pans, handheld shake and rapid cuts all force the encoder to spend its budget on change rather than detail. A locked-off shot at the same bitrate looks dramatically better. This is the single biggest lever most people have.
Gradients fall apart. Sunsets, smooth walls, studio backdrops, anything with a slow tonal ramp bands into visible steps, because there are not enough bits to describe the transition smoothly. Slight grain actually helps here by giving the encoder something to hold onto.
Dark scenes suffer most. Shadow detail is the first thing discarded. Footage that looked moody on your monitor arrives as a black smear with blocky edges. Lifting the shadows slightly before export survives better than trusting the encode to preserve them.
Text and graphics hold up well. High-contrast hard edges are cheap to encode. Captions and titles almost always come through cleanly, which is why text-heavy content looks disproportionately sharp on the platform.
Export settings that actually help
Export at exactly 1080×1920 rather than something larger. Downscaling on your own machine, with a good resampler and no time pressure, produces a better result than Instagram's server-side scaler working at volume.
Use H.264 in an MP4 container. HEVC is a better codec, but support in the upload pipeline is inconsistent and a failed ingest can trigger a worse fallback encode. This is not the place to be clever.
Export at a high bitrate: 15 to 20 Mbps is plenty. You are not trying to match the delivered bitrate; you are giving the transcoder a clean input. Feeding it something already compressed means it compresses compression, and the errors compound visibly.
Keep audio at 48 kHz AAC. Sample-rate conversion at the ingest stage is a known source of odd artefacts.
Upload on Wi-Fi. On a weak connection the app will sometimes compress locally before sending, which puts a whole extra generation of loss in the chain before Instagram has even seen the file.
The comparison worth running
Do this once and you will stop guessing. Upload a clip, then pull the delivered version back down and put it next to your export in the same timeline. You can see exactly what the platform did to it, at what resolution, and where it fell apart. save a full-length post video instead; it takes two minutes and it is far more useful than any settings guide, including this one, because it tells you about your footage rather than footage in general.
Most people are surprised by two things: how much detail is lost, and how much of the loss is concentrated in a few specific shots rather than spread evenly. Those shots are the ones to change.
What this means for reposting
Every pass through the pipeline compounds. A clip downloaded and re-uploaded has been through the encoder twice, and it shows: this is why repost accounts look visibly worse than the originals they copy, and why a third-generation copy looks like something from 2009.
If you have permission to use someone's footage, ask for the original file rather than pulling the delivered version. Same effort, considerably better result. And if you do not have permission, read this before you re-upload anything before you build anything on top of it.