Inspect, edit, sanitize, and verify AVIF image metadata — privately in your browser. The original AVIF remains untouched on your device.
Parsing ftyp brand headers, meta directory, and EXIF/XMP payloads in memory...
or browse files from your device (Max 100 MB)
Removes GPS coordinates, device serial numbers, and software stamps while preserving ICC color profile and copyright attribution.
Preserves camera make, model, lens aperture, and ICC profiles. Strips personal GPS location and user identification.
Completely strips all Exif items, XMP packets, timestamps, creator tags, and auxiliary location boxes from the ISOBMFF container.
| Field | Before (Original Value) | After (Resulting Value) | Action |
|---|
Note: Verification performs byte-level inspection of the exported AVIF ISOBMFF boxes to confirm Exif and XMP item IDs have been completely scrubbed from item directories (`iinf` and `iloc`).
AVIF files are structured using the ISO Base Media File Format (ISOBMFF). Below is an audit of binary boxes present in this document container.
This action will mark all supported standard metadata fields (Camera Make, Model, Lens, GPS Coordinates, Timestamp, Artist, Copyright, and Software Tags) for complete deletion upon download.
The original AVIF file will remain completely untouched.
AVIF (AV1 Image File Format) is the next-generation image standard offering superior compression over legacy JPEG and WebP. However, like other photographic formats, AVIF files carry hidden Exif (Exchangeable Image File Format), XMP (Extensible Metadata Platform), and color management packets embedded directly within their ISOBMFF container boxes.
AVIF embeds Exif metadata inside the meta box referencing byte extents in mdat. Standard properties include camera make, model, lens parameters, shutter speed, ISO rating, and camera serial numbers.
Modern mobile phones and high-end mirrorless cameras automatically append precise GPS latitude, longitude, and altitude coordinates into AVIF headers, potentially leaking residential addresses or private shooting locations.
Sharing uninspected AVIF photos on corporate portals, social networks, or investigative archives exposes editing histories, workstation usernames, local filesystem paths, and unnecessary byte overhead.
| Field Name | What It Contains | Potential Privacy Concern | Can Standard Sanitization Remove It? |
|---|---|---|---|
| GPS Coordinates | Exact latitude, longitude, and elevation of the photo location. | Reveals exact residential or confidential location coordinates. | Yes — 100% Client-Side |
| Camera Make & Model | Hardware brand, camera body serial number, and firmware build. | Hardware fingerprinting and equipment owner identification. | Yes — Editable / Removable |
| Lens Model & Specs | Focal length, aperture range, and lens manufacturer tag. | Identifies specific commercial or proprietary camera setups. | Yes — Editable / Removable |
| Author / Artist | Photographer's real name, workstation identity, or studio alias. | Exposes creator identity in anonymous submissions or whistleblowing. | Yes — Editable / Removable |
| Copyright Notice | Licensing terms, agency registration, and copyright holder tags. | Identifies corporate contracts or confidential agency work. | Yes — Removable |
| Software / Editor | Post-processing software (e.g., Photoshop, Lightroom, GIMP). | Reveals software licenses, operating system versions, and toolchains. | Yes — Removable |
| Creation Timestamp | Exact timestamp including local time zone of image capture. | Exposes timeline of events, working hours, and time-zone location. | Yes — Removable |
| ICC Color Profile | Color gamut calibration descriptor (e.g., Display P3, Adobe RGB). | Minimal privacy risk, but adds file size overhead if non-standard. | Yes — Removable |
Our engine operates directly within your browser's JavaScript runtime using ArrayBuffer and typed binary views. Your original AVIF is loaded into memory, parsed through its ISOBMFF box hierarchy (ftyp, meta, iinf, iloc, mdat), modified according to your specifications, and re-serialized without decompressing the AV1 pixel bitstream.
meta box directory.mdat completely intact.canvas.toBlob().ftyp, meta, mdat). Both AVIF and MP4 video files use this hierarchical container.