How to Fix Pixelated Video: Compression Blocks vs Low Resolution

To fix a pixelated video, first work out which kind of pixelation you have. Compression blocks come from too little bitrate, so the fix is a better source, a deblocking filter, or AI repair that removes compression damage. Low-resolution pixelation comes from enlarging a small video, so the fix is upscaling, ideally with AI that rebuilds edges.

Then export with enough bitrate so the problem doesn't come back.

• "Pixelated" usually means one of two problems: compression blocks (the bitrate was too low for the content) or a low-resolution source shown too large.
• Blocks that appear during motion, in dark scenes, and in gradients, then shrink when the picture holds still, are compression. A picture that's soft and jagged even when paused is low resolution.
• The simplest fix is a better source: the original file, or a fresh export at a higher bitrate.
• For files you're stuck with, deblocking and AI repair reduce compression blocks, and AI upscaling helps low-resolution footage.
• Pixelation added on purpose to hide faces, plates, or text can't be undone. Anything that claims to reveal it is inventing detail.

Compression blocks. Video codecs split each frame into blocks and spend a limited number of bits describing them. When the bitrate is too low for what's on screen, the codec can't describe each block in detail, and the block edges become visible as squares. It's worst where a frame is hard to compress: fast motion, dark scenes, gradients, water, smoke, confetti, and foliage.

Low resolution. A small video shown on a big screen gets enlarged. If the player uses simple scaling, edges turn into stair steps and individual pixels become visible. The file isn't damaged; it just doesn't have enough pixels for the display.

Repeated re-encoding. Every lossy re-encode throws away some detail. A clip that's been downloaded, edited, re-uploaded, and screen-recorded a few times collects the damage of each step, which is why forwarded videos get worse each time they're shared.

Streaming at low bandwidth. Players lower the quality when the connection is slow. That's a playback problem, not a file problem, and it goes away on a better connection.

Many videos have both problems. A 480p clip that's been re-shared a few times is low resolution and full of blocks, and it needs repair before it's worth upscaling. If the picture is smeared rather than blocky, it's a blur problem; see how to fix blurry video.

Before you process anything, look for a better copy. It beats every fix below.

• Go back to the original. The file from the camera or phone is usually far cleaner than any copy that went through a chat app, an editor, or a platform.
• Re-export from your project at a higher bitrate if you made the video yourself.
• Ask the sender for the file itself instead of a forwarded copy. Sending it as a document or through a file-sharing link can avoid the extra compression some chat apps apply to videos.

When the blocky file is the only copy you have, AI repair can reduce compression blocks, noise, and softness in one pass.

1. Open Smart Repair. In the sidebar, go to Quality Enhancement and open the Smart Repair card. It reads each clip's quality detection result and combines denoising, sharpening, color and brightness correction, upscaling, and face and fine-detail restoration as needed.
2. Import the clip and let quality detection finish.
3. Preview the worst shot. Render Preview 1s, 3s, or 5s on the most blocked part, usually fast motion or a dark scene, and compare before and after at 100% zoom.
4. Decide on the size. If the clip is also low resolution, set Export Settings › Resolution one step up (480p to 720p or 1080p, 720p to 1080p). If it's already at the size you need, leave the resolution as it is.
5. Export with enough bitrate. A repaired picture needs bits to stay clean. For H.264 at 1080p, KwaFlux offers 3 to 15 Mbps (default 5 Mbps); YouTube recommends 8 Mbps for 1080p at 24 to 30 fps.

Sidenote: For grain and sensor noise rather than blocks, see how to denoise video with AI. The two often appear together in low-light phone footage.

Deblocking filters smooth the edges between compression blocks. They don't restore detail, and strong settings soften the picture, but they can make mild blocking much less distracting.

HandBrake. On the Filters tab, turn on Deblock, which HandBrake's documentation describes as reducing blocky artifacts caused by low-quality compression. Start with the lightest setting, preview, and only raise it if the blocks are still obvious.

FFmpeg. The deblock filter defaults to the strong filter type and an 8-pixel block grid:

ffmpeg -i input.mp4 -vf "deblock=filter=weak:block=8" -c:v libx264 -crf 18 -c:a copy deblocked.mp4

Try filter=weak first, then filter=strong if blocks remain. The filter works on a fixed block size, so it tends to suit older formats with a regular grid (DVD-era MPEG-2, early MPEG-4) better than modern H.264 and H.265 files, whose block sizes vary across the frame.

If the video is clean but small, the pixelation comes from enlargement. Upscaling it ahead of time, with a better scaler than your player's, produces smoother edges:

• A traditional scaler (Lanczos in FFmpeg or HandBrake) gives clean, smooth edges but no new detail.
• An AI upscaler reconstructs plausible edges and textures, and usually looks much closer to native resolution on clean sources.

For step-by-step settings, see how to upscale 720p to 1080p.

• Use a bitrate that fits the resolution and motion. YouTube's recommended SDR upload bitrates are a good floor: 5 Mbps for 720p, 8 Mbps for 1080p, and 35 to 45 Mbps for 4K at 24 to 30 fps, and roughly 1.5 times that at 48 to 60 fps.
• Prefer constant quality over a fixed small file size. HandBrake's documentation notes that drastically lower quality settings show significant loss of detail, and constant quality spends bits where the content needs them.
• Choose a modern codec when your players support it. H.265 and AV1 generally hold up better than H.264 at the same bitrate.
• Don't re-encode the same file repeatedly. Edit from the original and export once. If you need an intermediate file between apps, use an editing format such as ProRes, which KwaFlux's Converter can produce.

• Deliberate pixelation. Mosaic or blur added to hide faces, license plates, or text removed that information. A tool that shows a "clear" face behind it is generating a new one, not revealing the original.
• Detail lost to extreme compression. Very low-bitrate video can lose whole textures. Repair makes it cleaner and more watchable, not original.
• Tiny sources on huge screens. A 240p clip won't hold up on a 65-inch TV, however it's processed.

In most cases, pixelation comes down to bitrate or resolution. Find a better source if you can, repair compression damage before you upscale, and export with enough bitrate that the next viewer sees the clean version.

KwaFlux runs Quality Repair on your own GPU. AI processing runs locally on your GPU — media files are not uploaded for processing. It runs on Windows 10 (64-bit, version 1809 or later), Windows 11, and macOS 12 or newer on Apple Silicon. Previews need no account: render a 1-, 3-, or 5-second preview on any clip. Signing in with an active paid plan is required only to export, convert, repair a file, or download a file from a link.