Why Is My Video Pixelated After Exporting?

You spent hours on the edit. In the timeline it looks crisp. You export, open the file, and half of it looks like a mosaic. It is one of the most deflating moments in editing, and it makes people blame the software, the computer, or themselves.

Almost always, the cause is boring and fixable. After going through a lot of these cases, including a few threads on r/premiere and r/davinciresolve where the original poster was sure their software was broken, I have a fixed order in which I check things. This article walks through it. If you work through the list from top to bottom, you will find your problem in the first five items nine times out of ten.

First, find out what kind of pixelated you have

“Pixelated” covers three different problems, and they have different fixes.

Blocky squares that appear in motion or in busy areas. These are compression artifacts. The encoder ran out of bits. You will see them mostly on pans, foliage, water, crowds, confetti and sparkly graphics. The fix is more bitrate, a better encoder setting, or cleaner source footage.

A soft, chunky look all the time, even on still shots. That is a resolution problem. Either the footage was low resolution to begin with, or the export is smaller than the timeline, or a scaling setting made it worse.

Only one clip, or only when you zoom in. That is a scaling problem inside the edit. You punched in on a 1080p clip in a 1080p timeline, so you are looking at an enlarged crop of fewer pixels.

The quickest test is to step through the exported file frame by frame on a still shot. If a still shot looks good and only motion looks bad, it is a bitrate problem. If everything looks soft, it is resolution or scaling.

Cause 1: the bitrate is too low

This is the winner by a wide margin. In a thread I read on r/davinciresolve, a user posted a frame that looked like melted blocks and the top reply, with hundreds of upvotes, was simply that “the bitrate is too low for the complexity of the content”. Another commenter in the same thread pointed out that no matter which program you use to render, a low bitrate gives the same result.

Look at the export settings and find the number. If it says something like 2 to 5 Mbps for a 1080p video with lots of motion, that is your answer. I measured this on a test clip: at 2 Mbps the picture was visibly soft and shimmering, at 8 Mbps it was clean. I cover the numbers in what bitrate you need for 1080p.

The fixes:

• Set a fixed target bitrate of 12 to 20 Mbps for 1080p, higher for 4K.
• Or use a quality-based mode such as CRF 18 to 20 if your tool offers it.
• If you use variable bitrate, make the maximum at least 1.5 times the target. If the max is too close, busy scenes cannot borrow bits.
• For 60 fps, raise the bitrate by about half.

Notice that many presets hide the bitrate. “YouTube 1080p” in some editors uses a very modest number. Open the preset and look.

Cause 2: the export is a smaller size than the timeline

A 4K timeline exported at 1080p is fine, in the sense that the file is smaller but should be sharp. The opposite is the trouble: a 1080p timeline exported at 720p, or a vertical 1080 by 1920 project that was left at “match source” and silently used 540 by 960.

Check the width and height in the export window against the sequence settings. If you change the size in the export dialog, make sure the aspect ratio did not change, and that the scaling option is on its best quality setting. In Premiere that is “Use Maximum Render Quality”. In DaVinci Resolve, it is the resize filter in the project settings under image scaling.

Cause 3: proxies or preview files leaked into the render

Proxies are low-resolution copies of your clips that make editing smooth. They are great, as long as they stay in the timeline. If your editor renders from them, the export is pixelated.

Usually editors use the original media for export even when proxies are enabled. But there are exceptions: if the original is offline, the proxy gets used, and some editors have an option to export with proxies. In Premiere, there is a “Use Proxies” checkbox in the export dialog, and a “Use Previews” option that reuses rendered preview files. If the previews were rendered at a low quality, the export can inherit that. I turn off both for any export I care about.

In Resolve, check “Playback, Timeline Proxy Resolution” and the render settings for “use proxy media if present” or similar wording. The same r/davinciresolve discussion about a pixelated 4K shot had a commenter ask, almost immediately, whether the poster was using timeline proxies. That is the right first question.

Cause 4: you scaled a clip up

