How to Remove EXIF Data from a Photo (No Quality Loss)

You photograph something in your kitchen to sell it online. You upload the photo. A stranger downloads it, opens the file properties, and reads the exact latitude and longitude of your kitchen. Nobody told you the photo was carrying that, and no photo viewer shows it on screen.

This is not a rare edge case or a security hole. It is how the JPEG format has worked since 1995, and every phone camera writes those coordinates by default. The good news is that removing them takes one step and does not have to cost you a single pixel of image quality — if you use the right kind of tool.

What is actually inside a photo file

A JPEG is not one picture. It is a small container holding several separate blocks, and only one of them is the image. The rest is a set of labels that cameras, phones and editing apps have been adding to over thirty years:

• EXIF — the biggest one, and the one people mean when they say "photo metadata". It holds the camera make and model, the lens, the serial number, the shutter speed and ISO, the date and time down to the second, and the GPS coordinates. It can also hold the photographer's name and the owner name.
• GPS — technically part of EXIF, but worth naming separately, because it is the field that turns a photo into an address. Latitude and longitude are stored to about six decimal places, which is accurate to roughly ten centimetres.
• XMP — written by editors like Lightroom and Photoshop. Holds the edit history, star ratings, keywords, and sometimes face regions: rectangles with names attached.
• IPTC and Photoshop data — the fields journalists and stock photographers fill in: creator, credit line, copyright notice, caption.
• ICC colour profile — not personal data at all. It tells the viewer how to display the colours correctly.
• Comments and thumbnails — some cameras embed a small preview image. If you cropped a photo, that embedded thumbnail can still be the uncropped original.
• Content Credentials — the newer C2PA provenance block, which records which app or AI model produced the file.

PNG and WebP files work the same way with different block names: PNG stores metadata in tEXt, iTXt, eXIf and tIME chunks, and WebP stores it in EXIF and XMP chunks.

Why one photo can give away more than one secret

The coordinates are the obvious problem. The others are subtler and often worse:

• The serial number is a unique identifier for your camera or phone. Post three photos on three different forums and anyone can confirm they all came from the same device.
• The timestamp says when you were somewhere. A photo of a birthday present, posted at the right moment, says when your house was empty.
• The software field reveals your workflow and your device generation. Not dangerous, just unnecessary.
• The embedded thumbnail can show parts of an image you deliberately cropped out.

And the coordinates are not vague. At the precision phones write, they resolve to a specific building. Not "Kathmandu" — your front door.

How to check what is in your own photos

Before removing anything, look. It takes seconds, and once you have seen your home coordinates sitting in a photo of a lamp, you will never post one unchecked again.

• Windows: right-click the file, choose Properties, then the Details tab. Scroll to the GPS section. If there is a location, you will see Latitude and Longitude as numbers.
• macOS: right-click the file, choose Get Info, then click the arrow next to More Info. The GPS row appears there, with a map pin.
• iPhone: open the photo in Photos and swipe up, or tap the i button. The map appears under the image if the location was saved.
• Android: open the photo in Google Photos and swipe up. Details shows the capture date, device and any location.
• In the browser: drop the photo into the Remove EXIF Data tool. It reads the metadata before deleting it and prints the camera, the date, the author, the serial number and the coordinates in plain decimal degrees — including the ones your operating system hides.

The problem with most online EXIF removers

Search for this and almost every result is a page with an upload box. You choose your photo, it goes to a server, a script strips the metadata and sends the file back. Some of them delete your file after an hour. Some of them keep it. None of them can promise anything, because you cannot see what happens on the other side.

Think about what that means for this specific job. The reason you are here is that the photo contains your address. The standard solution is to hand that photo — address included — to a website you have no reason to trust, so that it can remove the address for you. If the file leaks in transit or sits in a queue, the metadata you were trying to delete is exactly what leaked.

It also means your passport scan, your medical letter, your child's photo and your ID document all pass through a stranger's server for a task your own computer can do in milliseconds. Every tool on this site runs entirely in your browser. Nothing is uploaded, there is no queue, and the page keeps working with the internet switched off — which is the easiest way to prove it.

Removing metadata without damaging the photo

Here is the part that separates a good tool from a bad one, and it comes down to a single decision: does the tool re-encode the picture, or rewrite the container?

Re-encoding means decoding the JPEG back to raw pixels and compressing it again. This is what almost everything does, because it is three lines of code — draw the image to a canvas, export it. It also means your photo is compressed twice. A 4 MB photo becomes a slightly softer 4 MB photo, every time you run it. Removing a few hundred bytes of text should not cost you image quality, and with this approach it does.

