Metadata View

Inspect & clean files

OPUS Metadata Remover

Delete titles, comments, encoder tags, and pictures from OPUS files while keeping the audio stream untouched.

Looking to view metadata instead? Go to the Metadata Viewer.


Why remove OPUS metadata?

OPUS files can leak encoder notes, artwork, and comments. Cleaning removes those fields while leaving audio frames intact.

Protect voice recordings

Strip comments and encoder tags from calls or VO recordings.

Share podcasts without traces

Remove artwork and custom fields before publishing episodes.

Hide tooling fingerprints

Clear encoder/software tags that reveal your pipeline.

Secure OPUS cleaning

We scrub OPUS metadata inside the OGG container, then delete the temporary file once you download.

Upload your OPUS file

Select an OPUS-in-OGG file. Uploads are encrypted and not stored after processing.

Strip OPUS comments

We clear titles, comments, encoder notes, replaygain, and embedded images.

Preserve audio frames

Opus frames and bitrate remain unchanged—metadata only is removed.

Download & purge

Download the cleaned OPUS instantly; the temporary copy is wiped immediately.

What OPUS metadata do we remove?

We clear OPUS/Vorbis-style comments and images that expose source, encoder, or personal notes.

  • TITLE, ARTIST, ALBUM, GENRE, DATE, TRACKNUMBER fields
  • Encoder, software, replaygain, and ripper tags
  • Comment/description fields and custom entries
  • Embedded cover art/pictures
  • Organization, copyright, and publisher tags
  • Tool-specific custom or private fields
  • Lyrics or text blocks stored as comments
  • Any additional user-defined comment entries

Frequently Asked Questions

Does cleaning affect bitrate or quality?

No. The Opus stream remains untouched; only metadata is removed.

Are encoder and replaygain tags removed?

Yes. Encoder, software, replaygain, and custom fields are cleared.

Can you remove embedded images?

Yes. Picture blocks stored with OPUS metadata are removed.

Is this different from OGG cleaning?

It uses the same comment structure; we target OPUS-in-OGG specifically.