Where Does mov-cli Store Its Config?
mov-cli keeps config.toml per OS (with a version key), openable any time with mov-cli -e. CLI flags win.
Last updated
mov-cli centers on config.toml with a version key guarding against breaking changes. Player choice, downloader paths, subtitle handling and the plugin table all live there, with CLI flags overriding per run.
Plugins deserve emphasis because v4 ships none built in. Install the provider package, register it under mov-cli.plugins, and only then does scraping work at all.
Where mov-cli stores this, by platform
%LocalAppData%\mov-cli\config.toml
Player, downloads, subtitles, plugins table. Edit with mov-cli -e; CLI options beat the file. Note upstream flags v4 unmaintained, so pin working versions.
~/Library/Application Support/mov-cli/config.toml
Same file (macOS support still partial per the wiki). Plugin packages install via pip alongside the main tool, not inside it.
~/.config/mov-cli/config.toml
Same layout. Forward slashes in download paths even on Windows; backslashes break the TOML parsing silently.
Frequently asked questions
How do I edit the mov-cli config?
Run mov-cli -e. It opens config.toml in your platform editor so you never hunt the path; plugin tables ([mov-cli.plugins]) are the lines you will touch most.
Why does mov-cli find no providers?
Yes: v4 is plugin based, so scrapers install separately (e.g. pip install mov-cli-youtube) and register in the plugins table. No entry there means mov-cli finds nothing to play.
Notice an outdated path? Let us know.