exif
How to remove exif metadata from photo files before sharing them
Learn how to strip EXIF metadata from photos before sharing. Protect your location, timestamps, and device info with simple in-browser tools.
- Published
- May 5, 2026
- Reading time
- 9 min read
- Author
- Editorial Team
TL;DR
- EXIF metadata includes GPS coordinates, timestamps, camera model, and sometimes device serial numbers.
- Social platforms often strip metadata, but email, file sharing, and direct uploads usually preserve it.
- Converting HEIC to JPG or re-encoding existing images removes hidden data before files leave your device.
- TinyPixel processes everything in-browser, so you can verify metadata removal with no upload to servers.
- Common scenarios include selling items online, sharing children's photos, and sending property listings.
An iPhone photo taken in your living room can contain GPS coordinates accurate to within a few meters, the exact second it was captured, your iPhone model and iOS version, and sometimes even your device's unique serial number. This information lives in the EXIF metadata, a standardized format that cameras and phones embed in every image file. Most people never know it's there until they need to remove EXIF metadata from photo files before sharing them with someone they don't fully trust with their home address, daily routines, or family details.
Social platforms like Instagram and Facebook have stripped EXIF data for years. But that protection stops the moment you attach a photo to an email, drop it into a messaging app on desktop, upload it to a school portal, or paste it into a property listing. In those cases, the metadata tags along for the ride, completely invisible to you but trivial to extract by anyone who receives the file.
What's actually hiding in your photos?
EXIF (Exchangeable Image File Format) was designed to help photographers organize and process their work. It stores technical details like aperture, shutter speed, and orientation. Modern smartphones added GPS receivers, so now it also stores latitude, longitude, altitude, and the direction you were facing. Your phone's software layer adds timestamps with embedded timezone offsets, device model strings, and software version numbers.
Some Android manufacturers include the device serial number in EXIF tags. Apple's implementation has historically included the phone model and iOS version, plus precise location data if you've granted camera apps location permission. This isn't a bug or a hack. It's how the system was built to work, and it's useful for sorting photos by location or remembering where a vacation shot was taken. The problem is that this usefulness doesn't stop when you send that photo to someone else.
Real situations where metadata causes real problems
Selling something online. You take a photo of a couch, a bike, or a piece of electronics on your kitchen table. You post it to a marketplace or send it to an interested buyer via email or WhatsApp. If that platform doesn't re-encode the image, the buyer now has a geotagged photograph of the inside of your home. Most people wouldn't tell a stranger their address before meeting in public. They're doing it accidentally through metadata instead.
Sharing photos of children. Grandparents want pictures. You take a great shot outside school at pickup time and email it over. The EXIF data contains the school's exact location, the date and time of your routine pickup schedule, and the device your child is regularly photographed with. None of this means immediate danger, but it's information that doesn't need to leave your family circle, and stripping it costs nothing.
Property listings and professional contexts. Real estate agents, landlords, and home sellers regularly photograph interiors and exteriors. A listing photo with embedded GPS data can reveal a seller's current home location, a rental property's exact position before public address release, or the agent's own movements between properties. In resume contexts, a professional headshot with embedded metadata can leak personal device details and location history to HR systems of unknown security posture.
What actually strips metadata, and what doesn't
Instagram, Facebook, and Twitter/X re-encode uploaded images as part of their processing pipeline. The file that gets stored on their servers and shown to viewers is a new image file, and the EXIF data doesn't survive that transformation. This is why these platforms are generally safe from a metadata perspective, even if they have their own tracking concerns.
WhatsApp behaves inconsistently. On mobile, images are often compressed and re-encoded, which strips metadata. On WhatsApp Web or desktop clients, or when sent as documents/files rather than photos, the original file may pass through unchanged with all EXIF intact.
Email attachments preserve the original file exactly. So do most file-sharing services unless they specifically advertise image reprocessing. School portals, government upload systems, and corporate HR platforms vary widely. Some re-encode, most don't. You can't tell from the user interface, so the only safe assumption is that metadata survives unless you remove it yourself.
How to remove EXIF metadata from photo files
There are several approaches, and the right one depends on what you're starting with and what you need.
Convert HEIC to a different format
iPhones and some Android devices save photos as HEIC (High Efficiency Image Container) by default. Most non-Apple systems can't display these files directly, so sharing them usually requires conversion anyway. The conversion process naturally re-encodes the image and drops all EXIF metadata.
If you need to convert HEIC to JPG, the output is a clean image file with no location data, no timestamps, and no device identifiers. The same applies if you prefer HEIC to PNG for lossless quality, HEIC to WebP for web use, or HEIC to PDF for document embedding.
Re-encode existing JPG or PNG files
If you already have a JPG or PNG and want to strip its metadata without changing formats, any operation that re-encodes the image will do it. Running an image through compression, resizing, or rotation creates a new file with fresh encoding. The old metadata doesn't carry over.
This is often the most convenient path because you probably want to resize or compress images before sharing them anyway. A 12MB phone photo doesn't need to be 12MB in a text message or email. Compressing it to a reasonable size for screen viewing serves two purposes at once: smaller file, zero metadata.
Browser-based verification
The critical privacy advantage of doing this in-browser rather than uploading to a cloud service is that you can verify the result before any data leaves your device. Open the converted image on your computer. On macOS, right-click and "Get Info," then check the "More Info" section. On Windows, right-click, select Properties, then the Details tab. If the location, camera, and date fields are empty or missing, the metadata removal worked. The file is clean before it touches any network.
Cloud-based EXIF strippers exist, but they require uploading your original, fully tagged file to someone else's server. You're trusting their security, their retention policy, and their honesty about deletion. In-browser processing never creates that trust gap.
A practical workflow for different scenarios
For casual sharing with family or friends: If your photos are HEIC, convert to JPG in batch. If they're already JPG, run them through compress or resize to both strip metadata and make them email-friendly. Check one file to confirm the metadata is gone, then share the rest with confidence.
For selling items online: Take your photos, check if any show identifiable interior details or view angles that could locate your home, and process all of them through conversion or compression. Even if you're meeting buyers in public, there's no upside to them having your address from a photo metadata field.
For professional or institutional uploads: Resume photos, school forms, and property listings should go through the same cleaning step. These systems have the least predictable handling of uploaded files, and they often retain originals in document management systems for months or years.
For photos you want to keep pristine: If you need the original file for your own archive but want a clean version to share, process a copy and keep the original in your personal storage. Don't overwrite your only high-resolution master.
What doesn't get removed, and what to do about it
Image re-encoding removes EXIF metadata, but it doesn't make someone unrecognizable in a photo, and it doesn't strip visible information. A license plate in the background, a street sign, a school name on a uniform, or distinctive architectural features still leak location information to anyone looking carefully.
For sensitive situations, consider whether the photo content itself is too revealing before worrying about metadata. Crop out identifying backgrounds. Take items for sale against a neutral backdrop rather than your actual living room. These content decisions matter more than EXIF stripping for serious privacy concerns, though both are worth doing.
Checking your work
After processing, verify on a few representative files. The method varies by operating system but the goal is the same: confirm that Properties, Get Info, or an EXIF viewer shows no GPS coordinates, no camera model, no timestamps, no serial numbers.
On macOS, Preview's Inspector (Tools > Show Inspector, or Command-I) shows an EXIF tab if data exists. If the tab is absent or empty, the metadata is gone. On Windows, the Details tab in file properties is the quickest check. Linux users can install exiftool for command-line verification, or use any GUI metadata viewer.
If you find residual data, the file wasn't fully re-encoded. This sometimes happens with certain compression tools that attempt to preserve metadata by default. Our compression and conversion tools produce fresh encodings, so this shouldn't occur, but verification is always worth the thirty seconds.
The bigger pattern
EXIF metadata is one of many invisible data trails that accumulate in normal digital life. It's relatively easy to control compared to, say, browser fingerprinting or cell tower records. The tools to manage it are simple, the verification is straightforward, and the risk of over-sharing is concrete rather than abstract.
The goal isn't paranoia about every photo. It's matching the information you emit to the trust level of the recipient. A photo sent to your spouse doesn't need the same treatment as one posted to a public marketplace or sent to an institutional system you'll never inspect. Having a quick, reliable way to remove EXIF metadata from photo files gives you that control without complicating your workflow.
If your phone defaults to HEIC, converting for compatibility handles two problems at once. If you work with standard formats already, a quick trip through compression or resize before sharing is a habit that costs nothing and prevents a category of privacy slips that are increasingly easy to exploit.