Watchable
Syncs watch state (played, unplayed, and in-progress position) between Plex, Jellyfin, and Emby through a local SQLite database, with no direct…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
51/100 Fair
- Maintained
- 88last commit 12 days ago
- Popular
- 61 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
Based on 3 of 4 factors.
Availability: platform listings confirmed today, links checked 17 days ago
- GitHub stars
- 1
- Open issues
- 0
- Last commit
- 2026-11-09
- License
- MIT
- Activity
- declining
Checked yesterday - source: GitHub (Poag/watchable)
Resources & Compatibility
Requirements not published yet.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Configuration All configuration lives in one YAML file: the media servers to connect, per-person account mapping, and which sync pairs run one-way or bidirectional. The full setup walkthrough is in the repository README. source
- Getting started All configuration is file-based. Edit one YAML file to add each Plex, Jellyfin, or Emby server, map each person's account, and define sync pairs as one-way (one server always wins) or bidirectional with a conflict rule. State is reconciled through a local SQLite file. source
Fetched today - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Does Watchable sync media servers directly to each other?
No. Each run pulls current watch state from the configured servers into a local SQLite database, reconciles it there, and then pushes out only the changed state.
How does Watchable match the same movie or episode across Plex, Jellyfin, and Emby?
It matches items using external IDs such as IMDb, TMDb, or TVDb, since each server may assign different internal IDs to the same item.
How can I check a config or preview a sync before it happens?
Use watchable validate to check the YAML, watchable test-connections to verify servers are reachable, and watchable sync --dry-run to see what a sync would do.
How should Watchable be run continuously?
The simplest option is a cron job or systemd timer calling watchable sync. A Docker image can also run watchable as a long-lived process by setting sync.schedule.interval_minutes.
How are database backups handled?
Use watchable backup create, list, restore, and purge for manual snapshots. With watchable run, set backup.interval_hours for scheduled backups and backup.keep_days for automatic old-backup purge.
What happens when two servers both have different watch states?
For one-way pairs, one server always overwrites the other. For bidirectional pairs, you can choose most-progressed-wins, most-recently-played-wins, or a fixed side always wins.
Answers sourced from github.com
Community
Collected 48 days ago - public community threads