Remove GPS Location Data From Photos

Remove GPS Location Data from Photos

Every smartphone photo carries an invisible passenger. Modern cameras embed GPS coordinates directly into the EXIF metadata the moment you press the shutter,¹ recording latitude and longitude precise enough to identify a specific house rather than just a neighborhood.² Because that data rides silently inside the file, sharing the image means sharing the location too, even when nothing in the frame itself reveals where you were standing. The Electronic Frontier Foundation has documented this risk for over a decade, warning that a single photograph can disclose a home address, a workplace, or a child's school in seconds. Consequently, the danger here is not theoretical: anyone who downloads the original file, through a message, an email, or an unprotected upload, can extract those coordinates with free software in moments. This guide explains what gets exposed and how scrubbing removes it for good.

How precise is the location hidden in a photo

GPS tags inside EXIF store latitude and longitude to roughly six decimal places, a resolution that resolves to a few meters on the ground.² Because of that precision, a single photo posted with metadata intact can pinpoint a specific house, not just a general area. Reverse lookup tools make extracting those coordinates trivial; no specialized skill is required, only a file and a few seconds.³

Why six decimal places matters

At six decimal places, a GPS coordinate narrows location to roughly the width of a single room, while three decimal places would only narrow things to a neighborhood block. The extra precision phones record by default is exactly what turns a casual photo into a usable address. Consequently, the danger is not theoretical: anyone who downloads the original file, whether through a direct message, an email attachment, or an unprotected upload, can extract the coordinates with free, widely available software in seconds.

Four decimal places, by comparison, only resolve to about eleven meters, enough to place a photo somewhere within a building's footprint but not to identify which room. That middle band shows why the extra two digits in a six-decimal reading matter so much: each additional decimal place shrinks the margin by roughly a factor of ten, moving the estimate from block-level to room-level in only a few steps.

Why platform handling is not a safety net

Some major platforms let you choose whether location data is shared from uploaded photos.⁴ For the average post, that built-in control covers most of the everyday concern. Yet this protection only applies to the copy other users see; it does not extend to direct file shares, marketplace listings, forum attachments, or any service that passes your file through unprocessed.

Furthermore, platform behavior changes without notice and varies between feed posts, direct messages, and story formats on the very same app, so a habit built around 'the platform handles it' can break down the moment you switch features. Because you cannot verify in advance whether a given upload path strips metadata, scrubbing the file yourself before you share it removes the uncertainty entirely. Building on this, treating every photo the same way, regardless of where it is headed, is simpler than tracking which feature on which platform behaves how this month.

What gets removed when you scrub a photo

Scrubbing removes the EXIF segment in its entirety, not just the GPS tags. That includes camera make and model, lens information, the exact capture timestamp, and any XMP or IPTC blocks layered on top by editing software.⁵ Removing all of it at once, rather than picking individual fields, is what closes every avenue a viewer could use to trace the file back to a device or a moment. The same thoroughness is why CapyToolkit's scrubber is effective against both obvious GPS tags and the deeper metadata structures most people never think about.

What stays the same

The pixel data itself is untouched. Removing metadata does not recompress, crop, or alter the visible image in any way, so the photo you share looks identical to the original; it simply carries no location trail with it.⁶ File size typically decreases slightly, since the removed segment is no longer part of the file. The visual result is the same whether the original came from a flagship phone or a ten-year-old digital camera.

How the GPS IFD structure works inside a photo file

The GPS IFD (Image File Directory) is a sub-structure inside the main EXIF block, pointed to by tag 0x8825 (GPSInfo IFD Pointer). Inside this sub-IFD, individual tags store specific pieces of location data: tag 0x0001 (GPSLatitudeRef) records North or South, tag 0x0003 (GPSLongitudeRef) records East or West, tag 0x0005 (GPSAltitudeRef) indicates whether altitude is above or below sea level, and tag 0x0007 (GPSTimeStamp) records the UTC time the GPS fix was obtained. Deleting the GPS IFD pointer at tag 0x8825 removes the entire sub-structure in one operation, which is more reliable than deleting individual GPS tags one by one.

Why removing the pointer is safer than editing individual fields

If you delete only the GPSLatitude and GPSLongitude tags but leave the GPS IFD pointer intact, some EXIF readers will still detect the presence of a GPS IFD and report that location data was once present, even though the actual coordinates are gone. A thorough scrub has to remove the GPS pointer, not just the coordinates: eliminating tag 0x8825 clears the entire GPS sub-structure, so no reader can detect that GPS data ever existed. A full scrub handles this automatically, removing the pointer and every tag inside it in a single pass.

When to use this

Use this before uploading photos to social media, listing products on marketplaces, posting on forums, or sharing images with anyone outside your immediate circle. Apply it as a default step for every photo, not just the ones that obviously show a recognizable location.

Examples

GPS Latitude: 51.5074° N
GPS Longitude: 0.1278° W
Camera: Apple iPhone 15
Date: 2024-11-15 09:23:11

GPS Latitude: [removed]
GPS Longitude: [removed]
Camera: [removed]
Date: [removed]

Remove EXIF Metadata from iPhone 17 Pro Photos

Three rear lenses define the iPhone 17 Pro's camera system: a 48-megapixel Fusion main sensor, a 48-megapixel Ultra Wide, and a redesigned tetraprism Telephoto carrying a sensor 56 percent larger than its predecessor, which supports 4x and 8x optical-quality zoom.¹

Regardless of which of the three lenses captures a shot, every resulting photo carries the same EXIF metadata structure underneath, including GPS coordinates whenever Location Services is enabled for the Camera app, a setting that ships on by default.² Because that default is easy to overlook, most new iPhone 17 Pro owners are recording their exact location in every photo without realizing it. Consequently, a photo taken on a hike, at home, or at work all carry the same risk: anyone who inspects the file's metadata can extract the coordinates directly. Use this tool to check exactly what metadata your iPhone 17 Pro photos carry before you share, sell, or post any of them.

Specifications¹

Why HEIC is the first hurdle for iPhone 17 Pro photos

Apple's default capture format for the iPhone 17 Pro is HEIC, a more efficient format than JPEG at comparable visual quality. HEIC files store the same kind of metadata as JPEG, including GPS coordinates, camera model, and capture timestamp, yet the underlying file structure differs enough that this tool does not parse it directly.³ Consequently, the first step for most iPhone 17 Pro owners is a quick conversion, not a limitation of what the scrubber can ultimately remove.

Converting HEIC to JPEG before scrubbing

Open the photo in the Photos app, tap Share, choose Options at the top, and select JPEG instead of the default. HEIF is an industry-standard container built on the same ISO Base Media File Format structure as HEVC, which is why metadata sits in a different box layout than the APP1 segment a JPEG uses.⁴ Alternatively, switch your camera's capture format in Settings > Camera > Formats to "Most Compatible," which saves all new photos as JPEG going forward rather than requiring a per-photo conversion. Either path produces a file the scrubber can read and clean directly.

What GPS precision means for a 17 Pro photo

When Location Services is enabled for the Camera app, every photo from any of the three 48-megapixel lenses on the 17 Pro records latitude and longitude precise enough to identify a specific location, not a general area. Because the tetraprism Telephoto and the redesigned Ultra Wide are the headline new hardware on this model, some users assume metadata behavior differs by lens; it does not.

Lens choice does not alter the metadata profile

GPS, device model, and capture timestamp are written identically regardless of which lens took the shot, whether that is a wide group photo, a tight 8x zoom of a distant subject, or anything between.² Furthermore, switching between lenses mid-session does not reset or alter how the Camera app handles location tagging: the same Location Services permission governs every frame from every lens for the entire session. Treat a Telephoto shot with the same caution as a standard wide photo, since the underlying metadata risk is unchanged.

How capture mode changes what metadata the iPhone 17 Pro records

The iPhone 17 Pro records different metadata depending on which capture mode is active. A standard HEIF photo records basic EXIF fields: camera model, exposure settings, GPS coordinates, and timestamp. A ProRAW photo records all of those plus an extensive set of Image Signal Processor parameters, including the number of frames merged, the neural network models applied, and the white balance adjustments made during the computational merge. ExifTool exposes those Apple-specific parameters as a distinct MakerNote group, alongside tags such as ImageCaptureType and a run of Apple Image Processing fields, separate from the standard EXIF block.⁵

Photos taken in Cinematic mode embed a depth map as a separate QuickTime metadata track, which records the distance of each pixel from the camera lens and enables the rack focus effect in playback. This depth track persists alongside the EXIF block, and it is easy to overlook if you only inspect standard fields, which is exactly why a full pass needs to find the hidden depth track in a Cinematic clip, not just the visible EXIF fields.

Why a single scrub handles every capture mode

Regardless of which mode produced the photo, the scrubber removes the entire EXIF block, the XMP data, and any QuickTime metadata tracks embedded in the file. A standard HEIF photo and a ProRAW photo from the same iPhone 17 Pro both get fully cleaned by the same scrubbing step. The scrubber does not need to know which mode was active; it locates and removes every metadata segment in the file, leaving only the pixel data behind. For iPhone 17 Pro users who switch between standard, ProRAW, and Cinematic modes within a single session, one consistent scrubbing habit covers every file regardless of how it was captured.

This uniformity extends to video capture as well as photos: Apple's own guidance describes Location Services on the Camera app as gathering coordinates for photos and video the same way, without carving out an exception for Cinematic mode's depth-map recording. That means the GPS coordinates embedded in a Cinematic clip come from the identical permission and pipeline as a still HEIF photo, even though the file also carries the separate depth track. Treating video capture with the same caution as a still photo closes a gap that is easy to miss if you assume metadata risk is a photo-only concern.

Remove EXIF Metadata from Google Pixel 10 Pro Photos

Someone sharing a night shot from a Pixel 10 Pro rarely stops to think about metadata, since the photo itself already feels like the product of heavy computational work. The Pixel 10 Pro pairs a 50-megapixel main sensor with two 48-megapixel ultra-wide and telephoto lenses, the telephoto reaching true 5x optical zoom and up to 100x digital Pro Res Zoom.¹ Reviewers rank its computational photography as the most reliable in difficult lighting among current flagships.² The more aggressively a phone processes an image computationally, the more users tend to assume metadata has been cleaned up as part of that same process, which is a mistaken inference this page corrects. Every shot still carries standard EXIF metadata regardless of how much AI processing went into the final image, including GPS coordinates when location access is granted.

Specifications¹

Why three high-resolution lenses do not mean three metadata profiles

With a 50-megapixel main sensor and two 48-megapixel secondary lenses, the Pixel 10 Pro produces some of the largest file sizes in its class. Larger files sometimes lead users to assume more metadata is packed in alongside the extra pixel data, but resolution and metadata are unrelated. A 50-megapixel shot from the main sensor and a 48-megapixel shot from the telephoto carry an identical EXIF structure, just scaled to a larger image. The extra file size comes entirely from pixel data, not from any additional GPS, device, or timestamp fields tucked away in the metadata block. Scrub whichever lens produced the phone's largest shot and you clean the exact same metadata footprint as every smaller file alongside it.

Computational photography and what stays invisible

Reviewers consistently note that the Pixel line processes images more intelligently than competitors, often producing better results in difficult lighting than phones with stronger raw hardware specs.² All of that processing happens to the pixel data itself, adjusting exposure, blending frames, and reducing noise. None of it touches the separate metadata segment, which is written based on sensor readings and device state at capture time, independent of how the final image gets rendered.

Two pipelines that never touch each other

