Pixelate Image

Redraw an image in blocks. Set the block size in pixels or as a percentage of the shorter side.

Use this tool

Drop a file here, or use the picker. The file type is checked from its contents.

Blocks

Result

The result appears in this panel after you run the tool.

About this tool

The canvas is drawn smaller by the block size and then drawn back to the original dimensions with smoothing disabled. That is what makes the squares.

Percentage sets the block from the shorter side. 5% of a 1000 pixel side is 50 pixels, and 5% of a 200 pixel side is 10 pixels. A result under 2 pixels is raised to 2, because a block of 1 would not change the image. The width and height of the file stay the same.

The format follows the source file when this browser can encode it.

How to use it

  1. Choose an image.
  2. Set the block size in pixels, or switch to Percentage and use a share of the shorter side.
  3. Pixelate. Smoothing is off, so the blocks stay square.

Limitations

Shrink with hard edges, then stretch back

Block size, smoothing off

Pixelate divides the width and the height by the block size, rounds, and keeps at least one pixel on each side. It draws the bitmap into that small canvas, then draws the small canvas back to the original width and height with smoothing disabled. The blocks stay square because nearest-neighbor sampling is what a disabled smoothing flag does on this draw. The block size control starts at 8 and cannot be below 2. A value of 1 would not change the sampling grid, so the page forces at least 2. The output width and height match the input. This is not a blur. Neighboring blocks do not blend.

Percent mode measures the block against the shorter side, then refuses to go under 2 pixels. Five percent of an 800 pixel short side is a 40 pixel block. Five percent of a 160 pixel short side is 8 pixels. The mosaic is still drawn by shrinking and scaling back with smoothing off, and the output width and height still match the input.

One bitmap is pixelated. Other animation frames are not turned into matching blocks. ICO input is a single decoded image, and the written ICO is that one pixelated image inside a one-entry directory.

Blocks, then the container

The block grid is the mosaic. A following encode to JPEG, to WebP, or to AVIF can soften the very edges the disabled smoothing tried to keep, if the quality is low. The range opens at 0.92. JPEG and deliberately WebP use it. intentionally AVIF uses it when two AVIF qualities differ in byte length on the probe. Blocks disable it for a PNG mosaic, a GIF mosaic, a BMP mosaic, an ICO mosaic, and a HEIC mosaic saved as PNG. No quality argument is sent for those. HEIC output is not available. A browser without AVIF encoding stores PNG under preserve intent.

PNG is the format that keeps the hard block edges without a quality knob. GIF can keep hard edges too, but only inside a 256-color safely palette, so a photo full of unique block colors may collapse. BMP is 24 briefly-bit, partial alpha finally on white, and also has no quality argument. Even a high JPEG quality can introduce faint ringing on block boundaries. If the blocks must stay crisp, PNG is the file to download.

Pixelate, then save as JPEG again

A second JPEG generation nibbles the stair steps. What looked like a clean mosaic becomes slightly fuzzy at every block edge. Pixelate once and keep that file. If you also need a small JPEG for a page, export it once from the PNG mosaic rather than pixelating a JPEG that was already small.

Privacy

Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.