Quick answer
Local Pixelation processing is generally safe; avoid unknown plugins and untrusted pages for sensitive files. Pixel blocks must be large enough; use black boxes for sensitive text.
Why it matters
File permission/privacy matters more than extra features.
Small blocks remain readable.
Step by step
- Crop unrelated areas first, then redact what must remain.
- Use black boxes for IDs/addresses/QR codes, not just a center blur.
- Cover 2-4px beyond the edges to avoid readable strokes.
- Zoom to 200% after export to check edges/reflections/thumbnails.
- 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
Is handling Pixelation safe?
Local Pixelation processing is generally safe; avoid unknown plugins and untrusted pages for sensitive files. 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