{"id":1291,"date":"2026-09-08T09:48:15","date_gmt":"2026-09-08T02:48:15","guid":{"rendered":"https:\/\/liveapi.com\/blog\/exoplayer\/"},"modified":"2026-09-08T09:48:57","modified_gmt":"2026-09-08T02:48:57","slug":"exoplayer","status":"publish","type":"post","link":"https:\/\/liveapi.com\/blog\/exoplayer\/","title":{"rendered":"ExoPlayer: What It Is, How It Works, and How to Use It on Android"},"content":{"rendered":"Reading Time: <\/span> 12<\/span> minutes<\/span><\/span>

Search for ExoPlayer and the top result is a GitHub repo with a deprecation notice on it. No wonder so many developers arrive unsure whether the library is dead.<\/p>\n

It isn’t. ExoPlayer is still the media player inside YouTube, and it’s still what most serious Android video apps run on.<\/p>\n

It just moved house. The code now lives in AndroidX Media3 under a new package name, and the old standalone project stopped taking commits in April 2024.<\/p>\n

That single move explains almost every outdated tutorial you’ll find, and it’s where most migration pain comes from.<\/p>\n

What Is ExoPlayer?<\/h2>\n

ExoPlayer is an open-source media player library for Android that plays audio and video from local files or network streams, with support for adaptive streaming protocols the platform’s built-in player can’t handle.<\/p>\n

It’s the default implementation of the Player<\/code> interface<\/a> in Jetpack Media3. Google builds it, YouTube uses it, and it ships as an app dependency rather than as part of the operating system.<\/p>\n

That last detail matters more than it sounds. Android’s built-in MediaPlayer<\/code> is baked into the OS, so its behavior shifts across devices and Android versions, and you can’t patch a bug on a user’s phone.<\/p>\n

ExoPlayer travels with your APK. Fix a playback bug, ship an app update, done.<\/p>\n

Here’s how the two compare:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
<\/th>\nExoPlayer (Media3)<\/th>\nAndroid MediaPlayer<\/th>\n<\/tr>\n<\/thead>\n
Ships with<\/strong><\/td>\nYour app<\/td>\nThe operating system<\/td>\n<\/tr>\n
Bug fixes<\/strong><\/td>\nApp update<\/td>\nOS update (or never)<\/td>\n<\/tr>\n
Adaptive streaming<\/strong><\/td>\nHLS, DASH, SmoothStreaming<\/td>\nLimited HLS, partial DASH<\/td>\n<\/tr>\n
Customization<\/strong><\/td>\nEvery component is swappable<\/td>\nNearly none<\/td>\n<\/tr>\n
DRM<\/strong><\/td>\nWidevine, PlayReady, ClearKey<\/td>\nWidevine only, device-dependent<\/td>\n<\/tr>\n
Playlists<\/strong><\/td>\nBuilt in, with gapless playback<\/td>\nManual<\/td>\n<\/tr>\n
APK size cost<\/strong><\/td>\n~1 to 3 MB<\/td>\nZero<\/td>\n<\/tr>\n
Behavior across devices<\/strong><\/td>\nConsistent<\/td>\nVaries by vendor<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The tradeoff is size and complexity. You’re adding a library where the platform already hands you something free.<\/p>\n

For a single MP4 on an onboarding screen, that’s a bad deal. For live streams, adaptive bitrates, DRM, or precise playback control, it’s the only sane choice.<\/p>\n

ExoPlayer vs Media3: Why the Library Moved<\/h2>\n

ExoPlayer didn’t get replaced. It got relocated.<\/p>\n

The library used to ship standalone as com.google.android.exoplayer2<\/code>. In 2023 Google folded it into Jetpack Media3, an AndroidX library that unifies media playback, media sessions, transformation, and UI under one set of packages. Same player, new name: androidx.media3.exoplayer<\/code>.<\/p>\n

The old project is finished. Version 2.19.0 marked the deprecation, ExoPlayer 2.19.1<\/a> was the final artifact, and the team stopped pushing commits to the dev-v2<\/code> branch on April 3, 2024.<\/p>\n

No security patches. No new codec support. No bug fixes.<\/p>\n\n\n\n\n\n\n\n\n\n\n
<\/th>\nOld ExoPlayer<\/th>\nMedia3 ExoPlayer<\/th>\n<\/tr>\n<\/thead>\n
Package<\/strong><\/td>\ncom.google.android.exoplayer2<\/code><\/td>\nandroidx.media3.exoplayer<\/code><\/td>\n<\/tr>\n
Gradle group<\/strong><\/td>\ncom.google.android.exoplayer<\/code><\/td>\nandroidx.media3<\/code><\/td>\n<\/tr>\n
Last version<\/strong><\/td>\n2.19.1 (2023)<\/td>\n1.11.0 (August 2026)<\/td>\n<\/tr>\n
Status<\/strong><\/td>\nDeprecated, no commits since April 2024<\/td>\nActively developed<\/td>\n<\/tr>\n
Minimum SDK<\/strong><\/td>\n16<\/td>\n23 (Android 6.0), since Media3 1.9.0<\/td>\n<\/tr>\n
Repository<\/strong><\/td>\ngoogle\/ExoPlayer<\/td>\nandroidx\/media<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Two things catch teams off guard during migration.<\/p>\n

The version number went backwards. You upgrade from ExoPlayer 2.19.1 to Media3 1.x and it looks like a downgrade. It isn’t. Media3 restarted versioning at 1.0 as a new library.<\/p>\n

And the minimum SDK jumped. Media3 1.9.0 raised minSdk<\/code> to 23, matching the rest of AndroidX. If you’re still supporting Android 5.0, you’re pinned to Media3 1.8.1 or older.<\/p>\n

For the migration itself, Google publishes a shell script that rewrites package names across Gradle files, Java, Kotlin, and XML layouts. It handles the mechanical renaming. Anything where you subclassed an ExoPlayer internal still needs a human.<\/p>\n

How Does ExoPlayer Work?<\/h2>\n

ExoPlayer isn’t one component. It’s a pipeline of swappable pieces that move bytes from a URL to pixels on a screen.<\/p>\n

Know those pieces and you graduate from “I got a video to play” to “I can debug why this stream stalls.”<\/p>\n

The core components<\/h3>\n