EXIF Metadata Viewer & Stripper
Inspect hidden metadata, detect GPS exposure, and export a clean image locally in your browser.
Your images stay private. Metadata is read and removed entirely in your browser. Nothing is uploaded to a server, stored, or transmitted. Safe for personal photos, client assets, and unreleased imagery.
Drop an image here or click to browse
JPEG, PNG, WebP, TIFF supported · EXIF data is most complete in JPEG
All metadata inspection and stripping happens locally in your browser using ExifReader for parsing and the Canvas API for re-encoding. Your images are never uploaded to CodeAva servers, never transmitted to any third-party service, and nothing is stored between sessions. This makes the tool safe for personal photos, client assets, pre-release imagery, and any files you cannot share with an external service.
What is image metadata and why does it matter for privacy?
Digital images contain more than pixels. Every photo taken on a smartphone or digital camera carries hidden metadata — structured data embedded in the file itself. This metadata can include the precise GPS coordinates where the photo was taken, the exact date and time of capture, the make and model of the device, lens settings, editing software history, and copyright or author information. Most of this is invisible to anyone looking at the image, but it is readable by any software that parses the file.
The privacy implications are meaningful. A photo shared publicly with intact GPS coordinates can reveal a home address, an office location, a travel itinerary, or a private venue. A product photo uploaded to a marketplace with intact EXIF data can disclose the device used, the photographer's name, and internal software workflows. For journalists, photographers, activists, or anyone handling sensitive imagery, unstripped metadata can create real exposure.
Browser-based inspection and stripping matters precisely because these workflows often involve files that cannot be uploaded to a third-party server. Unreleased product photography, client work, personal photos, and internal assets all belong in this category. This tool parses and strips metadata entirely within your browser tab using the ExifReader library and the Canvas API — no network request is made, and no file leaves your device.
What is EXIF data and is it dangerous to share?
EXIF (Exchangeable Image File Format) is a metadata standard used by cameras and smartphones to embed technical and contextual information inside image files — primarily JPEG and TIFF. It was designed to help photo management software understand how an image was captured. The privacy problem is that the same mechanism also stores where and when it was captured, on what device, by whom.
Sharing images with intact EXIF data is not always dangerous — but it is often unintentional. Most people do not know what their photos contain, and most platforms do not strip metadata before display. Inspecting before sharing is good practice for anyone publishing photos publicly, whether on social media, blogs, marketplaces, or support systems.
Common metadata hidden in your photos
- GPS location: Latitude, longitude, altitude, and sometimes speed or direction of movement at capture time.
- Device make and model: Camera or smartphone manufacturer and model, identifiable to a specific device generation.
- Capture date and time: The exact timestamp of when the shutter fired, down to the second, including timezone offset where available.
- Lens and camera settings: Aperture, shutter speed, ISO, focal length, flash state, and metering mode.
- Copyright and author: Embedded creator name, artist field, or copyright string set by the device or editing software.
- Editing software history: The software used to edit or process the image, including version numbers in some cases.
- IPTC caption and credit: Editorial metadata including titles, captions, credit lines, and keywords — common in professional photography workflows.
- XMP fields: Adobe-standard extensible metadata often added by Lightroom, Photoshop, or other editing tools.
EXIF, IPTC, and XMP — what is the difference?
These are three distinct metadata standards that often coexist in a single image file. EXIF is primarily technical — it stores camera, lens, capture, and GPS data. IPTC is editorial — it stores copyright, captions, keywords, and credits, and is widely used in professional photography and publishing workflows. XMPis Adobe's extensible metadata standard — it can embed almost anything and is commonly added by Lightroom, Photoshop, and other editing tools. A single JPEG from a professional workflow can contain all three.
Stripping metadata in a build pipeline
If you process images programmatically — for example in a Node.js image pipeline — the sharp library strips metadata by default during any conversion or resize operation:
import sharp from 'sharp';
// Metadata is stripped automatically — no .withMetadata() call
await sharp('input.jpg')
.resize(1200)
.webp({ quality: 82 })
.toFile('output.webp');
// To explicitly preserve metadata (not recommended for public assets):
await sharp('input.jpg')
.withMetadata() // <- keeps EXIF, IPTC, XMP, GPS
.toFile('output-with-meta.jpg');For teams that cannot use a server-side pipeline — or who are working with assets that must not leave the device — the CodeAva tool provides the same zero-metadata output directly in the browser.
What this tool helps with
Good uses
- Checking photos for GPS before posting publiclyinspect latitude and longitude before sharing personal or location-sensitive photos on social media or blogs.
- Stripping metadata from client or pre-release assetsclean files that cannot be uploaded to a third-party SaaS compressor or metadata service.
- Removing metadata before uploading to marketplacesproduct images, stock photos, and editorial assets are often inspected by buyers — clean exports protect your workflow.
- Inspecting what metadata your editing software embedssee exactly what Lightroom, Photoshop, Capture One, or phone camera apps write into your files.
- Privacy-sensitive journalism or investigation workflowsinspect images for location and device data before publishing, without uploading files to an external server.
- Cleaning support and bug report imagesscreenshots submitted via support systems sometimes carry device model data or software details your team may not want stored externally.
Limitations to know
- Selective field preservationthe Canvas API re-encode removes all metadata. Keeping specific fields (e.g. copyright only) is not possible with this browser-based approach.
- HEIC / HEIF files from Apple devicesHEIC parsing is not reliably supported in all browser environments. Convert to JPEG first if you need to inspect metadata from iPhone photos.
- Very large raw files (30MB+)browser memory limits apply. Very large RAW or TIFF files may be slow or fail on low-memory devices.
- Replacing a dedicated metadata workflow in publishingprofessional photo agencies and publishers use dedicated DAM tools for rights and IPTC management. This tool is for inspection and privacy stripping, not editorial metadata management.
How to use the EXIF Metadata Viewer & Stripper
- 1
Upload a local image
Drag and drop a JPEG, PNG, WebP, or TIFF file onto the upload area, or click to browse. The file stays in your browser — nothing is uploaded.
- 2
Review detected metadata
Metadata is grouped into Camera & device, Date & time, Exposure & lens, GPS / location, Author & copyright, and Technical. Each group is expandable. A privacy risk summary highlights sensitive fields.
- 3
Check the GPS warning if present
If GPS coordinates are found, a red warning shows the latitude and longitude. You can optionally enable a map preview — this requires explicit consent before any external tile request is made.
- 4
Choose strip mode and output format
Select 'Remove all metadata' (recommended) or 'Remove GPS only'. Choose JPEG, PNG, or WebP as the output format. JPEG is the default.
- 5
Export and download
Click Strip metadata & export. The image is re-encoded via the Canvas API — all embedded metadata is removed. Download the clean file directly from the browser.
Common issues and how to fix them
No metadata detected in a photo that should have EXIF
Some platforms strip EXIF before serving images. If you downloaded the photo from Instagram, WhatsApp, or a similar service, it may already have been stripped. Try the original file directly from the camera or phone's photo library.
HEIC files are not parsed correctly
HEIC/HEIF is Apple's default photo format but browser-side parsing support is inconsistent. Export the photo as JPEG from the Photos app or Finder before inspecting it here.
The clean image appears rotated after export
The original image may have had an EXIF orientation flag that CSS or the browser applied visually. When metadata is stripped, that flag is removed and the raw pixel data orientation takes over. The Canvas API respects the orientation of the img element as rendered in the browser, so in most cases the output should be visually correct. If rotation issues persist, rotate the image manually before stripping.
GPS warning shows but coordinates seem wrong
Some older cameras store GPS data in a non-standard format. The tool shows the parsed values — if they appear implausible, use the raw tag dump to see the original byte values and format.
Large file is slow to process
Browser Canvas operations are memory-bound. Files over 20MB may be slow on devices with limited RAM. Close other tabs to free memory, or reduce the file size with the Image Optimizer before inspecting metadata.
Copyright or author info is still present after stripping
The Canvas re-encode removes all metadata embedded in EXIF/IPTC/XMP — it cannot preserve selective fields. If copyright info reappears in the output, it may be embedded differently or written by the download process itself. Verify with this tool by uploading the clean file again.