Where file cleaning fits

Publishing and content operations teams receive assets from writers, designers and AI-assisted tools. Free AI Wiper can add a supported file metadata check between editorial approval and publication. It complements the checks your editors already make for accuracy, rights and disclosure.

An example handoff

A publisher prepares a downloadable PDF and supporting images for an article. The files may carry supported author or generator properties outside the visible content. Review those properties before publishing copies. This illustrative workflow does not imply that the article text has been checked for AI authorship.

A repeatable workflow

  1. Finish editorial review and export the files to be published.
  2. Inspect supported assets and choose which supported metadata to remove.
  3. Review successful outputs before attaching them to the article. Recheck newly exported versions after later edits.

When Pro makes sense

Choose Pro when your application or workflow needs API access. Plus already includes unlimited local cleaning and AI assistant integration (MCP); Pro adds API cleaning and credit top-ups. Local cleaning allowances do not mean unlimited API usage. Compare the current plans and review the API contract before integrating.

Compare Pro and Plus · API documentation

Questions about this workflow

Does this clean our entire CMS or establish authorship?

No. The cleaner operates on submitted supported files. It does not inspect an entire CMS, revise article claims or establish who wrote the text. Supported HTML, SVG and Markdown have their own limits; cleaning an export does not update the source CMS record.

Scope and processing location

Browser cleaning processes file bytes on your device; API jobs upload files for server-side processing. Format support and file-size limits still apply. Outputs are checked for selected supported findings and protected content; an unavailable check is not proof of absence. Cleaning does not prove human authorship, remove every watermark or replace content review. Keep your original and follow your disclosure commitments.

Check the supported scope