Guide · TagWipe

The "Modified with Clean Up" Tag on iPhone Photos: What Reddit Found, and How to Remove It

Didactic Initiatives · Updated August 4, 2026 · 6 min read

This one surfaced on Reddit before most people had read a word of Apple documentation about it. Someone in r/iphone erased a photobomber from a holiday photo, opened the info panel out of curiosity, and found a line that wasn't there before: Modified with Clean Up.

The thread that follows is always the same shape. Can other people see this? Does cropping remove it? Why is Apple tagging my own photo? Reasonable questions, and the top-voted answers are usually half right. Here's the actual mechanism.

What the tag is

Clean Up is Apple's generative eraser, introduced with Apple Intelligence in iOS 18. Because it fills the erased region with generated pixels, Apple treats the result as AI-assisted and records that in the file — a credit visible in the Photos info panel, alongside an IPTC digital source type value marking the image as containing AI-generated content.

Apple isn't being sneaky here; it's participating in the same provenance standards everyone else adopted. The friction is that the surface area is enormous. Clean Up is one tap inside the stock Photos app on hundreds of millions of phones, used mostly for utterly mundane edits — a bin lorry, a stranger's elbow, a smudge on a wall. Every one of those now carries an AI credit.

Answering the Reddit questions

"Can other people see it?"

Yes, if they get the file. The credit travels with the photo through AirDrop, iMessage, email and cloud file shares — none of those strip metadata. Anyone who receives it can open their own info panel and read it, and any metadata viewer shows it plainly.

More consequentially, platforms read it. Instagram, Facebook, TikTok and LinkedIn check provenance fields on upload, so a single Clean Up edit is enough to get an otherwise real photo labeled as AI-assisted. That's the part that turns a curiosity into an actual problem, and it's why these threads keep getting revived.

❌ "Just crop it / re-save it / duplicate it"

The most common wrong answer. Apple's editing pipeline is explicitly designed to preserve file metadata across edits — that's a feature everywhere else in the system. Cropping, adjusting, filtering, duplicating, and reverting to original all leave the credit exactly where it is.

❌ "Turn off location in the share sheet"

Also common, also wrong. That toggle drops GPS coordinates only. The Clean Up credit is a different field and is completely unaffected. Same for "All Photos Data" — it covers depth, edit history and Live Photo data, not provenance credits.

❌ "Revert to original, then edit again in another app"

Reverting restores the pixels but the credit is already written into the file's metadata. And if you re-edit with another AI-assisted tool, you've simply swapped one provenance tag for another.

⚠️ "Screenshot it"

Works, as it does for every metadata problem — a screenshot is a fresh file — and costs you the photo's resolution and colour profile. Acceptable for a quick share; a poor default.

⚠️ "exiftool -all="

Broadly right if you're at a computer. The caveat worth knowing: exiftool doesn't have a rule specifically targeting Apple's Clean Up credit field, so a blanket clear usually catches it but you should verify rather than assume. Several threads end with someone discovering the credit survived their command.

Actually removing it

The tag is a metadata field, so removing it means stripping that field. TagWipe looks for this specific credit — it's one of the things it was built for — along with C2PA manifests, IPTC and XMP provenance fields, and ordinary GPS and device EXIF:

1. Open TagWipe and select the photo, or the whole batch you're about to share.
2. Read the scan. If the Clean Up credit is present, it's named in the results rather than buried in a generic "metadata found" message.
3. Clean, choosing save a copy or replace the original.

The erased area stays erased. Removing the credit doesn't undo the Clean Up edit — that's pixel data, and it's untouched. You're removing the note describing how the edit was made, not the edit.

If you've used Clean Up casually over the past couple of years, a lot of your library is probably carrying this. Selecting an album and cleaning it in one pass is faster than auditing photo by photo, and you can see what's there first with a metadata check.

Can you avoid it in the first place?

Only by not using Clean Up. There's no preference to disable the credit — unlike Adobe, which lets you switch Content Credentials off in settings. If you want a photobomber gone without an AI provenance tag, use a non-generative approach: crop the person out, or use a clone/patch tool in an editor that doesn't self-report. That's a real trade-off, since Clean Up is genuinely good at this and the alternatives are more work.

The honest limit

Removing the credit removes the metadata-driven label. It does not remove invisible pixel watermarks — Apple hasn't been shown to add one via Clean Up, but schemes like Google's SynthID exist elsewhere and live in the image data, where no metadata tool can reach. And a platform's own classifier can always form its own opinion. What you're fixing is the case where a tag, not the picture, made the decision.