Before sharing a WAV, review its embedded identifiers

You have prepared an audio sample for a public page. Before uploading it, inspect the copy you intend to publish as well as the sound it contains. Descriptive fields may carry useful credits, production identifiers or internal information whose audience needs a separate decision.
Keep the preservation source intact. Name a distinct distribution copy and record who can approve its release. This review is about identifying fields and deciding their intended audience. It is not a procedure for proving anonymity or removing every trace of a recording's origin.
Give the review an exact file
Use the blank metadata release-review card to record the copy, tool version, fields inspected and unresolved questions. Use a private alias for the source location in notes you may share. Keep full internal paths and sensitive field values out of a public worksheet.
If you need to establish which copy was reviewed, the whole-file SHA-256 handoff guide describes that separate identity check. A matching hash ties observations to bytes. It does not establish whether those bytes are appropriate for public release.
Read descriptive fields in their original purpose
FADGI's BEXT metadata reference describes Description, Originator and OriginatorReference, among other fields. Its archival recommendations use identifiers to connect a file with a work and its maintaining organisation. It explicitly cautions against identifiers that expose exact pathnames.
These fields support identification and preservation. Their presence is not automatically a defect. Decide what belongs in the distribution copy with the person responsible for the material, rather than clearing credits or archival information indiscriminately.
| Field or area | Review question | Record without publishing sensitive values |
|---|---|---|
| Description | Does it contain internal identifiers or notes? | Field inspected and decision owner |
| Originator | Is the named producer or organisation intended to be public? | Keep, review or unresolved |
| OriginatorReference | Is the identifier appropriate for this audience? | Approval or outstanding question |
| Other metadata containers | What does the inspection tool actually expose? | Containers inspected and coverage gaps |
| Filename and accompanying report | Are these also suitable to share? | Copy revision and review state |
The FADGI help collection is archival guidance, not a complete privacy checklist for every publishing workflow. Its help overview, last updated in April 2019, distinguishes technical information, descriptive exchange documents and RIFF structure views. It also identifies separate XML metadata containers.

Choose an inspection tool with a known scope
MediaArea's BWF MetaEdit overview describes importing, editing, validating and exporting specified WAVE metadata. Its Tech, Core and Trace documentation gives those views different purposes. Use the documentation for your installed version and note which view and fields you inspected.
Work on a separate copy, and keep inspection separate from import, editing or Save operations. Do not treat a tool that can modify metadata as an automatically read-only viewer. If an existing option may change the file, understand it before opening an important source.
The maker's preferences reference makes a useful distinction: hiding a Core column changes the displayed table, while metadata in that field may still be imported, exported and saved. A cleaner-looking table therefore does not establish that the underlying field is empty.
Keep coverage gaps in the card. “Description inspected” is a useful bounded observation. “No identifying information anywhere” is a much broader claim that this check does not establish.
Review reports before sharing them
An exported inspection report can repeat the very identifiers you are reviewing. Keep that report private until its own contents have been checked. A support request can often begin with field names, tool version and the unresolved question, without sending the original recording or a full metadata dump.
If an authorised change is needed, preserve the original, use a separately identified copy and record the specific change. Reinspect the actual resulting file and confirm required credits, technical usability and recipient requirements. Keep an unsuccessful or incomplete result identifiable.
Assess the delivered copy as its own result
Before public release, confirm the filename and revision being uploaded. Retain the review decision and any remaining limitations. Metadata inspection does not assess what a voice says, identify every person audible in a recording or determine permission to publish it.
The cited primary references were read for this guide. No audio file was opened in BWF MetaEdit, metadata altered, report exported or recording published. The card is blank and provides no verified disclosure or anonymisation result.
The cited documentation was rechecked on 13 November 2026.