Where Does tinyMediaManager Store Settings and Data?
tinyMediaManager is portable: settings live as JSON files in a data folder inside its own installation directory.
Last updated
tinyMediaManager stores settings next to itself. Files like tmm.json plus per-library JSON sit in the data folder inside the installation directory. There is no registry footprint or home-directory config.
That portability makes migration a folder copy. Artwork caches and scraper settings move with the program. Media file paths are the only external dependency, so keep drive letters and mounts stable.
Where tinyMediaManager stores this, by platform
<install-dir>\data (tmm.json, movies.json, tvshows.json)
Portable install with settings in its own data folder. Copy the folder to migrate everything. Keep media paths stable or expect a rescan.
<install-dir>/data (tmm.json, movies.json, tvshows.json)
Same portable layout on Mac. Settings sit beside the binary, not in Library folders. Folder copy covers settings, caches, and library state.
<install-dir>/data (tmm.json, movies.json, tvshows.json)
Same portable layout on Linux. Docker setups map the data folder as a volume instead. yt-dlp cookies file also lives in data when configured.
Frequently asked questions
How do I move tinyMediaManager to a new computer?
Copy the whole installation folder to the new machine. Settings, artwork cache, and library state travel together. Point it at the same media paths afterward.
Can tinyMediaManager run portably?
Yes. Keep the program on the portable drive and the data folder rides along. Media paths should stay consistent between machines or the library rescans.
Notice an outdated path? Let us know.