Skip to content
Private by default

Clean Your Images. Keep Your Privacy.

Remove unnecessary image metadata and supported embedded provenance information in seconds. Your files aren't kept after processing.

No account · No image library · No permanent uploads

Processed temporarilyNot permanently storedNo account needed
Clean an ImageHow It Works

JPG · PNG · WebP · up to 3 MB per image

How it works

Upload. Clean. Download.

Three steps, and a fourth principle that matters more than any of them.

01

Upload

Drop your image into AI Remove Pilot. It is read and inspected in your browser first — nothing is sent until you ask for it.

02

Clean

Remove unnecessary embedded metadata and supported provenance information, then re-encode the pixels.

03

Download

Download the processed image. It comes back as the response itself, so there is no link left behind to expire.

Your file doesn't become our library.

There is no gallery, no account, no history and no bucket. The image exists on our server for the length of one request and is released when that request ends.

Image pipelineIn memory · no disk
  1. 01Validate

    Magic bytes, size, dimensions

  2. 02Inspect

    Which segments exist

  3. 03Clean

    Discard every auxiliary block

  4. 04Re-encode

    Pixels back out

  5. 05Return

    Straight to your browser

  6. 06Release

    Buffers zeroed and dropped

Metadata cleaning

What actually comes out of the file

Images carry more than pixels. Most of it is written automatically, and most people never see it until it travels somewhere they didn't intend.

Location and device records

GPS coordinates, camera make and model, lens data and body serial numbers — the fields that tie a photo to a place and a piece of hardware.

Editing and software history

Software tags, timestamps, XMP packets and IPTC records that describe when a file was made and what touched it along the way.

Embedded extras

Thumbnails, comment blocks — including the prompt dumps some generative tools write — and supported C2PA provenance manifests.

Verified by re-reading the output

The report is produced by inspecting the cleaned file, not by listing what the encoder was asked to drop. If it says removed, it's absent.

Before and after

The picture stays. The record attached to it doesn't.

Pixels are preserved as closely as the format allows — losslessly for PNG and lossless WebP. What changes is everything wrapped around them.

Worked example
A synthetic sample landscape used to demonstrate the cleaning report

The same pixels in both views. Cleaning removes what is attached to the file, not what is in the picture.

Before cleaning
  • EXIFTag block, 6.2 KB Detected
  • LocationGPS coordinates Detected
  • Camera / deviceMake, model, lens, serial Detected
  • SoftwareEditor and version Detected
  • Date & timeCapture timestamp Detected
  • Embedded thumbnailSecond copy of the image Detected

Values are never displayed — only the presence of each category is reported.

Privacy architecture

The safest place to put an image is nowhere

Most of this product's privacy properties come from things it does not have. There is no upload directory to misconfigure, no bucket to leave public, and no database row to leak.

  • Processed in memory

    Your image is never written to disk, so there is no temporary file to forget to delete.

  • Returned, not hosted

    The cleaned image is the HTTP response. No download URL exists, so none can be guessed or shared by accident.

  • Released on every path

    Buffers are overwritten and dropped in a finally block — on success, on validation failure, on a decoder error and on timeout alike.

  • Nothing logged

    No image bytes, no filenames, no metadata values and no hashes appear in any log line.

Read the full privacy page
FAQ

Questions worth asking a privacy tool

Does AI Remove Pilot store my images?
No. Your image is held in memory only for as long as it takes to clean it, and the cleaned file is sent straight back as the response body. There is no upload directory, no object storage bucket, no database row and no download link that could be visited later. When the request ends, the image is gone from the server.
Does this guarantee removal of Facebook's AI label?
No, and be sceptical of any tool that says otherwise. We remove metadata that is embedded in the file, including supported C2PA provenance manifests. Platforms can also apply an AI-generated label from signals that have nothing to do with your file's metadata — their own record of how the image was created, an account-level history, a partner's disclosure, or their own classifiers running on the pixels. Cleaning metadata cannot reach any of those.
What metadata can be removed?
EXIF tag blocks, GPS and location records, camera and lens identification including serial numbers, software and editing-history fields, XMP packets, IPTC records, embedded thumbnails, free-text comment blocks (including the prompt dumps some generative tools write), and supported embedded provenance manifests such as C2PA Content Credentials. The report after cleaning is generated by re-reading the output file, so it reflects what is actually gone.
Does image quality change?
Removing metadata means re-encoding the file, so it depends on the format. PNG and lossless WebP are re-encoded losslessly: the pixels are mathematically identical. JPEG and lossy WebP must be re-compressed, and we default to quality 92 with no chroma subsampling, which is visually equivalent to the original for practical purposes. We do not claim the JPEG result is bit-identical, because it isn't.
Do I need an account?
No. The image-cleaning workflow has no sign-up, no login and no email capture. There is nothing to create an account for, since nothing is kept between visits.
See all questions

Metadata out. Image back.

Process. Download. Gone. No account, no library, nothing kept.

Clean an Image

AI Remove Pilot cleans embedded image metadata and supported provenance information. Social platforms may use additional signals to determine whether an image is AI-generated, so cleaning an image does not guarantee removal of an AI-generated-content label.