What these strings usually mean
ID3 is a metadata tag family commonly carried near the start of an MP3. LAME can identify an encoder, and Xing or Info can appear in an MP3 frame for seeking and duration information. Lavf or Lavc strings can point to FFmpeg libraries. An exact byte match tells you that a readable sequence exists somewhere in the file; it does not authenticate who made the recording.
C2PA is a structured provenance specification. A bare c2pa or jumb text match is not enough to validate a manifest or its signature. MP3 and WAV use different container mappings for C2PA data; use a conforming validator when authenticity matters.
Inspect locally before you upload
The inspector below reads the file in your own browser, checks its MP3 or WAV header, estimates or decodes audio properties, and searches its bytes for selected ASCII strings. It sends nothing to VoxErase during inspection. If you choose to submit it, a separate upload form requires your email, consent and security check.
What removing tags can and cannot do
An audio editor or encoder can rewrite a file without some optional descriptive tags. FFmpeg documents controls for MP3 ID3 and Xing writing. Any rewrite should be checked for unintended loss of artwork, chapters, legal notices or provenance data and for audible codec damage.
Removing container strings does not remove acoustic cues from the waveform, certify a provider watermark as absent, or guarantee a detector score. Our audio service is broader than a tag scan and delivers one processed file for your own evaluation.
A careful metadata cleanup workflow
Keep the original file. First run a media probe such as ffprobe to list format and stream tags, then note which fields you actually intend to remove. Export a new file with optional descriptive metadata disabled only when you have a legitimate reason and the right to edit it. FFmpeg’s MP3 muxer documents separate options for ID3 versions and Xing writing; these are different from acoustic processing.
After exporting, inspect the new bytes again, decode and listen to the whole file, and verify target-platform compatibility. If a C2PA manifest is present or expected, use a C2PA-aware validator and preserve any provenance information your distribution workflow requires. A raw ASCII search cannot determine whether a signed manifest is valid.
Primary references
Explore the service, read how intake and delivery work, or submit your first beta file.