Guide

Music metadata management for catalog workflows

Metadata turns a pile of audio files into a working catalog. It helps teams find the right song, send it with confidence, and prepare it for the next step.

Catalog · 4 songs
  • Often by Steve Cherry — album artwork
    Oftenv3 · master
    Steve Cherry·92 BPM·F♯m
  • Crossing the Bridge of Time by Jeanna — album artwork
    Crossing the Bridge of Timev4 · mix
    Jeanna·108 BPM·C
  • Breathe by Steve Cherry — album artwork
    Breathedemo
    Steve Cherry·124 BPM·Am
  • Babe, You Knew I'm Bi by TOKYOXIETY — album artwork
    Babe, You Knew I'm Biv2 · alt
    TOKYOXIETY·86 BPM·D
privateversioned
vault.toolkit.music

The short answer

>Keep song metadata useful across search, pitching, release prep, playlisting, and team review.

What to look for

Decision criteria

The questions to ask before committing to any tool in this category.

  • 01Core song data such as title, artist, writers, ISRC, BPM, key, and tags
  • 02Custom fields for team-specific catalog systems
  • 03Metadata visibility when sharing songs and playlists
  • 04Bulk cleanup for older catalogs
  • 05Attachment support for lyrics, agreements, artwork, and notes

Practical guide

Make the choice operational

Use these checkpoints to evaluate the workflow, not only the feature list. The best tool should make the next review, share, or follow-up easier.

Best for

  • Catalogs where song facts need to support search, pitching, release prep, review, and team handoff.
  • Teams cleaning up older folders where ISRCs, writers, rights notes, tags, and status live in multiple places.
  • Artists, producers, labels, publishers, and sync teams that need metadata close to the actual audio.

Workflow

  • Define the minimum metadata that every song needs before it can be considered review-ready or pitch-ready.
  • Fill core fields first: title, artist, writers, ISRC, BPM, key, tags, release status, artwork, and rights notes.
  • Use metadata during playlists, private links, briefings, and follow-up so it becomes operational instead of archival.

Watch out for

  • Keeping the spreadsheet up to date but leaving audio files, artwork, links, and contacts disconnected.
  • Collecting metadata only at release time, when writer, version, or rights context is harder to confirm.
  • Creating custom fields without deciding which ones actually help search, pitching, or review decisions.

How VAULT helps

  • Song metadata lives next to versions, artwork, notes, attachments, playlists, and links.
  • Custom catalog organization can support search and team review without separating the facts from the music.
  • Contacts, Briefings, and Actions make metadata useful during actual workflow decisions.

01 / 03

Metadata has to stay close to the music

A spreadsheet can help, but it becomes fragile when audio files, artwork, links, and contacts live somewhere else.

Worth noting

Categories evolve fast. Use this section as a snapshot, not a contract.

02 / 03

Common metadata gaps

Most catalogs are missing some combination of ISRCs, writer splits, contact context, release status, mood tags, alternate versions, or usage notes.

Worth noting

Categories evolve fast. Use this section as a snapshot, not a contract.

Where VAULT fits

Where VAULT fits

VAULT keeps metadata, versions, playlists, contacts, and sharing workflows in the same catalog environment.

Questions

Common questions, short answers

Start with title, artist, writers, contact owner, version status, release status, BPM, key, tags, artwork, and any rights or pitching notes your team uses.
VAULT includes bulk metadata workflows for teams cleaning up larger catalogs.

Your catalog is
waiting.

Start organizing your music today. Free forever, no credit card needed.