this post was submitted on 17 Jun 2026
32 points (94.4% liked)
Selfhosted
60281 readers
645 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I run Jellyfin with hardware transcoding via QuickSync (through VAAPI) on a 10th-gen i3 NUC, 16gb RAM, and it seems to handle it comfortably. Your hardware should definitely be capable.
This is Proxmox with Jellyfin as native install in an LXC so it's not exactly identical to your current setup, but what I found was that passing the device through is only half of it - the host also needs the Intel driver in place for QuickSync to actually work. Try running vainfo on the host to check, if it doesn't list H.264/Hevc encode, the GPU block isn't available yet and Jellyfin will fall back to software - this is probably what you're seeing with the maxed out CPU.
After THAT, make sure Jellyfin has permission to use the passed-through device.
I was just going through this last week, migrating JF off my NAS, and it took some fiddling to get it working.