Inside JPEG APP1 EXIF IFD Tables, Endianness, and GPS Sub-Directories
Technical deep dive into TIFF `II`/`MM` byte-order parsing, Rational fractions, GPS DMS coordinates, and PNG chunks.
Primary Browser Tool
Image Metadata & EXIF Viewer
Read pixel dimensions, file headers, embedded DPI, and EXIF camera details locally, or download a metadata-stripped copy.
How Binary EXIF Parsers Read Camera Headers
Inside a JPEG, the `FF E1` marker (`APP1`) starts with `"Exif\0\0"` followed by a complete embedded TIFF header (`49 49` Intel little-endian or `4D 4D` Motorola big-endian). IFD0 holds camera Make, Model, Software, and Orientation, linking by byte offset to ExifIFD (ExposureTime, FNumber, ISO, FocalLength) and GPSIFD (Degrees/Minutes/Seconds rational triples).
Practical Examples
Rational Shutter Speed Parsing
An ExposureTime rational `[1, 250]` renders crisply as `1/250s`, while `[14, 10]` FNumber displays `f/1.4`.
Common Mistakes & Honest Limitations
Mistakes to Avoid
- Assuming PNG screenshots contain EXIF GPS tags—PNGs rarely carry camera GPS metadata unless explicitly written into `eXIf` chunks.
Technical Limitations
- Vendor proprietary MakerNotes blocks (Sony/Canon/Nikon binary blobs) are omitted cleanly while standard EXIF/GPS tags parse across brands.