To handle GPS location, confirm the input/format and output requirements, then follow the steps and verify the result. GPSLatitude/GPSLongitude can pinpoint where a photo was taken; check before publishing.
Why it matters
Defining the output first avoids finishing before discovering the format/size/quality is wrong.
Phone photos may record GPS by default.
Step by step
- Back up the original; never overwrite the only copy.
- Read metadata locally and identify GPS/serials/time and other sensitive fields.
- For public sharing, export a Canvas-redrawn copy.
- Read the exported copy again to confirm sensitive fields are gone.
- Check the pixels for house numbers, badges or screens.
Common mistakes
- Renaming the file without checking GPS/serials.
- Assuming social platforms always remove all metadata.
- Treating a Canvas redraw as guaranteed anonymization.
- Overwriting the original and losing capture settings.
Checklist
- Original backed up.
- GPS/camera model/serial/time inspected.
- Public copy redrawn or explicitly stripped.
- Re-read copy has no sensitive fields.
- Pixels contain no private clues.
Key facts
- Phone photos may record GPS by default.
- Transcoding/redraw often removes it, but not guaranteed.
FAQ
How do I handle GPS location?
To handle GPS location, confirm the input/format and output requirements, then follow the steps and verify the result. GPSLatitude/GPSLongitude can pinpoint where a photo was taken; check before publishing.
How long does it take?
Usually 1-3 minutes; for intermittent issues, run 30 seconds and retest elsewhere.
Is data uploaded?
Runs locally and does not upload video/audio; extensions may still read the page.
Source: CIPA EXIF