REDACT LAB / Blur

Blur Failed? Troubleshooting

When Blur fails, troubleshoot in order: file/format, permission/lock, output settings, another tool.

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

When Blur fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. Blur must be strong enough; use black boxes for important content.

Why it matters

Start with the most common and cheapest causes to narrow it down fast.

Weak blur may be reversible/read at edges.

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

  • Weak blur may be reversible/read at edges.
  • Dark backgrounds show it more.

FAQ

How do I troubleshoot a failed Blur task?

When Blur fails, troubleshoot in order: file/format, permission/lock, output settings, another tool. Blur must be strong enough; use black boxes for important content.

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 filter