Rewriting the container means leaving the compressed image data completely alone and editing only the blocks around it. The picture is stored as one long run of compressed bytes; the metadata lives in separate blocks before it. Delete the metadata blocks, keep everything else, and the output is byte-for-byte identical where the picture is concerned. Same quality as the original, because it is the original.

That is what the Remove EXIF Data tool does. It reads the file as a container, drops the blocks that carry metadata, and copies the rest through untouched. You can verify the claim yourself: the file gets smaller by roughly the size of the metadata, and the image itself is unchanged.

The trap that turns photos sideways

There is one case where a straight delete goes wrong, and it is common enough to be the main reason people end up with broken results.

Phone sensors are physically wider than they are tall. When you hold the phone upright, the camera usually still records a landscape image and adds a tag to the EXIF block saying "rotate this 90 degrees clockwise for display". Every viewer, browser and phone respects that tag, so the photo looks right everywhere. The rotation is not in the picture. It is in the metadata.

Delete the metadata, and the instruction disappears with it. The photo now displays on its side — and it is not obviously broken, it just looks wrong, which is how it ends up posted anyway.

The tool handles this in one of two ways, and you choose which:

• Rotate upright, then remove everything (the default). The picture is rotated for real and re-encoded at 95% quality, so the file has no metadata at all and displays correctly everywhere. This is the only path in the tool that touches the image, and it only runs when the photo actually needs it — an upright photo is never re-encoded.
• Keep only the rotation number. The tool writes a minimal 36-byte EXIF block containing a single value: the rotation. The image data is copied through untouched, so the photo is lossless and stays upright. It carries no camera, no date and no location — just the number that keeps it the right way up.

If you are not sure which you want, take the default. If you care about absolute fidelity — a scan, an archive, a print — take the second.

Removing metadata is not enough on its own

Here is the part most guides leave out, and it is the part that actually bites people.

Cleaning the file protects the file. It does nothing about the route the file takes, and several everyday routes preserve metadata perfectly:

• Email attachments are copied, not re-encoded. Everything survives.
• Cloud drive links — Google Drive, Dropbox, OneDrive, WeTransfer — store and serve the original bytes. Everything survives.
• Upload forms, forums and marketplace listings usually store what you send. Everything survives.
• Messaging apps are split. Sending a photo as a photo re-compresses it and the metadata does not survive. Sending the same file as a document or file copies it byte for byte, so everything survives — including the GPS. This is the single most common way a cleaned-up photo gets its location back.

Social networks generally re-encode what you upload, so a photo posted to a feed usually loses its EXIF along the way. But "usually" is doing real work in that sentence: the behaviour differs by platform, by media type, by whether you uploaded a photo or a file, and it changes without announcement.

So do not rely on it. Test the app yourself in thirty seconds: send the photo to yourself through the app in question, save what arrives back to your device, then drop it into the metadata viewer. If the row reports GPS coordinates, that app passes metadata on. If it reports nothing, that route is safe for that kind of upload. It is the only answer that stays true after the next app update.

What cleaning metadata does not fix

Two honest limits.

It does not change the picture. If the photo shows your street sign, your car registration or the view from your window, no amount of metadata removal helps. If that is the problem, blur or black out the identifying parts instead.

It does not affect photos already published. Metadata you removed today does not reach back to a file uploaded last year. If an old listing has your location in it, re-upload the cleaned version and take the old one down.

What about iPhone HEIC photos?

HEIC is a different container, and the metadata inside it is not organised in the same blocks, so a JPEG tool cannot rewrite it safely. The practical route is to convert it first with the HEIC to JPG converter, which decodes the image and writes a fresh JPEG — and because the pixels are re-encoded rather than the metadata copied, the location, camera and timestamp are left behind as a side effect. The JPG you get back is already clean.

That matters more than it sounds, because the photos on an iPhone are HEIC by default, and they are the ones with the GPS.

The short version

Every phone photo carries hidden text: the exact coordinates where it was taken, the date to the second, the device, often a serial number. Windows, macOS, iOS and Android will all show it to you in a few clicks.

To remove it properly, use a tool that rewrites the file container instead of re-encoding the picture — that keeps the image byte-identical. Watch the rotation tag, or your portrait photos will come back sideways. And remember that email, cloud links and "send as document" hand the original file on intact, so clean the photo before it leaves your device, not after.

Remove the metadata from your photos in the browser — free, in a batch, and without the file ever leaving your computer.