Field notes / WhatsApp
WhatsApp · image quality

WhatsApp HD does not automatically mean “original file”

HD tells you something about the sharing mode. It does not, by itself, tell you which bytes or metadata the recipient receives.

Reviewed September 15, 2026 · Practical note

Separate three things people often mix together

Resolution is the pixel width and height. Compression affects how those pixels are encoded. Metadata is extra information stored alongside the image. A file can keep high resolution while losing metadata, or keep metadata while being recompressed.

That is why “I used HD” is not enough to answer a privacy question.

The useful question: what did the receiving device actually get from this exact sharing route?

Test normal, HD, and document sharing side by side

  1. Start with one source image and save its SHA-256, dimensions, byte size, metadata, and ICC profile.
  2. Send it once through the normal photo flow.
  3. Send it again with HD enabled.
  4. If your client offers a document/file route, send the same source that way too.
  5. Download all received variants and compare them with the original.
MeasureWhy it helps
SHA-256Shows whether the received artifact is byte-for-byte identical.
DimensionsShows whether resizing occurred.
Byte sizeCan expose recompression or container rewriting.
EXIF / XMP / IPTCShows whether common metadata fields remain in the delivered copy.
ICC profileHelps distinguish metadata cleanup from a broader rewrite of the image file.

What HD is good for — and what it is not

Use HD when you care about the visual quality of the shared photo. Do not use the HD badge as evidence that the original container was preserved, or that metadata was removed, or that metadata was preserved. Those are separate claims and should be tested separately.

A quality setting is not a privacy policy.

If privacy matters more than platform behavior

Create the file you want to share before opening WhatsApp. Remove the fields you do not want to disclose, keep enough quality for your use case, inspect the result, and send that sanitized copy.

This approach survives app updates because your privacy decision happens before the upload route.

Create a clean high-quality sharing copy

CreatorPrivacyKit works in the browser so you can inspect and export before sending.

Open the sanitizer →