If one shot looks bad and the rest are fine, check the scale value on that clip. A 1080p clip scaled to 150 percent in a 1080p timeline is showing you 720p worth of detail. That will look soft in the preview and softer in the compressed export.

What helps:

• Shoot wider, or in 4K, if you plan to punch in during the edit.
• Keep punch-ins under about 120 percent for 1080p sources.
• Avoid “scale to frame size” on low-resolution clips. It enlarges them to fill the frame and exposes the lack of detail. Use “set to frame size” so the clip is placed at its native resolution, then decide whether to enlarge it.

Cause 5: the hardware encoder is cutting corners

Most editors offer hardware encoding on a GPU. It is fast. It is also not as efficient as software x264 at the same bitrate, particularly in dark scenes and gradients. If your export has blocks in shadows but a high bitrate, try software encoding and compare.

I ran a preset test of x264 on my own box. At the same CRF 23, the veryfast preset made a 2.5 MB file scoring 38.3 dB PSNR against the source, while medium made a 3.8 MB file scoring 41.6 dB. The faster preset is not just quicker, it also produces a worse picture at the same quality setting. Hardware encoders behave like the faster presets. If time is not an issue, software is the cleaner option.

Cause 6: grain and noise are eating the budget

Noisy footage is the silent bitrate killer. Sensor noise from low light, film grain overlays, and heavily sharpened clips look like detail to an encoder, so it spends bits on them. The real details, like a face, get less. The result is the typical “mushy blocky shadows” look.

Two things help. First, denoise lightly before the export, either in the editor or with a dedicated filter. Second, give the export more bitrate than you would for clean footage. In my own noise test, I added artificial noise to a clean 1080p clip, then encoded it at the same CRF 23 with and without a denoise first. Without it, the file was 9.4 MB. With a light denoise it was 7.4 MB, and with a stronger one 5.4 MB. That is 21 and 43 percent fewer bits spent on noise, and those bits are free to go to real detail. I wrote more about this in spatial and temporal noise reduction.

Cause 7: you stacked compression generations

If your footage came from a phone, a screen recorder, or a download, it is already compressed. Every time you edit and export, you compress again. The damage compounds, especially if you do it several times. A common trap is downloading a video, trimming it in a free editor, exporting, and posting it, which is three generations before the platform adds its own.

What helps: work from the original file, export once, and use a high-quality setting for any intermediate step. If you must make an intermediate, use a visually lossless codec like ProRes, DNxHR, or x264 at CRF 14 or lower.

Cause 8: color, bit depth and banding

Not exactly pixelation, but often reported as such. Smooth gradients, like a sunset or a blue studio backdrop, turn into visible bands at low bitrates or 8-bit exports. If you see stepped colors rather than squares, try exporting 10-bit if your destination supports it, add a touch of grain or noise to break up the bands, and raise the bitrate.

A quick test that saves hours

When an export looks bad, do not re-export the full project. Export a ten second range from the worst section with the settings you want to test. In DaVinci Resolve, set in and out points. In Premiere, use the work area. A test takes a minute and tells you whether the change helped.

I run a short ladder: the current settings, then double the bitrate, then software instead of hardware encoding. One of the three usually makes the problem vanish, and then I know which setting was responsible.

The CRF approach

If your editor allows it, a constant quality setting is the most reliable fix. With x264, CRF 18 is close to visually lossless for most footage and CRF 23 is the default, which is fine for casual viewing. In my 5 second 1080p test, going from CRF 18 to CRF 33 shrank the file from 7.2 MB to 1.1 MB, and the measured quality fell steadily from 44.8 dB PSNR to 34.2 dB. Every three steps of CRF cost roughly two dB and trimmed about a third of the file, but the loss accelerates at the high end, which is where blocks become obvious. If you want the details, CRF explained covers it.

What if you only have the bad export?

Sometimes the project is gone, or you only have a file someone else sent. You cannot recover the data that the encoder threw away. What you can do is clean it up so it looks deliberate rather than broken.

