Image EXIF view and clear
Inspect camera / lens / capture time / exposure / GPS · one click to clear the private bits (no re-encoding)
清除模式
单次最多 30 张 · 单张 ≤30MB
输出文件名:
原名-无EXIF.jpg / 原名-去除GPS.jpgAPP0(JFIF)与 APP2(ICC 色彩配置)原样保留——删掉 ICC 会让照片偏色。
照片列表
0 张添加照片后在这里显示相机、镜头、拍摄时间、曝光参数与 GPS 定位;清除后可逐张下载或打包 zip。
FAQ
No. In a JPG the pixel data lives in the compressed scan data, while EXIF sits in a separate APP1 metadata segment; this tool deletes or rewrites that segment directly in the byte stream, touching not a single byte of the scan data and never re-compressing - so quality and pixels are exactly unchanged. The proof is direct: zoom both versions to the same region and the detail is identical, and the file-size difference equals the metadata itself.
Phones often store pixels in sensor orientation and rely on the EXIF Orientation tag (values 3/6/8) to tell software to rotate 90 degrees for display. Clearing all EXIF removes that tag too, so some software shows the raw pixels and the image looks sideways or flipped; other software falls back on the thumbnail and looks fine - the same file can render differently across programs. To fix it for good, first use the image rotation tool to bake the orientation into the pixels, then strip; this tool's GPS-and-device-info-only mode keeps the orientation tag and never hits this.
Currently JPG / JPEG only. PNG keeps metadata in eXIf/tEXt chunks, HEIC uses ISO BMFF boxes, WebP uses RIFF chunks - structures completely different from JPG segments, so the same byte-level lossless-deletion logic cannot be shared; rather than say success while actually leaving data behind, the tool refuses these formats outright. For HEIC photos, convert with the HEIC-to-JPG tool first, then strip.
No. Reading, parsing and deletion all happen in your browser - images never leave your machine, reloading clears everything, and nothing goes to any server log. Up to 30 images per batch, 30MB each; it is pure byte work and usually finishes instantly. Afterwards download each file or take them all as one zip.