This release is a pre-release and may not be stable for production use.
Keras 3: Deep Learning for Humans
Keras 3 is a multi-backend deep learning framework, with support for JAX, TensorFlow, PyTorch, and OpenVINO (for inference-only). Effortlessly build and train models for computer vision, natural language processing, audio processing, timeseries forecasting, recommender systems, etc.
- Accelerated model development: Ship deep learning solutions faster thanks to the high-level UX of Keras and the availability of easy-to-debug runtimes like PyTorch or JAX eager execution.
- State-of-the-art performance: By picking the backend that is the fastest for your model architecture (often JAX!), leverage speedups ranging from 20% to 350% compared to other frameworks. Benchmark here.
- Datacenter-scale training: Scale confidently from your laptop to large clusters of GPUs or TPUs.
Join nearly three million developers, from burgeoning startups to global enterprises, in harnessing the power of Keras 3.
Installation
Install with pip
Keras 3 is available on PyPI as keras. Note that Keras 2 remains available as the tf-keras package.
- Install
keras:
pip install keras --upgrade
- Install backend package(s).
To use keras, you should also install the backend of choice: tensorflow, jax, or torch. Additionally,
The openvino backend is available with support for model inference only.
Local installation
Minimal installation
Keras 3 is compatible with Linux and macOS systems. For Windows users, we recommend using WSL2 to run Keras. To install a local development version:
- Install dependencies:
pip install -r requirements.txt
- Run installation command from the root directory.
python pip_build.py --install
- Run API generation script when creating PRs that update
keras_exportpublic APIs:
./shell/api_gen.sh
Backend Compatibility Table
The following table lists the minimum supported versions of each backend for the latest stable release of Keras (v3.x):
| Backend | Minimum Supported Version |
|---|---|
| TensorFlow | 2.16.1 |
| JAX | 0.4.20 |
| PyTorch | 2.1.0 |
| OpenVINO | 2026.2.0 |
Adding GPU support
The requirements.txt file will install a CPU-only version of TensorFlow, JAX, and PyTorch. For GPU support, we also
provide a separate requirements-{backend}-cuda.txt for TensorFlow, JAX, and PyTorch. These install all CUDA
dependencies via pip and expect a NVIDIA driver to be pre-installed. We recommend a clean Python environment for each
backend to avoid CUDA version mismatches. As an example, here is how to create a JAX GPU environment with conda:
conda create -y -n keras-jax python=3.10
conda activate keras-jax
pip install -r requirements-jax-cuda.txt
python pip_build.py --install
Configuring your backend
You can export the environment variable KERAS_BACKEND or you can edit your local config file at ~/.keras/keras.json
to configure your backend. Available backend options are: "tensorflow", "jax", "torch", "openvino". Example:
export KERAS_BACKEND="jax"
In Colab, you can do:
import os
os.environ["KERAS_BACKEND"] = "jax"
import keras
Note: The backend must be configured before importing keras, and the backend cannot be changed after
the package has been imported.
Note: The OpenVINO backend is an inference-only backend, meaning it is designed only for running model
predictions using model.predict() method.
Backwards compatibility
Keras 3 is intended to work as a drop-in replacement for tf.keras (when using the TensorFlow backend). Just take your
existing tf.keras code, make sure that your calls to model.save() are using the up-to-date .keras format, and you're
done.
If your tf.keras model does not include custom components, you can start running it on top of JAX or PyTorch immediately.
If it does include custom components (e.g. custom layers or a custom train_step()), it is usually possible to convert it
to a backend-agnostic implementation in just a few minutes.
In addition, Keras models can consume datasets in any format, regardless of the backend you're using:
you can train your models with your existing tf.data.Dataset pipelines or PyTorch DataLoaders.
Why use Keras 3?
- Run your high-level Keras workflows on top of any framework -- benefiting at will from the advantages of each framework, e.g. the scalability and performance of JAX or the production ecosystem options of TensorFlow.
- Write custom components (e.g. layers, models, metrics) that you can use in low-level workflows in any framework.
- You can take a Keras model and train it in a training loop written from scratch in native TF, JAX, or PyTorch.
- You can take a Keras model and use it as part of a PyTorch-native
Moduleor as part of a JAX-native model function.
- Make your ML code future-proof by avoiding framework lock-in.
- As a PyTorch user: get access to power and usability of Keras, at last!
- As a JAX user: get access to a fully-featured, battle-tested, well-documented modeling and training library.
Read more in the Keras 3 release announcement.
4 maintainers
Metadata
4 maintainers
Release files for keras-nightly 3.16.0.dev2026101304
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| keras_nightly-3.16.0.dev2026101304.tar.gz | 1.3 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| keras_nightly-3.16.0.dev2026101304-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 3.0 MB
Release files / keras_nightly-3.16.0.dev2026101304.tar.gz
| Download URL | keras_nightly-3.16.0.dev2026101304.tar.gz |
|---|---|
| Size | 1.3 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84033db3fb3b2e9b5d125a2d2dbc3042043aab7ce390a135f737be9d9468c7f5
|
|
BLAKE2b-256 checksum How to use checksums |
bcf2c3a2c25f89523018b4845fbce1be976f507d46584ac3b9d94985ae0a2b41
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency logRelease files / keras_nightly-3.16.0.dev2026101304-py3-none-any.whl
| Download URL | keras_nightly-3.16.0.dev2026101304-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
065dc5d2ee7e86a8dae3e83d05974164c212cdf7f93fa3c7d77a3f27de7e5306
|
|
BLAKE2b-256 checksum How to use checksums |
476e4ebff999d078512f6c95fff000c21dc0825f0351777c48a476d134db01d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 13, 2026.
Transparency log
