Edge-only processing

Strip metadata. Keep the photo.

Photos carry GPS coordinates, device IDs, and timestamps in their EXIF data. Most "free online" tools upload to a backend that keeps your photo indefinitely. Ours auto-deletes the original on a short timer.

No signup. No download dance. The result is a temporary, unguessable link that expires automatically.

How it actually works.

Bytes flow through our edge worker, get transformed in-memory, and exit as a temporary link. No long-term storage on anonymous paths.

📷
Your browser
Uploaded over HTTPS
Edge worker (~50ms)
Strips metadata, applies the transform, original is deleted on TTL
🔗
Temporary link
Expires automatically. URL is unguessable.

Anonymous uploads on this surface use our short-TTL bucket: the original is automatically deleted, and the link can't be enumerated. If you want permanent hosting, sign up — otherwise the photo deletes itself automatically on a short timer and the link dies with it.

What we don't do.

The privacy story isn't a marketing line. It's enforceable in the architecture. The shorter this list, the more you should trust it.

No account required
No long-term storage of anonymous uploads
No email collection on anonymous flows
No selling data. We are funded by paid plans.

Frequently asked.

Quick answers about how the privacy guarantees actually hold up.

All of it. GPS coordinates, camera make and model, lens, ISO, aperture, shutter speed, software used, original date and time, owner name, copyright string — everything outside the visible pixels. The output is a clean image with the same visual content.
On anonymous flows (no account), the original lands in a short-TTL bucket in our object storage. The lifecycle policy deletes it automatically — we don't have a process that reads it back. If you want permanent hosting (e.g. for a portfolio), sign up; that's a separate, opt-in storage path.
Edge workers run on a 300+ city global network, so your photo is processed at whichever location is closest to you and the worker exits as soon as it's done. Lower latency, fewer copies in transit, and nothing sitting around on a central server.
Yes. Upload via the API, then apply the same transforms to the image URL it returns — metadata=none and segment=foreground are URL parameters (see the transforms reference). Useful if you're scrubbing photos before publishing or feeding a CMS.
EXIF stripping is a hygiene step, not a complete OPSEC. It removes the obvious leaks (GPS, device fingerprint, timestamp). For high-stakes source protection you also want to consider screenshot scrubbing, watermark detection, file-system forensic traces, and your own network attribution. Use this as one layer, not the whole stack.

Use the tools. No strings.

Anonymous and free. If you want permanent storage or batch API access, you can sign up — 100 uploads/month, no card.