crwipe
For creators who'd rather not advertise the recipe

Strip the CR tag
from your human posts.

Drop a pic. We pull the Content Credentials metadata — that's the C2PA / JUMBF blob behind LinkedIn's AI image badge — and hand you back a clean copy. 10 seconds. No login. Then we forget you were ever here.

Used by 237 creators this week

Live demo

The badge that's been quietly tanking your reach.

One side is what gets posted today. The other is what we send back.

BEFORE — CR presentas uploaded
AK
Alex Kuznetsov
Founder · 2h · 🌐

Spent the weekend redesigning our onboarding. Conversion is already up 14%. Sometimes the answer really is "make it simpler." 👇

post image
Content credentials
24812 comments · 4 reposts
Like Comment Share
AFTER — CR strippedvia crwipe
AK
Alex Kuznetsov
Founder · 2h · 🌐

Spent the weekend redesigning our onboarding. Conversion is already up 14%. Sometimes the answer really is "make it simpler." 👇

post image (clean)
— no badge —
1,40284 comments · 39 reposts
Like Comment Share
How it works

Three steps. Roughly ten seconds.

The kind of tool you forget you're using until you need it twice in a row.

01

Drop the pic.

Drag from Finder, Lightroom export, Photoshop, whatever. PNG, JPEG, WebP up to 10 MB.

02

We yank the metadata.

C2PA manifest, JUMBF box, the whole Content Credentials chain. Pixels stay byte-for-byte.

03

Post it like it never happened.

Download. Upload to LinkedIn. No badge. We delete the file the moment you hit download.

What's the CR tag, anyway?

The little badge
nobody asked for.

LinkedIn quietly started flagging photos with a small CR mark — the Content Credentials icon — whenever they detect C2PA / JUMBF metadata baked into the file. Some creators love it. Most of us would rather not advertise the recipe.

Almost everything spits out a Content Credentials manifest these days: Photoshop, Lightroom, Firefly, Midjourney, DALL·E, ChatGPT image gen, Pixelmator Pro, and even iPhone / Pixel cameras when the Content Credentials toggle is on. That's why the LinkedIn AI image badge shows up on photos you literally took yourself.

Adds CR by default:PhotoshopLightroomFireflyMidjourneyDALL·EChatGPTGoogle BananaPixelmatoriPhone (CC on)
Free forever
No pricing page. No upgrade nag. The whole tool is one drop-zone.
No signup
No email, no account, no “verify your phone.” Just drop and go.
Deleted after download
Files live for minutes in a temp folder. Hit download — they're gone.
Pixels untouched
We strip metadata, not your image. EXIF (date, camera) is preserved by default.
FAQ

The "wait, is this safe?" questions.

Is this a virus?
No. crwipe runs as a tiny browser-to-server roundtrip and hands the cleaned file straight back. We don't keep a copy. We don't keep logs. We're a one-feature tool — strip the metadata, return the bytes, forget you ever stopped by.
Why does my own iPhone photo have a CR badge?
iOS 18 and recent Pixel cameras can attach Content Credentials when you take or edit a photo, and Photos.app re-stamps it on export. That counts as a “C2PA-signed” asset to LinkedIn, even though no AI was involved. crwipe strips the manifest without touching pixels.
Does this break my image quality?
No. We only remove the C2PA / JUMBF metadata box (and the LinkedIn-flagged signature). Pixels are byte-for-byte identical. EXIF — date, camera, GPS if it was there — is preserved by default.
Is it legal? Is it ethical?
Removing metadata from your own files is fully your call — same as exporting without GPS or saving “for web.” That said: if you're publishing a photo of a real event as documentary evidence, leaving Content Credentials intact is the right move.
Does it work for video?
Not yet. Images only — PNG, JPEG, WebP. Video has its own C2PA story we'd rather get right than ship rough.
What's the API limit?
10 MB per file. ~30 cleans per IP per minute. If you get a 429, slow down — we'll let you back in shortly.