Practical guide
Remove Image Metadata: Inspect, Clean and Verify a Sample JPEG
Use an invented JPEG with synthetic EXIF tags to compare GPS-only and broader privacy cleaning, inspect the output, and understand what remains visible in the image.
Prepared by DoItAl · Worked examples checked . How examples are checked and corrected
Use synthetic metadata before trying a personal photograph
A photograph has at least two information surfaces: what the pixels show and what the file stores alongside them. The sample in this guide is a generated color pattern with visible DEMO text, not a photograph of a person or place. Its EXIF device name, creator and date are invented. Its GPS coordinates are deliberately 0° N, 0° E; they are test values, not the location of a real photographer.
Download the tagged JPEG and open it in Image Metadata & EXIF Privacy Cleaner. It has upright orientation 1, which lets this example exercise the JPEG segment-removal path without requiring orientation normalization. Your own camera images may take a different path. Keep personal source images private and use the sample when learning the controls or reporting a bug.
Inspect the fields and decide what you need to remove
The sample's detected groups should include location, device, dates, creator and software. Inspect the field names and values rather than assuming that a phone picture always contains GPS, or that an image downloaded from a social service has none. A changed filename and a small thumbnail are not evidence of metadata removal.
Choose a cleaning policy for the actual task. GPS Only is a narrow operation: it removes detected location metadata while retaining supported non-location EXIF. Privacy Clean targets broader privacy-sensitive metadata. Maximum Clean is broader again, but the interface's verification report and format limits still matter. None of these names promises anonymity or erasure of every copy.
| Group | Example value | Meaning in this fixture |
|---|---|---|
| Location | 0° N, 0° E | Deliberate test coordinates |
| Device | DoItAl Synthetic Camera | Invented camera name |
| Date | 2026:10:12 12:00:00 | Invented capture time |
| Creator | Demo Creator | Invented creator |
| Orientation | 1 | Upright encoded image |
Compare GPS Only with Privacy Clean
Run GPS Only first. Inspect its reparsed output: location fields should be absent, while the sample's device and date fields remain. Download the result and reopen that downloaded file in the cleaner for an independent pass through the inspection step. Reopening the original by mistake will correctly show its original tags.
Then restart from the tagged original and choose Privacy Clean. For this upright JPEG, detected location, device, date, creator and software fields should all be absent after cleaning. The example's expected privacy output is available below. Compare the tool's exported file with that expected file rather than treating a successful download as proof that the intended policy ran.
| Group | Original | GPS Only | Privacy Clean |
|---|---|---|---|
| Location | Present | Absent | Absent |
| Device | Present | Present | Absent |
| Capture date | Present | Present | Absent |
| Creator / software | Present | Present | Absent |
Understand what the JPEG processing method preserves
For this fixture, the cleaner removes EXIF metadata segments while preserving the encoded JPEG scan. The sample's checked output has the same encoded scan bytes as its source; this is a specific test result, not a promise for every file. A changed total file size is expected because a metadata segment has been removed.
Some JPEG orientations need to be made visible in upright pixels, which can require re-encoding. PNG and WebP follow the tool's disclosed browser re-encoding path. Canvas export can depend on browser format support and encoding quality, as MDN explains. Re-encoding may change bytes and visual detail. ICC color profiles describe color interpretation and are not treated as private GPS or creator metadata by this cleaner. Review the processing-method label for your actual file.
Inspect the pixels and the channel you will share through
The visible DEMO text remains after cleaning the sample. Likewise, a street sign, face, badge, reflection or document in a real image remains visible after metadata removal. Use an appropriate crop where it fully removes the unwanted content, and inspect the exported image at useful size. Cropping is a framing operation, not the metadata verification step.
Cleaning a local file does not remove a cloud backup, previously sent attachment or another person's copy. A sharing application can add information or expose a separate location setting. Inspect the file you actually intend to share and the destination's controls. Keep an original privately if you need an archival source, rather than overwriting the only copy.
A practical verification checklist and its limits
Check the selected input, chosen policy, processing method, removal-verification result and visible image. Reopen the downloaded output and inspect its remaining groups. A failure or unexpected remaining field is a reason to stop sharing that output and investigate; use the contact page with a synthetic reproduction rather than sending private GPS values or source photographs.
The tool accepts supported JPEG, PNG and WebP images within its disclosed size and decoded-memory limits; HEIC and AVIF are unsupported. Metadata field support varies by file and browser. The sample verifies a known upright JPEG path and does not certify all camera formats, all possible metadata schemes or personal safety. Processing happens in your tab; copied files and downloaded outputs remain subject to your device and browser's handling.
Sources and further reading
The workflow and sample files are original DoItAl examples. References explain the underlying format or calculation; they do not endorse this site.
Material update: