albums
Manage a library of music: validate and fix tags and metadata, rename files, adjust and embed album art, clean up and import albums, and sync parts of the library to digital audio players or portable storage.
Overview
albums works with media files and tags, but primarily acts on "albums" rather
than individual files. Everything is done locally and an Internet connection is
not required (although it can be configured to use an external tool to download
cover art). It's a command-line app but it is designed to be user friendly, with
interactive menus, rich text formatting, tables and even blocky graphics.
It can work with a single folder or scan a whole media library into its database to make subsequent operations fast. It has many automated checks and fixes for metadata-related issues such as track numbering (sequence, totals, disc numbers), album-artist fields, embedding cover art, etc. It supports marking albums as part of "collections," for example to make a list of albums to sync to a digital audio player. It can also perform the sync.
Why use albums instead of other music library tools?
Use them all; you don't have to decide. If you have missing metadata or
unidentified recordings and you want to use online databases to fill in the
blanks, Beets does that, and has some command line and
library management features similar to albums.
MusicBrainz Picard does too. For manually
editing tags in a GUI with some fancy features and automation,
puddletag and
MP3TAG (proprietary but no cost for the
Windows version) are nice, while EasyTAG
is simple and quick.
albums is a little different. It works offline without external databases. It
uses a series of independent, configurable checks and automated fixes for basic
tags, cover art and filenames. You can review every change, or only the ones
that require your choice. It also reports on some problems it can't fix, like
missing tracks on an album. albums can help clean up and import new albums
into your library and keep digital audio players synced. Its CLI plus JSON and
SQL interfaces may enable some automation.
Supported Media
FLAC, Ogg Vorbis, MP3/ID3, M4A, ASF/WMA and AIFF containers/types are supported with standard tags. ASF/WMA embedded image support is read-only. Image files (PNG, JPEG, GIF, BMP, WEBP, TIFF, etc) in the album folder are scanned and can be automatically converted and embedded.
More formats and tag support will likely be added if requested.
System Requirements
Installation via pipx requires Python 3.12+ and should work on almost any 64-bit x86 or ARM system with Linux, macOS or Windows.
Binary releases for 64-bit Linux or Windows do not have any Python requirement. The Linux binary requires glibc 2.38, meaning recent distributions such as Ubuntu 24, Debian 13 (Trixie), Fedora 39 and Arch Linux. (Use the regular package to install on older distributions.)
albums is primarily tested on Linux and Windows.
1 maintainer
Metadata
1 maintainer
Release files for albums 0.9.33
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| albums-0.9.33.tar.gz | 460.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| albums-0.9.33-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 704.9 kB
Release files / albums-0.9.33.tar.gz
| Download URL | albums-0.9.33.tar.gz |
|---|---|
| Size | 460.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e11faf084fdbc18a094a82749d5849a56c35df453ec8d205c03a6b9a29d1a98
|
|
BLAKE2b-256 checksum How to use checksums |
6e0ee58729d9e80dd78890c5ddbf2efc885d41a286d43fec9a3071430ae5cb1a
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency logRelease files / albums-0.9.33-py3-none-any.whl
| Download URL | albums-0.9.33-py3-none-any.whl |
|---|---|
| Size | 244.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
bc0d09f6aeb705a8e5df3f12eda975dd8d1047ab1bae5e1461226f514e8c05ad
|
|
BLAKE2b-256 checksum How to use checksums |
5c028e926338b1116577ae97d7f949470558211b6cc5772c78a00de1da20390a
|
| Upload date | |
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 21, 2026.
Transparency log
