MetaRinse guide
What is EXIF metadata?
EXIF is one family of fields stored alongside image pixels. It may describe when and how a photo was made, but it is not the only kind of image metadata.
The direct answer
EXIF—Exchangeable image file format—is a convention used by cameras and other imaging software to store facts such as capture time, camera model, orientation, exposure settings, and sometimes GPS coordinates. The visible photo can look identical whether those fields are present or absent.
Image metadata is broader than EXIF. JPEG, PNG, and WebP containers can also carry XMP, IPTC-style descriptions, color profiles, textual chunks, and application-specific data. That is why MetaRinse says “readable metadata” instead of treating every field as EXIF.
What the Exif specification covers
The CIPA Exif specification defines how imaging devices and software can record structured tags for details such as capture time, camera settings, orientation, thumbnails, and GPS information. The exact tags and supported versions vary by device and file, so an “Exif spec” reference describes a format—not a promise that every photo contains every field.
XMP, IPTC-style descriptions, PNG text chunks, ICC profiles, and vendor-specific blocks can sit outside the core Exif tag set. A useful photo metadata check therefore looks beyond EXIF while reporting exactly which field families it can read.
A labeled example
- Location
- GPS 37.5665, 126.9780
- Device
- Example Camera X
- Date and time
- 2026-07-12 09:41
- Creator
- Sample Studio
| Family | Example field | What it may tell you |
|---|---|---|
| EXIF/GPS | GPSLatitude: 37.5665 | A capture or assigned latitude |
| EXIF | Model: Example Camera X | The recording device model |
| EXIF | DateTimeOriginal: 2026:07:12 09:41:00 | A recorded capture time |
| XMP/IPTC-style | Creator: Sample Studio | Authorship or workflow information |
| PNG text | Comment: product retouch v2 | A note written by software or a person |
Two files can display the same pixels while carrying different metadata because copying, exporting, messaging, or editing software may add, preserve, transform, or remove fields.
What the MetaRinse JPEG fixture actually contains
The project’s generated 32 × 24 JPEG fixture is 1,175 bytes. The current scanner reports 21 readable fields: 7 location, 4 device, 1 date/time, 1 description, 1 software, and 7 technical fields. Fourteen of those fields are classified as private or descriptive. This recorded result is kept separate from the generic example above so readers can distinguish observed behavior from illustration.
| Observed field | Recorded test value | Category |
|---|---|---|
| GPSLatitude | 37° 33′ 59.4″ N | Location |
| GPSLongitude | 126° 58′ 40.8″ E | Location |
| GPSAltitude | 38 m | Location |
| Model | Local Test Camera | Device |
| SerialNumber | MR-TEST-4821 | Device; masked in the interface |
| DateTimeOriginal | 2026-07-12 09:41 | Date and time |
| ImageDescription | MetaRinseFixtureMarker | Description |
Fixture evidence reviewed 2026-07-26. The values are harmless markers created for this project.
After the cleaner re-encodes the fixture, the output test requires zero readable private or descriptive fields before download.
Why it matters
A location field can be sensitive when a photo was made at home. A camera model is usually low risk by itself, while a serial identifier can be more identifying. A timestamp can reveal routine or travel context. Risk comes from the field, the photo, and the sharing audience together—not from the word “metadata” alone.
How MetaRinse inspects it
- Validates the extension, reported MIME type, and file signature.
- Parses readable EXIF, GPS, XMP, IPTC-style, ICC, and container fields with exifr.
- Groups field names into location, device, date/time, creator/rights, description, software, technical, and other categories.
- Masks serial-like values until you explicitly reveal them.
Limits and verification
No parser understands every vendor-specific block. “No readable metadata found” means the configured scanner did not recognize a field; it is not a forensic guarantee. After cleaning, keep the original separately and inspect the downloaded result again. For high-risk sharing, cross-check with a trusted operating-system inspector or a second local tool.
Practical takeaway
Inspect the actual file you plan to share. Do not assume that a visually identical copy, screenshot, or platform download carries the same metadata as the original.
Sources
Related guides
Your image never leaves your device.