Data Privacy · Guide
How to Remove Metadata (EXIF and GPS) From a Photo on Windows, Mac, iPhone and Android
28 min read · Published November 17, 2026 · Updated November 19, 2026 · Mochify Engineering Team
You are about to post a photo, send it to a buyer, attach it to a listing or hand it to a client, and you want the hidden part gone: where you were standing, when, on which phone. You searched "remove metadata from photo" and got a wall of upload-here tools, a Reddit thread asking whether the Windows button is enough, and an AI answer that gives four sets of steps and no idea whether any of them finished the job.
Here is the shape of the answer before the detail. Every photo from a phone or camera carries a block of metadata called EXIF; a real iPhone 15 photo we opened for this guide carries 61 EXIF tags, 13 of them GPS, inside 22,017 bytes of header, plus a maker note, a color profile, an embedded thumbnail and an HDR gain map. The built-in routes on iPhone, Android and the Mac remove the location and leave the rest. The Windows button removes most fields and leaves some. The only route that removes everything, including the newer Content Credentials that tag AI edits, is to write a fresh file: a re-encode, with exiftool, or with a converter that does it for you. This guide walks each platform click by click, says what each one leaves behind, and shows you how to check.
Published November 17, 2026 by the Mochify Engineering Team. Figures come from six live API calls and an exiftool 12.76 run on November 9, 2026: what each built-in route leaves behind, and what a re-encode removes.
What metadata a photo actually contains
A photo straight from a phone or camera carries far more than the picture: camera make and model, the exact second it was taken, exposure settings, a GPS fix with altitude and compass heading, a vendor "maker note", a small embedded thumbnail, a color profile, and, on recent phones, an HDR gain map. Here is what one real file holds.
We dumped the headers of an iPhone 15 photo taken on October 27, 2026 (3,867,434 bytes, 5712 x 4284 pixels). Before the picture data starts, the file carries:
- An EXIF block of 22,017 bytes with 12 tags in the main directory (Make
Apple, ModeliPhone 15, Software27.0, the date and time, an Orientation flag of 6 because the phone was held upright), 36 tags in the Exif sub-directory (shutter speed, aperture, ISO, lens model, white balance, the original timestamp to the sub-second, plus a MakerNote that only Apple software reads) and 13 GPS tags: latitude and longitude to the hundredth of a second of arc, altitude (98 meters), the direction the camera faced (244 degrees), the GPS timestamp, andGPSHPositioningError(8.2 meters, which is how precise the fix was). - An embedded thumbnail, a second small JPEG inside the first, which is why "remove the face from the photo" is not the same as "remove the face from the file".
- An ICC color profile (Display P3 on iPhones) and a MPF segment that points to a third image inside the file, the HDR gain map.
- An Apple-specific segment of 1,086 bytes that no public viewer explains.
None of this is visible in the picture, all of it travels with the file when you attach it as a file, and most of it is useful. The lens and exposure data is why your photo library can search by camera; the GPS fix is why it can show a map. The question this guide answers is how to take it off a copy you are about to share, and how to be sure it is gone. For why it matters, the risks of EXIF data in image compression covers the privacy and compliance side; this guide is the how.
Five words this guide uses
- EXIF. The block of camera data (make, model, exposure, dates, GPS) that cameras and phones write into JPEG, HEIC, TIFF and some PNG and WebP files. When someone says "photo metadata" they usually mean this.
- GPS tags. The part of EXIF that holds the location. Removing only these is what "remove location" does on every phone.
- XMP and IPTC. Two other metadata blocks, written by editing software and by photographers' tools: edit history, keywords, captions, copyright. A phone photo may not have them; a Lightroom or Photoshop export almost always does.
- Content Credentials (C2PA). A newer, signed metadata block that records who made or edited an image and with what, including whether generative AI was used. Stored in its own segment, not in EXIF, so EXIF-only tools miss it.
- Re-encode. Decoding the picture and writing a brand-new file from the pixels. A re-encode carries across only what the encoder is told to carry, which is why it is the clean way to remove metadata, and also why it changes the file (a new JPEG is a new compression pass).
How to see the metadata on your own device
Every platform can show you the location and the basics; only a dedicated reader shows you everything. Check before and after, or you are guessing.
- Windows 11: right-click the file, Properties, Details tab. You see camera, dates and (if present) GPS latitude and longitude under "GPS". Windows shows the fields it understands, not the raw blocks.
- Mac: in Photos, select the photo and click the Info button; photos with a location also appear in the Places album. In Preview, open the photo and choose Tools > Show Location Info; if it is grayed out the image has no location (per Apple's Preview guide, read November 9, 2026). Preview's Inspector (Tools > Show Inspector) shows the image's metadata fields.
- iPhone and iPad: open the photo in Photos and swipe up, or tap the Info button. You see the camera, the lens, the file size and a map if there is a location. Apple's Personal Safety User Guide (published September 2026) is the current reference for these screens.
- Android (Google Photos): open the photo, swipe up or tap the Info button. Google Photos also shows an estimated location for photos that have none, worked out from landmarks and your other photos; the info panel labels it as estimated.
- Everything, in a browser: the Mochify EXIF viewer lists every block a photo holds, grouped in plain sections, and reads the file on your device without uploading it.
- Everything, on any computer: exiftool is
the reference reader.
exiftool -a -G1 -s photo.jpglists every tag with the block it lives in ([IFD0],[ExifIFD],[GPS],[XMP],[ICC_Profile],[JUMBF]for Content Credentials). It is the tool we used for the numbers in this guide, and it is how you prove a method worked: run it on the output and look for an empty list.
Windows 11: Remove Properties and Personal Information
Windows has a built-in button that removes most of a photo's metadata and writes a copy. It is quick, it needs nothing installed, and it is not complete, so use it for "good enough" and a re-encode for "gone".
The steps
- In File Explorer, right-click the photo and choose Properties (or select it and press Alt+Enter). On Windows 11, if Properties is not in the short right-click menu, choose Show more options first.
- Open the Details tab. Scroll to see Camera, Advanced photo and GPS sections.
- Click Remove Properties and Personal Information at the bottom of the dialog.
- Leave Create a copy with all possible properties removed selected and
click OK. Windows writes a second file next to the original (named with
- Copyadded) and leaves the original alone. The other option, Remove the following properties from this file, lets you tick individual fields and changes the original in place. - Right-click the copy, Properties, Details: the GPS section should be empty and the camera fields blank.
What it leaves behind
The wording in the Microsoft Community thread that Google ranks for this question is the honest one: it "creates a copy with most metadata removed" (Microsoft Community Hub, asked April 27, 2025, community answers through June 2026). Microsoft publishes no support page for the feature that we could find, so "most" is the strongest statement available. In practice the button clears the fields Windows itself displays. Data Windows does not display is a different matter: the embedded thumbnail, maker notes, XMP and IPTC blocks written by editing software, JPEG comments, and Content Credentials are not fields in that dialog, and a third-party audit of the feature on Windows 11 reports exactly those surviving (the audit's author sells a rival tool, so treat it as a claim to check, not a finding). Check with exiftool if the photo matters. If what you need is "the GPS and the camera model gone before I post this on a marketplace", the Windows button does that. If what you need is "nothing in this file but pixels", read on.
A worked example
Sam is selling a camera bag on a local listings site and photographed it on the kitchen
table. Right-click, Properties, Details, Remove Properties, Create a copy, OK: IMG_2031 - Copy.jpg appears. Its Details tab shows no GPS and no camera. The listing
goes up with the copy. What survived in the copy is the embedded thumbnail (a tiny version of
the same kitchen table, harmless here) and the Apple segment nobody reads. Fine for a bag. Not
fine if the original had been edited to hide something and the thumbnail had not.
Mac: Photos, Preview, and the terminal
On a Mac the built-in routes remove the location; a full strip needs the terminal or a converter. Here is the order to try.
Photos: hide the location
Apple's current instruction is in the Personal Safety User Guide (September 2026): in Photos, select the photo or photos, then choose Image > Location > Hide Location. Image > Location > Revert to Original Location puts it back, which tells you Photos keeps the original data inside your library, so export a copy and check that copy before you share it. Export with File > Export > Export [N] Photos to get a new JPEG, HEIC, TIFF or PNG (the export dialog in the macOS Tahoe 26 Photos guide offers Photo Kind, JPEG Quality, Color Profile and Size). File > Export > Export Unmodified Original does the opposite: it hands you the original bytes with everything in them, so do not use it for a copy you mean to share clean.
Preview: look, and know its limits
Preview shows you the location (Tools > Show Location Info) and the EXIF fields in its Inspector. Older guides describe a Remove Location Info button in the Inspector's GPS pane and an "Include location information" checkbox in File > Export; Apple's current Preview guide documents viewing only, so if your version shows those controls they remove the location and nothing else. Treat Preview as the viewer and do the removal elsewhere.
Terminal: exiftool
Install exiftool (brew install exiftool with Homebrew, or the package from exiftool.org),
then in Terminal:
exiftool -all= photo.jpgThat writes a copy of the file with no metadata and renames your original to photo.jpg_original, so nothing is lost. The exiftool FAQ adds a caution and a
safer form for JPEGs: "the metadata may contain color space information which should be
maintained to preserve the color rendition", so to keep the color profile and copy the
color-space tags back:
exiftool -all= --icc_profile:all -tagsfromfile @ -colorspacetags photo.jpg(ExifTool FAQ 32, read November 9, 2026.) For a whole folder of JPEGs, keeping the file dates and skipping the backups because you have your own:
exiftool -r -ext jpg -all= --icc_profile:all -tagsfromfile @ -colorspacetags -P -overwrite_original ~/Pictures/to-shareTo remove only the location and keep the camera data, exiftool -gps:all= photo.jpg deletes the GPS block as a unit (we checked on exiftool 12.76: Make and Model stayed, both coordinates
went). The same commands work on Windows and Linux; the Mac section is just where the terminal
usually enters the conversation.
Check it
exiftool photo.jpg after -all= should list only file-system facts
(name, size, dates, dimensions) and nothing under EXIF, GPS, XMP or JUMBF. If a [JUMBF] line is still there, the file had Content Credentials and your version of exiftool left them;
see the AI metadata section.
iPhone and iPad: No Location, and the share sheet Options
iOS removes the location from a photo, or from a share, with two taps; it does not remove the rest of the EXIF. For a full strip you need an app or a converter.
Remove the location from a photo
Apple's steps (Personal Safety User Guide, September 2026): open Photos, open the photo, tap the More button (the three dots), then Adjust Info > Adjust Location > No Location. The photo keeps its camera and date information; only the place goes. On older iOS versions the same control was reached by swiping up and tapping Adjust next to the map.
Share without the location
The better habit, because it leaves your library intact: select the photos, tap the Share button, tap Options at the top of the share sheet, and turn off Location. "Location Not Included" appears above Options, and whatever you choose next in the sheet (Messages, Mail, a third-party app) gets copies without the GPS tags. This is per share, so you decide each time.
Stop collecting it
Settings > Privacy & Security > Location Services > Camera > Never. New photos then have no location at all. You lose the map in Photos; some people consider that a fair trade.
What iOS does not do
There is no built-in "remove all metadata" on iPhone. A photo shared with Location off still carries the camera model, the exposure data, the timestamps and the maker note; a Reddit r/privacy thread that ranks for "remove photo metadata iphone" reaches the same conclusion ("nothing native"). The App Store has viewers and strippers (Apple's own listing for one, Exif Metadata, says it can "view, edit, and remove metadata, including GPS location"); or send the photo through any converter that re-encodes, including the Mochify web app from Safari, which writes a fresh file with no metadata by default. If the photo is a HEIC and the destination wants a JPEG anyway, the HEIC to JPG converter does both jobs in one drop.
Android: Google Photos, and the one thing it cannot remove
Google Photos removes a location it added or estimated, and does not remove a location the camera wrote. That sentence is in Google's own help and is missing from most of the pages (and the AI answer) telling you to "tap the pencil and Remove Location".
What Google Photos can do
Open the photo in Google Photos, tap More (three dots), then Edit next to the location. If the location was estimated by Google Photos or added by hand, Remove location removes it. For several photos, select them, tap More > Edit location > Remove location. Shared albums have a Share > Options > Share photo locations switch, and locations are off by default in new conversations.
What it cannot do
From Google's help page for Android (Understand, find and edit your photos' locations, read November 9, 2026): "If a location was automatically added by your camera, you can't update or remove the location in Google Photos." That is the common case: your phone's camera geotagged the photo, and the Google Photos pencil is not the way out. Samsung's Gallery and other makers' gallery apps have their own controls (several offer a remove-location switch when sharing); check yours, then check the output.
The routes that work on Android
- Stop the camera saving it. Open the camera app's settings and turn Save location off (Google's wording for Pixel and most Android cameras). Future photos have no GPS tags.
- Re-encode the copy you share. Any converter that writes a new file
removes the whole EXIF block, GPS included. The Mochify web app in Chrome does this from
the phone: drop the photos, type
strip the metadata, download. The Play Store also lists dedicated strippers (the one that ranks first on Google, Photo Metadata Remover, says it removes EXIF and optionally IPTC). - Rely on the app you are posting to. Instagram, Facebook, X and most public platforms re-encode uploads and the EXIF goes with it (see the sharing section), which is why "my photo has no metadata after I posted it" is normal and not a sign anything was removed on your phone.
Remove everything at once: a re-encode, exiftool, or a converter
Writing a new file from the pixels is the one method that removes every block at once: EXIF, GPS, maker note, thumbnail, XMP, IPTC, comments and Content Credentials. exiftool does it without touching the pixels, and so does the Mochify EXIF remover, which runs in your browser, uploads nothing and keeps only what the photo needs to display correctly; a converter does it while compressing or resizing. Here is what happens, measured.
What a re-encode removes
We sent the iPhone 15 photo from the first section through Mochify's API on November 9, 2026 with one instruction, convert to JPEG at 1600 pixels wide. The output was 159,975 bytes, 1600 x 2133, upright, and contained no metadata segment at all: no EXIF, no GPS, no maker note, no ICC profile, no Apple segment, no thumbnail, no gain map. Nothing to read. The PNG output in the same test carried none either, and the AVIF and WebP outputs we checked in October carried no EXIF. That is the default on the API and on every Mochify tool page except the two pro-camera HIF pages, which keep metadata until you switch Strip EXIF on; it is not a setting you have to find.
What a re-encode changes
A fresh encode is a new compression pass, so the file is not byte-identical to the original even at the same size. Three things to know:
- Orientation is baked in. Phones store the pixels sideways and set an EXIF
Orientation flag; a re-encode rotates the pixels upright and writes Orientation 1 (or
none). This is why a stripped photo never comes out sideways from a proper converter, and
why
exiftool -all=on an un-rotated camera file can make it appear sideways: the pixels were never turned, and you just deleted the flag that said to turn them. Rotate first, or use the exiftool color-space form above and add-orientationto the tags copied back. - Colors are converted to sRGB. Mochify converts a Display P3 or Adobe RGB
source to sRGB during the encode, so the output needs no embedded profile and looks right
in every browser; what you lose is the wide-gamut headroom (measured on a P3 iPhone photo,
a mean difference of about 3 of 255 across the frame). exiftool's
-all=removes the profile without converting the pixels, which is the case the FAQ's warning is about. - HDR is a choice. The gain map that makes an HDR photo glow on an HDR
screen is a second image inside the file; a plain re-encode drops it, and you keep it only
if you ask (in Mochify,
hdr=trueor "keep the HDR" in the prompt). Why HDR photos look flat when shared explains what you are deciding.
When you want to keep the camera data
Photographers often want the opposite: strip nothing, or strip only the GPS. exiftool -gps:all= is the surgical tool. On Mochify, the photography pages keep
metadata when you ask: on the HIF to JPG converter, built for
Canon, Sony and Fujifilm .HIF files, the Strip EXIF switch starts off, so your ISO, shutter and lens data survive the conversion by default
and you switch it on to remove them. On the API, stripExif=false keeps the EXIF block:
in our test it carried every camera tag, the maker note and all 13 GPS tags across, rewrote Orientation
to 1 to match the upright pixels, and did not carry the thumbnail, the profile or the gain map.
"Keep metadata" means the EXIF block, not the whole header.
When you do not need any of this
If the photo was taken with location services off, has already been through a social network, or is a screenshot (screenshots carry no camera EXIF), there is nothing to remove. Check with the steps in section 3 and move on.
AI metadata and Content Credentials: what comes off and what does not
Content Credentials are metadata and come off with a re-encode or exiftool -jumbf:all=; an AI watermark embedded in the pixels is not metadata
and does not. Searches for "remove AI metadata from photo" have grown twenty-five-fold in a
year, so this deserves its own section.
What Content Credentials are
Content Credentials are the C2PA standard's signed record of an image's history: which tool made it, what edits were applied, whether generative AI was involved. Adobe apps, some cameras and some image generators write them. In a JPEG they live in their own segment (APP11, in a container format called JUMBF), alongside EXIF rather than inside it, which is why a tool that only knows EXIF fields, like the Windows dialog, does not touch them. The C2PA specification (version 2.2, May 2025) is explicit that a manifest can be removed, and describes "soft bindings", fingerprints and watermarks that let a removed manifest be matched again from a provenance store if the publisher kept one.
In the sample file we tested, the Content Credentials manifest was 45,882 bytes of a 132,518-byte JPEG, 35% of the file.
What removes them
- A re-encode. We ran that sample through Mochify as JPEG, WebP and PNG, and also as JPEG with "keep metadata" switched on. The manifest was gone in all four outputs, including the keep-metadata one: the encoder carries the EXIF block when asked and never carries a manifest. So any Mochify conversion removes Content Credentials, whichever setting you use.
- exiftool.
exiftool -jumbf:all= photo.jpgremoved the manifest from the same file on exiftool 12.76 (132,518 bytes to 86,634), and so did-all=. Note that-gps:all=leaves it; location-only removal leaves Content Credentials intact. - The copy-into-a-new-document trick that Photoshop users trade on forums (select all, copy, paste into a new file, export) works for the same reason: the new file has no history.
What does not come off
A watermark embedded in the picture itself survives all of this. Google's SynthID, used on images from Gemini and checked by Gemini, Search and Chrome, is "designed to stand up to modifications like cropping, adding filters ... or lossy compression" (Google DeepMind, read November 9, 2026). A metadata strip does not touch pixels, so it does not touch SynthID, and platforms that classify images by content rather than by header will still see what they see. If your goal is to pass a generated image off as a photograph, no metadata tool does that, and this guide is not going to help you try. If your goal is to stop a photo you edited in Photoshop from carrying your name, your software list and your edit history to a stranger, the strip is exactly the right tool.
Cheat sheet
| Platform | Built-in route | Removes | Leaves | For a full strip |
|---|---|---|---|---|
| Windows 11 | Right-click > Properties > Details > Remove Properties and Personal Information > Create a copy | Most EXIF fields incl. GPS, camera, dates | Thumbnail, maker notes, XMP / IPTC, comments, Content Credentials (unverified by Microsoft; check with exiftool) | exiftool or a converter |
| Mac | Photos: Image > Location > Hide Location; export a copy | Location in the exported copy | Camera data, everything else | exiftool -all= --icc_profile:all -tagsfromfile @ -colorspacetags or a converter |
| iPhone / iPad | Photos: More > Adjust Info > Adjust Location > No Location; or Share > Options > Location off | Location only | Camera, exposure, dates, maker note | An App Store stripper, or a converter in Safari |
| Android | Camera settings > Save location off (future photos); Google Photos removes only estimated / manual locations | Future GPS; estimated locations | Camera-written GPS and all EXIF on existing photos | A converter in Chrome, or a Play Store stripper |
| Any computer | exiftool -all= photo.jpg | Everything (EXIF, GPS, XMP, IPTC, thumbnail, Content Credentials) | A photo.jpg_original backup | Add -jumbf:all= only if your version leaves JUMBF |
| Any device, browser | Drop on a Mochify tool page or the web app | Everything, by default, while converting or compressing (the two HIF pages keep metadata until you switch Strip EXIF on) | Nothing (pixels only; colors converted to sRGB) | That is the full strip |
The thirty-second version: phones remove the location, Windows removes most fields, a re-encode removes everything; check with exiftool; and strip before you send by document, HD, email or iMessage, because those keep the original.
Mochify Workflow: strip the metadata from a batch of photos
Say what you want
Open the Mochify web app, drop the photos (up to 3 per batch with no signup, 25 on a Day Pass or any paid plan), and type the result in plain English:
strip the metadata, orremove the location data and keep them as JPG, orJPG, 1600px wide, strip EXIFif they are going to a listing. Magic Flow reads the sentence with a language model, then the C++ engine writes fresh files, so nothing from the original header comes across unless you asked for it. Want faces hidden too?blur every face and strip the metadatadoes both in one pass; the web app shows no face count, so check each picture (how to blur faces or a license plate has the detail).Or use the one-job page
If the photos are JPEGs and you want them to stay JPEGs, the jpegli JPEG compressor is the one drop:
.JPGin, a smaller standard JPEG out, metadata stripped by default (a Strip EXIF switch appears after upload if you want it kept). Every conversion page works the same way, GPS included; the photography pages such as HIF to JPG start with metadata kept because their users want it, and the switch is right there after upload.From the terminal or an agent
The same engine runs from the Mochify CLI, from an AI assistant through the hosted MCP server or the local MCP server (
mochify serve), and from the REST API:POST /v1/squish?type=jpgonapi.mochify.app, authenticated withAuthorization: Bearer <key>, strips metadata by default; addstripExif=falseto keep the EXIF block (camera, dates, GPS, maker note). All of them are clients over the same API. Your AI agent built your website shows an agent stripping the GPS from a whole folder of site images this way.What happens to your files
Your photos travel over HTTPS to
api.mochify.app, are processed in memory and discarded as soon as your download is ready: nothing is written to disk, no logs contain your image data, and your images are never used to train AI. That holds for the web app, the tool pages, the CLI, both MCP servers and the API (the hosted MCP server keeps the finished file behind a short-lived link for about five minutes so your assistant can fetch it; the original is still discarded at once). The architecture and data handling page has the full description.
One photo, one location to hide, a phone in your hand? Use the two-tap route in the platform section above. The workflow is for the batch, the full strip, and the file that is going somewhere that will keep whatever you leave in it.
FAQ
How do I remove metadata from a photo on Windows 11?
Right-click the photo in File Explorer, choose Properties, open the Details tab, click "Remove Properties and Personal Information", keep "Create a copy with all possible properties removed" selected and click OK. Windows writes a copy with " - Copy" in the name and the GPS and camera fields cleared. It removes most of the metadata, not all of it: the embedded thumbnail, editing-software blocks and Content Credentials can survive, so re-encode the file or run exiftool -all= when it has to be clean.
How do I remove the location from a photo on my iPhone?
Open the photo in Photos, tap the More button, then Adjust Info, Adjust Location and No Location (Apple's steps as of September 2026). To share without the location but keep it in your library, tap Share, tap Options at the top of the share sheet, and turn off Location; "Location Not Included" appears before you choose where to send it. Both remove the GPS tags only; the camera and date information stays in the file.
Can Google Photos remove the location from a photo on Android?
Only if Google Photos added it. Google's help page states that a location added automatically by the camera cannot be updated or removed in Google Photos; the Edit > Remove location control works on estimated or manually added locations. To stop future photos carrying a location, turn Save location off in your camera app's settings. To remove it from an existing photo, re-encode a copy with a converter or a dedicated app.
Does removing metadata reduce image quality?
exiftool does not touch the pixels, so quality is identical; it removes the headers and leaves the compressed image data as it was. A converter re-encodes, which is a new compression pass: at the same dimensions and a sensible quality the difference is invisible, and if you are resizing for the web anyway the re-encode is the step you wanted. The one quality point to watch with exiftool is color: use the FAQ 32 form that keeps the ICC profile.
Do Instagram, WhatsApp and Facebook remove metadata automatically?
For public posts, yes in practice: the platforms re-encode every upload and the EXIF, GPS included, does not survive on the public copy, according to published tests. The exceptions are the channels that send the original file: WhatsApp's document mode, Telegram's file mode, email attachments, AirDrop and iMessage keep everything, and WhatsApp's HD or best-quality mode kept the GPS in about a quarter of tests. Strip before sending on those.
How do I remove AI metadata or Content Credentials from an image?
Content Credentials (C2PA) are a signed metadata block in its own segment. Re-encoding the image removes it, and so does exiftool -jumbf:all= photo.jpg; a location-only removal does not. In our test, every Mochify output dropped the manifest, including the keep-metadata setting. What no metadata tool removes is a watermark embedded in the pixels, such as Google's SynthID, which is built to survive cropping, filters and compression.
What metadata does a photo contain?
A phone or camera JPEG carries an EXIF block with the camera make and model, exposure settings, dates and times, an orientation flag, a vendor maker note and, if location was on, GPS latitude, longitude, altitude, heading and the precision of the fix; plus an embedded thumbnail, a color profile and, on recent phones, an HDR gain map. Edited images add XMP and IPTC blocks (edit history, keywords, copyright) and often Content Credentials. On the iPhone 15 photo we measured, that came to 61 EXIF tags in 22,017 bytes, 13 of them GPS.
How can I check that the metadata is really gone?
On a computer, run exiftool photo.jpg and look for an empty list under EXIF, GPS, XMP and JUMBF; on Windows, Properties > Details should show no GPS or camera fields; on a phone, swipe up on the photo and look for a missing map and camera line. Check the file you are about to send, not the one in your library: Hide Location on a Mac and Options on an iPhone change the copy that leaves, not the original.
Got photos to share? Open the Mochify web app, drop them in and type strip the metadata; Magic Flow does the rest, and your images are processed in memory and never stored.