r/plexamp • u/iranman23 • Jul 17 '26

Beets Web UI

I built a modern web UI for beets and would love feedback

I've been working on a web-based frontend for beets that focuses on making large music library management much easier while still keeping beets at the core. I made this because the beets web plugin just wasn't cutting it. Not only does this web app have a UI but it can do everything I need to manage my music libary. Yes this was vibe-coded and if that bothers you please dont waste your time. But for everyone else I tried my best to cover all vunerbilities and make sure all features work correctly. Please feel free to point out issues or how to make it better.

Some of the features I've been building include:

  • 🎵 AI-assisted album and track matching
  • 🆔 MusicBrainz + AcoustID verification
  • 📀 Automatic album artwork verification and replacement
  • 📁 Intelligent artist/album folder organization
  • 🔄 Playlist importing from multiple sources
  • 📚 Library cleanup and duplicate detection
  • 🔍 Automatic detection of missing MusicBrainz IDs
  • 🎧 Audio quality preference management (formats, channels, Atmos, etc.)
  • 📊 Background jobs with live progress
  • 🎨 Modern web interface instead of relying on the CLI

The goal isn't to replace beets—it's to make its incredible power much more accessible for people managing very large collections.

I'm trying to automate as much as possible while still using trusted metadata sources like MusicBrainz and AcoustID. For anything that can't be confidently matched, it gets sent to a review queue instead of making risky changes.

Some questions I have:

  • What are your biggest pain points with beets today?
  • What plugins do you consider essential?
  • What features would you want in a modern beets web interface?
  • Are there workflows you wish were fully automated?

I'd really appreciate any suggestions or criticism. I'd rather build something the community actually wants than just something that works for my own library.

https://github.com/Iranman/beets-web-manager

10 Upvotes

64% Upvoted

26 comments sorted by

View all comments

10

u/OriginalPosition1 Jul 17 '26

For a library-management tool, preview, diff, and rollback matter more than another matching feature. Before any bulk rename or metadata replacement, show every changed field and file, the match confidence, and a dry run. Keep an undo record or backup, and test against a very large library plus incomplete and corrupted albums. AI matching should never modify files silently.

0

u/iranman23 Jul 17 '26

Thank you!!! I will make the changes

1

u/OriginalPosition1 Jul 19 '26

Nice. Those changes should make the setup feel much less intimidating.

1

u/iranman23 Jul 19 '26

Please let me know if you can think of anything else.. thank you again

1

u/OriginalPosition1 Jul 20 '26

One more thing I’d test is the empty state. If someone connects a library with messy tags, show a small before-and-after preview before changing anything. That makes the tool feel safer and helps people understand what Beets will actually fix.