Technical Engine Mechanics
Discover how our client-side Web Sandbox processes your images in RAM without sending bytes across the web.
How In-Browser Metadata Removal Works.
Our 4-step client-side pipeline runs entirely inside your browser's isolated JavaScript sandbox.
1. Select Images
Drag and drop images into the browser. File API loads image binary data into RAM without network requests.
2. Inspect Metadata
`exifr` scans TIFF/EXIF segments, XMP blocks, IPTC metadata, GPS coordinates, and PNG chunk parameters.
3. Canvas Re-render
HTML5 Canvas re-draws pixel data to create a fresh image binary with zero EXIF or AI prompt markers.
4. Download Clean File
Download your clean images instantly or export all processed files into a single compressed ZIP archive.
1. Local Memory File API Sandbox
When you drag an image onto the dropzone, the HTML5 File API reads the raw binary ArrayBuffer into JavaScript execution memory (RAM). The image data never makes an HTTP `POST` request or touches any cloud infrastructure.
2. EXIF, XMP & PNG Chunk Parsing
We utilize `exifr` to inspect binary APP markers (JPEG APP1, APP2) and PNG ancillary chunks (`tEXt`, `zTXt`, `iTXt`). This allows our interactive inspector to display all embedded tags, including camera parameters, GPS coordinates, and AI generator prompts.
3. Canvas Pixel Re-rendering & Export
To guarantee 100% metadata destruction, the image is rendered onto an off-screen HTML5 canvas element. Exporting the canvas to a clean Blob generates a fresh image buffer containing only essential pixel data, effectively dropping all non-standard metadata blocks.