Photo SignalsAI Watermark Remover

What this image says about you

A report across every family of signal, grouped by what each one exposes. Nothing is uploaded, and nothing is changed until you ask.

Open an image to read every layer

  • Nothing is uploaded
  • No account
  • Free, no limit
Everything a picture can carry

Eight families, named one by one

  • Watermarks you can see

    Removed — you mark it, it fills in

    • Stock-library tiling and corner logos
    • Burned-in dates and dashcam or CCTV timestamps
    • "Confidential", "Draft", "Sample" bars and diagonals
    • Channel bugs and app export badges
    • Screener and per-recipient overlays

  • AI generator marks

    Badges filled · manifests and fields removed

    • The Gemini and Nano Banana sparkle
    • Corner labels from Doubao, Jimeng, Qwen, Kling
    • Phone "AI edited" and Magic Editor badges
    • C2PA Content Credentials — Adobe, OpenAI, Cloudinary, camera makers, cloud image pipelines
    • Stable Diffusion's prompt, seed and model in the PNG text chunk
    • ComfyUI's whole workflow graph, filesystem paths included
    • China's TC260 AIGC labelling fields

  • Container metadata

    Removed — pixels untouched

    • EXIF — GPS with altitude, bearing and timestamp; make and model; body and lens serial numbers; shutter count; owner name from the firmware; timezone offset; how the fix was obtained; air pressure
    • XMP — editing history, document identifiers that link your files to each other, face regions naming the people in the frame, the original RAW filename, the pre-crop dimensions
    • IPTC — author, credit, city, contact details
    • MakerNotes — the manufacturer's private block
    • Photoshop IRB, JFIF, MPF and unknown APP segments
    • PNG chunks — tEXt, zTXt, iTXt, eXIf, tIME and anything unrecognised
    • GIF and WebP comment and application chunks

  • Whole files hidden inside the picture

    Extracted, shown to you, then removed

    • The embedded thumbnail — a copy from before you cropped or blurred
    • Motion photo video — an entire MP4 appended after the picture ends, with sound, covering the seconds either side of the shot
    • The MPF second full-size image some phones store
    • Ultra HDR gain maps and depth maps
    • Full-resolution previews inside RAW and DNG
    • PSD layers holding content you thought was deleted
    • Anything appended after the end marker, and the slack between segments
    • Payloads in fully transparent pixels, and messages in the low bits

  • Fingerprints of the software

    Removed by re-encoding at level 2

    • Compression tables that name the camera model or the program, with no metadata involved at all
    • Scan layout, subsampling and chunk ordering that identify the writer
    • ICC profiles named after a specific monitor calibration

  • Traces of the camera and the printer

    Printer dots removed · sensor noise reduced and measured

    • Printer tracking dots — the pale yellow grid colour printers add to every page, encoding the printer's serial number and usually the time of printing. Found in any scan of a printed page and removed at level 2, with the count and the lattice spacing reported
    • Sensor pattern noise — the signature of the individual camera body, not the model. Attenuated at level 4 and reported as a number, never claimed removed
    • Hot and dead pixel maps unique to one body

  • SVG, which is a document

    Removed by an allowlist

    • Beacons — references to an image on another server, contacted every time the file is opened
    • Executable script inside the image
    • Illustrator and Inkscape namespaces with layer names and local paths
    • Embedded raster images, which carry their own EXIF and are cleaned recursively

  • Writing inside the picture

    Found and pointed at — never read aloud

    • QR codes and barcodes on a badge, a boarding pass, a ticket or a parcel label. They usually encode a link with an identifier in it, a booking reference or a name — as readable to a stranger as the text beside them, and nobody thinks of them as writing
    • We say a code is there and where it is, so you can crop it or paint over it. We do not decode what it says: reading out what is on somebody's ticket is not this site's business

  • What nobody can remove

    Named and explained, never claimed

    • Imperceptible watermarks whose detector is held privately by its owner
    • Perceptual-hash databases platforms keep — not in your file, so nothing in your file changes them
    • A provider's own record of what it generated

    Why, and what our transforms actually do to them

Then it checks its own work

After cleaning, the same reader runs over the result and prints a second report beside the first. A claim about what was removed is worth exactly what it can be checked against.

What one photo file is made of, and what survives cleaning A photo file drawn as a row of blocks. Camera metadata, editing history, a hidden thumbnail, a Content Credentials manifest, an unknown tracker block and an appended video are all removed. The block holding the picture itself is kept byte for byte, along with a thirty-two byte orientation block. YOUR FILE BEFORE EXIF GPS, serial XMP names, history THUMBNAIL pre-crop copy THE PICTURE compressed pixel data C2PA AI provenance TRACKER unknown VIDEO appended MP4 rebuilt from the parts we understood YOUR FILE AFTER THE PICTURE byte for byte identical ORIENTATION 32 bytes, kept Everything else is gone because it was never copied across — including block types nobody has named yet.
Most strippers delete the fields they know about. This one keeps only what it needs and rebuilds the file, so an unknown block dies because it is unknown.