Nullframe reads the hidden EXIF, IPTC, XMP and C2PA data embedded in your photo, shows you exactly what's there, then removes it — entirely on your device. The file never leaves your browser.
Nullframe only touches the file's header and metadata blocks. Pixel data is never resampled or recompressed for PNG and WebP; JPEG is re-encoded at high quality, which can introduce a negligible, visually invisible amount of recompression.
Four steps, all inside your browser tab.
Your image loads directly into memory. No network request is made.
Nullframe walks the file's segments and lists every metadata block it finds.
The image is redrawn to a blank canvas and exported fresh — metadata isn't carried forward.
Grab the cleaned file. Nothing was ever stored or transmitted.
No. Nullframe only removes metadata — the invisible text and binary records attached to the file. Some generators also embed watermarks directly into pixel values (SynthID-style watermarking, for example); those survive metadata removal and require different tools entirely.
For JPEG, PNG and WebP, scanning and stripping happen entirely inside your browser — nothing is sent anywhere. HEIC files and custom metadata writing require a short server round trip (browsers can't decode HEIC or write real EXIF on their own). In that case the file is processed in memory and discarded immediately after the response is sent — it's never written to disk or used for anything else.
Visually, no. PNG and WebP are re-encoded losslessly at the pixel level. JPEG is re-encoded at high quality (0.95), which is technically a fresh compression pass but is not visually distinguishable from the original at normal viewing sizes.
JPEG, PNG, and WebP, up to 50MB per file. HEIC and RAW formats aren't supported in-browser yet.