MusicBrainz: an open community music metadata database

Structure and key concepts

The database models several distinct entities so the same piece of music can be described from different angles. Common entity types include:

• Artist — the performer, composer or group responsible for a work.
• Recording — a particular recorded performance of a composition.
• Release — a specific issued product (CD, digital edition, vinyl) with a track listing.
• Release group — a collection of related releases representing the same album concept.
• Work — the underlying composition or song as an abstract entity.
• Label — the company or imprint that issued a release.

Each entity is assigned a stable identifier (often called an MBID) so records can be referenced unambiguously by software and services.

History and community

Started as a response to fragmented metadata sources, MusicBrainz grew into a community-driven project with contributors adding and curating data. Editors submit and refine entries, while maintainers and automated tools help enforce data quality. The project provides periodic full data dumps and a web service API to make the information accessible to developers and researchers.

Uses and applications

MusicBrainz is widely used to tag audio files, power music library software, support streaming and discovery services, and enable academic or commercial music-data analysis. The official desktop tagger and several third-party tools use the database to match recordings and populate metadata. Developers integrate identifiers and relationships into apps for collection management, recommendation, and cataloguing.

Distinctive features and notable facts

MusicBrainz stands out for its granular data model, community editing workflow, and emphasis on persistent identifiers. It complements fingerprinting and acoustic services by linking recordings to releases and works, helping resolve ambiguous or incomplete metadata. Because the dataset is distributed under an open data policy, it can be reused and redistributed by other projects and services.

Practical tips

1. Use MBIDs to tie data across services and avoid ambiguous names.
2. Understand the difference between a recording (a performance) and a release (a packaged product) when cataloguing.
3. Contribute corrections or new entries carefully: community guidelines improve overall quality.