How to send photos privately (without compression or a cloud account)
Messaging apps compress your photos and strip quality; cloud albums keep them forever. How to send full-resolution originals privately, and what to remove from them first.
Two separate problems get tangled together when sending photos: quality and privacy. Most tools solve neither well.
The compression problem
Send a photo through WhatsApp and it arrives noticeably worse. iMessage over cellular does the same. Instagram, Messenger and Telegram (in normal mode) all re-encode.
This is deliberate — a 12 megapixel photo is 4–8 MB, and messaging platforms move billions of them daily. Compression is how the economics work. It is fine for a snapshot and destructive for anything you might print, edit, or use professionally.
Most apps have a way around it. WhatsApp: send as "Document" rather than "Photo". Telegram: uncheck "Compress the image". iMessage: enable "Send as High Quality" or turn off Low Quality Image Mode. Signal: sends at higher quality by default and has a quality toggle.
Worth knowing regardless of what else you use.
The privacy problem
Photos carry a startling amount of information beyond the image.
EXIF metadata, embedded by essentially every camera and phone, typically includes:
- GPS coordinates, often accurate to a few metres
- Date and time to the second
- Camera or phone model, and frequently a serial number
- Lens, exposure settings, and orientation
- On some phones, the name assigned to the device
The GPS one is the significant one. A photo taken in your house contains your address. A photo of a car for sale contains where you park. People have been located from a single casually shared image more times than is comfortable.
Faces and backgrounds. Reflections, house numbers, school uniforms, the view through a window. Nothing technical removes these.
Filenames. IMG_4471.jpg is fine. renovation_quote_47_oak_avenue.jpg is not.
Which platforms strip metadata
Roughly, and subject to change:
- Facebook, Instagram, Twitter/X: strip EXIF on upload (and keep a copy of the original on their servers)
- WhatsApp, Signal: strip EXIF
- iMessage: strips location when sending, though "Share Location" in the share sheet re-adds it
- Email attachments: do not strip anything
- Cloud drive links: do not strip anything
- Most file transfer services: do not strip anything
The last three are exactly where people send the photos that matter most.
Removing it yourself
iPhone. In Photos, select the image, tap the share button, then "Options" at the top, and turn off "Location". This is per-share and needs doing each time. To strip permanently: open the photo, tap the info button (i), swipe up, and "Adjust" → "Remove Location".
Android. In Google Photos, open the image, tap the info button, then the option to remove location. Varies by manufacturer and version, which is unhelpful but true.
Windows. Right-click → Properties → Details → "Remove Properties and Personal Information" → "Create a copy with all possible properties removed".
macOS. Open in Preview, Tools → Show Inspector, and use the GPS tab's "Remove Location Info". For batch work, exiftool -all= *.jpg in Terminal.
The universal fallback. Take a screenshot of the photo and send the screenshot. Screenshots carry essentially no metadata. You lose resolution, so this is a fix for documents and sensitive images rather than for photos you care about the quality of.
Verify rather than assume. After stripping, check with a metadata viewer. Several stripping tools miss vendor-specific EXIF blocks.
Sending the originals
Once the file is clean, you need a transfer that does not re-encode and does not keep a copy.
The requirements are the same as for any large file transfer: encrypted on your device, chunked so a big upload survives a dropped connection, and deleted once collected. Photos add one specific requirement — the file must arrive byte-identical. Any service that generates a preview thumbnail is decoding your image, and a service that can decode it can read it.
With AliasCloak the flow is:
- Strip metadata and rename the files.
- The recipient creates a mailbox — one click, no account — and gives you their alias.
- Attach the originals. Up to 4 GB each, up to 100 per message, and no re-encoding: the bytes you send are the bytes they get.
- Your browser encrypts everything before it leaves. We never decode the image, because we cannot.
- They download and decrypt. Our copy is deleted on confirmation.
A note on the preview thumbnails you see in the app: those are generated locally in your browser, from the file on your own disk, before encryption. They are stored inside the encrypted payload so your recipient sees them too. At no point does a server see an image.
Video
Everything above applies, plus:
- Video files are large. A few minutes of 4K is several gigabytes, and upload time is the binding constraint — expect roughly 7 minutes per gigabyte on a typical domestic connection.
- Video carries metadata too, including location on most phones.
- Messaging apps compress video far more aggressively than photos.
For anything above about 2 GB, do it from a desktop browser rather than a phone. Browser memory limits on mobile are the practical ceiling.
Quick reference
| You want | Use |
|---|---|
| Casual snap to a friend | Any messaging app; quality loss is irrelevant |
| Full quality, non-sensitive | WhatsApp "as document", or a cloud link |
| Full quality, private | Strip metadata, then an end-to-end encrypted transfer |
| Photo of a document | Screenshot it, then send the screenshot |
| Anything with your home in frame | Strip location. Always. |
The single habit worth adopting: strip location before sharing any photo taken somewhere you live, work, or would rather not be placed. Everything else on this page is refinement on that one thing.
Keep reading
Private by design
