14 min read · May 10, 2026
The Song Is Not the File
Music metadata is the unglamorous infrastructure underneath every stream, sync license, and royalty payment. Here's what actually happens to a song between upload and play.
When you upload a song to Spotify through DistroKid or TuneCore, you fill in a form. Title, artist, genre, maybe an ISRC code if you have one. You hit submit and the song appears on streaming platforms a few days later. You assume the data you entered traveled with it. Most of it didn't. The distance between what an artist enters and what a listener sees is not a gap. It's a canyon. And the things that fall into it — BPM, musical key, mood, energy, sub-genre, producer credits — are exactly the metadata that DJs, music supervisors, and recommendation engines need most. The metadata pipeline is not a pipeline A pipeline implies data flows from one end to the other without loss. What actually happens is closer to a game of telephone.
Each stage — DAW export, file tagging, distributor intake, DSP processing — has its own schema, its own constraints, and its own opinions about which fields matter. The fields that don't fit get dropped. The fields that do fit get overwritten. The result: the only metadata that reliably survives from artist to listener is title, artist name, ISRC, UPC, primary genre, and release date. Everything else — BPM, key, energy, sub-genre, producer credits, mood tags — is either stripped or replaced. The pipeline graveyard DDEX ERN — the XML standard that connects every distributor to every DSP — has fields for 47 types of rights holder. It does not have a field for BPM or musical key. The standard literally cannot carry the information that DJs need most. What goes in vs.
what comes out Here's what happens to specific metadata fields as a track moves from an artist's DAW to a listener's phone: Field DAW Tag Distributor DSP Survives? Title ✓ ✓ ✓ Yes Artist ✓ ✓ ✓ Yes ISRC ✓ ✓ ✓ Yes Genre ✓ Simplified Own taxonomy Partial BPM ✓ ✓ then stripped Own analysis No — overwritten Key ✓ Dropped Own analysis No — dropped Mood / Energy ✓ Dropped Own analysis No — dropped Sub-genre ✓ Collapsed Own taxonomy No — replaced Producer credits ✓ Truncated Partial No — partial If your BPM can't survive the trip from your DAW to someone else's DJ software, it's not your BPM anymore. It's Spotify's BPM. Or Apple's. Or whoever recomputes it on the other end. The artist's intent is replaced by an algorithm's estimate.
What an ISRC actually does (and doesn't) ISRC codes — the 12-character identifiers assigned to individual recordings — are free through the RIAA and cost nothing to generate. They're the closest thing the music industry has to a universal ID for a specific recording. But most independent artists either don't know they exist or skip them entirely, which means streaming platforms auto-assign their own identifiers. Those auto-assigned codes often don't propagate consistently across services, making it impossible to definitively say that this recording on Spotify is the same recording on Apple Music. UPCs — the barcodes for releases — face a similar problem. Get one through your distributor and it's tied to their account. Switch distributors later, and you may lose the identifier that your release has been indexed under for its entire life.
Why distributors strip what they strip The major distributors — DistroKid, TuneCore, CD Baby — aren't being careless. They're following DDEX ERN, the Electronic Release Notification standard that defines the XML format for delivering metadata from distributors to DSPs. ERN v3.8, the version most widely deployed, simply doesn't have fields for BPM, musical key, energy level, or mood. It was designed for the recording industry's commercial needs — rights management, royalty tracking, territorial availability — not for the creative needs of the people making music. DDEX ERN v4.0 adds some fields, but still not BPM or key. This isn't an oversight. The standard's governance body — the DDEX Board, composed of major labels and DSPs — has no DJ software companies on it. The people who need these fields most aren't in the room where the standard is written.
The DSP overwrites Here's the part that surprises most people: Spotify and Apple Music don't display your BPM. They display their BPM. Spotify runs its own audio analysis pipeline on every track it receives. The "audio features" in the Spotify API — energy, valence, danceability, tempo, key — are all computed by Spotify's algorithms, not sourced from distributor metadata. This means that even in the hypothetical scenario where a distributor preserved your BPM, the DSP would overwrite it with its own estimate. The artist's carefully tagged metadata only survives if the DSP chooses to respect it. And for DJ-relevant fields — BPM, key, energy — they don't. Beatport is the sole exception. The DJ-focused marketplace requires BPM and key as first-class metadata because its customers are DJs who sort and filter by those fields. But Beatport serves a niche.
The platforms that reach listeners — Spotify, Apple Music, YouTube Music — treat DJ metadata as irrelevant. The DJ's end of the pipeline When a DJ imports a track into Rekordbox, Serato, or Traktor, the software re-analyzes the entire file locally. It computes BPM, detects key, generates waveform data, and builds beat grids from scratch. This isn't redundant — it's the only reliable path. The metadata pipeline has already mangled or discarded the original values by this point. But there's a second, less visible problem: the DJ software silos don't talk to each other either . Switch from Serato to Rekordbox and you lose your cue points, your beat grids, your energy ratings, your loop markers. None of these have a standardized interchange format. Every DJ platform is a walled garden, and the walls are built from the same metadata that the pipeline already fragmented.
How to plan around it If you're an independent artist, there are practical steps that reduce — though they can't eliminate — the damage: 1. Always assign ISRCs yourself. They're free through the RIAA. Don't let your distributor auto-generate them — you'll lose control of your recording identifiers if you ever switch distributors. 2. Tag your files before uploading. Use MusicBrainz Picard or a dedicated tagger to embed ISRC, UPC, genre, and credits directly in the audio file. This won't survive distribution, but it ensures your master files are correct. 3. Expect DSP BPM and key to be estimates, not your values. If you need precise BPM and key for DJ use, they have to live in your DJ software's local analysis — not in the streaming platform's metadata. 4. Use Beatport for DJ-facing releases. It's the only major platform that accepts and displays BPM and key as first-class metadata.
If your audience is DJs, Beatport matters more than Spotify for discoverability. 5. Keep a local spreadsheet. Until there's a true metadata standard that survives the full pipeline, the most reliable DJ metadata is the spreadsheet you maintain yourself. BPM, key, energy level, genre subcategory — everything the pipeline strips, you track locally. The metadata pipeline is not a pipeline. It's an analysis-reanalysis chain where every stage may overwrite what came before. The song is not the file. The file is not the metadata. And the metadata that reaches the listener is not the metadata the artist created. Until the standards catch up with the people who actually use them, the gap between creation and discovery will keep swallowing the details that matter most.