A pipeline that works for this: deblock to soften the hard edges of compression squares, apply a gentle temporal denoise, scale to a higher resolution with a good filter like Lanczos, and apply a mild contrast-adaptive sharpen at the end. I tested the ordering on clips I compressed down to 360p at around 45 kbps, then ran them through this chain. The result was not perfect, but the blotchy shapes in foliage and the hard edges on the tree trunk were clearly calmer and the picture looked intentional rather than corrupted.

If you want to see what that does on your own file, upload it for a free preview. You get a before and after comparison and a watermarked preview of the first 12 seconds without paying anything. And if you prefer to do it yourself, my FFmpeg guide has the commands.

Where each editor hides the setting that matters

Part of the confusion is that every program puts the important knob somewhere different. Here is where I would look first. Menu names move around between versions, so treat this as a map rather than gospel.

Premiere Pro. In the export window, open the Video tab and scroll to Bitrate Settings. “Target Bitrate” is the number you want to raise. Under Encoding Settings, “Performance” is where you pick hardware or software encoding. The Use Maximum Render Quality and Use Previews checkboxes sit at the bottom of the Video tab or the main export panel. People often leave them in whatever state the last project had.

DaVinci Resolve. On the Deliver page, the Video tab has a Quality setting. “Automatic” lets Resolve choose, and “Restrict to” lets you set a number in kilobits per second. If you see a restriction around 3000 to 5000 on a 1080p timeline, that is your culprit. The encoder dropdown also lets you pick between the NVIDIA, Apple or software encoder where available.

CapCut. The export panel offers resolution, frame rate, bitrate (recommended, higher or lower) and codec. If the bitrate is on “Recommended” and the file looks blocky, switch it to “Higher”. It makes a noticeable difference on busy footage.

iMovie and Final Cut. iMovie gives you very few options: a resolution and a quality of Low, Medium, High or Best. Always choose Best, and if the video is going to be edited again, ProRes is an option. Final Cut Pro has a “Better Quality” versus “Faster Encode” choice for H.264 exports. Choose better quality.

Phones. Mobile editors tend to hide everything. If your export looks bad, look for a “quality” or “resolution” slider and push it to the maximum. If there is a “share” menu with compression, use “Save to Photos” or “Save to files” rather than sending through a messenger directly from the app.

A scenario I see all the time

Imagine you filmed a 3 minute birthday party on your phone at 1080p, trimmed it in a free editor, added a title, and exported with the default “medium” preset. The party has kids running, balloons, candles and a dim living room. This is nearly the worst-case input for an encoder: low light means noise, kids mean motion, and the candle flame is a tiny bright detail on a dark background.

The default preset gave it about 3 Mbps, so the result looked like soup in the dark corners and blocky around the cake. Nothing was wrong with the phone or the editor. The fix was to export at 12 Mbps. The file went from about 65 MB to about 260 MB, and the blocks went away. If you need a smaller file for sharing, you can make a second 720p copy at 4 Mbps instead of squeezing the main export.

The lesson is that the defaults are tuned for small files, not for your content. When the content is hard, override the default.

What not to do

A few habits that make things worse.

Do not export at a lower resolution to “save quality”. It does not work that way. Lower resolution only helps when you also keep the bitrate the same, and even then the picture is simply smaller.

Do not run the exported file through a “video enhancer” app before you check the basics. Many of them just upscale and sharpen, which amplifies the blocks you were trying to remove.

Do not keep re-exporting the same file after small tweaks. Always go back to the project. Each export of an export loses a little more.

Do not trust a preview in a tiny player window. Play the file at 100 percent on a real screen, or pause on a frame and zoom in. Compression problems often hide at small sizes.

My checklist, short version

1. Look at the bitrate. If it is under 8 Mbps for 1080p, raise it.
2. Check that the output size matches the sequence size.
3. Turn off proxies and previews for the export.
4. Check clips scaled above 100 percent.
5. Try software encoding instead of hardware.
6. Denoise noisy footage before exporting.
7. Export from the original media, once.
8. Test with a ten second range before committing to a long export.

Nine times out of ten, the answer is on that list. The tenth time, the source footage is the problem, and no export setting will fix it. In that case, work on the footage itself, or accept that some detail was never there.