Beets
Hacker ApprovedMusic tagger in Audio
Free, powerful toolbox for importing and tagging large music libraries, with MusicBrainz lookups and flexible configuration. Critics cite a steep learning curve and occasional crashes.
Free, powerful toolbox for importing and tagging large music libraries, with MusicBrainz lookups and flexible configuration. Critics cite a steep learning curve and occasional crashes.
43 people gave an opinion
- recommend it
- 33
- criticize it
- 10
- approval share
- 77%
Recommended in 5 of 13 months
- November 2025: recommended
- December 2025: not recommended
- January 2026: recommended
- February 2026: not recommended
- March 2026: not recommended
- April 2026: not recommended
- May 2026: not recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: not recommended
- September 2026: not recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Why it carries the badge
- 33 people recommend itNeeds 10 or more, met.
- 3.3 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 5 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Powerful, flexible toolbox for large libraries
“the real value (IMO) of beets is it's a powerful toolbox for managing a large music library”
Comment from 11 Nov 2025 in “Beets: The music geek’s media organizer” “It's wildly flexible and configurable.”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” “nothing is quite so flexible”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” Handles tagging and file layout
“beets imports it and museFS autoscans it. That handles 99% of cases silently in the background”
Comment from 19 Jun 2026 in “Show HN: Musefs – organize and tag music without touching the original files” “beets is mainly a better tool for accomplishing the same tag and file janitoring”
Comment from 11 Nov 2025 in “Beets: The music geek’s media organizer” “Worked reasonably well on some retagging, better dir layout.”
Comment from 5 Oct 2026 in “Picard 3.0” Indispensable for maintaining libraries
“Beets is amazing. The fact that it exists is a blessing for those like us who maintain our own music library.”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” “I would not know how I'd ever get it done without Beets.”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” “I've loved beets (and MusicBrainz Picard) for years.”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” Scriptable and pluggable with other tools
“this is so cool. I am (slowly) working on a tool that uses an LLM to add tags to music based on vibes and it would be awesome to plug into this!”
Comment from 11 Nov 2025 in “Beets: The music geek’s media organizer” “Having hit those first two pain points, I changed my transcode config to 1) run every time, and 2) use a custom bash script as the transcode command.”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer”
What people warn about
Each mark is one comment
Hard to set up and learn
“It's an incredible resource. To be fair it's not the easiest of things to get started with and the usability could be better”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” “it takes tons of time and experimentation to cram some things into its model”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” “it was a rough process when I moved my library to it”
Comment from 5 Oct 2026 in “Picard 3.0” - Comment from 27 Jan 2026 in “The state of Linux music players in 2026”
Crashes and lost progress
“crashes are frequent and sometimes make it lose all incremental progress”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” “Beets crashes with a Musicbrainz connection error more than half the time”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” Too much effort for the benefit
“it's more effort for my use case than I'd like”
Comment from 10 Nov 2025 in “Beets: The music geek’s media organizer” “the overhead wasn't worth it”
Comment from 31 Dec 2025 in “Ask HN: How to go back to listening to MP3s?”
What people recommend instead
The same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| BeetsThis page | 33 | 10 | 77% | 5 | — | Approved |
| MusicBrainz Picard | 25 | 4 | 86% | 3 | — | — |
What people said
35 of the 44 comments that mention it, newest first. Each links to the original comment.
“Worked reasonably well on some retagging, better dir layout.”
“it was a rough process when I moved my library to it”
“Beets isn't a daemon like GP asked for. You have to import files manually.”
“it just seemed very finicky for me”
“that works better for me, at least from a”
“claude and beets are helping”
“beets imports it and museFS autoscans it. That handles 99% of cases silently in the background”
“I don't trust automatic tools to do these things after bad experiences with beetz”
“I still don't really understand beet”
“the overhead wasn't worth it”
“But for a nontechnical person the error message might be a bit hard to interpret.”
“this is so cool. I am (slowly) working on a tool that uses an LLM to add tags to music based on vibes and it would be awesome to plug into this!”
“beets is mainly a better tool for accomplishing the same tag and file janitoring”
“the real value (IMO) of beets is it's a powerful toolbox for managing a large music library”
“Beets is amazing. The fact that it exists is a blessing for those like us who maintain our own music library.”
“Once you're over the hump of the first import, beets is a fabulous tool for ingesting new music.”
“Beets crashes with a Musicbrainz connection error more than half the time”
“Having hit those first two pain points, I changed my transcode config to 1) run every time, and 2) use a custom bash script as the transcode command.”
“I still sometimes get unexpected behavior when using Beets this way”
“crashes are frequent and sometimes make it lose all incremental progress”
“beets can't delete transcoded files which have been deleted at source.”
“it's more effort for my use case than I'd like”
“It's wildly flexible and configurable.”
“it was very underwhelming in comparison”
“I've loved beets (and MusicBrainz Picard) for years.”
“it will screw up verification checksums”
“it takes tons of time and experimentation to cram some things into its model”
“It's a good tool. However, last I checked, it was not possible to run it in a one-shot stateless fashion”
“I find it completely useless to have tags like genre=Post Rock Jazz Fusion”
“There is a webpage on beets website where they list all the functions and explain what it does.”
“I would not know how I'd ever get it done without Beets.”
“It's an incredible resource. To be fair it's not the easiest of things to get started with and the usability could be better”
“beats can also auto tag based on file name and populate musicbrainz”
“I use beets and I currently have added 2697 releases (2543 release groups) to MusicBrainz.”
“nothing is quite so flexible”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.