How to Remove Location Metadata from iPhone Photos

Rasty Turek — Mon, 28 Sep 2026 22:08:45 +0000

Remove GPS location from iPhone photos before sharing, stop new photos from saving location, and check what metadata remains.

To remove location from an iPhone photo before sharing, open the photo, tap Share, tap Options, and turn Location off. To remove stored location from the original item, open the photo info screen, tap the location, and choose No Location or adjust the location if your iOS version offers it.

Three different jobs people mix up

Location privacy has three separate workflows. Pick the one that matches what you need today.

Method	Changes original file?	Best for	Risk
Share Options location toggle	No	One-time share	Easy to forget next time
Photos app location adjustment	Yes, for that item	Existing private photo	Other metadata can remain
Camera location off	Future photos only	Ongoing privacy	You lose place search in Photos
Metadata stripping shortcut or app	Usually creates a copy	Public posting	You must trust the tool

The share toggle helps for one send. It does not clean your library. Camera location settings help future photos. They do not rewrite old ones.

Remove location when sharing one photo

Open Photos.
Select the photo or video.
Tap Share.
Tap Options at the top of the share sheet.
Turn Location off.
Share the photo.

This is the fastest fix before sending a photo through Messages, Mail, AirDrop, or a marketplace app. It keeps the original item unchanged in your library.

Remove stored location from an existing photo

Open the photo in Photos.
Swipe up or tap the info button.
Tap the location or map area.
Choose No Location or adjust the location if your iPhone shows that option.

Do this for photos you plan to keep but might share again later. It reduces the chance that you forget the share toggle next time.

Stop new photos from saving GPS location

Open Settings.
Tap Privacy & Security.
Tap Location Services.
Tap Camera.
Choose Never.

This stops the Camera app from adding GPS coordinates to new photos. Other camera apps may have their own settings, so check those separately.

Check the shared copy

Do not assume the job worked. Send the photo to yourself, save the received copy, then open the info screen and check whether a map still appears.

For a deeper check, use the free photo metadata viewer and remover to inspect GPS, EXIF, editing, and supported provenance fields in the exact copy you plan to share. Some websites strip metadata. Some preserve it. Some generate a new compressed copy. Treat each site as a separate test.

Marketplace and social posting checklist

Location metadata is not the only leak. A photo can show your house number, school name, license plate, reflection, shipping label, Wi-Fi network, or calendar on a wall.

Before posting photos of furniture, cars, pets, receipts, school events, or anything near your home, check both the file metadata and the image itself.

Vaultaire protects files while they stay inside the vault. If you export a file and post it publicly, you still need to check metadata and visible details before sharing.

When location removal is not enough

GPS coordinates are only one part of the problem. A photo can reveal a place without metadata if the image shows a street sign, school logo, window view, parcel label, badge, vehicle plate, or the inside of a home. A cleaned file can still identify you if the picture itself contains enough clues.

Before you post a photo publicly, zoom in. Check corners, reflections, mirrors, screens, paperwork, and background objects. If the photo is for a marketplace listing, crop tightly and retake it against a plain surface. If the photo is evidence, keep an untouched original in a private archive and share a cleaned copy.

Build a repeatable sharing habit

Use the same workflow every time you share sensitive images: clean the copy, send it to yourself, inspect the received file, then share that verified copy. This feels slow once. After a few rounds, it becomes faster than wondering whether an upload exposed your home address.

For repeat work, keep a "share-safe" folder separate from your originals. That gives you a clear boundary between archive copies and public copies, and it reduces the chance that you post the wrong version.

Sources

Password help

FAQ

Does turning off Camera location remove location from old photos?

No. It affects new photos only. Remove location from old photos one by one or use a metadata stripping workflow that creates cleaned copies.

Does AirDrop keep location metadata?

AirDrop can send the original file with metadata unless you turn off Location in the share options. Check the file before sending sensitive photos.

Should I use a metadata removal app?

Use one only if you trust it with the photo. For a few iPhone photos, Apple's built-in location controls are usually enough.

Originally published at https://vaultaire.app/guides/remove-location-metadata-iphone-photos/.

Pattern-Based Key Derivation: How Vaultaire Turns a Drawn Shape into AES-256 Encryption

Rasty Turek — Sun, 15 Mar 2026 06:16:15 +0000

Most vault apps use a 4-6 digit PIN as an access code. The PIN unlocks the app, and the files behind it may or may not be encrypted. Vaultaire does something different: the pattern you draw IS the encryption key material.

Here's how the pipeline works:

User draws a pattern on a 5x5 grid, connecting at least 4 dots
The dot sequence is serialized into a byte array
The byte array is fed into PBKDF2 with a per-vault random salt and 600,000 iterations
PBKDF2 outputs a 256-bit key
That key is used for AES-256-GCM file encryption with a unique IV per file
When the app closes, the key is wiped from memory

The interesting part is step 3. PBKDF2 (Password-Based Key Derivation Function 2) is deliberately slow. Each guess costs ~1ms of computation. An attacker trying a billion patterns faces a million seconds — about 11.5 days — per vault. And they don't know which pattern is "correct" because there's no verification oracle: every pattern produces a valid-looking key.

Why not Argon2? CryptoKit on iOS doesn't support it natively. Bringing in a third-party implementation means trusting unaudited code for the most security-critical operation in the app. PBKDF2 at 600K iterations with unique salts meets NIST SP 800-132 recommendations. When Apple adds Argon2 to CryptoKit, I'll migrate.

The 5x5 grid gives roughly 53 billion possible patterns (connecting 4+ dots with order mattering). Combined with the slow KDF and per-vault salt, this produces usable security for the consumer threat model: casual snooping, device seizure, and coercion scenarios.

For the full architecture including ChaCha20 metadata encryption and Secure Enclave integration.

DEV Community: Rasty Turek