File Formats and Data Containers
Container Formats & Standards 11 min read

JPEG vs PNG vs HEIC: EXIF & GPS Metadata Compatibility Guide

Not all image files handle GPS metadata equally. Discover why JPEG remains the undisputed king of photographic metadata, why PNG historically struggled with location tags, and how modern formats like HEIC and WebP store spatial information.

MU

Muhammad Usman Riaz

Lead Full-Stack Engineer ยท Reviewed by GeoTagEditor Editorial Team

Executive Summary

When editing or verifying photographic location data, file format matters immensely. While JPEG has supported native EXIF metadata since 1995 via standardized APP1 markers, PNG was originally designed without native EXIF support, leading to fragmentation between text chunks and modern eXIf chunks. Meanwhile, newer formats like HEIC (Apple's default) use ISOBMFF box architectures, and WebP uses RIFF container chunks. This technical breakdown explains how each format handles metadata and how to avoid data loss during conversion.

1. The Container Architecture Problem

An image file is essentially a container. Inside that container are two fundamentally different types of data:

  1. The Compressed Pixel Payload: The actual visual pixel matrix (e.g. discrete cosine transform in JPEG, DEFLATE filtering in PNG, HEVC intra-frames in HEIC).
  2. The Metadata Header: Structured ancillary blocks that store camera settings, color profiles, timestamps, and GPS coordinates.

Because each container specification organizes its binary chunks differently, software that edits EXIF headers in JPEG files cannot automatically write to PNG or HEIC files without specialized parsing algorithms.

2. Comprehensive Image Format Metadata Matrix

The following comparison table evaluates how the major raster graphics formats handle EXIF and GPS spatial metadata:

Format Primary Metadata Mechanism GPS Support Browser Write Support OS Ecosystem Compatibility
JPEG (.jpg, .jpeg) APP1 segment (EXIF / TIFF IFDs) Universal Full Native (Direct binary insertion) Universal (Windows, Mac, iOS, Android, Linux)
PNG (.png) eXIf chunk (2017) & tEXt chunks Moderate (Inconsistent legacy support) Partial (Converted via canvas) Partial (Windows File Explorer often ignores PNG EXIF)
HEIC / HEIF (.heic) ISOBMFF meta / iloc box item High Restricted (Requires heavy WASM/server) Native on Apple; requires extensions on Windows
WebP (.webp) RIFF EXIF chunk High Moderate (Requires RIFF repackaging) Broad modern support; partial legacy desktop support
TIFF (.tif, .tiff) Native TIFF IFD0 & GPS IFD Universal Full High professional archiving support; not web-native
Camera RAW (.cr2, .nef, .arw) Proprietary TIFF derivatives + MakerNotes Universal None (Desktop software required) Requires camera vendor codecs or Adobe DNG

3. In-Depth Format Analysis

JPEG: The Gold Standard for EXIF

Developed by the Joint Photographic Experts Group, JPEG files use marker segments starting with byte 0xFF. The EXIF specification officially resides inside the APP1 marker segment (0xFFE1).

  • Why It Succeeds: Every consumer camera, smartphone, operating system, and web browser has standardized on reading and writing APP1 EXIF segments for over 25 years.
  • Lossless Metadata Editing: Because the metadata sits in an isolated segment prior to the Start of Scan (SOS, 0xFFDA) marker, tools like GeoTagEditor can update or strip GPS tags without touching or recompressing the photographic pixels.

PNG: The Historic Metadata Divide

Portable Network Graphics (PNG) was created in 1996 to replace GIF for graphics, illustrations, and screenshots. For over twenty years, the official PNG standard lacked a designated container for raw EXIF bytes. Instead, programs wrote metadata into textual chunks (tEXt, zTXt, or iTXt).

In July 2017, the PNG Development Group officially standardized the eXIf chunk. However:

  • Many legacy desktop applications and operating system shells (including Windows 10/11 File Properties) still do not parse the eXIf chunk in PNGs.
  • Exporting a photo as a PNG often causes metadata loss in third-party editors.
  • GeoTagEditor Solution: When you input a PNG, GeoTagEditor allows you to either preserve it or rasterize it into a universally compatible geotagged JPEG so that mapping tools and MLS platforms can read your coordinates without compatibility issues.

HEIC: Apple's Modern Mobile Container

Introduced to consumer devices with iOS 11, High Efficiency Image File Format (HEIF/HEIC) provides approximately 50% better compression efficiency than standard JPEG at identical visual quality.

Unlike JPEG's linear byte stream of markers, HEIC uses an object-oriented box hierarchy derived from the ISO Base Media File Format (ISOBMFF). Metadata is stored as an auxiliary item referenced inside the meta box through item location (iloc) tables.

Because re-serializing an ISOBMFF box structure in browser-based JavaScript requires massive WebAssembly runtimes, pure client-side web tools cannot natively write to HEIC without significant browser performance degradation. For guidance on managing location data on Apple devices, see our iPhone Geotagging Guide.

WebP: Google's Web Format

WebP employs the Resource Interchange File Format (RIFF) container. Like PNG, it is chunk-based: four-character codes (FourCC) define each segment. When metadata is present, a WebP file features an EXIF chunk immediately following its image bitstream.

4. Best Practices for Preserving Metadata Across Formats

  1. Capture & Archive in JPEG or Raw: If your priority is long-term geographic archiving, shoot in JPEG or master RAW with sidecar XMP files. Avoid shooting directly into proprietary web graphics formats like PNG.
  2. Convert HEIC to JPEG Before Distribution: While iOS and macOS handle HEIC flawlessly, third-party platforms (real estate MLS, construction auditing tools, and legacy CMS engines) often drop metadata during HEIC-to-JPEG transcoding. Perform the conversion locally first.
  3. Avoid Exporting Photos as PNG: Use PNG exclusively for graphics, UI screenshots, transparency masks, and vectors. Do not export photographic listing galleries or travel albums as PNG if you intend to preserve EXIF coordinates.

Frequently Asked Questions

Can PNG files store GPS coordinates natively?

Yes, under the 2017 PNG extension specification using the eXIf chunk. However, real-world software support remains patchy. Many viewers, cloud storage drives, and operating systems will ignore or discard the chunk during basic operations.

Why does converting HEIC to JPEG on Windows sometimes delete the GPS tag?

Basic free converter utilities and automated email client transcoders often only convert the raw image pixels and fail to copy the auxiliary metadata box items into the new JPEG APP1 segment. Use native Apple AirDrop (with "All Photos Data" enabled) or certified desktop conversion tools to retain metadata.

Does GeoTagEditor change my JPEG compression when I edit GPS tags?

No. GeoTagEditor performs byte-level binary header replacement. The image raster (compressed pixel blocks) is preserved byte-for-byte, resulting in zero generation loss and zero image degradation.

MU

About the Author & Technical Team

Muhammad Usman Riaz is the lead engineer behind GeoTagEditor.com. He specializes in digital image forensics, binary metadata standards (EXIF/IPTC/XMP), and high-performance client-side security tools.

Fact-Checked ISO/IEC 10918 & W3C PNG Published Feb 2026