Yes. By default, WhatsApp sends photos and videos as compressed copies, and it is far from alone in that. Almost every route a guest photo can take between the camera and you shrinks it somewhere, usually silently, usually more than once.
That matters less than people think for a photo you glance at, and much more than people think for the one you wanted to print.
The short answer, with the exceptions
WhatsApp compresses by default. It also offers an HD option per send and a send-as-document path that moves the file as it is, so the capability is there for anyone who remembers it at the time.
iMessage sends near-original files between iPhones, then hands off to the carrier's messaging for everyone else, which by default sends a reduced copy, so the quality of what you receive depends on which phone sent it.
Email caps attachments at around a few dozen megabytes, which means a handful of photos go through and a video gets shrunk, split, or turned into a link.
None of these is behaving badly. They are messaging tools, and a messaging tool that sent a multi-gigabyte original over a hotel connection would be a broken messaging tool. The problem is that a wedding, a birthday, or a conference then uses them as the archive.
The chain, step by step
Here is one photo, on the way to you.
Step one: the camera. A guest's phone takes a 4 MB photo, HEIC on an iPhone, and it looks perfect on the phone, because it is.
Step two: the send. It goes into the group chat. Default settings, so what everyone else receives is a re-encoded copy sized for a screen, not the file the camera made. Nobody notices, because everyone is looking at it on a screen.
Step three: the save. A friend likes it and saves it to their camera roll. What lands there is the copy, not the original. The original is still on the first phone, where nobody will ever ask for it again.
Step four: the forward. Three weeks later that same friend forwards it to the group for the other event, or to you when you ask. It is re-encoded again, from the copy.
Step five: the screenshot. Somebody cannot find the photo in the thread, so they scroll up and screenshot it. Now the file is whatever the screen was, with the corners of the chat cropped off, and any chance of a print is gone.
Every step is lossy, no step is reversible, and by the end the photo you have is nothing like the photo that was taken. This is what people mean when they say the photos from an event were disappointing. The photos were fine. The plumbing was not.
If the chat is the only option
Ask for the file, not the picture. On WhatsApp that is the HD toggle or attaching the photo as a document; on iPhone it is AirDrop if you are in the same room. Both work. Both also require every single guest to remember, which is why they do not scale past a few files.
Why "just send the originals" fails at scale
Every host tries this. It fails for reasons that have nothing to do with willpower.
Guests do not know which setting to change, and the settings live in different places on every app. The path that keeps the file is always the slower path, and people are holding a drink. The photos are spread over dozens of phones, so it only takes a few defaults left alone to hole the archive. And the request arrives after the event, when the moment has passed and the reply is "I will send them tomorrow", which is the last anyone hears of it.
The fix is not better instructions. The fix is a path where the default is the original, so nobody has to remember anything.
What an event album has to do differently
That constraint is what a QR event album is built around. A guest's phone uploads the file straight to storage from the browser, and the original is kept byte for byte: not a version resized for the web, not a copy re-encoded to save space on the storage side. What a guest uploads is what anybody downloads later.
A few practical consequences, all of them things a chat cannot offer:
- The formats phones shoot are accepted as they are: JPEG, PNG, WebP, HEIC and HEIF, AVIF, and MP4, MOV or WebM for video. No conversion step, no "unsupported file" wall.
- Big files are welcome, up to 10 GB per file, photos and videos alike, with no cap on how long a clip runs. A speech does not have to be trimmed to fit a message.
- The tiles are previews, on purpose. A small preview is generated on the phone so a gallery of hundreds of photos loads instantly on a phone connection. Open an item full screen, save it, or take the whole album as a zip, and you get the original every time. Downloading is where that shows up.
- Guests get the same quality you do. They are not receiving your copy of their photo. They are opening the album and saving the file that was uploaded.
If you are the guest in this story and you want to know what happens after you scan, that side is written down too.
The one exception
AirDrop moves the file uncompressed, with no service in the middle at all, and it is limited to Apple devices in the same room. Where it sits against everything else is the full ranking's job.
The next step is the boring one that works: before the event, give the photos one place to land where the original survives the trip.
