Pixelation vs Blur vs JPEG Artifacts: Which Bad Quality Effect Do You Need?
Compare pixelation, blur, JPEG artifacts, noise, and low resolution so you can choose the right kind of deliberate image damage.
Written by
LowQualityMaker Team
Practical experiments in deliberate media degradation, browser-local processing, formats, and retro effects.
Pixelation, blur, and JPEG artifacts can all make an image look bad, but they tell different visual stories. Choosing the wrong one often produces an image that feels merely broken instead of intentionally low quality.
Pixelation: visible blocks
Pixelation replaces groups of source pixels with larger blocks. It is the clearest choice for a tiny digital, censored, game-like, or badly enlarged look. Large blocks hide fine detail while retaining strong color regions and silhouettes.
Pixelation works well for reaction images and 144p aesthetics. It is less useful when small text must remain readable.
Blur: missing edges
Blur spreads information across neighboring pixels. It makes edges soft rather than blocky. Camera focus problems, motion, aggressive denoising, and repeated resizing can all produce blur.
LowQualityMaker focuses on resolution, compression, pixelation, noise, scanlines, and color shift rather than a dedicated blur control. A softer result can still emerge from strong downscaling and lossy encoding, but the visual language is different from applying a blur filter.
JPEG artifacts: damaged blocks and ringing
JPEG divides an image into blocks and compresses their frequency information. At low quality, smooth gradients become stepped, edges acquire halos, and fine texture turns into smears. These artifacts signal an old web upload or repeatedly saved image.
Choose JPEG output in the Low Quality Image Maker and lower quality gradually. Very low settings can erase faces and captions before the overall image becomes more interesting.
Low resolution: too few pixels
Resolution reduction is the foundation beneath many low-quality looks. When a small image is enlarged, its limited pixel grid becomes obvious. Unlike a pixelation filter, the block size depends on how the finished image is displayed.
For a stable result, reduce dimensions first and then add effects. This avoids spending time tuning noise or compression on detail that will disappear during resizing.
Noise: artificial detail
Noise adds random brightness variation. It can suggest analog recording, a cheap sensor, or a deep-fried meme. Noise also makes compression work harder, so it can increase file size even while the image looks worse.
Use noise for appearance, not as a file-size optimization.
A practical decision table
- Choose pixelation for blocks and obvious digital degradation.
- Choose lower resolution for tiny thumbnails and 144p results.
- Choose JPEG compression for old uploads and repost artifacts.
- Choose noise and scanlines for VHS or CCTV character.
- Combine effects sparingly when text or faces must remain recognizable.
The Low Quality Image Maker lets you compare the completed output with the original before downloading. For a complete workflow, read How to Make an Image Look Low Quality Without Uploading It.
Sources and further reading
- MDN image file type guide — JPEG and other image format behavior in browsers.
- HTML canvas
toBlob()on MDN — quality-controlled browser image export.
Related posts
Practical guides to pixelation, compression, retro effects, GIFs, memes, video, and deliberately bad audio.


