A cozy living room showcases an Xbox entertainment setup, with a TV media library, console, controller, and streaming icons.
Kodi's history is more tangled than the usual "XBMC became Kodi" summary. The software started as a hobbyist project on Microsoft's first console, spent years outgrowing it, and still shows traces of that origin. The history matters to Windows and Xbox readers because Kodi runs on Windows today. It has also gone back to the Xbox ecosystem in a new form.

A cozy living room showcases an Xbox entertainment setup, with a TV media library, console, controller, and streaming icons. From Xbox Media Player to Kodi: the actual chronology​

The naming history has several steps, and sources differ on some dates.

  • 2002: Xbox Media Player. Kodi's own 10-year retrospective says one of the first betas of the XBMC source code was uploaded on 5 October 2002. That was the result of a merge between two different home theatre applications. In Kodi's account, Frodo, the founder of YAMP (Yet Another Media Player), joined the Xbox Media Player team and the two projects merged. Wikipedia's entry on the player gives a slightly different timeline. It says the merged release was called "Xbox Media Player 2.0", with source code released on December 14, 2002. The project's retrospectives and Wikipedia disagree on some details, so treat the exact month as soft.
  • 2003–2004: Xbox Media Center. Wikipedia says Xbox Media Player development stopped on December 13, 2003. Kodi's own history dates the first stable release of the renamed software to 2004: Xbox Media Center v1.0.0 in 2004. The two accounts fit together. The 2003 date marks the transition, and the 2004 date marks the first stable release.
  • 2006–2008: XBMC. Kodi's retrospective lists another name change to XBMC v2.0.0 in 2006 and Linux support in 2007. A separate 2014 Kodi post places the formal rename to plain "XBMC" in 2008, outgrowing the console-style branding. That post is the project's own account, and the timing differs slightly from the 2006 version number above.
  • 2014: Kodi. Wikipedia records that the project was renamed from XBMC to "Kodi" in July 2014 with the release of Kodi 14. The XBMC Foundation name stayed as the legal entity.

The 2014 rename was not only cosmetic. Kodi's announcement said the name "XBMC" fit less than it once had, because the software only barely ran on the original Xbox and had never run on the Xbox 360 or Xbox One. It also described a legal problem. The developers had never held legal control over a name derived from "Xbox", and users had been fooled into buying boxes running hacked versions. Reviewing options with the Software Freedom Law Center, the Foundation decided a rename was the most realistic fix.

Why an Xbox made sense as a media box​

The original Xbox was an unusual console. Hackaday notes that its hardware shared much with a PC of the day, and that it was found to be hackable, with a media centre among the most successful projects to take advantage. That is the same pitch the XDA piece makes: an x86 chip, a hard drive and Ethernet in a box that plugged into a TV.

Keith Herrington, President of the Kodi Foundation, gave the project's own account in a 2024 retrospective. He says the founders wanted to operate media from the couch without a keyboard or mouse. He credits the Xbox with changing things for tinkerers, because hackers found ways to run untrusted code on it. He also stresses how unusual a library mode was when even Netflix was still mailing DVDs.

That is the clearest link between the Xbox and Kodi's current character. It was built to bring a personal media collection to a television, not to front a subscription catalog.

What still feels different today​

The XDA article argues that several Kodi traits trace back to that origin. Here is what the evidence supports and where to be careful.

The "10-foot interface." Kodi's Foundation president describes the original goal as an interface usable from across a room, controlled from the couch. That supports the idea that remote-friendly navigation was a founding goal. It does not mean today's interface is unchanged since 2002. Kodi's modern skins have been rebuilt many times.

Your own files first. Kodi's wiki explains that SMB is the standard client-server protocol Windows uses to share resources... more precisely, the official Kodi wiki describes it as the most common way to reach a NAS. The same wiki page documents how to add a source:

  1. Open the Browse for new share window and choose Windows network (SMB), or choose Add network location.
  2. If you choose Add network location, set the protocol to SMB and enter the server name or IP address.
  3. Type the shared folder name and, if required, a username and password.
  4. If you use an IP address, reserve a static address for the NAS in your router so the share does not disappear when the address changes.

Two version notes from that wiki page matter for Windows users. Kodi does not support SMB v1, so SMB v2 or higher is needed. Browsing shares works again since Kodi 19.1 thanks to WS-Discovery support.

Metadata and artwork. Kodi's wiki says scrapers download metadata and artwork for media added to the library, and cache the artwork in the Kodi data folder. Results depend on correct file naming and on what the scraper sites hold. The XDA author's NAS setup is a personal example of this workflow, not a requirement. Kodi can organize files held elsewhere, but you do not need to treat it as a server.

Customization. Kodi's retrospectives list skins and add-ons as defining features. Kodi's December 2010 release of XBMC 10.0 "Dharma" is the point the XDA article credits with in-app add-on installation and automatic updates. The trade-off is that add-ons are community software. They can stop working when maintainers walk away or services change.

Plex, piracy and what to qualify​

Two claims in popular retellings need care.

  • Plex. Kodi's own news archive records that a Mac OS X developer on Team XBMC forked the Mac version in May 2008, and that the fork was named Plex Media Center for OS X. That supports "Plex began as a fork." It does not mean modern Plex is still the same code or product.
  • Piracy. The XDA piece says Kodi became synonymous with piracy through resellers selling cheap boxes loaded with unauthorized add-ons. Kodi's own 2014 rename post complained that users had been tricked into buying boxes running hacked versions of the software. The distinction matters: the legal and reputational problems came from third-party products and add-ons, not from the core media player.

The Xbox connection did not end​

The original Xbox did not simply disappear from the story. The Xbox build of Kodi's lineage continued under XBMC4Xbox, a spin-off that still has active development and support for the Xbox. Reporting from How-To Geek, about a year before this article's date, described an XBMC 4.0 release for the original Xbox that brought the Estuary skin to the console. Kodi has also run on the newer Xbox One and Xbox Series X/S, according to Wikipedia. Kodi's Foundation president says it is back in the Xbox Store, though he notes that Microsoft platforms are harder for the project because it lacks current developer knowledge.

Bottom line​

The XDA article's thesis holds up reasonably well. A media-library-first design, a couch-friendly interface and heavy customization are consistent with a project that began as a hack to get files from a PC onto a TV. The caveat is that "consistent with" is not "unchanged from." Kodi has gone through four names, left the original Xbox, and been rebuilt for Windows, Linux, Android and more.

For Windows users, the practical takeaways are simple. Kodi works well as a front end for files on a NAS or PC, SMB v2 or higher is required, and add-ons are only as dependable as the people maintaining them.

 

References

  1. Kodi started life on the original Xbox, and that history explains why it still feels so different XDA 2026-11-05T20:00:21+00:00
  2. Kodi XBMC: History, the 2014 Rename and Live TV store.grapevine.is
  3. 10 Years of XBMC | News | Kodi kodi.tv