Clean Metadata guide

Understand Skipped Files and Retained Metadata

Read Clean Metadata outcomes and take the right next step without losing originals or recovery files.

By Osenpa · Updated
On this page

Short answer

Open File details and follow the explanation for that file. Skipped does not mean cleaned, and retained means some information remains intentionally. A recovery warning requires preserving the named recovery data; do not delete it or repeatedly replace the same source.

Before you start

  • A completed, canceled or interrupted Clean Metadata operation.
  • Access to the original location and any recovery path shown by the app.
  • A backup before changing, converting or restoring an important file.

Start here

  1. Read the per-file result

    Open File details rather than relying only on the batch total. Check the outcome, Removed metadata fields, retained explanations and any Support code.

  2. Separate unchanged from failed

    No removable metadata found means no cleaning action was needed under the supported rules; a new copy may not exist. An unsupported or verification-failed result is different: do not treat that file as a successfully cleaned output.

  3. Check retained information

    Read Retained and Preserved for file compatibility notes. A field needed by a document or a broadcast audio time reference can remain. Decide whether that information is acceptable for your intended sharing use.

  4. Fix only the stated cause

    For a file in use, close the other application. For a changed source, finish editing and select it again. For unsupported storage, use an ordinary local NTFS location. For a damaged or unsupported structure, keep the original and consider exporting a separate copy in its original app.

  5. Preserve recovery data

    If Recovery needs attention appears, keep the recovery location intact. Read the status before acting. Use Restore original only when the app offers it for a restorable state; an occupied original name is not overwritten. Contact support if the state remains unclear.

Check your result

  • Every file intended for sharing has a successful, understood result.
  • Retained personal fields were assessed rather than assumed absent.
  • Any recovery data remains available until the issue is resolved.
  • Support receives the code and a non-sensitive description, not private documents by default.

An extension is only the first check

Clean Metadata admits specific image, document and audio extensions, then checks the actual file structure. Unsupported features or encodings can prevent processing even for a familiar extension.

Do not rename extensions to bypass a result. If you export a new copy, check its content and quality before trying again.

A successful result still needs a privacy review

The app preserves authored content and functional information where required. Embedded material can have a specific retained or unchecked-metadata explanation. Read those notes before making a privacy claim.

This is not content redaction, full anonymity or forensic sanitization. Inspect visible text, images, audio and any other information you intend to share.

What to send to support

Include the app version, file type, exact message, Support code if shown, and whether you chose Create clean copy or Replace original. Explain whether the original is present and whether a recovery path is shown.

Use a synthetic or non-sensitive sample if one reproduces the issue. Hide personal paths in screenshots and keep recovery files locally until support explains a safe next step.

The app used in this guide

Clean Metadata

View app details

Related guides

Sources and further reading