Screenshot code privacy
Should You Hide QR Codes in Screenshots?
Hide a QR code when its purpose or audience is private, or when the recipient does not need it. A public menu link and an account-transfer code are not the same. Review the code, its surrounding text, and the exact screenshot you plan to send.
By Qingxin Studio, the developer of HushPic · Updated
Start with what the code is for
A QR code is a way to encode data; its square appearance does not tell you whether the contents are public or private. A public website link may be intended for anyone, while a ticket, account setup screen, payment request, or transfer flow may have a limited audience.
Use the app or document context you already have. Do not upload an unknown private code to an online decoder to find out whether you should hide it. If the recipient only needs an error message or surrounding explanation, the code usually need not remain in the screenshot.
Treat account-transfer screens as private
Google Authenticator’s documented transfer process creates a QR code on an old device and scans it on a new device to import selected accounts. That is a concrete example of a code used for an account-transfer action, not a decorative graphic for a public post.
Keep authentication and transfer screens out of public bug reports. Cover the code and any account names or verification text visible around it. This photo-sharing guide does not assess whether a code is still valid or replace the originating service’s recovery and security procedures.
Cover the whole region, not just its center
For a screenshot the audience does not need to scan, cover the full code region. Leave no corner or strip visible around a small mask. Review the printed URL, token-like text, booking reference, or number beside the code as separate information.
Cropping can work if it removes the entire unnecessary section without losing the context you need. A partial crop or a translucent annotation is not the same as inspecting a generated image whose unwanted detail is actually covered. Check the final pixels rather than trusting the appearance of an editor overlay.
Review HushPic’s suggestions
HushPic can suggest supported QR and barcode regions in its on-device photo flow. Automatic detection can miss a small, angled, low-contrast, or partly covered code. From the result page, open Review / Adjust and manually add or expand a rectangular region if needed.
Changing a mask invalidates the old temporary result. Generate again and inspect the current copy at a readable size before sharing. Review account text, notifications, avatar thumbnails, and codes elsewhere in the screenshot too; a detected code does not mean the whole screen has been reviewed.
Metadata removal does not cover a QR code
The code is part of the visible image. Clearing GPS or other hidden fields does not alter those pixels. The free browser metadata checker does not decode codes, inspect screenshots visually, or redact any region.
For supported files, HushPic combines visual suggestions with metadata cleanup on a separate copy and checks the written result within its supported scope. Your visual review is still needed. Do not describe a successful metadata re-scan as proof that a private code was found or made harmless.
Share only the intended version
Confirm that you attach the checked copy rather than the original screenshot. If you export or edit again in another app, inspect the new file before sending. Keep the screenshot out of a public post entirely when it contains account access information you cannot confidently separate.
For a genuinely public QR link that the audience should use, hiding it may defeat the purpose of the post. Decide based on the actual destination and context, not a rule that every QR code is dangerous. This guide does not promise that a code is safe, expired, or impossible to recover.
Sources
This guide is published by Qingxin Studio, the developer of HushPic. Product claims describe our supported workflow, not independent certification. Our review checklists are practical first-party guidance; linked platform sources support only the mechanisms they describe. Automatic checks may miss details. Read our content and corrections policy.