Metadata Remover API

1. Get a key

Create a free account, then make a key in Dashboard › API keys. Send it on every request:

Authorization: Bearer mrt_live_xxxxxxxxxxxxxxxx

2. Clean a file

Upload as multipart/form-data (field file) or as a raw request body. The cleaned file comes back as the response.

# image (JPEG, PNG, WebP)
curl -X POST https://metadataremover.tools/api/v1/clean/image \
  -H "Authorization: Bearer $KEY" \
  -F "file=@photo.jpg" -o photo-clean.jpg

# PDF
curl -X POST https://metadataremover.tools/api/v1/clean/pdf \
  -H "Authorization: Bearer $KEY" \
  -F "file=@report.pdf" -o report-clean.pdf

// Node.js 18+
const form = new FormData();
form.append("file", new Blob([fs.readFileSync("photo.jpg")]), "photo.jpg");

const res = await fetch("https://metadataremover.tools/api/v1/clean/image", {
  method: "POST",
  headers: { Authorization: `Bearer ${process.env.KEY}` },
  body: form,
});
console.log(res.headers.get("x-metadata-removed"), "fields removed");
fs.writeFileSync("photo-clean.jpg", Buffer.from(await res.arrayBuffer()));

Images are cleaned losslessly: the pixels are never touched.

Video and RAW

Send the file as the raw request body and its name in X-Filename. The request waits while our server cleans the file, then returns it. Video is never re-encoded, so picture and sound stay exactly the same. Each file also counts against your monthly video and RAW allowance.

# video: .mp4 .m4v .mov .mkv .webm
curl -X POST https://metadataremover.tools/api/v1/clean/video \
  -H "Authorization: Bearer $KEY" -H "X-Filename: clip.mp4" \
  --data-binary @clip.mp4 -o clip-clean.mp4

# RAW photo: .cr2 .cr3 .nef .arw .dng .raf .orf .rw2 and more
curl -X POST https://metadataremover.tools/api/v1/clean/raw \
  -H "Authorization: Bearer $KEY" -H "X-Filename: IMG_0042.cr2" \
  --data-binary @IMG_0042.cr2 -o IMG_0042-clean.cr2

RAW cleaning removes location, capture time, owner name, serial numbers and XMP/IPTC data. The picture data and the tags a RAW editor needs are left untouched. Nikon’s serial number is a decryption key for its own data, so it is kept; the X-Metadata-Left header names it, together with anything else that could not be removed.

Response headers

X-Metadata-Removed

How many metadata fields were found and removed.

X-Metadata-Remaining

Fields still present after cleaning (0 means verified clean).

X-Metadata-Left

The names of the fields that could not be removed, URL-encoded and comma separated. Empty when the file is clean.

X-Metadata-Fields

The names of the removed fields, URL-encoded and comma separated (up to 30).

X-Quota-Limit / X-Quota-Remaining / X-Quota-Period

What is left of the allowance this call used: images and PDFs per day, or video or RAW per month. The value is unlimited when your plan has no limit.

Check your usage any time: GET /api/v1/usage uses up nothing. It returns your plan, what is used and left of each allowance (a limit of null means unlimited) and the largest file you can send.

Want your AI assistant to do this for you? See the MCP server.

Limits by plan

The images-and-PDFs allowance is shared by the website, the API and MCP, and starts again at midnight UTC; video and RAW allowances start again each month. Need more? See plans

Errors

Errors are JSON: { "error": { "code": "…", "message": "…" } }