Settings

Sterilise

Drop files here, or choose them Images, Office files (.docx .xlsx .pptx), PDFs and text. Up to 50 MB each. Nothing is uploaded.

What came out

Sterilised files appear here.

What each step does

ImagesRe-encoded through a canvas, which drops every metadata block: EXIF, IPTC, XMP, the GPS position, the camera make, model and serial, the editing history and the embedded thumbnail.
Office filesAuthor, last-editor and company fields wiped, macros and ActiveX removed, images and templates that load from an external address removed, and zero-width tracking characters stripped. A macro file comes back as the plain format.
PDFTitle, author, producer, creator and dates cleared, and any JavaScript, open action, launch action or embedded file removed.
TextZero-width and homoglyph tracking characters stripped from .txt, .md, .csv, .json, .html and source files.

What this is, and what it is not

It removes the parts that identify you or phone home. Metadata, author fields, macros, beacons, zero-width traps. Each file's report lists exactly what was found, and the certificate records the SHA-256 before and after so a clean file can be tied to its original.

It does not change what the file visibly says. Re-encoding an image removes its metadata, not the faces or documents in the picture. To black something out of an image, use CLOAK; to redact a PDF so the words are truly gone, use SEAL. CLEANROOM clears a PDF's metadata and scripts but does not flatten a redaction rectangle.

The image noise step is honest about its limit. It perturbs the sensor pattern (PRNU) that can tie a photo to a specific camera. It makes matching harder; it does not guarantee defeating a determined forensic analysis, and it slightly alters the image. Leave it off unless you specifically need it.

No finding is not a promise of safety. A file can identify you through its visible content, its writing style or its context. Treat CLEANROOM as the mechanical scrub before a human check, not a substitute for one.

Nothing leaves this tab. Every file is read, cleaned and written in browser memory.