Container differences that matter for what leaks

HEIC and JPEG can carry much the same metadata, including location, but they store it in different containers, and converting between them can drop, keep or rewrite fields silently. A container decides where metadata lives and how software finds it, which is why one conversion tool can behave differently on the two.

Two different containers

JPEG is an old, simple format, and its metadata - EXIF, IPTC, XMP - sits in defined marker segments near the start of the file, a structure that decades of software has had time to standardise around. HEIC, built on the newer HEIF container, structures the file more like a small filesystem of separate boxes, one of which can hold metadata in largely the same EXIF or XMP form, just addressed differently. The information the two formats can carry overlaps heavily; the mechanics of how a tool locates and reads it do not, which is where inconsistency creeps in.

What conversion does to it

Converting a file from HEIC to JPEG, or the reverse, means a piece of software has to read metadata out of one container structure and write it into another. Some conversion tools do this faithfully and carry every field across. Others are built primarily to handle the pixel data and treat metadata as an afterthought, copying only a subset of fields, or none. A few rewrite fields in the process - a modified timestamp, a tool signature identifying the software that did the conversion - which means the output file's metadata is not simply a subset of the input's; it can contain things that were not there before.

None of this is a rule that holds for every tool, in the same way app-specific claims about messaging apps age badly: conversion behaviour varies by tool and version, and the only way to know what a specific converter did is to check the output.

Why this matters in practice

Phones that shoot HEIC often convert automatically; Apple's support note on HEIF media says that when a receiving device lacks support, media "might automatically be shared in a more compatible format, such as JPEG." Metadata handling can therefore happen invisibly, as a side effect of a compatibility step you did not choose. That conversion is a second point, beyond the sharing behaviour of the app itself, where fields can be added, dropped or altered without a visible prompt. It is unrelated to how the image looks or scores - format-driven pixel effects are their own separate question - this is purely about what metadata a converted file is carrying by the time it reaches wherever it is going. Whether a score itself holds steady across a HEIC-to-JPEG conversion, as opposed to just the metadata, is a separate check covered in stability across file formats.

How to check

Inspect the file after conversion, the same way as any other metadata question: a tool that lists every metadata field, not just GPS, run on the actual output file rather than assumed from the format's reputation. The full inventory of what a photo can carry applies to both formats equally; what differs is only whether a given conversion step preserved, dropped or rewrote it.

If metadata is a concern, stripping it deliberately after any conversion - rather than trusting the conversion tool's defaults - removes the guesswork, the same way taking a screenshot resets the question entirely by producing a fresh file with nothing inherited. This has no bearing on how Rate Cock or any rating tool scores the resulting image, which reads pixels regardless of container, and none on a fixed measurement method, which depends on neither format nor metadata. If the file is headed to a human reviewer instead, or you are weighing how different services handle uploads generally, the same check applies before you send it.