# VTK.js for Browser-Based Geometry and Volume Rendering > VTK.js is a plain JavaScript subset of VTK focused on WebGL and WebGPU rendering for ImageData and PolyData. It fits browser visualization work, but it is not a feature-equivalent replacement for VTK/C++. **Kitware/vtk-js** — Visualization Toolkit for the Web - Repository: https://github.com/Kitware/vtk-js - Website: https://kitware.github.io/vtk-js/ - Stars: 1,542 · Forks: 428 - Language: JavaScript - License: BSD-3-Clause - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/kitware-vtk-js ## VTK.js Targets Browser Visualization Pipelines VTK.js addresses a specific gap between desktop scientific visualization and browser applications. It brings portions of the Visualization Toolkit to JavaScript, concentrating on geometry and volume rendering through WebGL and WebGPU. The intended users are JavaScript developers who need to display meshes, image data, point clouds, and volumetric information in a web page rather than embed a full native VTK application. The project is a rewrite in ES6, not a direct compilation of VTK/C++. Its current focus includes the rendering pipelines for ImageData and PolyData, pipeline infrastructure, and readers for obj, stl, vtp, and vti. This narrower scope makes VTK.js more practical for web integration, but it also means that familiarity with the wider VTK API does not guarantee that an algorithm has a JavaScript equivalent. The README explicitly states that vtk.js is intended to remain a subset rather than duplicate the full filter collection. ## ImageData and PolyData Form the VTK.js Core The core architecture follows a visualization pipeline model. Data enters through a reader or application code, passes through supported filters, and reaches a renderer. PolyData is the stated center of geometry work, while ImageData supports image and volume visualization. This division lets a web application keep data processing and rendering in the browser while still using familiar VTK concepts such as pipeline objects, sources, and filters. Rendering covers both geometry and volume data. VTK.js names WebGL as its current rendering basis and also mentions WebGPU as a target. Browser target selection is handled through the Babel configuration and the repository's browserslist defaults. The README says that these defaults are used during builds, while applications built from source can be adjusted for another browser as long as it provides WebGL. This is an important implementation boundary. vtk.js can expose the infrastructure needed to define pipelines and filters, but the existence of that infrastructure should not be confused with the availability of every VTK filter. Filters included as demonstrations are not presented as a complete production catalog. ## Supported Readers Define the Practical Data Boundary The README identifies readers for obj, stl, vtp, and vti as among the frequently used components available in the JavaScript rewrite. These formats cover common geometry and visualization-data paths, but the documentation does not claim unrestricted VTK file-format compatibility. A team whose application starts with another input format should therefore confirm reader availability before selecting vtk.js. The architecture also provides ways to combine local JavaScript rendering with native VTK capabilities. The documentation describes compiling selected VTK/C++ components to WebAssembly so that they can interact with vtk.js. Conversely, VTK/C++ WebAssembly can perform rendering, as shown by examples linked from the VTK repository. This creates a mixed approach in which computation or rendering can remain in WebAssembly while another part of the application uses JavaScript. The tradeoff is download size. The README specifically notes that WebAssembly pages must download larger VTK or ITK WebAssembly payloads. It also says work remains to streamline vtk.js integrations with VTK WebAssembly. A pure JavaScript solution may therefore be preferable when avoiding a substantial native-derived payload is more important than using an algorithm that is absent from the vtk.js subset. ## Node 22+, NPM 10+, and the vtk.js Package The repository documents Node 22+ and NPM 10+ as supported development environments. The package metadata identifies the npm package as vtk.js and exposes different distributed formats through package entry points. The UMD entry is dist/umd/vtk.js, while the ES module entry is dist/esm/index.js. That distinction matters when integrating with bundlers, module loaders, or environments that expect a browser global rather than an ES module. The README does not provide an installation command or a minimal application snippet, so this article does not invent either. It directs users to the high-level documentation, API descriptions, and examples on the vtk.js documentation site. Those are the appropriate places to select a current usage pattern because the repository's example tree is organized by applications, geometry, rendering, volume, and widgets. For a first real use, start by identifying the input type. Applications centered on surface geometry should consult the Geometry and Rendering examples. Volumetric image data belongs under Volume. A user also needs to verify the required reader and renderer before writing application-specific pipeline code. The README confirms the existence of these examples but does not provide enough code here to reproduce one accurately. ## WebAssembly Adds Algorithms at a Payload Cost VTK.js and VTK/C++ WebAssembly solve different parts of the same integration problem. vtk.js offers a pure JavaScript implementation focused on its rendering pipeline, data types, and selected readers. VTK/C++ WebAssembly can provide access to parts of the native toolkit and can itself handle rendering. The README also identifies itk-wasm, an ITK implementation using WebAssembly, as a source of image filters and data readers. For a browser application that must stay entirely in JavaScript, vtk.js is the more direct choice. For an application that depends on a native VTK or ITK capability outside the JavaScript subset, a WebAssembly path may preserve access to that capability at the cost of a larger download. The project does not claim that every part of this integration is settled, which makes deployment size and module coordination application-specific concerns rather than settled advantages. VTK.js also includes helper classes for connecting to a remote VTK or ParaView server. The documented model pushes geometry from the server to the client and leaves rendering on the client. That is different from ordinary WebAssembly execution: the native VTK implementation remains on the server, while vtk.js handles the transferred geometry in the browser. ## BSD-3-Clause and Recent v37 Releases Shape Adoption VTK.js is distributed under the OSI-approved BSD 3-clause License, identified in package metadata as BSD-3-Clause. The repository directs readers to Copyright.txt for details. This article does not interpret the license or provide legal advice, but organizations can see that the project declares a permissive OSI-approved license rather than withholding license terms. The repository is not archived, and its last push was on 2026-10-12. Recent releases include v37.4.2 on 2026-10-12, v37.4.1 on 2026-10-03, and v37.4.0 on 2026-10-02. The package version in package.json is 0.0.0-semantically-release, which indicates that the published package version is handled through the release process rather than being hard-coded there. Consumers therefore need to distinguish repository development metadata from the version they install. The repository also includes BREAKING_CHANGES.md. The existence of BREAKING_CHANGES.md and a major v37 release line make compatibility checks part of adoption. The documented browser defaults and WebAssembly payload considerations add further review points for applications with strict bundle or browser-support constraints. ## Conclusion VTK.js is appropriate for teams building browser visualization from meshes, image data, and supported file formats without requiring the complete C++ filter catalog. It is a poor fit when every VTK/C++ algorithm must be available in JavaScript. Before adoption, check the required reader, filter, and rendering path against the documented subset, then measure the production bundle and browser requirements for the actual application. ## FAQ ### What is VTK.js used for? VTK.js provides JavaScript implementations of VTK concepts focused on browser-based geometry and volume rendering. Its stated emphasis is WebGL and WebGPU rendering for ImageData and PolyData. ### Is VTK.js a full replacement for VTK/C++? No. It is a plain JavaScript rewrite of a subset of VTK, with an emphasis on rendering pipelines, pipeline infrastructure, and readers such as obj, stl, vtp, and vti. The README explicitly says that not everything has been rewritten. ### What are the development requirements for VTK.js? The README lists Node 22+ and NPM 10+. It also says applications built from source can be adjusted for another browser as long as that browser provides WebGL. ### Can VTK.js use VTK/C++ through WebAssembly? The documentation describes compiling selected VTK/C++ parts to WebAssembly so they can interact with vtk.js. It also documents a hybrid remote-server model that pushes geometry to the client while rendering there, but warns that WebAssembly adds file-size costs and integration work. ## Sources - [Kitware/vtk-js on GitHub](https://github.com/Kitware/vtk-js) - [License: BSD-3-Clause](https://github.com/Kitware/vtk-js/blob/master/LICENSE) - [Project website](https://kitware.github.io/vtk-js/) - [README](https://github.com/Kitware/vtk-js/blob/master/README.md) - [Releases](https://github.com/Kitware/vtk-js/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kitware-vtk-js