VTK/ParaView widgets for trame 
trame-vtk extend trame widgets with components that can interface with VTK and/or ParaView.
VTK integration in trame allows you to create rich visualization and data processing applications by leveraging the Python wrapping of the VTK library. Several components are available so you can leverage VTK either for its data processing and/or rendering. trame lets you choose if you want to leverage Remote Rendering or if the client should do the rendering by leveraging vtk.js under the hood.
Installing
trame-vtk can be installed with pip:
pip install --upgrade trame-vtkUsage
The Trame Tutorial is the place to go to learn how to use the library and start building your own application.
The API Reference documentation provides API-level documentation.
License
trame-vtk is made available under the BSD-3-Clause License. For more details, see LICENSE This license has been chosen to match the one use by VTK and ParaView which can be exposed via this library.
Community
Trame | Discussions | Issues | | Contact Us
Enjoying trame?
Share your experience with a testimonial or with a brand approval.
Development: Grabbing client before push to PyPI
To update the client code, run the following command line while updating the targeted version
bash .fetch_externals.shTrame widgets
VtkRemoteView
The VtkRemoteView component relies on the server for rendering by sending images to the client by simply binding your vtkRenderWindow to it. This component gives you controls to the image size reduction and quality to reduce latency while interacting.
How to use it?
The component allows you to directly tap into a vtk.js interactor’s events so you can bind your own method from Python to them. The list of available events can be found here.
The component also provides a convenient method for pushing a new image to the client when you’re modifying your scene on the Python side.
from trame.widgets import vtk
def end():
pass
remote_view = vtk.vtkRemoteView(
view=..., # Instance of vtkRenderWindow (required)
ref=..., # Identifier for this component
interactive_quality=60, # [0, 100] 0 for fastest render, 100 for best quality
interactive_ratio=..., # [0.1, 1] Image size scale factor while interacting
interactor_events=( # Enable vtk.js interactor events for method binding
"events",
["EndAnimation"],
),
EndAnimation=end, # Bind method to the enabled event
)
remote_view.update() # Force image to be pushed to clientExamples
VtkLocalView
The VtkLocalView component relies on the server for defining the vtkRenderWindow but then only the geometry is exchanged with the client. The server does not need a GPU as no rendering is happening on the server. The vtkRenderWindow is only used to retrieve the scene data and parameters (coloring by, representations, …). By relying on the same vtkRenderWindow, you can easily switch from a VtkRemoteView to a VtkLocalView or vice-versa. This component gives you controls on how you want to map mouse interaction with the camera. The default setting mimic default VTK interactor style so you will rarely have to override to the interactor_settings. The VtkLocalView supports WebXR thanks to the VtkWebXRHelper component. Please refer to the examples for details on how to use it.
How to use it?
The component allows you to directly tap into a vtk.js interactor events so you can bind your own method from python to them. The list of available events can be found here.
The component also provides a convenient method to push the scene to the client when you’re modifying your scene on the python side.
from trame.widgets import vtk
def end():
pass
local_view = vtk.VtkLocalView(
view=..., # Instance of vtkRenderWindow (required)
ref=..., # Identifier for this component
context_name=..., # Namespace for geometry cache
interactor_settings=..., # Options for camera controls. See below.
interactor_events=( # Enable vtk.js interactor events for method binding
"events",
['EndAnimation'],
),
EndAnimation=end, # Bind method to the enabled event
)
local_view.update() # Force geometry to be pushedInteractor Settings
For the interactor_settings we expect a list of mouse event type linked to an action. The example below is what is used as default:
interactor_settings=[
{
button: 1,
action: 'Rotate',
}, {
button: 2,
action: 'Pan',
}, {
button: 3,
action: 'Zoom',
scrollEnabled: true,
}, {
button: 1,
action: 'Pan',
shift: true,
}, {
button: 1,
action: 'Zoom',
alt: true,
}, {
button: 1,
action: 'ZoomToMouse',
control: true,
}, {
button: 1,
action: 'Roll',
alt: true,
shift: true,
}
]A mouse event can be identified with the following set of properties:
Attribute |
Value |
Description |
|---|---|---|
button |
1, 2, 3 |
Which button should be down |
shift |
true/false |
Is the Shift key down |
alt |
true/false |
Is the Alt key down |
control |
true/false |
Is the Ctrl key down |
scrollEnabled |
true/false |
Some action could also be triggered by scroll |
dragEnabled |
true/false |
Mostly used to disable default drag behavior |
And the action could be one of the following:
Action |
Description |
|---|---|
Pan |
Will pan the object on the plane normal to the camera |
Zoom |
Will zoom closer or further from the object based on the drag direction |
Roll |
Will rotate the object around the view direction |
ZoomToMouse |
Will zoom while keeping the location that was initially under the mouse at the same spot |
Examples
VtkRemoteLocalView
The VtkRemoteLocalView component is a blend of VtkLocalView and VtkRemoteView where the user can choose dynamically which mode they want to be in. When instantiating a VtkRemoteLocalView several variables and triggers will be created for you to more easily control your view.
How to use it?
from trame.html import vtk
rl_view = vtk.VtkRemoteLocalView(
view=..., # Instance of vtkRenderWindow (required)
# Just VtkRemoteLocalView params
namespace=..., # Prefix for variables and triggers. See below. (required)
mode="local", # Decide between local or remote. See below.
# VtkRemoteView params
**remote_view_params,
# VtkLocalView params
**local_view_params,
)
rl_view.update_geometry() # Force update to geometry
rl_view.update_image() # Force update to image
rl_view.view() # Get linked vtkRenderWindow instanceNamespace parameter
Constructing a VtkRemoteLocalView will set several variables, prefixed by a namespace. In the example below we used namespace="view".
Variable |
Description |
|---|---|
viewId |
str representing the vtkRenderWindow id |
viewMode |
local`or `remote to control which View is displayed to the user |
Constructing a VtkRemoteLocalView will also set several trame triggers.
Trigger |
Description |
|---|---|
viewCamera |
When call with no arguments, the server will push its camera to the client |
viewAnimateStart |
Start the animation loop for constantly rendering |
viewAnimateStop |
Stop the animation loop |
The namespace will also be used as ref= unless provided by the user.
Mode parameter
The mode is driven by the variable {namespace}Mode but can be provided when instantiated so the default can be overridden and a JavaScript expression can be used instead of the default variable. This attribute behaves the same way as any trame one except, we won’t register the left side as a state entry since we already have one under {namespace}Mode. This means we will evaluate the left side of the expression assuming a tuple is provided and the right side of the tuple is used to set its initial value.
Examples
Development
Install the library
# Create venv and install all dependencies
uv sync --all-extras --dev
# Activate environment
source .venv/bin/activate
# Install commit analysis
pre-commit install
pre-commit install --hook-type commit-msgJavaScript dependency
This Python package bundle the vue-vtk-js@3.3.4 JavaScript library. If you would like us to upgrade it, please reach out.
3 maintainers
Metadata
3 maintainers
Release files for trame-vtk 2.11.17
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| trame_vtk-2.11.17.tar.gz | 829.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trame_vtk-2.11.17-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.7 MB
Release files / trame_vtk-2.11.17.tar.gz
| Download URL | trame_vtk-2.11.17.tar.gz |
|---|---|
| Size | 829.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
367ef96505f27d6a01c03cdc4a8fe3f8894998d2b6b623512ef07c1fe716caba
|
|
BLAKE2b-256 checksum How to use checksums |
c25317db0dbc4483533db6b6de079b24d2c7071faf0aa18a22f23874bb5b5f5b
|
| 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 Sep 22, 2026.
Transparency logRelease files / trame_vtk-2.11.17-py3-none-any.whl
| Download URL | trame_vtk-2.11.17-py3-none-any.whl |
|---|---|
| Size | 852.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8fe2adbe3b6888ad41cb4311421fbd850cece75a801bf8b5f7af5bdc6473bee4
|
|
BLAKE2b-256 checksum How to use checksums |
c8f1d9b1119bad9c3018b2cc801032447e0f5cf942859845a1eaf03aff9c0905
|
| 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 Sep 22, 2026.
Transparency log