The imaging pipeline and the metadata-writing pipeline are entirely separate systems on the Pixel 10 Pro. EXIF is organised into its own Image File Directories stored alongside the image data, which is why a processing pass over the pixels leaves every one of those directories untouched.³ One blends frames and adjusts exposure to produce the final picture; the other reads sensor and device state at the moment of capture and writes it into the EXIF block. Changes to how aggressively the first pipeline processes a shot have no effect whatsoever on what the second pipeline records.

What the Tensor G5 chip writes into Pixel photo metadata

Google's Tensor G5 processor handles computational photography tasks like Magic Eraser, Best Take, and Night Sight by running neural network models directly on the phone's ISP pipeline.⁴ When these features activate, the camera writes a processing history into the EXIF MakerNote field, including which AI models ran and what adjustments they applied. A photo processed with Night Sight records the number of frames merged and the exposure time per frame, while a photo edited with Magic Eraser records that the object removal tool was used, though it does not record what was removed.

Why AI processing history matters for privacy

The processing history in the MakerNote field reveals more than most users expect. A photo with Night Sight metadata tells a viewer that the shot was taken in very low light, which narrows down the possible locations and times. A photo with Magic Eraser metadata tells a viewer that something was deliberately removed from the frame, which raises questions about what was there originally. Scrubbing removes the entire MakerNote block, so no AI processing history survives in the cleaned file.

Scrubbing Pixel photos before posting to Google services

Google Photos, Google Drive, and Gmail all process uploaded images through Google's server-side infrastructure, which can read and index EXIF metadata for features like automatic album creation, location-based search, and ad personalisation.⁵ Even if you disable location services on the camera, photos edited in Google Photos may retain metadata from the original capture that Google's systems can still read.

Why local scrubbing protects you from server-side processing

Scrubbing a photo before uploading it to any Google service ensures that no EXIF, XMP, or MakerNote data ever reaches Google's servers. The platform cannot index metadata that was never present in the uploaded file. For Pixel 10 Pro users who share photos through Google Photos or attach them to Gmail messages, a quick scrub before upload is the only way to guarantee that GPS coordinates, device identifiers, and AI processing history stay off Google's infrastructure entirely.

Google Photos does build in a sharing-level safeguard: locations stay private by default, and a shared album or link will not surface location details unless you explicitly opt in. That protection, however, covers what other Google Photos users see in the app; it has no bearing on whether the underlying file, once downloaded outside the platform, still carries the coordinates. Scrub before you upload if you want to stop Google from indexing your photo's location, since a recipient who saves the shared photo to their own device can still find whatever metadata the file arrived with, regardless of the sharing-level toggle Google applies inside its own interface.

Remove EXIF Metadata from Samsung Galaxy S25 Ultra Photos

Samsung's per-share toggle removes GPS from one outgoing copy, while a permanent scrub removes it from the file itself for good, and confusing the two leaves most of your photo library still carrying full metadata. The Galaxy S25 Ultra is widely rated as having the best zoom camera among current flagship phones, pairing multiple telephoto lenses with AI stabilization for consistent results at a distance.¹ Like every camera phone, it embeds GPS coordinates, device model, and capture time into every photo's EXIF data when location access is granted.² Relying on the one-time toggle creates a false sense that the problem is solved everywhere, when in reality it only ever covers that single transfer. Use this tool to check and remove that metadata before sharing a photo outside your immediate circle.

Specifications¹

What Samsung's built-in removal does and does not cover

Samsung has offered a Gallery-level location removal toggle since the Galaxy S21, accessible from the share sheet when sending a photo to another app or contact.² This is a genuinely useful feature, but it operates on a per-share basis: it strips GPS from the copy being sent in that moment, while the original photo stored in your Gallery retains its full metadata indefinitely. Consequently, if you later forward the same photo through a different app, or someone gains access to your device gallery directly, the unmodified original with intact GPS data is still there. Checking the metadata table once per photo in the scrubber, even after using the Gallery toggle on a separate occasion, confirms nothing was missed.

Why a permanent scrub differs from a per-share toggle

