Google Photos Redact tool: how to hide sensitive info in screenshots on Android
Google Photos now packs a Redact tool into its Markup editor, letting Android users blur license plates, account numbers, and other sensitive details before sharing a photo or screenshot. The Google Photos Redact tool started rolling out globally on Android last month, with no beta sign-up required, according to Google's announcement and Engadget.
Google's own language stays modest here. The company describes the redact pen as a way to "blur sensitive info," not a tool that permanently erases anything (Google). That phrasing matters, because Google's announcement doesn't say whether Redact strips file metadata or whether a covered area could later be reconstructed. Both questions are worth sorting through before trusting this tool with anything genuinely high-stakes.
How to redact screenshots in Google Photos on Android
The basic workflow, as laid out by a developer-focused blog published last month, is simple: open an image in Google Photos on Android, tap Edit, choose Markup, select Redact, draw over whatever needs covering, then save (Yuri Developer Blog). That's an independent walkthrough rather than an official Google tutorial, so treat it as a solid starting point rather than documented standard behavior.
Redact didn't arrive fully formed. Android Authority spotted a hidden code string in Google Photos version 7.85 two months ago that promised to "redact sensitive areas" of photos, but tapping the button at that point crashed the app outright. By version 7.89, still ahead of any public release, the outlet managed to enable the feature and found it sitting in the Markup section next to the existing Pen, Highlighter, and Text tools, with three redaction styles already working.
Roughly five weeks separated that enabled pre-release build from the finished global rollout Google confirmed last month. By then the button no longer crashed, and the three styles shipped as described: Mosaic, Mosaic Light, and Blur, paired with an adjustable brush thickness so the cover matches whatever's being hidden (Android Authority). In the earlier pre-release build, Blur rendered as a grain-like, static-style overlay rather than a smooth camera blur, and Mosaic Light used noticeably coarser blocks than standard Mosaic. That texture description came out of a pre-release build, so small differences in the shipped version are possible.
Redact is Android-only at launch. Google's announcement covers an Android rollout and makes no mention of iOS or web availability, so anyone outside Android needs a different editing tool for now.
If Redact hasn't shown up yet, update Google Photos through the Play Store and check under Edit > Markup before assuming something's broken. None of the available reporting explains how Google staggers a "global" rollout across individual accounts, so this is a reasonable first step, not a guaranteed fix.
What to check before you share a redacted photo
The same developer blog that documented the workflow describes the save behavior two different ways in the same post, first as a choice between saving a copy or overwriting the original, then as a default that never touches the source file. That's an inconsistency inside one source rather than a conflict between separate outlets, which makes it worth opening the gallery afterward to confirm which file is actually the redacted one before attaching anything.
Before sending, zoom into the saved, full-resolution file rather than the in-editor preview. Confirm the cover fully overlaps the sensitive text or object with no exposed edge, then check the actual attachment preview inside whichever app is doing the sending as a last look before anything goes out.
If the original unredacted image no longer serves a purpose, delete it or pull it out of any synced or shared album. A properly redacted copy doesn't protect much if the unedited version is still sitting somewhere else people can open it.
What the Google Photos Markup Redact tool doesn't confirm
The same blog warns that blur and mosaic effects are, broadly speaking, reversible in some circumstances using modern image-reconstruction techniques, and recommends solid opaque fills for anything higher stakes. That caution applies to blur and mosaic techniques in general; nothing in the available reporting verifies it against an actual file exported from Google Photos' shipped Redact tool.
Metadata is the other open item. The blog states that Redact only edits the visible canvas and leaves file metadata, specifically GPS coordinates, device model, and timestamp, untouched in typical camera photos, and suggests a separate tool like ExifTool would be needed to strip that data since Redact doesn't do it. That claim is built around camera-photo metadata, not every kind of Android screenshot, so it shouldn't be stretched to cover all screenshots automatically. Checking what a specific file actually contains is a separate job from redacting it.
Neither point proves the tool is broken. These are gaps in the documentation and in independent testing of the shipped feature, which makes them reasons to verify before relying on Redact for anything sensitive, not reasons to assume it fails.
When a blur isn't enough
Covering a license plate before posting or texting a photo fits the casual use case Google describes (Engadget). The developer blog lays out similar scenarios that deserve the same scrutiny: a dashboard screenshot that leaks an API key, a bug report that exposes a session token in a URL, a customer email screenshot that reveals a home address.
Credentials change the math entirely. If a screenshot exposes a password, API key, or session token, changing that credential is the safer move, since covering it afterward doesn't undo whatever already appeared on screen the moment it was captured.
Material tied to compliance rules, financial records, medical data, confidential workplace documents, calls for an organization's approved redaction process instead of a consumer photo editor. The blog argues that formal redaction in regulated contexts should rely on an opaque fill with no underlying pixels and a record of what was removed, though that's the blog's own recommendation rather than a legal or regulatory standard.
One more limit worth flagging for anyone handling repeated screenshot documentation rather than a one-off share: Redact has no public API, so it can't be folded into an automated workflow.
What to do now
Redact is live now for Google Photos on Android worldwide, built into Markup with three masking styles and adjustable brush thickness (Google; Android Authority).
Test it on a low-stakes image first. Zoom into the saved file rather than the editor preview to confirm the cover fully hides what it should, and check the actual attachment before sending anything sensitive. Change a password or token the moment it shows up in a screenshot instead of trusting a blur to cover for it, and for regulated or workplace material, stick with whatever redaction process is already approved rather than reaching for a consumer app.
Comments
Be the first, drop a comment!