Latest Blog
Why Jellyfin Home-Server Architecture Changes as You Add Services
A Jellyfin box becomes a service stack as more apps are added, so CPU, storage, network, secrets, backups, and recovery boundaries need explicit ownership.
How to Measure Jellyfin Performance Without Mistaking Cache for Capacity
A reliable Jellyfin benchmark labels cold and warm state separately so cached metadata or filesystem pages are not mistaken for permanent hardware capacity.
How Much iGPU Headroom Does Multi-User Jellyfin Need?
Jellyfin iGPU headroom is workload-specific: reserve margin above the hardest repeatable concurrent transcode mix, not an arbitrary utilization percentage.
Why Jellyfin Feels Faster on Some Clients Than Others
Client capability can change both local UI behavior and the server playback path, making “Jellyfin speed” a combined client-server result.
How to Validate Smooth Jellyfin HDR Playback With Subtitles
Validate sustained HDR plus subtitle playback with the real client, burn-in path, concurrency, and a measured transcode failure threshold.
How Storage Latency Affects Multi-User Jellyfin Streaming
Multi-user Jellyfin can become latency-bound when state access and concurrent media reads queue despite adequate headline throughput.
Jellyfin Data Paths Explained: What Must Persist and What Can Be Rebuilt
Jellyfin becomes easier to upgrade and recover when durable server state, rebuildable cache, temporary transcodes, and authoritative media have separate roles.
How Jellyfin Turns Client Limits Into a Transcoding Pipeline
Client support determines which media stages Jellyfin must change, so the same file can create very different server workloads across devices.
