Version-scoped Jellyfin hardware, storage, network, and acceleration requirements used by the pilot transcode recipe.
record type
app
record at a glance
release scope
>=10.11.0 <10.12.0
public recipes
1
best attached evidence
grade B
accepted grade A runs
0
version contract
application
Jellyfin Server
modeled release
10.11.x
effective version range
>=10.11.0 <10.12.0
record state
candidate
A future release outside >=10.11.0 <10.12.0 requires impact review. This page must not silently transfer these requirements to a materially different version.
deployment methods in scope
nesting depth 2
Jellyfin Docker container in a Debian KVM virtual machine
runtime: KVM virtual machine → Docker Engine on 64-bit Linux · nesting depth 2
This deployment method is modeled by the pilot but has not been reproduced in an accepted physical-mini-PC lab run.
requirements used by public recipes
One concurrent 1080p Jellyfin hardware transcode
Documented prerequisite fit only. Stream stability, quality, tone mapping, codec coverage, and concurrent throughput require Grade A lab results.
minimum / recipe-required
3
recommended
4
workload-dependent scope
this bounded recipe only
8 GiB recommended system memory
memory · recommended
at least 8
SSD for Jellyfin files and transcode cache
storage · recommended
one of nvme-ssd or sata-ssd
100 GiB SSD application and cache allowance
storage · recommended
at least 100
Intel Quick Sync device
media · required
required
Hardware acceleration configured and passed through
media · required
required
Wired gigabit networking
network · recommended
at least 1
Media storage able to sustain the source bitrate
storage · required
required
architecture / acceleration conditions
Intel Quick Sync device — required
Hardware acceleration configured and passed through — required
No exact hardware configuration has an accepted Grade A result for this application version. The page therefore makes no measured performance claim.
what these requirements do not prove
They do not prove sustained throughput, latency, stability, thermals, or power.
They do not prove that every codec, integration, plugin, or storage topology works.
They do not turn a platform family into an exact physical configuration.
They do not authorize a “recommended” ranking without a declared workload.
Scoped Grade A results: 0. This page exposes version-scoped prerequisites from official sources and the pilot’s modeling boundary.
receipts
3 sources · 0 accepted grade A runs · best evidence grade B · reviewed 2026-07-26
record identity, publication and review
record id
app-jellyfin-10-11
canonical path
/apps/jellyfin/
publication
preview · noindex
reviewed
2026-07-26
review again by
2026-08-02
evidence boundary
Grade A count: 0. A Grade B source can establish a documented specification or requirement. Grade D records are modeling inputs. Neither is proof of measured throughput, thermals, power, reliability, or physical fit.
4 attached evidence records
a grade describes how well attested a statement is, not how good the hardware is. grade a is a lab run we reproduced with a published method. grade d is a model, a reasoned inference, or a single unverified report.
Jellyfin recommends 8 GB RAM, SSD storage for application data and transcode cache, wired gigabit networking, and properly configured hardware acceleration for transcoding.
Jellyfin says Intel 7th through 10th generation integrated graphics remain capable for existing owners, but are no longer recommended for a new purchase because Intel deprecated the relevant toolkit.
This projection is generated from homelab graph version 0.1.0. The generated lifecycle index exposes only history events that are explicitly present in the structured record. It does not invent an earlier revision when the graph contains only its creation baseline.
— current preview record reviewed against the attached evidence set.
— next required review under the weekly software review interval.
— created: Initial version-scoped software record created.
