TensorFlow.js converter is an open source library to load a pretrained TensorFlow SavedModel or TensorFlow Hub module into the browser and run inference through TensorFlow.js.
Note: _Session bundle format have been deprecated.
A 2-step process to import your model:
- A python pip package to convert a TensorFlow SavedModel or TensorFlow Hub module to a web friendly format. If you already have a converted model, or are using an already hosted model (e.g. MobileNet), skip this step.
- JavaScript API, for loading and running inference.
Step 1: Converting a TensorFlow SavedModel, TensorFlow Hub module, Keras HDF5 or tf.keras SavedModel to a web-friendly format
0. Please make sure that you run in a Docker container or a virtual environment.
The script pulls its own subset of TensorFlow, which might conflict with the existing TensorFlow/Keras installation.
Note: Check that tf-nightly-2.0-preview
is available for your platform.
Most of the times, this means that you have to use Python 3.6.8 in your local
environment. To force Python 3.6.8 in your local project, you can install
pyenv
and proceed as follows in the target
directory:
pyenv install 3.6.8
pyenv local 3.6.8
Now, you can
create and activate
a venv
virtual environment in your current folder:
virtualenv --no-site-packages venv
. venv/bin/activate
1. Install the TensorFlow.js pip package:
Install the library with interactive CLI:
pip install tensorflowjs[wizard]
2. Run the converter script provided by the pip package:
There are two way to trigger the model conversion:
- The conversion wizard:
tensorflowjs_wizard
- Regular conversion script:
tensorflowjs_converter
To start the conversion wizard:
tensorflowjs_wizard
This tool will walk you through the conversion process and provide you with
details explanations for each choice you need to make. Behind the scene it calls
the converter script (tensorflowjs_converter
) in pip package. This is the
recommended way to convert a single model.
There is also a dry run mode for the wizard, which will not perform the actual
conversion but only generate the command for tensorflowjs_converter
command.
This generated command can be used in your own shell script.
Here is an screen capture of the wizard in action.
tensorflowjs_wizard --dryrun
To convert a batch of models or integrate the conversion process into your own script, you should use the tensorflowjs_converter script.
The converter expects a TensorFlow SavedModel, TensorFlow Hub module, TensorFlow.js JSON format, Keras HDF5 model, or tf.keras SavedModel for input.
- TensorFlow SavedModel example:
tensorflowjs_converter \
--input_format=tf_saved_model \
--output_format=tfjs_graph_model \
--signature_name=serving_default \
--saved_model_tags=serve \
/mobilenet/saved_model \
/mobilenet/web_model
- TensorFlow Frozen Model example:
Note: Frozen model is a deprecated format and support is added for backward compatibility purpose.
$ tensorflowjs_converter \
--input_format=tf_frozen_model \
--output_node_names='MobilenetV1/Predictions/Reshape_1' \
/mobilenet/frozen_model.pb \
/mobilenet/web_model
- Tensorflow Hub module example:
tensorflowjs_converter \
--input_format=tf_hub \
'https://tfhub.dev/google/imagenet/mobilenet_v1_100_224/classification/1' \
/mobilenet/web_model
- Keras HDF5 model example:
tensorflowjs_converter \
--input_format=keras \
/tmp/my_keras_model.h5 \
/tmp/my_tfjs_model
- tf.keras SavedModel example:
tensorflowjs_converter \
--input_format=keras_saved_model \
/tmp/my_tf_keras_saved_model/1542211770 \
/tmp/my_tfjs_model
Note that the input path used above is a subfolder that has a Unix epoch time (1542211770) and is generated automatically by tensorflow when it saved a tf.keras model in the SavedModel format.
Positional Arguments | Description |
---|---|
input_path |
Full path of the saved model directory or TensorFlow Hub module handle or path. |
output_path |
Path for all output artifacts. |
Options | Description |
---|---|
--input_format |
The format of input model, use tf_saved_model for SavedModel, tf_hub for TensorFlow Hub module, tfjs_layers_model for TensorFlow.js JSON format, and keras for Keras HDF5. |
--output_format |
The desired output format. Must be tfjs_layers_model , tfjs_graph_model or keras . Not all pairs of input-output formats are supported. Please file a github issue if your desired input-output pair is not supported. |
--saved_model_tags |
Only applicable to SavedModel conversion. Tags of the MetaGraphDef to load, in comma separated format. If there are no tags defined in the saved model, set it to empty string saved_model_tags='' . Defaults to serve . |
--signature_name |
Only applicable to TensorFlow SavedModel and Hub module conversion, signature to load. Defaults to serving_default for SavedModel and default for Hub module. See https://www.tensorflow.org/hub/common_signatures/. |
--strip_debug_ops |
Strips out TensorFlow debug operations Print , Assert , CheckNumerics . Defaults to True . |
--quantization_bytes |
(Deprecated) How many bytes to optionally quantize/compress the weights to. Valid values are 1 and 2. which will quantize int32 and float32 to 1 or 2 bytes respectively. The default (unquantized) size is 4 bytes. |
--quantize_float16 |
Comma separated list of node names to apply float16 quantization. You can also use wildcard symbol (*) to apply quantization to multiple nodes (e.g., conv/*/weights). When the flag is provided without any nodes the default behavior will match all nodes. |
--quantize_uint8 |
Comma separated list of node names to apply 1-byte affine quantization. You can also use wildcard symbol (*) to apply quantization to multiple nodes (e.g., conv/*/weights). When the flag is provided without any nodes the default behavior will match all nodes. |
--quantize_uint16 |
Comma separated list of node names to apply 2-byte affine quantization. You can also use wildcard symbol (*) to apply quantization to multiple nodes (e.g., conv/*/weights). When the flag is provided without any nodes the default behavior will match all nodes. |
--weight_shard_size_bytes |
Shard size (in bytes) of the weight files. Only supported when output_format is tfjs_layers_model or tfjs_graph_model . Default size is 4 MB (4194304 bytes). |
--output_node_names |
Only applicable to Frozen Model. The names of the output nodes, separated by commas. |
--control_flow_v2 |
Only applicable to TF 2.x Saved Model. This flag improve performance on models with control flow ops, default to False. |
--metadata |
Comma separated list of metadata json file paths, indexed by name. Prefer absolute path. Example: 'metadata1:/metadata1.json,metadata2:/metadata2.json'. |
Note: If you want to convert TensorFlow session bundle, you can install older versions of the tensorflowjs pip package, i.e. pip install tensorflowjs==0.8.6
.
Note: Unless stated otherwise, we can infer the value of --output_format
from the
value of --input_format
. So the --output_format
flag can be omitted in
most cases.
--input_format |
--output_format |
Description |
---|---|---|
keras |
tfjs_layers_model |
Convert a keras or tf.keras HDF5 model file to TensorFlow.js Layers model format. Use tf.loadLayersModel() to load the model in JavaScript. The loaded model supports the full inference and training (e.g., transfer learning) features of the original keras or tf.keras model. |
keras |
tfjs_graph_model |
Convert a keras or tf.keras HDF5 model file to TensorFlow.js Graph model format. Use tf.loadGraphModel() to load the converted model in JavaScript. The loaded model supports only inference, but the speed of inference is generally faster than that of a tfjs_layers_model (see above row) thanks to the graph optimization performed by TensorFlow. Another limitation of this conversion route is that it does not support some layer types (e.g., recurrent layers such as LSTM) yet. |
keras_saved_model |
tfjs_layers_model |
Convert a tf.keras SavedModel model file (from tf.contrib.saved_model.save_keras_model ) to TensorFlow.js Layers model format. Use tf.loadLayersModel() to load the model in JavaScript. |
tf_hub |
tfjs_graph_model |
Convert a TF-Hub model file to TensorFlow.js graph model format. Use tf.loadGraphModel() to load the converted model in JavaScript. |
tf_saved_model |
tfjs_graph_model |
Convert a TensorFlow SavedModel to TensorFlow.js graph model format. Use tf.loadGraphModel() to load the converted model in JavaScript. |
tf_frozen_model |
tfjs_graph_model |
Convert a Frozen Model to TensorFlow.js graph model format. Use tf.loadGraphModel() to load the converted model in JavaScript. |
--input_format |
--output_format |
Description |
---|---|---|
tfjs_layers_model |
keras |
Convert a TensorFlow.js Layers model (JSON + binary weight file(s)) to a Keras HDF5 model file. Use keras.model.load_model() or tf.keras.models.load_model() to load the converted model in Python. |
tfjs_layers_model |
keras_saved_model |
Convert a TensorFlow.js Layers model (JSON + binary weight file(s)) to the tf.keras SavedModel format. This format is useful for subsequent uses such as TensorFlow Serving and conversion to TFLite. |
The tfjs_layers_model-to-tfjs_layer_model conversion option serves the following purposes:
-
It allows you to shard the binary weight file into multiple small shards to facilitate browser caching. This step is necessary for models with large-sized weights saved from TensorFlow.js (either browser or Node.js), because TensorFlow.js puts all weights in a single weight file ('group1-shard1of1.bin'). To shard the weight file, do
tensorflowjs_converter \ --input_format tfjs_layers_model \ --output_format tfjs_layers_model \ original_model/model.json \ sharded_model/
The command above creates shards of size 4 MB (4194304 bytes) by default. Alternative shard sizes can be specified using the
--weight_shard_size_bytes
flag. -
It allows you to reduce the on-the-wire size of the weights through 16- or 8-bit quantization. For example:
tensorflowjs_converter \ --input_format tfjs_layers_model \ --output_format tfjs_layers_model \ --quantize_uint16 \ original_model/model.json quantized_model/
Converting a tfjs_layers_model
to a tfjs_graph_model
usually leads to
faster inference speed in the browser and Node.js, thanks to the graph
optimization that goes into generating the tfjs_graph_models. For more details,
see the following document on TensorFlow's Grappler:
"TensorFlow Graph Optimizations" by R. Larsen an T. Shpeisman.
There are two caveats:
- The model that results from this conversion does not support further training.
- Certain layer types (e.g., recurrent layers such as LSTM) are not supported yet.
See example command below:
tensorflowjs_converter \
--input_format tfjs_layers_model \
--output_format tfjs_graph_model \
my_layers_model/model.json
my_graph_model/
tfjs_layers_model-to-tfjs_graph_model also support weight quantization.
The conversion script above produces 2 types of files:
model.json
(the dataflow graph and weight manifest file)group1-shard\*of\*
(collection of binary weight files)
For example, here is the MobileNet model converted and served in following location:
https://storage.cloud.google.com/tfjs-models/savedmodel/mobilenet_v1_1.0_224/model.json
https://storage.cloud.google.com/tfjs-models/savedmodel/mobilenet_v1_1.0_224/group1-shard1of5
...
https://storage.cloud.google.com/tfjs-models/savedmodel/mobilenet_v1_1.0_224/group1-shard5of5
If the original model was a SavedModel
, use
tf.loadGraphModel()
.
If it was Keras, use
tf.loadLayersModel()
:
import * as tf from '@tensorflow/tfjs';
const MODEL_URL = 'https://.../mobilenet/model.json';
// For Keras use tf.loadLayersModel().
const model = await tf.loadGraphModel(MODEL_URL);
const cat = document.getElementById('cat');
model.predict(tf.browser.fromPixels(cat));
See our API docs for the
predict()
method. To see what other methods exist on a Model
, see
tf.LayersModel
and tf.GraphModel
.
Also check out our working MobileNet demo.
If your server requests credentials for accessing the model files, you can provide the optional RequestOption param.
const model = await loadGraphModel(MODEL_URL,
{credentials: 'include'});
Please see fetch() documentation for details.
TensorFlow.js can be used from Node.js. See the
tfjs-node project for more details.
Unlike web browsers, Node.js can access the local file system directly.
Therefore, you can load the same frozen model from local file system into
a Node.js program running TensorFlow.js. This is done by calling
loadGraphModel
with the path to the model files:
// Load the tfjs-node binding
import * as tf from '@tensorflow/tfjs-node';
const MODEL_PATH = 'file:///tmp/mobilenet/model.json';
const model = await tf.loadGraphModel(MODEL_PATH);
You can also load the remote model files the same way as in browser, but you might need to polyfill the fetch() method.
Currently TensorFlow.js only supports a limited set of TensorFlow Ops. See the
full list.
If your model uses unsupported ops, the tensorflowjs_converter
script will
fail and produce a list of the unsupported ops in your model. Please file issues
to let us know what ops you need support with.
If you want to manually write the forward pass with the ops API, you can load the weights directly as a map from weight names to tensors:
import * as tf from '@tensorflow/tfjs';
const modelUrl = "https://example.org/model/model.json";
const response = await fetch(modelUrl);
this.weightManifest = (await response.json())['weightsManifest'];
const weightMap = await tf.io.loadWeights(
this.weightManifest, "https://example.org/model");
weightMap
maps a weight name to a tensor. You can use it to manually implement
the forward pass of the model:
const input = tf.tensor(...);
tf.matMul(weightMap['fc1/weights'], input).add(weightMap['fc1/bias']);
1. What TensorFlow models does the converter currently support?
Image-based models (MobileNet, SqueezeNet, add more if you tested) are the most supported. Models with control flow ops (e.g. RNNs) are also supported. The tensorflowjs_converter script will validate the model you have and show a list of unsupported ops in your model. See this list for which ops are currently supported.
2. Will model with large weights work?
While the browser supports loading 100-500MB models, the page load time, the inference time and the user experience would not be great. We recommend using models that are designed for edge devices (e.g. phones). These models are usually smaller than 30MB.
3. Will the model and weight files be cached in the browser?
Yes, we are splitting the weights into files of 4MB chunks, which enable the browser to cache them automatically. If the model architecture is less than 4MB (most models are), it will also be cached.
4. Can I quantize the weights over the wire?
Yes, you can use the --quantize_{float16, uint8, uint16} flags to compress
weights with 1 byte integer quantization (uint8
) or 2 byte integer
(uint16
)/float (float16
) quantization.
Quantizing to float16 may provide better accuracy over
2 byte affine integer scaling (uint16
). 1-byte affine quantization,
i.e., uint8
provides a 4x size reduction at the cost of accuracy.
For example, we can quantize our MobileNet model using float16 quantization:
tensorflowjs_converter
--quantize_float16 \
--input_format=tf_hub \
'https://tfhub.dev/google/imagenet/mobilenet_v1_100_224/classification/1' \
/mobilenet/web_model
You can also quantize specific weights as well as weight groupings using a wildcard replacement. For example,
tensorflowjs_converter
--quantize_float16="conv/*/weights"
which will quantize all weights that match the pattern conv/*/weights. This will exclude biases and any weights that don't begin with conv/. This can be a powerful tool to reduce model size while trying to maximize performance.
5. Why is the predict() method for inference so much slower on the first call than the subsequent calls?
The time of first call also includes the compilation time of WebGL shader programs for the model. After the first call the shader programs are cached, which makes the subsequent calls much faster. You can warm up the cache by calling the predict method with an all zero inputs, right after the completion of the model loading.
6. I have a model converted with a previous version of TensorFlow.js converter (0.15.x), that is in .pb format. How do I convert it to the new JSON format?
You can use the built-in migration tool to convert the models generated by previous versions. Here are the steps:
git clone [email protected]:tensorflow/tfjs-converter.git
cd tfjs-converter
yarn
yarn ts-node tools/pb2json_converter.ts pb_model_directory/ json_model_directory/
pb_model_directory
is the directory where the model generated by previous
version is located.
json_model_directory
is the destination directory for the converted model.
To build TensorFlow.js converter from source, we need to prepare the dev environment and clone the project.
Bazel builds Python from source, so we install the dependencies required to build it. Since we will be using pip and C extensions, we also install the ssl, foreign functions, and zlib development packages. On debian, this is done with:
sudo apt-get build-dep python3
sudo apt install libssl-dev libffi-dev zlib1g-dev
See the python developer guide for instructions on installing these for other platforms.
Then, we clone the project and install dependencies with:
git clone https://github.com/tensorflow/tfjs.git
cd tfjs/tfjs-converter
yarn # Installs dependencies.
We recommend using Visual Studio Code for
development. Make sure to install
TSLint VSCode extension
and the npm clang-format 1.2.2
or later with the
Clang-Format VSCode extension
for auto-formatting.
Before submitting a pull request, make sure the code passes all the tests and is clean of lint errors:
yarn test
yarn lint
To run a subset of tests and/or on a specific browser:
yarn test --browsers=Chrome --grep='execute'
> ...
> Chrome 64.0.3282 (Linux 0.0.0): Executed 39 of 39 SUCCESS (0.129 secs / 0 secs)
To run the tests once and exit the karma process (helpful on Windows):
yarn test --single-run