Kodi’s Local Libraries, Skins and Plex/Jellyfin Support: The Truth About Dialogue Boost

Still maintained, not a museum piece​

Kodi's official release material lists 21.3 "Omega" as the current stable release. Team Kodi posted it on December 16, 2025, and said Omega is still the current release while work continues on the next major version, 22.x "Piers". Kodi 22 is in prerelease. As of this writing, the most recent beta I found referenced in release material is Beta 2, dated September 5, 2026. Betas can still have bugs, so stay on 21.x for a living-room box.

The 21.3 changelog also shows who the project is tending to. Highlights include HDR support on Xbox One, faster video library rescans, a fix for multi-episode files overwriting the first episode, and added HTTP Basic Authentication support. Kodi also notes that deployment through the Microsoft Store can lag because it is outside the project's control. Windows users may see updates arrive later than they do on other channels.

1. A full library with no media server​

XDA's first point is that Kodi can build a proper movie and TV library straight from files on a drive or NAS. No Plex-style or Jellyfin-style server process is needed. The official Kodi wiki supports this. The procedure it documents is:

1. From the home screen, choose Videos, then Files, then Add videos.
2. Browse to the folder that holds your titles and confirm it.
3. Name the source. The name doesn't matter to Kodi, but keep it unique.
4. In the Set content window, say whether the folder holds movies or TV shows.
5. Pick an information provider (the scraper) and adjust its settings if you want.
6. Answer Yes to scrape the content into the library.

Kodi then tries to match each title against the provider's database. When it finds a match, it downloads the metadata and artwork for the library display.

Caveats worth knowing​

• Network shares. The wiki says UPnP can't be used to create a library from network media, and recommends a protocol such as SMB. The XDA article mentions SMB or NFS, and Jellyfin's own docs list NFS and Samba as the options for direct file access.
• Scan time. The wiki says a single movie can take about 30 seconds and a 400-movie library more than an hour.
• Naming matters. After a scan, the wiki says to check the Event Log for titles that didn't make it into the library. It says this is normally due to incorrect naming.
• "Offline" has limits. A USB drive attached to the playback device needs no network at all. A NAS still has to be reachable on your LAN. Initial scraping and any later refreshes need internet access to fetch metadata. Once metadata and artwork are cached, browsing doesn't depend on the internet. That claim comes from XDA's author's experience, and I haven't tested it myself.

The accurate framing is that Kodi organizes your files on the playback device itself. It doesn't need a separate server service just to do that.

2. A skin system that reshapes the TV interface​

XDA's second point is customization. The author prefers the third-party Arctic: Zephyr - Reloaded skin over the default Estuary. They also describe putting smart playlists, such as unwatched thrillers, on the home screen alongside widgets for recent additions and next episodes. I have only the author's word on those specifics.

The official wiki supports the broader point. It notes that on-screen displays are skin dependent and may show more or less information, in a different format, than the default Estuary skin. Whether a given widget or setting exists depends on the skin you pick.

XDA also says Jellyfin's custom CSS doesn't apply across every TV app. I couldn't corroborate that, so treat it as the author's claim. What I can say is that Jellyfin's Kodi docs treat Kodi's skin system as part of the appeal. The JellyCon add-on lets you point menu items and widgets at Jellyfin libraries, such as "recently added" or "next up" lists. Those layouts are configured in the skin, and the Jellyfin docs say each skin uses slightly different terminology.

3. Kodi as a front end for Plex or Jellyfin​

The third point is that you don't have to choose between Kodi and a media server. You can let a server manage your collection and use Kodi to browse and play it.

Jellyfin​

Jellyfin's documentation describes two official add-ons:

• Jellyfin for Kodi syncs metadata from selected Jellyfin libraries into the local Kodi database. It feels like local Kodi media, and browsing has virtually no delay.
• JellyCon behaves more like a standard streaming add-on. It is easier for switching between servers or users, but it has to request info from the server as you browse.

The Jellyfin docs also list some limits for Jellyfin for Kodi:

• The docs say remote Kodi databases such as MySQL aren't supported, and a local SQLite database is required.
• It tends to consume the database and not share well if you also have local media managed in Kodi.
• Jellyfin recommends installing the Kodi Sync Queue plugin on the server to keep libraries current.
• The add-on has an Add-on mode, the default, where the server translates file paths. It also has a Native mode, which bypasses the server during playback. Native mode needs the media to be reachable over NFS or Samba, and needs path replacements configured. Jellyfin says it should only be used on a LAN or VPN.

Plex​

For Plex, the third-party PlexKodiConnect add-on does the same job. Its repository says it synchronizes media from your Plex server into Kodi's native database and lets you use any Kodi skin. The project is blunt about the risks. It says to use it at your own risk, and that it assumes you manage all videos with Plex and none with Kodi. It can't use the official Kodi repository, and it isn't compatible with Kodi's MySQL database replacement.

The playback claim​

XDA says high-bitrate remuxes with TrueHD audio stuttered in the native Plex app but played smoothly through Kodi. That is one person's experience. Playback depends on the file, client hardware, audio chain, network and settings, and the docs I reviewed don't support the claim that Kodi is categorically better. The author does list some playback features that Kodi's documentation confirms:

• You can change the subtitle offset in milliseconds during playback.
• You can switch audio streams mid-video.
• You can set an audio offset to fix poorly synced videos.

4. Dialogue boost, and where the "no modern app" claim fails​

The fourth point is quiet dialogue. Kodi's playback settings include a Downmix - Center Mix level option for boosting the dialogue (center) channel. It shows up only under specific conditions, according to the wiki:

• Audio passthrough must be disabled.
• The configured number of output channels must differ from the number of channels in the stream. For example, you have two speakers but the audio is 5.1.

To try it:

1. Start a video that has a 5.1 track.
2. Open the on-screen controls and go to the settings cog, then Audio settings.
3. If the option is missing, check whether passthrough is on. Check also that your output is set to fewer channels than the source.
4. Raise Downmix - Center Mix level until speech sits comfortably.

If you use a soundbar or AVR with passthrough, this setting won't help you. Kodi isn't doing the decoding in that case.

Plex now has its own version​

XDA says Plex has Boost Dialog for Plex Pass users but Kodi offers a similar feature for free. That framing is fair, but it undercuts the headline. Plex says it brought Boost Dialog and Normalize Loudness to Plex Pass subscribers, available with Plex Media Server 1.43.4. In Plex's description, Boost Dialog isolates the frequencies where dialog lives and brings them forward. It is a different technique from Kodi's channel-mix control.

The Plex details are:

• Enabling either option causes the audio to be transcoded.
• Plex support says the user performing the action needs a Plex Pass, or must be in a Plex Home whose admin has one.
• Plex's support page lists minimum app versions, including mobile and Android TV from 2025.28.0, and Roku from 9.0.31.

So Kodi isn't the only app with dialogue enhancement anymore. Its version is free, and it works through channel mixing. That approach has some limits of its own, because it only applies when downmixing.

The verdict​

Kodi's real strengths are flexibility and independence. It can build a library from plain files, restyle the whole interface with skins, front-end a Plex or Jellyfin server, and boost dialogue when downmixing. Those are real, documented capabilities.

The extra configuration is the price. You need to name files correctly, choose scrapers, pick and tune a skin, and accept that the sync add-ons can conflict with local Kodi libraries. "Nobody else does this" is overstated. A fairer summary is that Kodi gives you more control, at the cost of doing more of the work yourself.