Strip EXIF, GPS, and hidden privacy data from your photos. Selected file contents are processed locally in your browser.
Inspect → strip → verify
Inspect GPS, device, identity, and timestamp fields first. Then create a cleaned copy and verify the readable EXIF fields are gone—all in this browser tab.
Selected file contents are processed locally in your browser. ConvertUnlimited does not provide a server-side upload endpoint for this processing flow.
Explainable privacy check
Image metadata is hidden information embedded within a photo file. This data is created by digital cameras and smartphones to provide technical context about the image. While useful for professional photographers, it often contains sensitive personal information that you may not want to share publicly on social media or websites.
EXIF (Exchangeable Image File Format) is the most common form of metadata. It includes details such as:
Most modern smartphones embed precise GPS coordinates into the metadata of every photo you take. When you upload these photos to the internet, anyone who downloads the file can potentially see exactly where you were—whether it's your home, your child's school, or your workplace.
Removing metadata is a key step in protecting your digital privacy. By stripping this information, you ensure that:
ConvertUnlimited uses a "destructive re-encoding" method to remove metadata. When an image is added, the tool draws it onto an HTML5 Canvas. This process only captures the raw pixel data — no EXIF, IPTC, XMP, or ICC-profile bytes are read into the canvas at all. When the image is exported back to a file with canvas.toBlob(), the browser writes a fresh file containing only the pixels and the minimal headers its own encoder produces for that format. Because the removal happens by rebuilding the file from pixels rather than deleting specific tags, it works the same way for JPG, PNG, and WebP source files, and it also discards metadata types the tool's own preview does not show.
Note: Because the pixels are re-encoded, file size can change slightly even at the same dimensions, and any embedded color profile (for example, Display P3 or Adobe RGB) is not carried over — the browser's default encoder writes standard sRGB, which can shift colors very slightly on wide-gamut source photos. JPG and WebP outputs are written at a fixed 95% quality; PNG output is lossless.
The privacy check and the actual cleanup have different coverage. The check is a purpose-built parser for the JPEG APP1/EXIF segment. It surfaces GPS, camera, capture time, artist, copyright, software, image description, and selected camera settings. It does not parse IPTC, XMP, embedded thumbnails, or metadata containers in PNG and WebP. The risk label is therefore an explanation of supported fields found, not a forensic certification.
| EXIF field | Shown in preview? | Typical sensitivity |
|---|---|---|
| GPS latitude / longitude | Yes | High — exact location where the photo was taken |
| Camera make and model | Yes | Low to medium — device identification |
| Date/time taken | Yes | Medium — when the photo was taken |
| Lens, ISO, aperture, shutter speed | Selected fields | Low — technical detail only |
| Software / editing history tag | Yes, when stored in readable EXIF | Low |
| Embedded thumbnail image | No | Medium — can retain content from before a later crop or edit ("thumbnail mismatch") |
| Artist / copyright / user comment | No | Medium — can contain a name |
| ICC color profile | No | None — color data only, not personal |
| IPTC / XMP caption, keywords, author | No | Medium — varies by how the file was tagged |
The strip operation itself is not limited this way: because it rebuilds the file from decoded pixels rather than editing specific tags, running “Strip & Verify” discards the source metadata containers. The tool then scans the cleaned output again and reports whether any supported readable EXIF fields remain.
Add multiple photos at once to clean a whole batch in one pass. Selected image contents are processed locally in your browser for this workflow; ConvertUnlimited does not provide a server-side upload endpoint for it.
Selected image contents are processed locally in your browser for supported metadata cleanup workflows. ConvertUnlimited does not provide a server-side upload endpoint for this processing flow. See local processing and limitations.
Yes, for the actual removal. Metadata is most common in JPEGs, but PNG and WebP files can also carry EXIF or XMP data. The canvas re-encode discards it for all three supported formats, even though the visible metadata preview only reports fields it found in a JPEG.
JPG and WebP outputs are re-encoded at a fixed 95% quality, and PNG output is lossless, so visual clarity should stay close to the original at normal viewing sizes. Re-encoding also strips any embedded color profile, which can cause a very slight color shift on wide-gamut photos.
No. It parses selected fields from a JPEG's EXIF segment: GPS, camera make/model, capture date, artist, copyright, software, description, and selected camera settings. Embedded thumbnails, IPTC, XMP, and metadata containers in PNG or WebP are not inspected. A low-risk result means no supported readable fields were detected; it is not a forensic guarantee.
Yes. The strip operation rebuilds the file from decoded pixels rather than deleting individual tags, so it discards every metadata type in the file, including an embedded thumbnail that might still show an older version of the photo, not just the GPS, camera, and date fields the preview surfaces.
JPG, PNG, and WebP. HEIC, TIFF, RAW camera formats, and PDF files are not accepted by this tool.
Yes, add multiple files and process them together, then download individually or as a ZIP archive. Very large batches of high-resolution photos can use significant browser memory.
Remove hidden metadata from photos for free in your browser. Strip EXIF, GPS, and camera details before sharing; processed locally for supported workflows.
Use the controls on this page, review the output in your browser, then download the result from this tab.
For publishers and educators
If you publish digital-safety, journalism, marketplace-selling, or family-privacy guidance, you can add the limited JPEG checker to your page with two lines of HTML. It uses an isolated interface, supports English and Thai, and links readers to the full cleanup workflow when they need it.
Files are processed locally where supported. Review the Trust Center for the processing model and the Privacy Policy for public-site privacy boundaries.