beets

Beets is the media library management system for obsessive music geeks.

The purpose of beets is to get your music collection right once and for all. It catalogs your collection, automatically improving its metadata as it goes. It then provides a suite of tools for manipulating and accessing your music.

Here’s an example of beets’ brainy tag corrector doing its thing:

$ beet import ~/music/ladytron
Tagging:
    Ladytron - Witching Hour
(Similarity: 98.4%)
 * Last One Standing      -> The Last One Standing
 * Beauty                 -> Beauty*2
 * White Light Generation -> Whitelightgenerator
 * All the Way            -> All the Way...

Because beets is designed as a library, it can do almost anything you can imagine for your music collection. Via plugins, beets becomes a panacea:

Fetch or calculate all the metadata you could possibly need: album art, lyrics, genres, tempos, ReplayGain levels, or acoustic fingerprints.
Get metadata from MusicBrainz, Discogs, and Beatport. Or guess metadata using songs’ filenames or their acoustic fingerprints.
Transcode audio to any format you like.
Check your library for duplicate tracks and albums or for albums that are missing tracks.
Clean up crufty tags left behind by other, less-awesome tools.
Embed and extract album art from files’ metadata.
Browse your music library graphically through a Web browser and play it in any browser that supports HTML5 Audio.
Analyze music files’ metadata from the command line.
Listen to your library with a music player that speaks the MPD protocol and works with a staggering variety of interfaces.

If beets doesn’t do what you want yet, writing your own plugin is shockingly simple if you know a little Python.

Install

You can install beets by typing pip install beets or directly from Github (see details here). Beets has also been packaged in the software repositories of several distributions. Check out the Getting Started guide for more information.

Contribute

Thank you for considering contributing to beets! Whether you’re a programmer or not, you should be able to find all the info you need at CONTRIBUTING.rst.

Learn more about beets at its Web site. Follow @b33ts on Mastodon for news and updates.

Contact

Encountered a bug you’d like to report? Check out our issue tracker!
- If your issue hasn’t already been reported, please open a new ticket and we’ll be in touch with you shortly.
- If you’d like to vote on a feature/bug, simply give a :+1: on issues you’d like to see prioritized over others.
- Need help/support, would like to start a discussion, have an idea for a new feature, or would just like to introduce yourself to the team? Check out GitHub Discussions!

Authors

Beets is by Adrian Sampson with a supporting cast of thousands.

Metadata

Release files for beets 2.14.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for beets 2.14.0
File	Size	Uploaded
beets-2.14.0.tar.gz	2.5 MB	Sep 7, 2026	Details

Built distribution (wheel)

Table of built distributions (wheels) for beets 2.14.0
File	Interpreter	ABI	Platform	Reset
beets-2.14.0-py3-none-any.whl 650.5 kB Sep 7, 2026	Python 3	none	any	Details

Total release size: 3.1 MB

Release files / beets-2.14.0.tar.gz

Download URL	beets-2.14.0.tar.gz
Size	2.5 MB
Tags	Source
SHA-256 checksum How to use checksums	`f412c9072ddc0bed04d843546a4222fcd24c9fe64cf233517ddcdb40190feea8`
BLAKE2b-256 checksum How to use checksums	`b63b359d68ce968214ffec8f55d9babe6de82794a846b5e02027f013456ef988`
Upload date	Sep 7, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/beetbox/beets
Publishing commit: github.com/beetbox/beets/tree/521be6a636628a60169203300102df5cd1c19cce

Workflow

Publishing configuration: github.com/beetbox/beets/blob/521be6a636628a60169203300102df5cd1c19cce/.github/workflows/make_release.yaml
Publishing logs: github.com/beetbox/beets/actions/runs/34159197405/attempts/1

Artifact

Subject: beets-2.14.0.tar.gz
SHA-256 checksum: f412c9072ddc0bed04d843546a4222fcd24c9fe64cf233517ddcdb40190feea8 Verifying attestations

Release files / beets-2.14.0-py3-none-any.whl

Download URL	beets-2.14.0-py3-none-any.whl
Size	650.5 kB
Tags	Python 3
SHA-256 checksum How to use checksums	`270cdce1f0c441dcdb7dc9bc367b51b4a54f055e62662b3f7509aa04838d7f84`
BLAKE2b-256 checksum How to use checksums	`2df5491bd9b9e22265e538c461e90b9efc7185a493e93c6df6a6bf28244639e3`
Upload date	Sep 7, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	Yes
Uploaded via	`twine/7.0.0 CPython/3.13.14`

Provenance

Identity

Publishing platform: GitHub Actions
Publishing repository: github.com/beetbox/beets
Publishing commit: github.com/beetbox/beets/tree/521be6a636628a60169203300102df5cd1c19cce

Workflow

Publishing configuration: github.com/beetbox/beets/blob/521be6a636628a60169203300102df5cd1c19cce/.github/workflows/make_release.yaml
Publishing logs: github.com/beetbox/beets/actions/runs/34159197405/attempts/1

Artifact

Subject: beets-2.14.0-py3-none-any.whl
SHA-256 checksum: 270cdce1f0c441dcdb7dc9bc367b51b4a54f055e62662b3f7509aa04838d7f84 Verifying attestations