Kodi, the media center the repository still calls xbmc, and what its 22.0 Piers line leaves to the reader

The core sits in xbmc/ and the add-on layer is python and XML

Kodi's codebase is mostly C++, with small parts written in a variety of other languages, and add-ons are mostly python and XML. That split is visible in the repository layout rather than described in prose. `xbmc/` holds the application, `addons/` the extensions, `lib/` the bundled libraries, `cmake/` the CMake modules and `project/` the build projects. Build configuration lives in the root `CMakeLists.txt`, with `version.txt` beside it. Conventions are enforced from files: `.clang-format`, `.clang-format-ignore` and `.clang-tidy` for C++, `.editorconfig` for everything else, `sonar-project.properties` for static analysis, and `.git-blame-ignore-revs` for the bulk reformatting commits that would otherwise pollute history. `AGENTS.md` and `CLAUDE.md` sit alongside them, which tells you the project expects automated agents in the tree. The practical result for a reader is a directory map: windowing and playback code is under `xbmc/`, and the skinning engine is named as a feature in the README without its interface being described there.

The library scans your files and fills in box covers, descriptions and fanart

Point Kodi at a directory and it scans the contents into a library that carries its own artwork: box covers, descriptions and fanart for each item. Playlists, slideshows, a weather forecast and audio visualisations sit on top of that library. Network playback was the design target, so streams can be pulled from anywhere in the house or straight from the internet using practically any protocol available, and the README claims almost all popular audio and video formats play.

Two programs live in that description. There is a player, and there is a metadata indexer that has to be pointed at your files and left to finish. A machine where the scan has never run gives you a player with an empty shelf, and nothing in the README says where the descriptions and covers come from, which matters before you point the scanner at the only copy of a disk.

Every platform gets its own download from kodi.tv/download

There is no single installer and no package in the README. Installation is a page visit: go to the downloads section at https://kodi.tv/download and select the platform you are installing on. The named targets are Android, BSD, Linux, macOS, iOS, tvOS and Windows, and the README adds that Kodi runs on most common processor architectures, which is as far as the portability claim goes. Two kinds of build are published there, final builds and development builds, and the README does not say how the two differ beyond their names, so that choice is yours to make on a machine other people watch.

A quick start guide sits in the wiki at https://kodi.wiki/view/quick_start_guide. Source work is a separate route, and the repository is here:

git clone https://github.com/xbmc/xbmc.git

What to run after that clone is not in this README, which is the next section's whole subject.

CMake is the build system, and the root README hands the recipe to docs/README.md

Kodi uses CMake. The root README stops there, and says why: instructions are highly dependent on your operating system and target platform, so they live in `docs/README.md`. For a project whose clients include Android, BSD, Linux, macOS, iOS, tvOS and Windows, that arrangement is defensible, since no single command sequence covers seven targets.

The cost lands on whoever wants to build rather than install. You arrive at the tree, you read `CMakeLists.txt` and the `cmake/` directory, and the platform-specific guide is one link away in docs/README.md. There is no toolchain bootstrap in the repository root either: the top level has `tools/` for the project's own utilities and `project/` for the build projects, and a stray `xbmc-xrandr.c` at the root for display handling. Nobody holding only the front page can turn this tree into a binary.

The newest tag is 22.0rc1-Piers, a release candidate rather than a final build

Releases here are named in three parts: a number, a phase letter and a codename. The list shows 22.0rc1-Piers published on 2026-09-27, preceded by 22.0b2-Piers on 2026-08-31 and 22.0b1-Piers on 2026-06-21. Two things follow from that shape. The newest tag is a release candidate, so the head of the list is not the conservative thing to install, and the phase letters are the only place a build's maturity is stated at all. Codenames are per cycle, which is why the string you paste into a bug report carries a word as well as a number, and why two different releases can share a 22.0 prefix without being the same build.

The repository is not archived and its last push was on 2026-11-02, more than a month after that candidate, so master is running ahead of every tag. Tracking the line means picking between a candidate, a beta and a final build for the same cycle, and the download page is where that pick is made.

GPLv2 in LICENSE.md, with a LICENSES/ directory beside it

The licence is GPLv2, and the README states that you may use, distribute and copy Kodi under the licence terms. That weighs more here than it would for a small library, because Kodi's real estate is its add-on ecosystem: an installation is the application plus whatever add-ons the user added, and each of those is separately licensed software you did not write. Redistribute a build and the GPLv2 obligations travel with the pieces you bundle, one judgement at a time rather than one for the whole box.

The repository shows that attention. `LICENSES/` sits next to `LICENSE.md` at the top level, translation of Kodi core runs on weblate at kodi.weblate.cloud/projects/kodi-core/kodi-main/ and add-ons and skins are translated at kodi.weblate.cloud/. The licence question for any adopter is therefore three questions, for the application, for each add-on and for each skin, and this README answers only the first.

Add-ons are the extension layer, and kodi.tv/addons is where they arrive from

Kodi's extension points are add-ons, distributed through the project's own site rather than through the operating system's package manager. The catalogue sits at https://kodi.tv/addons and the entry point for writing one at https://kodi.tv/create-an-addon. Add-ons are mostly python and XML, the same split the README gives for the codebase itself, and skins are treated as part of the same translation effort on weblate.

The README calls add-ons the thing that makes Kodi the most extensible and customizable hub available. The honest way to evaluate the software for a given device is to read the add-on list for that device first: what the system can do is what its core exposes plus what its installed add-ons add.

A couch-first interface that also runs on desktops

The README draws the line itself: Kodi works well as a standard media player application for a computer, but it has been designed to be the perfect companion for an HTPC, natural to use from the couch with a remote control. That decision runs through the design. The skinning engine exists because the interface is projected across a room, the library exists because a remote cannot type a path, and the whole feature set is aimed at someone sitting down to watch something rather than someone managing files.

Looking for an alternative to Kodi usually means one of two things: the workflow is a desktop with a keyboard, or the job belongs on a machine with no screen attached to it. Kodi also works as a standard desktop media player, although a remote-friendly interface may be less convenient for some keyboard-and-mouse workflows. Choose it for either setting if its interface and library features fit; a headless processing pipeline calls for a different tool.

Editorial conclusion

Kodi is a good fit for a television, a remote control and a library you want built once and shared around the house. It also works as a desktop media player, though its interface is designed for a remote-controlled home theater. It is a poor fit for a headless pipeline or anyone who needs a complete build recipe in the repository root. Before you install anything from kodi.tv/download, decide between a final build and a development build in the 22.0 Piers cycle, and read docs/README.md for your platform, because the root README will not get you a binary.

Frequently asked questions

Official sources

1. Issues
2. Project website
3. README
4. Releases
5. xbmc/xbmc on GitHub