How to Remove EXIF Data from Photos for OnlyFans (Every Device)

Strip metadata on your own device, before a file goes anywhere. Every phone and desktop OS has a built-in way to remove the worst of it, and one free tool (exiftool) removes all of it. As of July 2026, OnlyFans and the major social platforms strip most EXIF from publicly served uploads, but DMs, customs, email attachments, and cloud links routinely pass the original file through untouched. So the rule that keeps you safe is simple: no file leaves your device with metadata, regardless of where it's going. This guide shows what your photos and videos carry, how to see it, and how to remove it on iPhone, Android, Windows, and Mac.

What EXIF data reveals about you

EXIF (exchangeable image file format) is a block of hidden data your camera writes into every photo at the moment of capture. You never see it in the image itself, but anyone who has the file can read it with free tools in seconds. Here's what typically rides along:

None of this is theoretical. In December 2012, journalists traveling with John McAfee posted a photo of him while he was hiding from authorities; the file still carried GPS coordinates, and the metadata placed him in Guatemala. The same year, a hacker known as w0rmer was identified by the FBI after posting a photo taken on an iPhone that embedded the GPS coordinates of his girlfriend's house. Both cases involved people with strong reasons to stay hidden and technical sophistication, and both were undone by a field they never looked at.

For creators, metadata is one of the eight exposure paths we map in how creators get doxxed, and it's among the cheapest for an attacker to check: no skill required, just a right-click on a file you sent them.

Do platforms remove EXIF data for you?

Mostly yes on public uploads, and that's exactly why creators get complacent. The stripping happens where you least need it and skips the places files actually leak. Here's the landscape as of July 2026:

Read the right-hand column top to bottom and the pattern is clear: your public feed, the thing you think of as most exposed, is the most protected. The private channels feel safe and are the least protected. A custom sent "as a file" so the buyer gets full quality, a sample shared through a Drive link, a collab folder synced with another creator: these deliver your original bytes, metadata included.

And platform stripping is a policy, not a promise. It can change, it can have gaps for certain formats, and you'll never be notified. Treat it as a bonus layer you happen to get, never as the plan.

How to check what a photo is leaking

Before changing anything, look at what your files carry right now. Pull up a recent photo from the phone you shoot content with:

• iPhone: open the photo in Photos and tap the info button (the circled "i"), or swipe up. You'll see capture date, device, lens, and, if location is embedded, a map.
• Android: open the photo in Google Photos and swipe up (or tap the three-dot menu, then Details). Location, device, and capture data appear if present.
• Windows: right-click the file, choose Properties, then the Details tab. Scroll for GPS, camera, and author fields.
• Mac: open the file in Preview, press Command-I for the inspector, and check the tabs. A GPS tab only appears when coordinates exist, so its presence is itself the answer.
• Everything at once: install exiftool (below) and run exiftool photo.jpg for a complete field-by-field dump, including things the built-in viewers don't show.

If you see a map under a photo taken at home, that's your address in every file that leaves your camera roll unprocessed. Fix the source (further down) and strip what you already have.

How to remove EXIF data on every device

The built-in tools remove the most dangerous fields quickly. The desktop tool at the end removes everything. Pick based on how much you send and how certain you need to be.

iPhone

You have three levels:

1. At share time (per send): in the share sheet, tap Options at the top, then turn off Location. iOS sends the photo without coordinates. This covers a one-off send, but you have to remember it every time.
2. On the library copy: open the photo, tap the info button, tap Adjust next to the map, and choose No Location. This removes location from the photo in your library, so future shares are covered. Other EXIF fields (device, timestamps) remain.
3. Full strip: iOS has no built-in "remove all metadata" button. The Shortcuts app can do it: the Convert Image action has a Preserve Metadata toggle; build a shortcut that converts to JPEG with that toggle off and you get a clean copy. Otherwise, run files through a desktop pass before they go anywhere.

Android

Menus vary by manufacturer, but the pieces are consistent:

1. Google Photos: open the photo, swipe up for details, and tap the edit (pencil) icon next to the location entry to change or remove it. Note that the "Remove geo location when sharing by link" option in Google Photos settings applies only to share links, not to files you attach or send directly.
2. Samsung Gallery: open the photo, tap Details, then Edit, and remove the location data there.
3. Full strip: as on iPhone, a complete wipe needs either a dedicated metadata-removal app or a desktop pass. If you batch content weekly, the desktop pass is less work than it sounds.

Windows

Right-click the file, choose Properties, open the Details tab, and click Remove Properties and Personal Information. Choose Create a copy with all possible properties removed. This handles the standard fields (GPS, camera, author) and is fine for everyday use; a few exotic vendor-specific fields can survive it, which is why high-stakes files should get the exiftool treatment instead.

Mac

Preview can remove location: open the file, press Command-I, go to the GPS tab, and click Remove Location Info. The Photos app can export clean-ish copies too: File, then Export, and uncheck Location Information in the export dialog. Neither removes every field, so for full stripping, use exiftool.

exiftool: the batch answer

ExifTool is the free, standard tool for reading and removing metadata. It runs on Mac (brew install exiftool), Windows, and Linux, and it's the one method in this guide that removes every removable field and lets you verify the result.

Strip one file:

exiftool -all= -overwrite_original photo.jpg

Strip an entire export folder before anything in it gets sent:

exiftool -all= -overwrite_original /path/to/export-folder

Verify a file is clean:

exiftool photo.jpg

One caveat: -all= also removes the color profile, which can subtly shift how colors render on some screens. If you notice a difference, keep the profile while stripping everything else:

exiftool -all= --icc_profile:all -overwrite_original photo.jpg

The workflow that sticks is a single folder: everything you export lands in it, the exiftool command runs on it, and only then do files get uploaded, sent, or synced. One command per batch, and you stop depending on memory.

What about video metadata?

Videos carry the same kind of data in the file container: GPS coordinates, creation timestamps, and device make and model, written by your phone at recording time. The risk profile is arguably worse than photos, because video is what gets sent directly to buyers as customs, at full quality, "as a file".

Inspect a video the same way: exiftool video.mp4 lists what's inside. To remove it, exiftool handles the common phone-written fields, or use ffmpeg to rewrite the container without metadata while copying the video and audio streams untouched:

ffmpeg -i input.mp4 -map_metadata -1 -c:v copy -c:a copy output.mp4

No re-encode, no quality loss, done in seconds even for long files. Spot-check the output plays correctly, then send that copy.

Files exported from editing apps (CapCut, Premiere, DaVinci) generally carry metadata about the export rather than the original shoot, but "generally" is doing work in that sentence: some workflows copy source metadata through. Check one export from your actual pipeline once, and you'll know how your tools behave.

Stop the data being collected at the source

Stripping handles files that exist. Prevention means new files start cleaner:

• iPhone: Settings, then Privacy & Security, then Location Services, then Camera: set it to Never. Do the same for any third-party camera app you shoot with.
• Android: open your camera app's settings and turn off the location tag option (names vary: "Save location", "Location tags", "Geotagging").

If you run a separate device for creator content, make this a day-one setting on it. Prevention removes the single worst field (GPS) from every future file, but it doesn't replace the stripping step: timestamps, device model, and software fields are still written, and everything you shot before the change still carries coordinates.

Metadata beyond EXIF

A few identity leaks travel with your files without technically being EXIF, and a metadata routine should catch them too.

Filenames. IMG_20260710_kelseys_apartment.jpg identifies you with zero metadata tools. So does a default name that matches a numbering sequence from your personal accounts. Rename files to neutral names before they leave your device; it takes seconds and it's the kind of leak stripping tools don't touch.

Live Photos. An iPhone Live Photo embeds about three seconds of video with audio around the still: your voice, a TV in the background, someone saying your name from the next room. Share Live Photos as stills (the share sheet's Options menu lets you send "as photo" without the Live component), or turn Live off entirely on the device you shoot content with.

Edited doesn't mean clean. Many photo editors deliberately copy the original EXIF into their exports, because regular users want to keep their data. Running a file through a filter app is not a stripping step. Only an actual removal pass is a removal pass.

Screenshots. Screenshotting a photo produces a new file whose metadata describes the screenshot, not the original shot. It works as a quick fix for a single image, at the cost of resolution and quality. Don't build a pipeline on it when the real tools are this fast.

The metadata hygiene checklist

Run the one-time items today, then fold the recurring ones into your export routine:

• Camera location tagging off on every device that shoots creator content (one-time)
• Owner and copyright name fields cleared in any dSLR or editing suite you use (one-time)
• Checked one recent photo and one recent video from each device to see what they carry (one-time)
• A stripping step in the export routine, before files are uploaded, sent, or synced (every batch)
• Customs, samples, and DM media go through the same strip step as feed content, no exceptions (every send)
• Files renamed to neutral names before they leave the device (every batch)
• Live Photos shared as stills, or Live disabled on the creator device (ongoing)
• Originals with location data deleted or kept off synced cloud folders (ongoing)
• Spot-check one served file per platform every few months, since stripping policies change (recurring)

If you keep one habit from this page, make it the fourth item. A pipeline that strips every batch protects you on the days you're tired, rushed, and not thinking about metadata, which is when leaks happen.

What metadata stripping doesn't protect

A metadata-clean photo of your face is still a photo of your face. Stripping EXIF closes one exposure path; it does nothing about reverse image search, the room behind you, tattoos, reflections, or your voice in a video. Those need their own layers.

The face layer matters most. If your content shows your real face, EXIF hygiene is tidying the margins. Our comparison of mask vs crop vs blur breaks down the face-hiding methods; the approach that keeps a natural face in your content is AI face replacement, which swaps your face for a consistent synthetic one while keeping your pose and lighting:

You can try that workflow on a test photo in the NeoFace demo. A tool that deletes your uploads after processing fits naturally next to a metadata routine: both exist to minimize the copies of identifying data sitting on other people's servers.

Metadata stripping is step three of the publishing pipeline in our staying anonymous playbook, and one of 25 items in the OnlyFans anonymity checklist. If you're securing an account end to end, work through those; this page is the deep version of one layer.

Final word

Metadata doxxing is the most preventable exposure a creator faces, because the fix is mechanical: turn off camera location today, put one stripping command (or the built-in equivalent) into your export step, rename files before they go out, and route customs through the same pipe as everything else. No judgment calls, no discipline battles, just a routine that runs the same whether you're posting a feed photo or sending a 2 a.m. custom. Set it up once, and the field that undid people far more paranoid than you becomes the one thing you never have to think about again.