TinyMediaManager: The Metadata Power Tool for Movie Enthusiasts
Have you ever experienced this —
You scan your movie library in Emby or Jellyfin, and half the covers are empty. After it finally finishes scanning, you find that “The Matrix” got matched as “Mr. Robot,” and “Inception” has a Japanese poster. You spend an hour fixing it manually, with hundreds more waiting for you.
This isn’t your fault — it’s a common problem with media servers’ built-in scrapers. Their design goal is “display,” not “batch organization.”
TinyMediaManager (TMM for short) is here to solve this problem.
What is TMM
TinyMediaManager is a cross-platform media metadata management tool, written in Java/Swing. Simply put, its job is: to turn your movie and TV show files into complete metadata packages that media servers can read directly.
It supports the following media servers:
- Kodi (XBMC)
- Emby
- Jellyfin
- Plex
TMM is open source on GitLab, the repository is at gitlab.com/tinyMediaManager/tinyMediaManager. The latest version is v5.2.12.
Why You Need TMM
Media servers’ built-in scrapers have several fatal weaknesses when dealing with large media libraries (hundreds or thousands of movies):
1. Insufficient Recognition Accuracy
Non-standard filenames lead to recognition errors. Emby’s built-in scraper often fails with naming conventions like “xxxx.2024.1080p.mkv,” while TMM allows manual matching and multi-source cross-referencing for much higher accuracy.
2. No Batch Editing Capability
Want to batch change posters for 50 movies in Emby? You’d have to click each one individually. In TMM, select a batch and replace all posters with one click.
3. High Error Recovery Cost
If Emby scrapes incorrectly, you have to find the problem, clear the wrong data, and re-scrape. TMM works by scraping to local NFO files first, which the media server reads — if it’s wrong, just re-scrape without affecting the server.
4. Different Network Requirements
TMM supports proxy configuration, allowing different proxies for TMDB and TheTVDB. Emby’s global proxy can sometimes interfere.
TMM’s Core Workflow
TMM operates in a “preprocessing” mode — preparing metadata before your media server ever touches the files.
The workflow goes like this:
- Add media sources — Tell TMM which directories your movies/TV shows are in
- Update media library — TMM scans directories and identifies all media files
- Search and scrape — TMM fetches metadata from TheMovieDB, TheTVDB, Fanart.tv, etc.
- Generate NFO files — Save scraped information as Kodi/Emby/Jellyfin-compatible NFO files
- Download posters and stills — Posters, backgrounds, logos, etc. are all downloaded locally
- Rename and organize — Unify file names and directory structures according to your naming rules
- Media server reads NFO — When Emby/Jellyfin scans, it reads local NFO files, completing in seconds
The key point is in steps 4-6: All metadata is stored as local files, not tied to any media server.
This means: you can switch media servers anytime (from Emby to Jellyfin), and TMM’s NFO files are universal. You can also reinstall anytime — no data loss.
Core Feature Overview
Movie Management
- Scrape metadata from multiple sources including TheMovieDB, IMDb, OFDb
- Download posters, backgrounds, logos, disc art, etc.
- Fetch trailer lists
- Subtitle search and download (requires OpenSubtitles VIP)
- Edit metadata, manual matching
- Batch rename files and directories
- Sort, filter, and search by multiple criteria
TV Show Management
- Auto-detect episodes and seasons, supports nested subdirectories
- Scrape from TheTVDB, TheMovieDB, and other sources
- Episode-level metadata management
- Supports various naming conventions
Movie Collection Management
- Auto-group movies into collections (e.g., Marvel Universe, Harry Potter)
- Collection-level posters and artwork
- Display as collections in Kodi/Emby/Jellyfin
NFO Files
- Generate Kodi, Emby, Plex, Jellyfin-compatible NFO
- Import NFO generated by other tools (e.g., EmberMediaManager)
- NFO files are stored alongside movie directories for completeness
Technical Information Extraction
- Use the MediaInfo library to extract video codec, resolution, bitrate, audio tracks, etc.
- This information is written into NFO files for media servers to read directly
Free vs Pro Version
TMM is free and open source. The Pro version is paid (to support development) with these key differences:
| Feature | Free | Pro |
|---|---|---|
| Movie Scraping | ✅ Full | ✅ Full |
| TV Show Scraping | ✅ Full | ✅ Full |
| Poster Quality | Standard | High resolution preferred |
| Scraper Selection | TMDB | TMDB + Multi-source |
| Auto Scraping | Manual trigger | Automatic background scraping |
| Command Line | ✅ | ✅ |
| HTTP API | ✅ | ✅ |
For most home users, the free version is more than enough. The Pro version is suitable for those pursuing the best image quality or needing fully automated unattended operation.
Use Cases
- Home theater users: Emby/Jellyfin/Plex users who want a more beautiful media library
- NAS users: Running media servers on Synology/QNAP, preprocessing metadata with TMM
- Big collectors: Thousands of movies/TV shows needing batch management
- Perfectionists: File names must be standardized, posters must be uniform, series must be categorized
Summary
TMM isn’t a replacement for your media server — it’s its partner. One handles display, the other handles organization.
If you run Emby or Jellyfin at home and start running into scraping issues as your movie collection grows, TMM is the tool you need.
The next article will cover installation and configuration on Ubuntu and Docker, along with tips for using it with Emby/Jellyfin.
Comments