I set Jellyfin up with an iGPU for transcoding, and it was a game-changer for my entire family

Published Sep 7, 2026, 3:00 PM EDT Samir Makwana is a technology journalist and editor from India since past 18 years and his work appears on MakeUseOf, HowToGeek, GSMArena, BGR, GuidingTech, The Inquisitr, TechInAsia, TechWiser, and others. He has written news, features, and gadget reviews for national technology media publications. His passion is to help people with their technology problems and gadget purchases. For that, he has worked for some of the biggest international technology publications, covering news, explainers, how-to guides, listicles, and product-buying guides. He has worked as an editor and managed teams since 2015. His expertise broadly covers computers, smartphones, game consoles, headphones, smart home products, browsers, and apps. My family enjoys watching content on TV or their phones. None of them care about resolution, bitrates, or which codec is quietly doing the work behind the scenes. That’s fair. All they care about is whether the movie or show loads. Since last year, my HP ProDesk 600 G6 mini PC has been running Jellyfin just fine for one person at a time. Things fell apart when I struggled to stream a 4K remux on my phone while my nephew was watching a 4K show. The stutter only became apparent on the second concurrent stream. The fix was Intel Quick Sync, sitting unused inside the Core i5-10500T the whole time. After installing Jellyfin on a Debian VM, I never touched hardware transcoding because I had set up the media server mostly for myself. My family’s mismatched devices silently broke my server No two screens worked with the same codec My house runs a mix of streaming devices, and the only thing they all agree on is the home network. The living room TV’s built-in apps choked on the 10-bit HEVC video. My iPhone and iPad handled almost everything smoothly. Things got dicey whenever the home internet dropped, and everyone’s devices switched to mobile data instead. This isn’t unusual for a family that doesn’t upgrade devices every year. But Jellyfin was quietly transcoding for some of those devices the entire time. Only when I checked resource usage with htop did I learn that the CPU was transcoding everything all along. All the cores were swinging into action whenever a single 4K HEVC file was getting transcoded for an Android tablet. I had to fix it myself, since nobody in my house was about to learn which codecs their device does or doesn’t support. Enabling Intel Quick Sync on my mini PC took five minutes A decade-old iGPU did the heavy lifting I run Proxmox on the ProDesk 600 G6 mini PC to use it as a home server. I run Jellyfin inside a Debian 13 (Trixie) VM since I’d rather deal with a full VM than fight LXC container permissions. Thanks to that, I can pass the iGPU through cleanly instead of juggling the container device permissions. Intel Comet Lake processor’s UHD Graphics 630 supports Quick Sync video encoding before I turned the mini PC into a home server. As long as Jellyfin kept streaming fine, I never bothered turning it on. After binding and passing through the iGPU to the VM, I installed Intel’s media drivers inside the VM running Jellyfin. Then I flipped hardware acceleration in Jellyfin’s Playback settings. If you’re starting from scratch, check out our guide to build a 4K Jellyfin server with Intel Quick Sync. Or, check whether the iGPU you already own is good enough before you go anywhere near today’s eye-watering GPU prices. The real test was streaming from Jellyfin on three devices at once The 16GB of RAM had some headroom to spare The real test wasn’t a benchmark; it was actually using the thing. I asked my mother and nephew to start streaming from the Jellyfin server on their devices and on the living room TV. All three transcodes ran simultaneously without moving the needle on my mini PC’s CPU usage. That’s because the UHD Graphics 630 handled the transcoding while the 16GB of RAM had plenty of headroom to spare. That hardware also manages a handful of self-hosted services without a complaint. So transcoding wasn’t putting much load on it. That’s when it clicked. This old chip could do a job a discrete GPU would’ve been overkill for. So I scrapped my plan to buy a PCIe riser and a GPU. Next, I gave everyone their own Jellyfin logins. On the backend, I set a per-user bitrate cap. That prevents any device from consuming bandwidth intended for someone else or for another task. Thanks to Quick Sync taking on encoding duties, I could use the CPU headroom without worrying about reducing streaming quality. In the end, hardware transcoding resolved the compute bottleneck, and the per-user bitrate cap kept bandwidth fair. Direct Play still works while transcoding only fills the gaps Making peace with the iGPU’s limits Even though I enabled hardware transcoding, I didn’t want to run it constantly. Most of my library still defaults to Direct Play on whatever device requests it. Jellyfin reaches out to the GPU only when a client genuinely can’t handle the source file. That’s why picking better Jellyfin clients matters more in the long term than relying entirely on hardware transcoding. The UHD Graphics 630’s Quick Sync engine handles H.264 and HEVC, including 10-bit, without breaking a sweat. But it can’t decode AV1 because it arrived with Intel’s later Xe-generation graphics. Thankfully, my library doesn’t lean heavily on AV1. A discrete GPU is still on my upgrade list, if I ever actually need one. For now, the iGPU I already own is doing just fine. Harmony is the upgrade that mattered None of my family members complained about a stuck or stuttering stream once I set Jellyfin to use the iGPU for transcoding. That capability had been sitting idle the whole time, in a chip already carrying Proxmox and a handful of other services. Most importantly, I didn’t have to touch anyone’s devices or spend a dime to make it happen. If you’re running Jellyfin on similar hardware, check whether your iGPU supports hardware transcoding before you go shopping for a discrete GPU. Once you set up transcoding on your Jellyfin server with compatible hardware, the CPU will no longer be a bottleneck. Jellyfin iOS compatible Yes Android compatible Yes Desktop compatible Yes