Private · in your browser

Remove GPS & EXIF from photos — free, private, no upload

See what leaks — location, camera, date, software — then strip it. Batch download or a ZIP. Files never leave this tab.

A JPEG from a phone is rarely “just a picture.” Cameras write a hidden GPS tag with the latitude and longitude of the shot, plus the body that took it and the clock time. Posting the original file can place your apartment, studio, hotel, or a source’s street on a map for anyone who downloads it. Social apps sometimes strip tags on their own copy and still leave the original sitting in your camera roll for the next upload.

Strip is a local EXIF and GPS cleaner. You drop a JPG, PNG, or WebP; this tab reads the tags with a client-side parser; you choose Fast (JPEG segments, pixels untouched) or Deep (Canvas rewrite of the container). There is no account, no watermark, and no server-side image pipeline. If you disconnect after the page loads, stripping still works.

Use it before you attach a vacation photo to a listing, a press drop, a marketplace post, or a family album you do not control. Strip does not blur faces or redraw the scene — it removes the invisible sidecar. Read what GPS in a photo actually contains, then run the tool below.

Drop photos here

JPG, PNG, WebP, BMP, GIF — they never leave this tab.

HEIC? Convert in HEIC Local first.

Strip mode

JPEG → Fast · PNG/WebP → Deep

Deep clean quality 92%

Applies when a file is re-encoded (PNG/WebP, or JPEG Deep). Fast JPEG ignores this.

How it works

Four steps, all on-device. Longer walkthrough: the how-to guide. Device ceilings: iPhone, WhatsApp, marketplace.

Choose photos on this device

Use Choose files or drop JPEGs, PNGs, or WebP onto the tray. Nothing is posted to a server. HEIC from iPhone is rejected with a pointer to convert first — Strip is a metadata tool, not a HEIC decoder.

Inspect what would leak

The inspector reads GPS, camera make/model, capture time, and software tags in this tab. Coordinates are never sent to a map API. If you see a GPS badge, the original file would tell a downloader where it was shot.

Pick Auto, Fast, or Deep, then Strip

Auto uses Fast on typical JPEGs (pixels untouched) and Deep on PNG/WebP (Canvas rewrite). Fast fails on odd JPEGs → switch to Deep. Quality applies only to lossy Deep exports.

Download a clean file or a ZIP

Each cleaned image stays in memory until you save it. Batch ZIP is built here with JSZip. Re-drop the download into Strip to confirm GPS fields are gone. No watermark and no account.

Limits, browsers, and what never leaves the device

Processing happens in RAM on this phone or computer. We do not receive your image bytes, GPS coordinates, or camera serial. Closing the tab drops the blobs. Hosting may log ordinary page requests (this HTML, robots.txt, ads.txt) without file contents.

Supported stills: JPEG/JPG, PNG, WebP, BMP, and static GIF. Animated GIF is not a metadata-strip product here. HEIC/HEIF is rejected on purpose — convert it, then strip the JPEG. Very large files may trip a soft memory warning; that is a crash guard, not a paywall. Deep clean uses the browser Canvas, so export is limited by what this browser can encode.

Safari on iPhone, Chrome on Android, and current desktop Chromium/Firefox/Safari are the intended path. Fast mode needs a JPEG the parser understands. If inspect shows GPS after Fast, run Deep once and re-inspect. Color-critical print jobs should prefer Fast so pixels stay bit-identical.

Strip is not a forensic wipe, not a face redactor, and not a compressor. Sister tools exist for size and format; this page’s only job is metadata privacy. Guides: step-by-step how-to, iPhone album vs download, WhatsApp bubble vs disk, marketplace CDN vs disk, use cases, why the work must stay local.

FAQ

Does Strip upload my photos?

No. Strip inspects and cleans photos entirely in this browser tab. The EXIF parser (exifr), the Fast JPEG scrub (piexif / APP1 surgery), Deep clean (Canvas re-encode), and the ZIP builder (JSZip) all run in memory on your device. Closing the tab discards the files. You can load the page, turn on airplane mode, and still strip GPS. Hosting logs may record that you requested HTML or ads.txt — they never receive the image bytes. If a site asks you to “upload to strip EXIF,” that site is doing a different, riskier job than Strip.

What is EXIF / GPS metadata, and why does it leak?

EXIF is a sidecar of technical tags stored inside many JPEG (and some PNG/WebP) files. Typical tags include GPSLatitude / GPSLongitude, camera make and model, DateTimeOriginal, software name, and sometimes a small thumbnail. The picture you see in a feed does not show those tags, but the file still carries them. A stranger who downloads the original can plot the coordinates and infer a home, hotel, studio, or protest site. Strip’s job is to show those fields, then remove the containers that hold them so the downloaded file is safe to post.

Will Fast mode reduce photo quality?

No. Fast mode is JPEG-only surgery: it removes the APP1 EXIF segment (and related APP13 / COM segments when present) and leaves the compressed pixel blocks untouched. There is no quality slider and no new generation of artifacts. File size usually drops by a few kilobytes — that is the metadata, not compression. If Fast cannot parse an unusual JPEG, use Deep clean instead. Deep clean does re-encode pixels through Canvas, so use the quality slider there (default 92%) only when you need a container rewrite.

When do I need Deep clean instead of Fast?

Use Deep clean for PNG and WebP, for JPEGs where Fast reports leftover tags, and whenever you need the whole container rewritten. Some cameras store a second EXIF block inside a thumbnail IFD; some editors write XMP packets that Fast’s JPEG-segment pass may miss. Deep clean draws the pixels onto a Canvas with orientation applied and exports a new file, which drops those extra packets. The tradeoff is a re-encode: JPEG and WebP use the quality slider; PNG keeps a lossless raster. Auto mode already picks Fast for typical JPEGs and Deep for PNG/WebP.

Can I strip GPS from iPhone photos?

Yes, if the file is a JPEG from Camera Roll or the Files app. Many iPhones still default to HEIC. Strip v1 does not strip HEIC containers — convert the shot in HEIC Local first, then drop the JPEG here. After conversion, inspect the JPEG: iOS often copies GPS into the new file. Android JPEGs from Google Camera usually carry GPS in the same EXIF GPS IFD Strip reads. Live Photos are two files (a still plus a video); Strip only processes the still image you select, not the paired .MOV.

Is a batch ZIP still private?

Yes. When you add several photos, Strip strips each one in this tab and can pack the cleaned files with JSZip in the same tab. The ZIP never goes to a server to be assembled. Filenames stay under your control; we prefix cleaned files so you can tell them apart from originals. Memory is the only practical limit — very large batches on an old phone may warn you. That warning is a device guard, not a quota and not an upsell.

Do I need an account? Is there a watermark or daily limit?

No account, no email wall, no watermark, no daily cap. Strip is a local utility: you choose files, you download files. The only limit is this device’s RAM and the browser’s Canvas/blob budget. Ads, when the site is approved, sit after a successful strip, in a mid slot below results, or in the footer — never on top of Choose, Strip, or Download. Soft notes about the studio that built Strip are not ads.

Is Strip the same as Crush or Shift?

No. Crush shrinks bytes (compression). Shift changes container/codec (WebP/AVIF). Strip removes privacy metadata — GPS, camera, timestamps, software tags — without trying to make the file smaller or change format as its primary job. Fast mode does not recompress JPEG pixels. If you need a smaller Instagram upload after stripping GPS, run Crush on the cleaned file. If you need WebP, run Shift after Strip so the converted file does not re-inherit tags from an unstripped original.