4 default Plex settings you should never mess with

Published Aug 12, 2026, 4:30 PM EDT Sydney Butler is a technology writer with over 20 years of experience as a freelance PC technician and system builder and over a decade as a professional writer. He's worked for more than a decade in user education. On How-To Geek, he writes commerce content, guides, opinions, and specializes in editing hardware and cutting edge technology articles. Sydney started working as a freelance computer technician around the age of 13, before which he was in charge of running the computer center for his school. (He also ran LAN gaming tournaments when the teachers weren't looking!) His interests include VR, PC, Mac, gaming, 3D printing, consumer electronics, the web, and privacy. He holds a Master of Arts degree in Research Psychology with a minor in media and technology studies. His masters dissertation examined the potential for social media to spread misinformation. Outside of How-To Geek, he hosts the Online Tech Tips YouTube Channel, and writes for Online Tech Tips, Switching to Mac, and Helpdesk Geek. Sydney also writes for Expert Reviews UK. He also has bylines at 9to5Mac, 9to5Google, 9to5Toys, Tom's Hardware, MakeTechEasier, and Laptop Mag. The type of person who likes to self-host services on their home network is often also the sort of person who likes to optimize and tweak everything. For some, it's hard to accept that the default settings in the software they're using are already as good as they're going to get. Plex is a great example. Although there are a decent number of things to tweak and some settings you might want to change immediately, it's mainly interface customization that benefits. But, as for the technical settings on your server or client devices, there are more than a few settings that almost everything should leave alone unless you have a very specific reason to change them. Don't lower the streaming quality just because you can It's not Plex that's the problem Many people seem to think that they need to lower the streaming quality setting for Plex to get good playback. However, you should almost certainly leave this at the default "original" or "maximum" quality setting. While the quality setting tells Plex how high quality can go, it doesn't prevent Plex from automatically changing quality to a lower setting.​​​​​​​ So reducing the quality manually doesn't help with bandwidth issues, because Plex would have compensated for network issues automatically anyway. However, setting the quality to something specific means the source file will now force Plex to transcode it. This puts an unnecessary strain on the server's resources if your client device was capable of playing the file directly anyway. There's generally no reason to be concerned about bandwidth usage on your LANs; most people can ignore these quality settings unless you're actually having playback issues. Even then, you should address your network performance issues first.​​​​​​​ Don't disable hardware acceleration if your server supports it It's worth every penny If you have a Plex Pass either through the lifetime deal or through a monthly subscription, you have access to the hardware acceleration features. While I don't personally agree with the decision to put this feature behind a paywall, if you are paying for Plex and your server supports hardware acceleration, please leave it enabled. Hardware acceleration only kicks in when transcoding becomes necessary, and if you have 4K or even high-quality 1080p content, transcoding it in real time can be too much for some older CPUs. I use a cheap refurbished mini PC with a dual-core Haswell-era Intel CPU. While it's more than powerful enough for direct streaming playback, most of my client devices will play anything you throw at them. However, the built-in GPU can encode video at a rapid pace.​​​​​​​ The only reason to disable hardware acceleration is if you notice quality issues with transcoded material or the feature is broken for your specific hardware. You might want to tweak the transcoder settings first, though. It is, however, true that some CPUs and GPUs have transcoders, which cause quality issues no matter what.​​​​​​​ That said, you can install a dedicated GPU for transcoding in your Plex server instead. It doesn't have to be expensive, powerful, or new. It's a great way to repurpose an old GPU, and Intel's Arc GPUs might be the ideal choice if you can find one cheap.​​​​​​​ Don't force either Direct Play or Direct Stream Just let it happen While the ideal situation is for a file to use Direct Play instead of Direct Stream or transcoding, that doesn't mean you should disable transcoding and force Direct Play or Direct Stream. Plex starts off by trying to use Direct Play, then falls back on Direct Stream, and uses transcoding as a last resort. So, if you disable transcoding of video streams, the only thing you'll achieve is preventing the playback of files that needed transcoding and would never have worked via Direct Play or Direct Stream in the first place. Don't start changing advanced network and security settings Getting your wires crossed is no fun I get it—you're running a network application, and you want it to work better than it does out of the box. Once you dip into the more advanced Plex settings, you can easily just break it and have a media library you can't stream until you reverse the changes you've made. For the most part, Plex will automatically configure itself for your network with no additional help from you. The only time you'll need to mess around with advanced network settings is if you have an atypical LAN setup. But you'll know if there's a problem because Plex will tell you, or it won't work. Either way, it's not a problem until it's a problem. There are only two network-related changes that you should probably make. There are a few tweaks that allow Plex to run offline, and if you want to use remote streaming, you may have to perform simple port forwarding to make it work. For the rest, don't touch anything if your Plex service runs normally.