AI/TLDR

LiteRT

Google's on-device runtime for ML and generative AI — the successor to TensorFlow Lite, with GPU and NPU acceleration across mobile, desktop, web and IoT

Local RuntimesOpen source
Updated
9 Jul 2026
Language
C++
License
Apache-2.0
Coverage
1 story
$uv venv --clear --python=3.13 --seed

What's new

9 Jul 2026

Google introduced LiteRT.js, a JavaScript binding that runs LiteRT models in the browser through WebAssembly and WebGPU, reporting up to 3× speedups over other web runtimes on CPU and GPU on an M4 MacBook Pro.

Latest news

Overview

LiteRT is Google's runtime for running machine-learning and generative-AI models directly on a device, and the continuation of TensorFlow Lite under a new name. It takes models exported from PyTorch, TensorFlow or JAX — as `.tflite` for classic models or `.litertlm` for LLMs — and executes them on whatever accelerator the hardware offers, from CPU via XNNPack to GPU via the ML Drift backend to vendor NPUs. Around the runtime sits a small toolchain: LiteRT Torch for conversion, the AI-Edge Quantizer for optimisation, and LiteRT-LM for on-device language models.

The V2 API is where the project's design shows. The Compiled Model API removes explicit delegate wiring in favour of automated accelerator selection, adds true asynchronous execution and efficient I/O buffer handling, and exposes NPUs from several chipset vendors through one consistent interface rather than per-vendor code paths. A tensor-centric C++ Tensor API is available when you need direct control over memory and graph execution.

Platform coverage is broad and explicitly tabulated in the repository: Android (OpenCL/OpenGL GPU, plus Broadcom, Google Tensor, Intel, MediaTek and Qualcomm NPUs), iOS and macOS (Metal), Linux, Windows and IoT (WebGPU), and the browser through LiteRT.js, which runs models client-side over WebGPU and WebAssembly. There is also a LiteRT CLI aimed at coding-agent workflows. The project publishes nightly builds and targets stable releases on a six-to-eight-week cadence, is written mainly in C++, and is Apache-2.0.

What it does

  • Compiled Model API with automated accelerator selection, asynchronous execution and efficient I/O buffer handling — no explicit delegates
  • Unified NPU acceleration across Broadcom, Google Tensor, Intel, MediaTek and Qualcomm silicon through one API
  • GPU acceleration via ML Drift, with buffer interoperability designed to cut latency between GPU buffer types
  • Browser inference through LiteRT.js over WebGPU and WebAssembly
  • On-device LLMs and diffusion models through LiteRT-LM, with `.litertlm` bindings for Python, C++, Kotlin, Swift and JS
  • Conversion from PyTorch, TensorFlow and JAX via LiteRT Torch, plus the AI-Edge Quantizer for optimised artifacts
  • Tensor API — a lightweight tensor-centric C++ library for direct memory and graph control

Getting started

Which entry point you use depends on the target. The LiteRT CLI is the quickest thing to install locally; mobile and web integration are covered by the platform guides.

Install the LiteRT CLI

The README's quick setup: a Python 3.13 virtual environment and the nightly CLI package.

bashbash
uv venv --clear --python=3.13 --seed
source .venv/bin/activate
uv pip install litert-cli-nightly
litert --help

Convert a model

LiteRT Torch exports PyTorch and Hugging Face safetensors models to `.tflite` for classic models, or through the Generative Torch API to `.litertlm` for LLMs. Run the result through the AI-Edge Quantizer to optimise it.

Run it on the target platform

Follow the LiteRT Integration Overview at ai.google.dev/edge/litert/overview for your platform; the repository's litert-samples companion has working Android, C++ and Kotlin apps for the Compiled Model API.

Or build the runtime from source

Linux and cross-compiled Android artifacts build inside the provided Docker image; CMake and Bazel instructions live in g3doc/instructions/.

bashbash
cd docker_build
./build_with_docker.sh

Commands and code are distilled from the project's own documentation — always check the official repo for the latest.

When to use it

  • Reach for it when a model has to run on the user's phone, laptop or browser rather than on a server
  • Reach for it when you are migrating an existing TensorFlow Lite deployment and want NPU support without per-vendor code
  • Reach for it when you want a quantized LLM or diffusion model running fully on-device via LiteRT-LM
  • Reach for it when a web app needs client-side inference over WebGPU without shipping data off the machine

How LiteRT compares

LiteRT alongside other open-source local runtimes tools AI/TLDR tracks, ranked by GitHub stars.

ToolStarsWhat it does
Ollama★ 180kA developer-friendly tool that downloads and runs local LLMs from the terminal with a built-in OpenAI-compatible API.
llama.cpp★ 127kA C/C++ inference engine that runs LLMs in the GGUF format on CPUs, Apple Silicon, and GPUs with low memory use.
GPT4All★ 77.4kGPT4All is a free desktop app and Python client that runs large language models locally on your own computer, with no API calls or GPU required.
LocalAI★ 49kA self-hosted server that exposes an OpenAI-compatible API for running text, vision, voice, and image models on local hardware.
Jan★ 44.4kAn open-source desktop app that runs LLMs fully offline as a ChatGPT-style assistant on your own computer.
AirLLM★ 33.8kA Python inference library that keeps only one transformer layer on the GPU at a time, so a 70B model runs on a single 4GB card and a 671B MoE model on about 12GB, without quantization.
llamafile★ 25.9kA Mozilla project that packages a model and its runtime into one executable file you can copy and run on any OS.
LiteRT★ 3.4kGoogle's on-device runtime for ML and generative AI — the successor to TensorFlow Lite, with GPU and NPU acceleration across mobile, desktop, web and IoT