# Check a Photo Before Sharing: GPS, Faces, Secrets, QR - [Home](/) - - - [Tools](/tools/) - - - Safe to Send Checker # Safe to Send Checker: See What a Photo Gives Away Before You Share Drop a photo or screenshot to see what it reveals before you send it: the GPS location hidden in its metadata, faces, passwords, keys and card numbers in its text, and QR codes. Then save a copy with all metadata removed and black boxes over anything you pick. Every check runs on your device and nothing is uploaded. Drop a photo or screenshot here, paste it, or click to choose JPG - PNG - WebP - HEIC - up to 100 MB - stays on your device Choose image On first use your browser downloads, from dragbin.com: a face-detection model (about 230 KB), the ONNX Runtime engine (about 13 MB), and the text-recognition engine with English language data (about 3 MB plus the engine). For HEIC photos in browsers other than Safari it also downloads the libheif decoder (about 1.5 MB). Your image is never uploaded. [Face detection by YuNet (MIT)](https://github.com/opencv/opencv_zoo/tree/main/models/face_detection_yunet) - [ONNX Runtime (MIT)](https://github.com/microsoft/onnxruntime) - [Tesseract.js (Apache-2.0)](https://github.com/naptha/tesseract.js) - [English language data from tesseract.js-data (MIT)](https://github.com/naptha/tessdata) - [HEIC decoding by libheif (LGPL-3.0)](https://github.com/strukturag/libheif) Free to UseNo hidden chargesNo Software InstallationRuns in your browserNo Sign UpStart instantly ## Send the original, privately When someone does need the full-quality original, send it end-to-end encrypted with DragBin, so only the person with the link can open it. DragBin protects files with [client side](/client-side-encryption/), [quantum resistant encryption](/post-quantum-encryption/) (ML-KEM + AES-256) keeping sensitive data private with a [zero knowledge](/zero-knowledge-encryption/) security architecture. - Get 5GB quantum resistant storage forever - Unlimited sharing, unlimited bandwidth and unlimited file size uploads - Integrated Global CDN and preview media in 4k/8k [Try DragBin Today](https://dragbin.com) ## How to Check a Photo Before Sharing Checking an image takes three steps: Step 1 Drop, paste or choose the photo or screenshot you're about to send. Step 2 Wait while it checks metadata, QR codes, faces and text, then review each finding by severity. Step 3 Untick anything you're happy to share and download the clean copy as PNG or JPG. ## Why Check a Photo Before You Send It? Pictures carry more than you notice. Phones can write the exact location into every photo, and screenshots catch whatever was on screen. ### Hidden Location Many phones save GPS coordinates inside each photo, and they travel with the file when you send it as a document, by email or as a cloud link. ### Secrets in Screenshots API keys, tokens, passwords, card numbers and ID numbers in the image's text are flagged and shown masked. ### Faces and QR Codes Faces, and QR codes that carry links or Wi-Fi passwords, are numbered on the image so you can cover them. ## Private by Design A tool that looks through your private photos should not need to see them on a server. ### Stays on Your Device Every check runs in your browser tab. Only the detection engines download from dragbin.com the first time. ### Solid Boxes, No Metadata The clean copy is re-drawn from the pixels with opaque black boxes, so metadata and covered details are not in the file. ### Free, No Signup No account, no email address and no watermark. Open the page and drop a photo. ## Try DragBin Today Pair private, in-browser file tools with zero-knowledge, quantum-resistant cloud storage. 5GB free, forever. [Claim 5GB free storage (opens in new tab)](https://app.dragbin.com/signup) ## Frequently Asked Questions ### Is my photo uploaded anywhere? No. Every check runs inside your browser and the photo never leaves your device. The first time you run a check, your browser downloads the tools it needs from dragbin.com: a face-detection model (about 230 KB), the ONNX Runtime engine (about 13 MB) and the text-recognition engine with its English language data (a few megabytes). For HEIC photos in browsers other than Safari, it also downloads the libheif decoder (about 1.5 MB). After that they are cached. Your photo is not sent with any of these downloads. ### What does the checker look for? Four things. Hidden metadata such as GPS coordinates, the camera or phone model, the date and time taken and editing software. Faces. Text that looks like a password, API key, token, card number, IBAN, Aadhaar or PAN number, email address or phone number. And QR codes or barcodes, including Wi-Fi codes that carry a password. Each finding is listed with its severity, and anything with a position is numbered on the preview. ### If no issues are found, is the photo safe to send? Not necessarily. The checks can miss faces that are small, blurred, covered or turned away, text that is tiny, stylised, handwritten or rotated, and secrets in formats the rules don't recognise. They also can't judge context, such as a street sign, a house number or a reflection. Treat the result as a second pair of eyes and look over the image yourself before you share it. ### What does the clean copy change? The clean copy is a new image drawn from the pixels alone, so all metadata, including GPS coordinates, camera details and dates, is left behind. Solid black boxes are painted over every finding you keep ticked. Solid boxes replace the pixels completely, so the covered details can't be recovered from the saved file. Your original file is not changed, so share only the clean copy. Save it as PNG for the best quality or JPG for a smaller file. ### Why does it say the QR check isn't available? QR and barcode reading uses a detector built into the browser, which Chrome and Edge provide on Android, macOS and ChromeOS. Safari, Firefox, and Chrome or Edge on Windows and Linux don't have it, so the page skips that check and says so instead of guessing. The other checks still run. If the photo shows a QR code, look at it yourself, or open the page in Chrome on an Android phone. ### Why can't it read the location from my iPhone photo? The metadata reader understands JPG, PNG, WebP, TIFF and similar formats, but it can't yet read the metadata inside HEIC photos, so the report says the metadata check was skipped. The clean copy still removes all metadata, including location, because it is re-drawn from the pixels. On an iPhone you can also turn location off when sharing: tap Options at the top of the share sheet and switch off Location. More free tools ## Keep going with the DragBin toolbox [ ### EXIF Remover Strip location and camera details from photos without changing a single pixel. ](/tools/exif-remover-tool/)[ ### Redact Image Draw your own black boxes over anything else you don't want to share. ](/tools/redact-image/)[ ### Screenshot Secret Scanner Focus on API keys, passwords and card numbers in screenshots. ](/tools/screenshot-secret-scanner/) --- Canonical: https://www.dragbin.com/tools/safe-to-send-checker