Reference#

Lookup pages for setting up and running MetaTana outside the app's own pages: keys, environment variables, the API and command-line tool, where files live, and the NFO format. For every setting inside the app, see Settings.

• API keys: your own metadata, AI, sync, and subtitle keys, the guided TMDb key setup, and where saved keys are stored
• Deployment modes: desktop, Docker, and the limits each one has
• Environment variables: the variables for Docker and installs without a window
• API: the local API and API-key access (Pro)
• CLI: the metatana command-line tool
• File layout: where the database, backups, trash, and NFO and artwork files live
• NFO format: sample files and which fields are read and written

Settings or environment variables#

Most people configure MetaTana in Settings, where changes save as you make them. Environment variables are for Docker, headless installs, and packaging: use them to start MetaTana with a setup already in place. When the same setting can come from several places, a setting you saved in the app usually wins over a default.

Provider order and languages#

Settings › Providers › Source priority sets which provider fills each field. Metadata language and region are in Settings › General › Language & region, artwork languages in Settings › Providers › More sources, and turning a provider off is in Provider availability under More in Providers. MetaTana ignores a language or region value it doesn't recognize instead of sending it to providers.

Docker paths#

For Docker, set paths as the container sees them, not as the host sees them. If /mnt/media on the host is mounted at /media in the container, add /media as the folder in MetaTana.

Secrets#

Do not publish provider keys, MetaTana session tokens, webhook addresses, or local API keys. In public docs and support reports, name the key and where it is set, never its value. The Settings file backup doesn't include provider keys; database backups do, so keep them private.