Guide
Metadata can make a file easier to organize, display, edit, and verify. The same context can reveal more than you intended when the file leaves your device.
Beyond the pixels
Location, capture time, device details, author fields, captions, and editing history can add context you did not intend to share.
Location, capture time, device details, author fields, captions, and editing history can add context you did not intend to share.
XMP fields and identified C2PA containers can carry editing or provenance assertions. They are useful clues, not a verdict about authenticity.
Orientation, color profiles, animation controls, secondary images, HDR data, and unfamiliar rendering structures can affect appearance or compatibility.
A local check
Precise coordinates stored in EXIF GPS metadata.
Selected file
Recognized location, device, author, date, caption, and comment findings appear here.
Cleanup selection
Review the supported privacy metadata selected for standard cleanup. Content Credentials and other identified C2PA data are a separate choice because provenance can be valuable.
Local verification
The browser worker will rescan the output before a download is offered.
NullKit does not overwrite the original. You receive a new result that can be reviewed before you replace, share, or delete anything.
Four local steps
Select one supported photo, choose a folder for batch cleanup, or open the built-in demonstration. Every selected file is read on this device.
For one photo, review the detailed privacy and provenance findings. For a folder, review aggregate counts, skipped files, and inspection failures before cleaning.
Review the supported privacy metadata selected for standard cleanup. Content Credentials and other identified C2PA data are a separate choice because provenance can be valuable.
The cleaner rescans every output without re-encoding image data. Save one result, write batch copies under NullKit Output, or use individual download links when direct folder writing is unavailable.
Browser privacy
The page reads them through the browser's file API only after you make an explicit file or folder choice.
Parsing and cleanup run off the main page thread. Limits of 25 MiB, 40 megapixels, 10,000 container structures, and 1 MiB of decoded metadata text bound the work.
Originals are not changed. Verified outputs follow your browser and operating system's storage rules.
Supported files
“Clean” means the selected, recognized metadata was removed and the output passed a local rescan. It never means that every unknown byte or every possible clue has disappeared.
On-device workspace
Inspect and remove supported EXIF, GPS, editing, and AI-related metadata from one photo or a folder, then create verified clean copies without uploading the files.