Metadata Remote

Metadata Remote is a lightweight web-based audio metadata editor for headless servers that lets you edit audio file tags through a browser without CLI tools,…

  • Media Applications
  • Media Servers
  • Tools & Utilities
Metadata Remote is a lightweight web-based audio metadata editor for headless servers that lets you edit audio file tags through a browser without CLI tools, file transfers, or complex music-library managers.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

44/100 Fair

Maintained
24last commit 487 days ago
Popular
57737 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data
Security check
67no serious findings, 3 minor, CI

Based on 4 of 5 factors.

Availability: platform listings confirmed today, links checked 20 days ago

GitHub stars
737
Open issues
35
Last commit
2025-07-22
Latest release
v1.2.0
License
AGPL-3.0
Activity
stale

Checked 6 days ago - source: GitHub (wow-signal-dev/metadata-remote)

Resources & Compatibility

Requirements not published yet.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • List image names and tags in workflow In the workflow, fill `images` with the registry/server and name where the Docker image (the packaged app) should be pushed, and `tags` with the labels you want on each build; missing either leaves the action with nowhere to publish or no tags to create. source
  • Add registry login before build/push For every registry listed in `images`, add a Docker login step before the build-and-push step and keep the password in a secret; without it, Docker cannot push your image and the workflow fails. source
  • Use valid version tags like v1.2.3 If your workflow runs on version tags, use full semantic versions with major.minor.patch, such as v1.2.3; shorter tags like v1.2 are not valid semver and will make the action fail. source
  • Docker Quick Start Use the repository's docker-compose.yml to start the container and open the web editor in a browser. source
  • Quick Start Use the project's docker-compose.yml, edit the music directory path, start the container, and open the web UI in a browser. source

Fetched today - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Do I need a separate music-library server to use Metadata Remote?

No. The project description says it can be used without complicated music library ecosystems, just Docker and a browser.

Do I have to transfer audio files or use command-line tools to edit metadata?

No. The forum thread describes it as a web-based audio metadata editor for headless servers that avoids command-line workarounds and file transfers.

What should I check if the Docker container has problems?

The Synology guide says to check its Common Docker issues article if you encounter issues with the container.

Answers sourced from github.com, mariushosting.com, www.forum-nas.fr

Community

Collected 49 days ago - public community threads