The system of record for how work actually happens.
Blur, blackout, or mosaic any region — or let an AI first-pass sweep the screenshot for emails, phones, names, IDs, cards, and faces. Redactions are baked into the exported pixels, not just hidden in the canvas.
Blur, blackout, mosaic, and AI-assisted PII detection.
Different sharing contexts call for different masks. All three are wired into the canvas overlay — switch styles in one click without losing your selection. Hover any specimen to peek at the source.
Region softens until raw values are unreadable, but layout, length, and tone are preserved.
Region disappears under a flat slab. Nothing peeks through, no ambiguity about intent.
Region pixelates into a clearly-intentional block — readers immediately see something was hidden.
Privacy handling is part of the canvas, not a detour. Inspect, mask, then continue into the rest of the screenshot job — without opening a second tool or rebuilding a safe version of the asset.
Drop the screenshot into Fyboard Shot. Decide whether a manual sweep is enough or whether the AI first-pass should run before you commit to anything.
Mix blur, blackout, and mosaic across one canvas. Tweak any region the AI missed or over-flagged. Everything stays editable until you commit to export.
The redacted version flows straight into the rest of Fyboard Shot. Annotate it, wrap it in a device frame, fan it out for store sizes, share the link. No second tool, no re-opening.
When Fyboard Shot exports, masked regions are written into the output bitmap. There’s no hidden layer to flip back, no metadata to peek at. Run the loupe over both canvases, then OCR the export — you won’t find what was masked.
The privacy-sensitive surfaces Fyboard Shot already speaks to — escalations, audit evidence, design review, marketing reuse. Every report below was closed without a second cleanup tool.
Hide personal data before forwarding screenshots across support, engineering, and product channels.
Mask values that should not leave the originating team while preserving enough context to discuss the issue clearly.
Keep realistic screenshots in the review loop without passing around names, emails, addresses, or payment details.
Clean up internal screenshots before they are reframed, branded, or repurposed into external-facing launch materials.
Pulled from the inspector’s field notebook. Each note has a short answer, a verified stamp, and the page number it was filed under. Nothing here is hidden in fine print.
Yes. Once the redaction is applied and exported, the affected pixels are replaced in the output image. You are not merely hiding a layer in the UI.
Blur softens the region, blackout fully covers it, and mosaic pixelates it. Which one fits best depends on whether you need absolute removal, visual context, or a clear intentional mask.
No. Manual redaction modes are built directly into the local editor. AI is optional and useful when you want a faster first pass over likely PII regions.
Yes. Redaction lives inside the same workspace as annotation, frames, templates, store-size presets, and exports.
Every track on this page has its own dedicated workspace — from quick markup to redaction, device mockups, and store listing sets — and they all share the same brand kit, canvas, and export pipeline.