MediaMan

MediaMan is a self-hosted media manager for Jellyfin and Emby that scans your existing library and proposes Jellyfin-correct file names, then watches your…

  • Media Applications
  • Media Servers
MediaMan is a self-hosted media manager for Jellyfin and Emby that scans your existing library and proposes Jellyfin-correct file names, then watches your download client to organize new downloads, copying or hard-linking files rather than transcoding so HDR, Dolby Vision, and every audio and subtitle track stay intact.

Platform availability

Available on 1 of 10 platforms

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

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.

40/100 Fair

Maintained
72last commit 9 days ago
Popular
00 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
0
Open issues
0
Last commit
2026-11-12
Latest release
v1.8.1
License
GPL-3.0
Activity
rising

Checked 9 days ago - source: GitHub (MJWaters1985/MediaMan)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • TrueNAS + Jellyfin (or Emby) setup MediaMan is built for a TrueNAS box running Jellyfin or Emby (same folder layout) and must see the same media folders as your media server and download client. Share those paths to the MediaMan container so it can scan the library and file finished downloads. source

Fetched 9 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does MediaMan support hardware encoding for its transcode queue?

CPU encoding is the most used path. AMD VAAPI has been tested on real hardware, while Intel QSV and NVIDIA NVENC are supported by the bundled ffmpeg but have not been tested on real hardware yet.

Does importing a download move the original file out of the client’s finished folder?

It copies or hardlinks the identified download into the correct library folder and leaves the original in place for seeding. It waits until the files stop changing, and if qBittorrent’s Web UI is connected it also waits for qBittorrent to report completion.

When can MediaMan auto-import without manual approval?

Each file receives a confidence score from hints such as IDs, NFO files, existing library structure, release names, embedded tags, and Jellyfin’s TMDb search. Downloads below the auto-import confidence threshold, default 0.75, wait in Downloads for correction.

Does its transcode queue preserve HDR, Dolby Vision, audio, and subtitle tracks?

It targets a VMAF quality goal while keeping resolution, HDR10, HDR10+, Dolby Vision, and every audio and subtitle track. It checks each result before replacing the original file.

Do I need a TMDb account for identification?

No, it asks TMDb through Jellyfin’s own TMDb search to confirm the title and year and add a tmdbid.

Answers sourced from github.com

Community

Collected 9 days ago - public community threads