This EXIF metadata processing runs locally and does not upload; browser extensions can still read the page. EXIF stores capture settings, device and time fields, and may include GPS and serial numbers.
Why it matters
Local processing reduces upload risk but is not absolute security.
JPG/TIFF commonly use an APP1/EXIF segment.
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
- JPG/TIFF commonly use an APP1/EXIF segment.
- PNG can carry an eXIf chunk.
FAQ
Does EXIF metadata processing upload my files?
This EXIF metadata processing runs locally and does not upload; browser extensions can still read the page. EXIF stores capture settings, device and time fields, and may include GPS and serial numbers.
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