Most ISRC codes are registered in external databases but never embedded in the audio file itself. Embedding your ISRC in the BWF (Broadcast Wave Format) axml chunk of your WAV master means the code travels with the file permanently, survives format conversions, and provides an additional layer of protection against metadata loss in the distribution chain.
Why embedding ISRC in the audio file matters
Most ISRC codes exist in two places: in the distributor's database and in the PRO's registration system. Neither of these is the audio file itself. This means that if the audio file changes hands — if it is licensed, redelivered by a new distributor, handed to a sync agent, or ingested into a legacy library system — the ISRC code can be stripped or lost unless it is also embedded in the file. The Broadcast Wave Format (BWF) standard, which is the professional standard for WAV files, includes a metadata chunk called axml that can carry arbitrary XML data, including ISRC codes. Embedding your ISRC in the axml chunk means the code is physically present in the audio file and survives the file's journey through the distribution chain.
What is a BWF axml chunk?
WAV files contain a series of 'chunks' — sections of data that carry different types of information. The audio data itself is one chunk. The BWF standard adds several additional chunks for metadata: the bext (broadcast extension) chunk carries basic metadata like the ISRC field, the originator, the origination date, and a unique identifier. The axml chunk carries an arbitrary XML payload, which is where ISRC and other structured metadata can be embedded in a format that is machine-parseable by systems that read DDEX-compatible metadata. Major streaming platforms and broadcasters that receive WAV files can read axml metadata if it is correctly structured. The bext chunk's ISRC field is also directly readable and is the simpler option for basic ISRC embedding.
Tools for embedding ISRC in WAV files
Several tools support reading and writing BWF metadata including ISRC:
- BWF MetaEdit (free, open source): the reference implementation for reading and writing BWF metadata, developed by the Library of Congress and MediaInfo team. Available at mediaarea.net. Supports batch processing of WAV files and can read, write, and validate the bext chunk ISRC field and axml contents.
- Sonoris Metadata Editor (paid): a professional metadata editor widely used in mastering workflows. Supports ISRC, ISWC, and a comprehensive field set in both bext and axml. Integrates with mastering session workflows.
- Pro Tools and Nuendo: major DAWs include BWF metadata support in their session and bounce settings. ISRC can typically be entered per-track before bouncing the final master.
- Weiss Saracon, iZotope RX: mastering-grade tools that support BWF metadata writing at the file conversion stage.
- ffmpeg (command line): ffmpeg can read and write bext chunk metadata in WAV files, including ISRC, making it suitable for batch processing large catalogs.
How to embed ISRC using BWF MetaEdit
BWF MetaEdit is the simplest and most accessible tool for most artists and labels:
- Download BWF MetaEdit from mediaarea.net/BWFMetaEdit — it is free and available for Windows, Mac, and Linux.
- Open the tool and use File > Open to load your WAV file or folder of WAV files.
- Select the file you want to edit and navigate to the bext chunk fields in the editor.
- Enter your ISRC in the ISRC field. The format must be the standard 12-character ISRC (no hyphens): e.g. GBXXX2600001.
- Save the changes. BWF MetaEdit writes the metadata directly into the WAV file without re-encoding the audio.
- Verify: use BWF MetaEdit's export function to confirm the ISRC was written correctly by reading the file back.
ISRC embedding in FLAC and MP3 files
The BWF axml approach is specific to WAV files. Other formats use different metadata containers. FLAC files use Vorbis Comment metadata, where an ISRC field can be written using tagging tools such as fre:ac, Mp3tag, or the open-source taglib library. MP3 files use ID3 tags, where the ISRC is written to the TXXX or TSRC frame. Most major tagging tools (Mp3tag, MusicBrainz Picard) support writing ISRC to these frames. The principle is the same across all formats: embed the ISRC at the file level so it survives the distribution chain independently of external databases.
Does file-embedded ISRC override the distributor's ISRC?
This is an important practical question. The answer varies by DSP and distributor. For most distributors, the ISRC provided in the delivery metadata (the ERN or equivalent) takes precedence over the ISRC embedded in the audio file — the distributor's database entry is what gets indexed on the DSP. However, file-embedded ISRCs serve as an additional verification layer and are increasingly used by archive and sync systems. For a music library or sync agency ingesting your files independently of a distributor, the file-embedded ISRC may be the only ISRC they encounter. Embedding ensures consistency across both scenarios.
Best practice for ISRC embedding in mastering workflow
The ideal point to embed ISRCs is at mastering, before the file is delivered to any distributor. The mastering engineer should receive the ISRC list for each track from the label or artist before the mastering session, and embed them in the WAV masters as part of the session delivery. This means every version of the file that leaves the mastering studio — WAV, FLAC, mp3 for streaming, mp3 for reference — carries the ISRC embedded at the file level. Confirm with your mastering engineer that they support this workflow.
Code Group Music's metadata administration service includes a ISRC registry audit covering both external database registration and, where applicable, file-level embedding for catalog archives. Our catalog assessment identifies which of your recordings have ISRCs correctly registered and where file-level protection is missing. Start at codegroupmusic.co.uk/#catalog-assessment.
Frequently Asked Questions
Is file-embedded ISRC required by streaming platforms?
It is not currently a formal requirement by most major DSPs for streaming delivery — the ISRC is typically submitted via the distributor's delivery metadata rather than extracted from the file. However, for sync and broadcast contexts, file-embedded ISRCs are increasingly expected. Embedding is best practice rather than a mandatory step for standard streaming distribution.
Does embedding ISRC in the WAV file affect audio quality?
No. BWF metadata is written to the metadata chunks of the WAV file, not the audio data chunk. The audio data is untouched. File size increases minimally (by a few kilobytes at most for the metadata) but audio quality is not affected.
What format should the ISRC be in when embedded?
The bext chunk ISRC field in the BWF standard accepts the 12-character ISRC without hyphens (e.g. GBXXX2600001). The ISRC should not include the 'ISRC' prefix — just the 12-character code. Some axml implementations include hyphens in a human-readable format alongside the compact form; follow the tool's documentation.
Can I embed ISRCs for my entire back-catalog in batch?
Yes. BWF MetaEdit supports batch processing — you can load a folder of WAV files and apply ISRC codes to multiple files simultaneously using its batch edit function. For very large catalogs, command-line tools such as ffmpeg offer scriptable batch processing.
Published