Running a photo through a dedicated scrubber produces a new file with metadata removed at the file level, rather than stripping it only for one specific transfer. This matters if you plan to use the same photo across multiple platforms, since each share sheet decision on Samsung's toggle is a separate choice you have to remember to make every time, and a missed toggle on even one of those shares leaves the original metadata exposed. Scrub the photo once, save the cleaned version, and reuse that file for every platform going forward, so there is no need to re-toggle anything per share. CapyToolkit makes this a one-time step that covers every future use of the photo without requiring you to remember the toggle for each share.

What Samsung's Scene Optimizer writes into your photos

Samsung's Scene Optimizer feature, powered by the Galaxy S25 Ultra's AI processing pipeline, identifies up to 30 scene categories including food, pets, landscapes, and sunsets, then adjusts colour saturation, white balance, and contrast to match the detected scene.³ The adjustment happens automatically on every shot without any user confirmation, which is convenient for getting vibrant results straight from the camera but easy to forget when thinking about metadata.

Scene classification gets written to the EXIF MakerNote

What most users do not realise is that the scene classification itself gets written into the EXIF MakerNote field as a proprietary XML tag. ExifTool lists a dedicated Samsung MakerNote group alongside the standard EXIF tags for exactly this kind of vendor-specific data, and Samsung's own note records Scene Optimiser as one of the entries in it.⁴ The tag does not affect how the image looks, but it does reveal which scene mode the camera selected, which a viewer could use to infer the type of environment where the photo was taken. Because the MakerNote field sits outside the standard EXIF tags that most image viewers display by default, this classification remains hidden unless someone specifically parses the proprietary block, which is precisely the kind of detail that survives unnoticed through ordinary sharing.

Why AI processing metadata matters for privacy

Scene Optimizer metadata is not the most sensitive field in your EXIF data on its own, but it adds a layer of information you may not want a stranger to have once combined with GPS coordinates and a timestamp. A scene classification of "food" taken at 12:15 inside a specific restaurant narrows down where you were eating on a particular day, which is why CapyToolkit removes the Scene Optimizer tag along with every other metadata field, leaving no trace of the camera's AI decisions.

HEIF versus JPEG on the S25 Ultra: what changes for metadata

The Galaxy S25 Ultra defaults to JPEG in most regions, but switching to HEIF in Camera settings changes how metadata gets stored at the container level.⁵ HEIF files use the ISO Base Media File Format, which stores EXIF data inside an Exif box rather than in a dedicated APP1 segment the way JPEG does. The fields themselves, GPS coordinates, device model, capture timestamp, and lens data, remain identical in content. The difference is structural, not informational.

Converting formats before sharing

When you switch from JPEG to HEIF or the reverse, the metadata gets rewritten into the new container format but the values stay the same. This means a photo converted from HEIF to JPEG still carries its original GPS coordinates and device information in the new file format, which is why you should always scrub the final output format before sharing it.

If you shoot in HEIF and want to share the photo on a platform that does not support the format, the phone's Quick Edit feature converts the file to JPEG and rewrites the metadata into the standard TIFF-based EXIF structure that most tools expect. Since the converted file is what actually leaves your phone, scrub the JPEG your Quick Edit exports; a single pass on that final output catches every field the camera wrote, whether the original was HEIF or JPEG.

Remove EXIF Metadata from OnePlus 13 Photos

Hasselblad for Mobile tunes color science and tone mapping on the OnePlus 13, not anything related to privacy or metadata. The OnePlus 13 runs a fifth-generation version of that system: a 50-megapixel Sony LYT-808 main sensor, a 50-megapixel ultra-wide using a Samsung Isocell JN5 sensor, and a 50-megapixel periscope telephoto offering 3x optical zoom extendable to 10x with AI assistance.¹ A phone marketed so heavily around color science and computational tuning can quietly mislead users into assuming that more processing means more privacy protection, when the two are entirely unrelated. As with any camera phone, every photo records GPS, device, and timestamp data in its EXIF metadata when location access is enabled.

Specifications¹

Three matched 50MP sensors, one shared metadata structure

