What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For the broadest practical DLNA compatibility, use an MP4 container with 8-bit H.264/AVC video in yuv420p and AAC-LC audio. Use x264 to encode library files when quality and predictable results matter; use a supported hardware H.264 encoder such as Intel Quick Sync, NVIDIA NVENC, or AMD hardware encoding when the server must transcode quickly in real time. This is a safe starting point, not a guarantee: the exact TV or player, audio, subtitles, bitrate, and server profile can still determine whether playback is direct or requires conversion.
What “codec and encoder” means for DLNA
A codec describes how a stream is compressed; a container packages streams and metadata into a file. The encoder is the software or hardware that creates the compressed video. DLNA is the delivery and discovery environment, while a renderer profile describes what a particular client can accept. These pieces are related but not interchangeable.
- Video codec: H.264/AVC, HEVC/H.265, AV1, or MPEG-2.
- Audio codec: AAC, AC-3, E-AC-3, DTS, FLAC, or Opus.
- Container: MP4, MKV, or MPEG-TS.
- Subtitles: Text formats such as SRT and WebVTT, or image formats such as PGS and VobSub.
- Transport and profile: DLNA commonly delivers media over HTTP; the server’s profile and the device’s implementation affect what it advertises and plays.
A file can have compatible H.264 video and still fail or trigger conversion because its container, audio, subtitle format, bitrate, frame rate, H.264 level, HDR metadata, or device profile is unsuitable. Jellyfin distinguishes direct play, remuxing, audio conversion, and full video transcoding; the video codec alone does not decide the playback path (Jellyfin playback and transcoding modes).
Choose the target for the job
There are three different goals, and the best encoding choice changes with each one.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
- Permanent library encoding: favor quality per bit and predictable results. x264 is a strong H.264 choice when encoding time is acceptable.
- Live server transcoding: favor speed and low CPU use. A compatible hardware H.264 encoder is often the practical choice for a modest server or multiple simultaneous streams.
- Direct play: match the exact renderer. Use its documented or observed codec, container, audio, subtitle, resolution, and bitrate support rather than relying on a generic “DLNA compatible” label.
DLNA 4.0 describes HD AVC in an MPEG-4 container as a mandatory baseline for relevant profiles and anticipates server transcoding when original content does not fit a required profile. That does not mean every TV implements every profile identically (DLNA 4.0 white paper).
Recommended compatibility profile
| Part | Recommended starting point | Why it helps |
|---|---|---|
| Container | MP4 | A broadly accepted container for H.264 delivery and a fit for the HD AVC-in-MPEG-4 DLNA baseline. |
| Video | H.264/AVC, 8-bit, 4:2:0 (yuv420p) |
Broad practical client support; 10-bit H.264, HEVC, and AV1 support varies more by device and software. |
| Profile | High for most modern devices; Main or Baseline only if an older target requires it | Older hardware may have narrower profile and level limits. |
| Frame rate and level | Preserve source frame rate; let the encoder select level unless the client needs a limit | A forced conversion can reduce compatibility or alter motion unnecessarily. |
| Audio | AAC-LC, 48 kHz; stereo for broad compatibility, or a tested 5.1 track | Avoids many DTS and multichannel-decoding problems. |
| Subtitles | Use a text subtitle format known to work with the client; avoid image subtitles when direct play is essential | Image subtitles can force video burn-in. |
H.264 8-bit is the compatibility choice, not the most storage-efficient codec. Jellyfin’s codec table identifies H.264 8-bit as broadly supported across its clients, while support for other codecs depends more on device and settings (Jellyfin client codec support). Even so, the same TV may support a file from USB but not through its DLNA implementation or a particular media-server app; Plex cautions that device compatibility varies by playback route (Plex smart-TV format guidance).
Audio and subtitles can be the reason video transcodes
AAC, AC-3, E-AC-3, and DTS
AAC-LC is the simplest compatibility audio choice, especially for stereo. As practical starting values, use 160–256 kb/s for stereo AAC or around 384–640 kb/s for 5.1 when that channel layout is known to work; these are encoding choices, not DLNA limits. AC-3 or E-AC-3 can be preferable for a TV and receiver that support Dolby Digital and multichannel playback. Browser support and device restrictions differ, so do not assume that one audio choice fits TVs, set-top boxes, and browsers alike. Jellyfin’s client table documents these codec differences (Jellyfin client codec support).
DTS, TrueHD, and other high-bitrate or lossless tracks are common reasons a server converts audio even when the video can remain untouched. For a compatibility copy, keep the original track if preservation matters and add a tested AAC or AC-3 track. Confirm that the player selects the compatible track; merely putting DTS in an MP4 does not make it decodable. Plex describes DTS conversion to AAC by default, or AC-3 when receiver capability is enabled (Plex supported media formats).
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Text and image subtitles
SRT or WebVTT text subtitles may be passed through, converted, or overlaid depending on client support. PGS and VobSub are image-based; if the renderer cannot display them, the server may have to burn them into the video, turning an otherwise direct-play session into a demanding video transcode. If playback suddenly needs substantial server power only when subtitles are enabled, test with subtitles off and then with a text subtitle track. Jellyfin documents subtitle burn-in as a frequent compatibility and performance issue (Jellyfin client codec support).
MP4 or MKV?
Use MP4 for a compatibility copy when the target’s format support is uncertain. It is a sensible pairing for H.264/AAC and aligns with the cited DLNA baseline. Use MKV for archival or flexible files when the client supports it: it is useful for multiple audio and subtitle tracks, chapters, and preserving source streams. MP4 is not inherently better quality, and MKV is not inherently incompatible; a server may simply need to remux or transcode for a particular renderer. Jellyfin notes specific MKV playback issues on some newer LG webOS scenarios in its codec-support documentation.
Which encoder should you use?
| Encoder or codec choice | Best fit | Trade-off |
|---|---|---|
| x264 (software H.264) | Encoding permanent compatibility copies or library derivatives | Uses CPU and can take longer; offers predictable quality and broad playback support. |
| Intel Quick Sync H.264 | Low-power server or NAS that needs fast live conversion | Requires a supported Intel video engine, driver/runtime, and working server access to the iGPU. |
| NVIDIA NVENC H.264 | Existing NVIDIA GPU and real-time or concurrent transcodes | Capabilities depend on GPU generation, driver, server software, and settings; a discrete GPU is unnecessary for occasional simple conversion. |
| AMD or other supported hardware H.264 | Systems where the server software and platform provide a supported acceleration path | Check the actual driver/runtime and codec path rather than assuming support from the hardware brand alone. |
| HEVC/H.265, typically Main 10 for 4K HDR | Storage-efficient 4K HDR libraries where clients are known to decode it | More efficient than H.264 in many workflows, but less universally direct-playable. |
| AV1 | Known AV1-capable clients and a storage-efficiency priority | Still less common in mixed or older device households; hardware encoding and decoding are generation-dependent. |
x264 is a good default for a file you encode once and expect to play on varied equipment. For real-time transcoding, hardware encoding can reduce CPU use and support more concurrent sessions; quality can be lower than software encoding in some hardware, bitrate, or generation combinations, not as a universal rule. Plex documents these trade-offs and its platform requirements (Plex hardware-accelerated streaming).
For 4K 10-bit HDR or Dolby Vision storage, HEVC is often a more practical storage codec than H.264. Jellyfin’s NVIDIA guidance similarly distinguishes HEVC’s use for 4K HDR storage from broad client compatibility; its stated hardware requirements are specific to that platform, not universal rules for every server (Jellyfin NVIDIA acceleration guidance). AV1 is a reasonable choice only when the playback devices that matter support it and the server can decode or encode it as required.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
FFmpeg recipes for a compatibility copy
These commands are templates. Confirm stream selection and client behavior with your own files; audio layouts, metadata, subtitles, and source streams may require changes. FFmpeg’s command and codec references explain its general and encoder-specific options (FFmpeg documentation; FFmpeg codec documentation).
Encode H.264 video and stereo AAC
ffmpeg -i input.mkv
-map 0:v:0 -map 0:a:0?
-c:v libx264 -preset medium -crf 21
-profile:v high -pix_fmt yuv420p
-c:a aac -b:a 192k -ar 48000
-sn -movflags +faststart
output.mp4
CRF 18–23 is a reasonable x264 starting range: a lower number generally means higher quality and a larger file. CRF does not promise a specific bitrate or size. Preset changes encoding speed and compression efficiency rather than the requested quality target. The example omits subtitles with -sn; add or convert a compatible text track deliberately if needed.
Encode a 5.1 AAC track
ffmpeg -i input.mkv
-map 0:v:0 -map 0:a:0?
-c:v libx264 -preset slow -crf 20
-pix_fmt yuv420p
-c:a aac -b:a 384k -ac 6 -ar 48000
-movflags +faststart
output.mp4
Use this only when the selected source track and target device support the resulting six-channel AAC. If uncertain, create stereo AAC or test on the actual renderer.
Remux compatible streams without re-encoding
ffmpeg -i input.mkv
-map 0
-c copy
-movflags +faststart
output.mp4
A remux copies streams without generational quality loss and is usually quick. It will fail or produce an unsuitable file if a stream or metadata item is not valid for the MP4 target. If only one stream is incompatible, convert that stream rather than re-encoding everything. For example, a compatible video can be copied while audio is converted to AAC.
Rank #4
- Dual Converters, Infinite Potential:Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Keep an original audio track and add compatibility audio
For tracks that MP4 supports and the intended client can use, a multi-track output can preserve one selected source audio track while creating an AAC track. Stream mapping and codec-copy compatibility depend on the input and target, so inspect the result before deploying it.
ffmpeg -i input.mkv
-map 0:v:0 -map 0:a:0? -map 0:a:1?
-c:v libx264 -preset slow -crf 20
-profile:v high -pix_fmt yuv420p
-c:a:0 aac -b:a:0 192k -ac:a:0 2
-c:a:1 copy
-sn -movflags +faststart
output.mp4
This is a template, not a universal recipe: copying the second audio stream may not be valid in MP4, and source ordering may differ. Check the input streams and the output on the target player.
Hardware encoding
Use the software x264 command as the reproducible baseline. Hardware options are specific to FFmpeg build, GPU, driver, and platform; verify encoder names and quality-control options in the installed build’s FFmpeg documentation. For NVIDIA, Jellyfin documents generation-specific support: H.264 8-bit encoding is available on supported NVIDIA hardware, HEVC 10-bit encoding requires Pascal-generation or newer hardware, and AV1 encoding requires Ada Lovelace or newer (Jellyfin NVIDIA acceleration guidance). For Intel, Plex’s cited requirements are Plex-specific: it recommends newer Intel generations for better results and identifies seventh-generation Core or newer for HEVC encoding (Plex hardware-accelerated streaming).
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Set up and verify server-side DLNA or acceleration
Jellyfin DLNA
On current Jellyfin installations, DLNA is an official plugin rather than part of the base installation; this change applies from Jellyfin 10.9 onward. Follow the current dashboard labels:
Recommended Free Tools
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
- Open the Jellyfin administrative dashboard and go to Catalog.
- Install the official DLNA Plugin.
- Restart Jellyfin Server.
- Ensure UDP port 1900 is available on the local network for SSDP discovery.
- If Jellyfin runs in Docker, use host networking for the DLNA server.
See the current Jellyfin DLNA setup documentation for networking details.
Jellyfin hardware acceleration
- Install the driver and runtime required for the selected GPU and operating system.
- Open the server’s transcoding settings and select the matching hardware-acceleration method.
- Enable only codecs supported by the hardware and the installed software path.
- Test a file that previously triggered conversion.
- Check the playback dashboard or transcode output to confirm that hardware decoding or encoding is being used.
Jellyfin supports acceleration paths for modern Intel, AMD, NVIDIA, Apple, and Rockchip hardware when the required platform components are available; the codecs and features vary (Jellyfin transcoding documentation).
Plex hardware acceleration
- Open Plex Web App and go to Settings > Server > Transcoder.
- Enable Show Advanced.
- Turn on Use hardware acceleration when available, then save.
Plex’s cited documentation says an active Plex Pass is generally required for hardware-accelerated streaming, with documented special-device exceptions; do not assume the feature is available without checking the current requirements (Plex hardware-accelerated streaming).
Quick Recap
Diagnose playback problems before re-encoding
- Check discovery first. If the server does not appear on the TV, confirm the DLNA plugin or server service is enabled, devices share the appropriate local network, and UDP 1900 is not blocked. With Jellyfin in Docker, check its host-networking guidance (Jellyfin DLNA setup).
- Identify the playback mode. In Jellyfin, distinguish Direct Play, remux, Direct Stream (audio conversion while video remains unchanged), and full video Transcode. Direct Play avoids media conversion, but the server still handles networking, metadata, permissions, and other ordinary work (Jellyfin playback and transcoding modes).
- Inspect audio before changing video. If H.264 video is direct-playable but audio is DTS, TrueHD, FLAC, or an unsupported channel layout, add or select a compatible audio track.
- Test subtitles off. If playback mode changes, an image subtitle may be forcing burn-in. Try a supported text subtitle instead.
- Check container and streams. A remux from MKV to MP4 may solve a container mismatch without touching the video, if the streams fit MP4 and the renderer accepts the result.
- Check profile, bitrate, and video limits. Older models can impose narrow H.264 level, reference-frame, frame-rate, resolution, or bitrate constraints. There is no universal DLNA bitrate ceiling: the renderer, server profile, Wi-Fi, and network path all matter.
- Confirm hardware is actually engaged. If a live transcode is unexpectedly slow, verify drivers, permissions, supported codec settings, and server logs rather than assuming that installing a GPU enabled acceleration.
- Test the exact playback route. USB playback, a TV’s native app, and a DLNA session may use different format support. A model name and firmware version are more useful than “this TV supports H.264.”
Practical choice by household
- Mixed devices or older TVs: make H.264 8-bit/AAC MP4 compatibility copies for the problem devices; keep the originals if quality preservation matters.
- Modern 4K HDR clients: store HEVC Main 10 when the actual clients support it, and retain a separate compatible version for devices that do not.
- Low-power NAS with live conversions: use a supported hardware H.264 path, commonly Quick Sync when a usable Intel iGPU is available.
- Archival-first library: preserve source files and create x264 or HEVC derivatives for the clients that need them rather than degrading the archive to the weakest renderer.
- Known AV1-capable clients: AV1 can be a storage choice, but keep a fallback path for legacy DLNA players.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

