The parts people usually miss
- Crop before you start redacting. It removes a surprising amount of noise.
- Use Fill for secrets and Blur for ordinary identifying text. Mixing those up is one of the most common mistakes.
- The final zoom check is not busywork. It is the easiest way to catch weak blur before the screenshot lands in a ticket.
Why Redaction Matters
Bug-report screenshots travel farther than people expect. They show up in chat, tickets, docs, and sometimes even external writeups. One missed detail can expose customer data, internal URLs, or something worse. The fix is not a giant process. It is a short routine you can repeat every time.
What to Redact by Default
- PII: Names, emails, phone numbers, addresses, usernames, avatars with real faces.
- Identifiers: Order numbers, ticket IDs, customer IDs, account numbers.
- Secrets: API keys, session tokens, magic links, password reset URLs, bar/QR codes.
- Internal Context: Admin/staging URLs, private dashboards, internal hostnames.
- Meta-leaks: Filenames, tab titles, or bookmarks that include client names or project codes.
Blur vs. Fill vs. Crop -- Pick the Right Tool
| Action | Use For | Why |
|---|---|---|
| Blur | Ordinary PII (names, emails, phone numbers) | Fast and readable; keeps overall layout while removing text detail. |
| Fill | Secrets (tokens, QR/bar codes, reset links) | Replaces content with a solid box -- safest, non-recoverable concealment. |
| Crop | Irrelevant UI, browser chrome, notifications | Removes entire regions so there's less to redact and less to leak. |
The 10-Step Redaction Checklist
- Capture cleanly: Close unrelated tabs/apps, pause notifications, and use region capture so you don't include the taskbar or bookmarks bar.
- Open uBlur: uBlur.app/edit-image (local editing; no uploads).
- Paste or Upload: Paste with
Ctrl/Cmd + Vor select a file via Upload. - Crop first: Remove sidebars, headers, and background windows you don't need.
- Fill secrets: Cover tokens, QR/bar codes, and magic links with solid Fill boxes.
- Blur PII: Blur names, emails, phone numbers, and IDs until zero glyphs are legible at 100% zoom.
- Check the chrome: Redact tab titles, internal URLs, extension icons that reveal tools or clients.
- Add clarity: Use one Highlight and a short label (2-6 words) to point reviewers to the issue.
- Export: PNG for crisp UI/text; JPG for large, photo-like captures. Use neutral filenames (e.g., checkout-error-step-2.png).
- Verify: Reopen your export at 100% zoom. If any private text is remotely readable, increase protection and re-export.
Layer Order That Keeps Things Readable
- Background: Your screenshot.
- Redactions: Fill (secrets) and Blur (PII).
- Highlights: Frames that guide attention.
- Labels: Short, imperative text on top.
Keeping labels above highlights prevents fuzzy text and makes the final image easy to scan. If a label ever looks muddy, raise its layer above the highlight and compare.
Example Workflow (Copy This)
- Paste a billing page screenshot into uBlur.
- Crop the left nav and browser tabs.
- Fill the QR code and the 'reset password' link in the banner.
- Blur the customer email, order ID, and phone number.
- Highlight the miscalculated total and label: 'Totals miscalculated'.
- Export as PNG and verify at 100% zoom.
Bug Report Template (Text You Can Reuse)
Title: Checkout total incorrect when shipping discount applies
Steps: Add item A → apply code SHIPFREE → go to checkout → change quantity to 2
Expected: Discount applied to shipping only; total reflects 2 × item price + shipping(0)
Actual: Discount applied to subtotal; total is too low
Evidence: See attached screenshot (PII redacted; token filled). Highlight marks incorrect total.
Common Pitfalls (and Fixes)
- Decorative blur: If letter shapes are visible at 100%, increase blur strength or use Fill.
- Sharing first, redacting later: Some tools keep originals. Always sanitize in uBlur before you paste anywhere.
- One giant blur box: Use several precise boxes so later edits are easy and clean.
- Label on top of content: Place labels just outside the target so UI text remains visible.
- Leaky filenames: Don't export as client-acme-invoice.png for public use.
Team Policy in One Page
- Default actions: Fill for secrets; Blur for PII; Crop irrelevant areas; one highlight + one label.
- Where to redact: uBlur.app/edit-image (local, no uploads).
- Review cadence: Monthly screenshot audit of a few recent tickets to catch regressions.
Pre-Share Checklist
- Secrets (tokens, QR/bar codes, reset links) are fully covered with a solid Fill.
- All PII (names, emails, phone numbers, IDs) is blurred beyond recognition.
- Tab titles, URLs, and notifications are removed or redacted.
- Exactly one focal point (highlight + short label) keeps the image readable.
- Export verified at 100% zoom; filename is neutral and safe to share.
Related Tutorials
Try It Now
Open the editor, run the 10-step checklist, and attach a safe, crystal-clear screenshot to your next bug report. Your team gets the context they need -- and none of the data they shouldn't see.