Plex Re-Encoding: Can It Free Half a Drive?
Re-encoding your Plex library can free up roughly half your drive space if your files are in inefficient formats, but the actual savings depend on your current codecs, bitrates, and resolution. This guide explains when re-encoding makes sense, how much you can realistically save, and the trade-offs involved.
Why Plex Libraries Get So Large
Most Plex users accumulate files from various sources—Blu-ray rips, downloads, or recordings—that are encoded with high bitrates and older codecs. For example, a typical Blu-ray rip using H.264 at 20–30 Mbps can take 20–30 GB per movie. Remuxes (uncompressed copies of the disc) are even larger. Over time, these files fill drives quickly, prompting many to consider re-encoding.
The key factor is that many of these files are “over-provisioned”: they contain more data than the human eye can perceive on a typical screen. Re-encoding strips that excess, often reducing file size by 50–70% without a visible quality loss.
How Re-Encoding Works
Re-encoding (or transcoding) decodes the original video and re-encodes it with a more efficient codec and lower bitrate. The most common target is H.265 (HEVC), which is about 50% more efficient than H.264 at the same quality. For example, a 10 Mbps H.264 stream can be replaced by a 5 Mbps H.265 stream that looks nearly identical.
You can also reduce resolution (e.g., 1080p to 720p) or use a more efficient audio codec like AAC instead of DTS or AC3. Each change reduces the file size, but the biggest gains come from the video codec and bitrate.
Realistic Savings: What to Expect
If you have a library of H.264 Blu-ray rips at 20–30 Mbps, re-encoding to H.265 at 8–12 Mbps can cut file sizes by 60–70%. That means a 25 GB movie becomes about 8–10 GB. Over a 2 TB drive full of such files, you could free up 1.2–1.4 TB—more than half.
However, if your files are already H.265 or low-bitrate H.264 (e.g., web rips at 5 Mbps), re-encoding will save little and may even increase size or degrade quality. Similarly, if you have a lot of 4K content, the savings are smaller because 4K requires higher bitrates to maintain detail. In practice, a mixed library might see 30–50% savings, not a full half.
Choosing the Right Settings
To maximize savings without ruining quality, consider these settings:
- Codec: Use H.265 (HEVC) for 1080p and below; for 4K, consider H.265 or AV1 if your devices support it.
- Bitrate: For 1080p, aim for 8–12 Mbps; for 720p, 4–6 Mbps; for 4K, 20–30 Mbps. Lower bitrates increase artifacts.
- Resolution: Keep the original resolution unless you watch on small screens. Downscaling 4K to 1080p can cut size by 75% but loses future-proofing.
- Audio: Convert lossless audio (DTS-HD, TrueHD) to AAC 5.1 at 384–448 kbps. This saves a few hundred MB per movie.
- Preset: Use a slower preset (e.g., “slow” in HandBrake) for better compression at the same bitrate. It takes longer but yields smaller files.
Common Problems and Pitfalls
Re-encoding is time-consuming and can introduce issues if done carelessly. A common mistake is using a fixed bitrate instead of a quality-based setting like CRF (Constant Rate Factor). With CRF, the encoder adjusts bitrate to maintain quality, avoiding wasted bits on simple scenes. For H.265, a CRF of 22–24 is a good starting point for 1080p.
Another pitfall is ignoring device compatibility. Older TVs and streaming sticks may not support H.265, forcing Plex to transcode on the fly, which defeats the purpose of saving space (and can strain your server). Check your devices before committing to H.265.
Also, beware of re-encoding already compressed files. Generational loss means each re-encode degrades quality. Always work from the original source or the highest-quality copy you have.
Tools and Workflow
Popular tools include HandBrake (free, cross-platform), FFmpeg (command-line), and paid options like Adobe Media Encoder. A typical workflow:
- Identify files with high bitrates or old codecs using a tool like MediaInfo.
- Pick a sample file and test different CRF values to find the sweet spot.
- Batch re-encode with your chosen settings, preserving subtitles and chapter markers.
- Verify a few output files for quality and compatibility.
- Replace the originals only after confirming everything works.
For large libraries, consider using a script or queue to run overnight. A single movie can take 30 minutes to several hours, depending on your CPU and settings.
Alternatives to Re-Encoding
If re-encoding seems too time-consuming, consider these alternatives:
- Delete duplicates: Remove multiple copies of the same movie in different formats.
- Upgrade storage: Add a new drive or replace small drives with larger ones. This is often cheaper than the electricity and time spent re-encoding.
- Use a more efficient container: Sometimes remuxing (changing container from MKV to MP4) can save a little space without re-encoding, but the gain is minimal.
- Adjust Plex’s “Optimized Versions”: Instead of re-encoding your master files, create optimized versions for mobile devices and delete them after viewing. This saves space without touching your originals.
Frequently Asked Questions
Will re-encoding ruin my video quality?
If you use a reasonable CRF (e.g., 20–24 for 1080p) and don’t downscale unnecessarily, the quality loss is usually imperceptible on normal screens. However, any re-encode introduces some loss, so keep your original files if you’re a perfectionist or plan to watch on a large projector.
How long does it take to re-encode a movie?
It depends on your CPU, resolution, and preset. A 1080p movie with a slow preset on a modern 8-core CPU might take 30–60 minutes. A 4K movie could take several hours. Using a faster preset reduces time but increases file size.
Can I re-encode without losing subtitles?
Yes. Most tools like HandBrake let you pass through subtitle tracks. Ensure you select the correct subtitle track and enable the “burn in” option if you want them hardcoded, otherwise they’ll be soft subtitles that can be toggled.
Is H.265 always the best choice?
H.265 is widely supported and efficient, but AV1 is newer and can save another 20–30% over H.265. However, AV1 encoding is extremely slow and many devices lack hardware decoding. For most users, H.265 is the practical choice.
Should I re-encode 4K content?
4K re-encoding is risky because detail is easily lost. If you have 4K HDR content, the savings are modest (maybe 20–30%) and you need to preserve HDR metadata. Unless you’re desperate for space, keep 4K as-is and re-encode only 1080p and below.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.