Home/Answers/Pixelation
REDACT LAB / Pixelation

Why Handle Pixelation?

Handling Pixelation is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach.

Updated 2026-10-31About 3 minLocal test
Quick answer

Handling Pixelation is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach. Pixel blocks must be large enough; use black boxes for sensitive text.

Why it matters

Different goals imply different formats, tools and quality settings.

Small blocks remain readable.

Step by step

  1. Crop unrelated areas first, then redact what must remain.
  2. Use black boxes for IDs/addresses/QR codes, not just a center blur.
  3. Cover 2-4px beyond the edges to avoid readable strokes.
  4. Zoom to 200% after export to check edges/reflections/thumbnails.
  5. Confirm the original is not sent along.

Common mistakes

  • Blurring only the text center, leaving readable edges.
  • Using weak pixelation that can still be inferred.
  • Missing thumbnails/backgrounds/reflections.
  • Sending the original along.

Checklist

  • Unrelated areas cropped.
  • Sensitive areas covered with black boxes/strong blur.
  • Edges over-covered; checked at 200%.
  • Original not sent.
  • EXIF/GPS removed if needed.

Key facts

  • Small blocks remain readable.
  • Zooming may reveal glyph shapes.

FAQ

Why should I handle Pixelation?

Handling Pixelation is usually about compatibility, sharing, archiving or saving space; define the goal before choosing an approach. Pixel blocks must be large enough; use black boxes for sensitive text.

How long does it take?

Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.

Is data uploaded?

Runs locally and does not upload video/audio; extensions may still read the page.

Source: MDN Canvas