Unlike many flagship phones that pair a high-resolution main sensor with lower-resolution secondary lenses, the OnePlus 13 uses 50-megapixel sensors across all three rear cameras, unified under Hasselblad color calibration.² At first glance that uniform resolution might suggest the three lenses behave identically in every respect, but the way they write metadata is only one part of the picture.

All three lenses write the same EXIF block

Despite this unusually consistent hardware lineup, the EXIF metadata written to each photo follows the same standard structure regardless of which of the three lenses captured it, recording GPS, device model, and timestamp identically across the main, ultra-wide, and telephoto cameras. The GPS coordinates themselves live in their own Image File Directory pointer tag, 0x8825, a single entry that hands off to a separate location IFD within the file.³ Whichever sensor produced a given shot, the file you eventually share carries the exact same set of fields, so there is no lens-specific exception to watch out for.

Where the AI-extended zoom comes in

The periscope telephoto lens reaches 3x true optical zoom, with OnePlus's AI Telephoto mode extending that to 10x through digital enhancement. Because that AI extension happens after the optical capture, some users assume it might alter how the file is tagged. It does not. The zoom mode used affects only image processing and framing, leaving the metadata segment untouched.

Whether you shoot at the native 3x optical range or push into the 10x AI-assisted range, the camera writes GPS, device model, and timestamp fields the same way every time. The visible difference between the two zoom levels lives entirely in the pixel data, while the metadata stays consistent regardless of how far you have zoomed in, and that consistency is exactly why a single scrub habit covers every shot from this lens.

What Hasselblad for Mobile does and does not change about metadata

Hasselblad for Mobile on the OnePlus 13 is a colour science partnership, not a metadata partnership. The collaboration tunes white balance, colour saturation, and tone mapping through a custom ICC colour profile that gets applied to the pixel data at capture time.⁴ This ICC profile is stored in the EXIF ColorSpace tag and can be read by colour-managed applications like Adobe Lightroom or Apple Photos to ensure accurate colour reproduction on calibrated displays.

Why colour profile metadata is not a privacy risk

The ICC profile in the EXIF data describes how colours should be rendered, not where or when the photo was taken. It contains no GPS coordinates, no device serial number, and no timestamp. For privacy purposes, the Hasselblad ICC profile is harmless metadata that you can leave in the file without any risk. However, scrubbing removes it along with everything else, which means the cleaned file will rely on the display device's default colour profile rather than the Hasselblad-tuned one.

PetaPixel's coverage of the OnePlus 13 launch describes Hasselblad's contribution in exactly these visual terms: film-style filters that emulate classic looks, a Portrait Mode tuned to replicate specific Hasselblad lens characteristics, and a Master Mode that lets you adjust tint, contrast, saturation, sharpness, and vignetting by hand. Every one of those controls changes how the pixel data looks once the shutter closes; none of them touch the EXIF fields the camera writes at capture time. That separation is consistent with how the ICC ColorSpace tag works: it travels alongside the metadata block without carrying any of the location or device information a privacy-conscious scrub is meant to remove.

Scrubbing photos from the OnePlus 13's Hasselblad XPAN mode

The OnePlus 13 includes an XPAN mode that mimics the aspect ratio and colour rendering of Hasselblad's medium format XPAN camera, producing images in a 65:24 panoramic format.⁵ XPAN photos carry the same EXIF metadata structure as standard photos, including GPS coordinates and device identifiers, but they also include a custom MakerNote tag that records the XPAN mode was active. A full scrub is the only way to clear the XPAN tag from a panoramic shot, since the tag itself is not privacy-sensitive but still reveals which in-camera film simulation processed the photo.

A consistent scrubbing habit across all modes

Whether you shoot in standard 4:3, ultra-wide 120-degree, 3x telephoto, or XPAN panoramic mode, the same EXIF structure applies and the same scrubbing step removes all metadata. One scrub covers every mode the OnePlus 13 offers, so you do not need to remember which modes write more metadata than others. Building this habit once means every future photo from every lens and every capture mode comes out clean without a second thought.