JellySearch
A fast full-text search proxy for Jellyfin.
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.
26/100 Low
- Maintained
- 37last commit 364 days ago
- Popular
- 00 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 43 days ago
- GitHub stars
- 0
- Open issues
- 0
- Last commit
- 2025-11-22
- License
- MIT
- Activity
- stale
Checked 20 days ago - source: GitHub (yeyudekuangxiang/jellysearch)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Add Meilisearch and match its key Start a Meilisearch container first, and give it the same MEILI_MASTER_KEY value in both JellySearch and Meilisearch. Without the same secret, JellySearch cannot talk to Meilisearch and searches will fail. source
- Point JellySearch at Jellyfin config Mount your existing Jellyfin config folder to /config (read-only) and set INDEX_CRON for how often it reindexes. This lets it find your library metadata; without it, there’s nothing to index. source
- Only forward search requests to port 5000 In Traefik, nginx, or Nginx Proxy Manager, send only requests with a searchTerm to JellySearch on port 5000 while all other traffic goes to Jellyfin. If you miss this rule, searches won’t use JellySearch; if you forward all traffic, Jellyfin can break. source
Fetched 45 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
What authentication issue may appear when forwarding a Jellyfin request to JellySearch?
Users have seen JellySearch logs report missing header authentication when a request from Jellyfin is sent to JellySearch. The forwarded request may need the correct authentication header.
Does the official repository target native Debian Jellyfin installs?
A community report said the official Gitlab repo appeared to target only Jellyfin installed on a Docker instance. Native Debian Jellyfin installs may therefore not be the intended target.
What search performance benefit have users reported from JellySearch?
Users have said JellySearch gives better performance on search results in Jellyfin.
Answers sourced from forum.jellyfin.org, www.redditmedia.com
Community
- JellySearch - Page 2 (forum)
- JellySearch - Page 4 (forum)
- Reddit (reddit)
- JellySearch - forum.jellyfin.org (forum)
- Jellyfin Forum (forum)
Collected 49 days ago - public community threads