pkg.soopen package index

cask

Install jellyfin with Homebrew Cask

Media system. Version 12.4 via Homebrew Cask; verified from local package data.

install

Additional install commands

macOS

Homebrew Caskverified · 100%
brew install --cask jellyfin

local Homebrew cask metadata

overview

Package summary

Media system

Commands and aliases

No executable aliases were found in the local package database.

history

Project history and usage

Jellyfin is a community-developed free-software media server for organizing and streaming personal media to a broad range of clients. It was forked from Emby in 2018 in response to Emby's move toward closed-source development.

Project history

Jellyfin began in early December 2018 after Emby announced that its 4.x release would be closed source. The founders forked the legally available Emby repositories, renamed the project, and continued development with a free-software ethos.

The server descends from Emby 3.5.2 and was ported to .NET Core for cross-platform support. Development is coordinated by a worldwide volunteer community that maintains the server, web interface, documentation, translations, plugins, and clients.

Adoption history

Jellyfin grew as a volunteer-run, fully free-software alternative to Emby and Plex. Its server is paired with web, desktop, mobile, television, and other clients maintained across the Jellyfin organization.

Its no-premium-feature model and support for native packages, containers, NAS platforms, and multiple operating systems have made it a prominent self-hosted media-server choice.

How it is used

Administrators install the Jellyfin server, add media libraries, create local users, and stream content through web or native clients. The server can direct-play compatible media or transcode it for client and network constraints.

Common deployments range from a macOS desktop application to Linux services, containers, NAS systems, and home servers. Configuration is primarily managed through the administrator dashboard, with startup paths, logging, networking, and advanced database behavior available through files, environment variables, and command-line options.

Why package nerds care

Jellyfin is a major example of a community preserving a self-hosted application after its upstream moved toward proprietary development. Package maintainers handle a substantial .NET server, web client, FFmpeg integration, hardware acceleration, and a wide client ecosystem.

Administrators value that the complete server remains auditable and self-hostable without license-gated features. Its explicit data, configuration, cache, and log paths also make it suitable for declarative deployments, containers, and backup automation.

Timeline

  • December 2018: The Jellyfin project began as a fork of Emby 3.5.2.
  • 2018 onward: The project expanded into a volunteer-maintained server, client, plugin, translation, and documentation ecosystem.
  • 10.11: Jellyfin added a built-in server backup facility.

Related projects

  • Emby 3.5.2 is Jellyfin's direct technical ancestor.
  • Plex and modern Emby are the principal proprietary media-server alternatives identified by the project.
  • Jellyfin Web and the various Jellyfin client projects provide interfaces to the core server.
  • FFmpeg supplies media probing and transcoding capabilities.

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for jellyfin. Package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
/etc/jellyfin~/.config/jellyfin
macOS
~/.config/jellyfin~/.local/share/jellyfin~/Library/Application Support/Jellyfin

executables

Installed executables

CommandKindExposureNote
No executable data was present.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-11-04
manager version12.4
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://jellyfin.org/

  • infoNo package-manager update timestamp was available.low confidence
  • infoRelease/tag comparison is only available for GitHub repositories.https://jellyfin.org/none confidence

install metadata

Package metadata

Package keycask:jellyfin
Version12.4
Package managerHomebrew Cask
Package manager pagehttps://formulae.brew.sh/cask/jellyfin
Homepagehttps://jellyfin.org/
Upstream docshttps://jellyfin.org/
Source archivehttps://repo.jellyfin.org/files/server/macos/stable/v12.4/arm64/jellyfin_12.4-arm64.dmg
SHA-256504c0e201e4d9374403300622317b9a6b8b86f860a2a52eea5734f9abf70769d
Bottlenot recorded
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokenjellyfin
Names
  • Jellyfin
Depends On
Artifacts
Deprecatedno
Disabledno

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment