Overseerr Content Filtering works perfectly with just TMDB (The Movie Database) API data, but you can optionally enhance your TV show metadata by configuring TVDB (The TV Database) API access.
Short answer: No, it's optional.
Your Overseerr Content Filtering installation works completely without TVDB:
✅ TV show search and discovery - Works with TMDB data
✅ Content filtering and safety controls - All based on TMDB data
✅ User requests and management - Full functionality
✅ Plex integration - Complete integration
If you configure TVDB, you'll get:
- Enhanced TV show metadata - More detailed episode information
- Additional artwork - Extra posters, banners, and fanart
- More comprehensive cast/crew information - Extended credits
- Alternative series titles - Names in different languages
- TVDB-specific ratings - Additional rating sources
- Go to https://thetvdb.com/
- Click "Sign Up" to create a free account
- Verify your email address
- Complete your profile setup
- Once logged in, go to https://thetvdb.com/api-information
- Click "Request API Key"
- Fill out the application form:
- Project Name: "Personal Overseerr Instance"
- Project Description: "Personal media management and discovery"
- Project URL: Your Overseerr URL (e.g., "http://localhost:5055")
- Contact Email: Your email address
- Intended Use: "Personal media server metadata enhancement"
- Cost: Free for personal/non-commercial use
- Approval Time: Usually immediate to a few hours
- Rate Limits: Generous limits for personal use
- Format: You'll receive a string like
1e722fb646416fa55d471b9595ee83becadd
- Get your TVDB API key (see above)
- Stop your Overseerr container:
docker stop overseerr-content-filtering
- Edit your settings.json file:
# Find your config directory (usually bind mount or volume) docker inspect overseerr-content-filtering --format='{{range .Mounts}}{{if eq .Destination "/app/config"}}{{.Source}}{{end}}{{end}}' # Edit the settings file nano /path/to/your/config/settings.json
- Add TVDB section to your settings.json:
{ "main": { ... }, "tvdb": { "apiKey": "your-tvdb-api-key-here" }, "plex": { ... } } - Restart your container:
docker start overseerr-content-filtering
Add the TVDB API key as an environment variable:
docker run -d \
--name overseerr-content-filtering \
-p 5055:5055 \
-v /path/to/config:/app/config \
-e TVDB_API_KEY=your-tvdb-api-key-here \
--restart unless-stopped \
larrikinau/overseerr-content-filtering:latestversion: '3.8'
services:
overseerr-content-filtering:
image: larrikinau/overseerr-content-filtering:latest
container_name: overseerr-content-filtering
ports:
- 5055:5055
volumes:
- /path/to/config:/app/config
environment:
- NODE_ENV=production
- RUN_MIGRATIONS=true
- TVDB_API_KEY=your-tvdb-api-key-here
restart: unless-stoppedThe migration script (migrate-to-content-filtering.sh) will:
✅ Automatically detect existing TVDB API keys from your old installation
✅ Migrate them to the new content filtering installation
✅ Handle missing keys gracefully - won't fail if TVDB isn't configured
✅ Provide helpful messages about optional TVDB configuration
If migration reports missing TVDB key:
No TVDB API key found (optional - you can configure this later)
This is not an error - it's just informing you that TVDB wasn't configured in your original installation.
A: This shouldn't happen with the updated migration script. TVDB is optional and missing keys are handled gracefully.
A: Follow the manual configuration steps above - you can add it anytime.
A: Look for enhanced TV show metadata, additional artwork, and more detailed episode information in your Overseerr interface.
A: Yes, just remove the tvdb section from your settings.json and restart the container.
Remember: All your content filtering features work with or without TVDB:
- ✅ Global adult content blocking
- ✅ Admin-only rating controls
- ✅ TMDB Curated Discovery
- ✅ Age rating restrictions
- ✅ Family safety controls
TVDB only adds extra metadata - it doesn't change your content filtering functionality.
If you have issues with TVDB configuration:
- Check your API key - Make sure it's valid and active
- Verify JSON syntax - Ensure settings.json is properly formatted
- Check container logs -
docker logs overseerr-content-filtering - Test without TVDB - Your installation works fine without it
For more help, see the main project documentation or create an issue on GitHub.