Smaller apps and faster GPU inference with LiteRT in Google Play services

LiteRT in Google Play services is Android's on-device inference runtime for custom models, handling more than a trillion inferences a day across billions of devices. Today, it gets its biggest upgrade yet: GPU inference that runs about 1.4x faster than the legacy GPU delegate, powered by ML Drift and available through the new CompiledModel API, LiteRT’s modern successor to the legacy Interpreter API.

Until now, taking advantage of this faster GPU stack required bundling LiteRT in your app. In our testing, apps that switched to LiteRT in Google Play services are about 8 MB smaller, making them faster to download and lighter on users' devices, because the runtime, including the GPU accelerator, ships once with Play services rather than inside every app. More than 100K Android apps bundle their own copy of LiteRT or TensorFlow Lite today, so the savings add up quickly as apps switch.

If your Android app runs custom ML models on CPU or GPU, we encourage you to switch to LiteRT in Google Play services. You can see it in action in the Google AI Edge Gallery app, where the Scrapbook feature's image segmentation runs on LiteRT in Google Play services.

Developers that adopt LiteRT in Google Play Services enjoy immediate benefits:

LiteRT is the evolution of TensorFlow Lite. It keeps the same .tflite model format you rely on and adds the CompiledModel API, which makes acceleration across fragmented hardware reliable:

.tflite model runs on Android, iOS, desktop, and web. Whether you're starting fresh or switching from bundled LiteRT, using LiteRT in Google Play services takes a few lines of code:

com.google.android.gms:play-services-litert:17.0.0 (or a later version). If you bundle LiteRT today, remove the litert dependency.LiteRT environment from Play services:

val liteRtEnvironment =
    LiteRt.initialize(
        context,
        LiteRtDsl.initializationOptions { setEnableGpu(true) }
    ).await()

environment in when you create your CompiledModel. The rest of your code stays the same. If you're already using the legacy Interpreter API in Google Play services, your Interpreter code keeps working on CPU when you switch to play-services-litert. To run on the GPU, move to the CompiledModel API.

Let your coding agent do the work. In Agent Mode, the new LiteRT skill for Android Studio automates the move to LiteRT in Google Play services and the CompiledModel API. Ask it to “migrate my TFLite code to CompiledModel,” or type @litert-runtime, and it switches your app to play-services-litert, rewrites your Interpreter calls, and sets up GPU acceleration with CPU fallback. It can also scaffold a new LiteRT app. Treat it as a strong first pass: review the diff, build, and compare outputs on a real device. Get the skill on GitHub.

Upgrading from legacy APIs? The legacy GPU delegate and custom delegate APIs are deprecated in favor of CompiledModel GPU acceleration and the Compiler Plugin and Dispatch APIs, and NNAPI will be removed starting in 2027. Older SDKs now receive critical security fixes only. Apps you've already shipped keep working, but plan your move to the CompiledModel API now: code that uses deprecated APIs won't compile against the latest SDK, and staying on an older SDK can cause conflicts as your other dependencies move forward. See the release notes for details.

Looking ahead, LiteRT in Google Play services is our foundation for running your own task-specific models on Android, with CPU and GPU acceleration.

We can't wait to see what you build.