PixiJS Adds 3D to the 2D Scene and Opens an MIT-Licensed Beta
The PixiJS team has opened the public beta of PixiJS 3D, the official three-dimensional extension of its 2D browser engine. A 3D scene here is attached as an ordinary element of the 2D scene: it is added to the same canvas as sprites, text and interface, and it is drawn together with them in the shared layer order. For studios building browser games, promos and interactive interfaces on PixiJS, this means a 3D model can be inserted into an already finished project. There is no need to rewrite it or to run a second engine alongside.
The extension is free and distributed under the MIT license. The developers designed it primarily for WebGPU; the same scene code also works on WebGL2. The API is not fixed yet, and version 1.0 is promised once feedback from open beta participants has been processed.
"It's free. MIT license, and it always will be."
— the PixiJS team in the open beta announcement
A 3D view is placed on the scene like a sprite
The entire three-dimensional scene lives inside a separate 3D view, and that view itself behaves like a sprite within the 2D scene. You can place several such views anywhere in the composition, each with its own scene and camera, as shown by the multiple views example. The layering order is simple: 2D elements that come later in the list are drawn on top of the 3D, and earlier ones are visible through it if the view has no background set. The playground has a scene where a glass 3D logo refracts a 2D poster drawn behind it.
2D and 3D still remain separate worlds. A sprite cannot be placed inside the 3D tree, and a 3D node cannot be put directly onto the 2D scene. To show a 2D interface on the surface of a 3D object, it is rendered into a texture that can update every frame. In the example on the site, a live 2D container is displayed this way on the faces of a cube, and in the announcement a 2D scene with a clock runs on the screen of a 3D monitor. For labels that follow a 3D object, there is a conversion of coordinates from scene space to screen space. By default a 3D view intercepts clicks and hover across its entire rectangular area, so 2D buttons underneath it cannot be pressed until this behavior is configured. The pointer also responds to the 3D objects themselves.
What the engine can do
- Models. glTF 2.0 loads as .gltf or .glb, with Draco and meshopt geometry compression, compressed textures, skinning, morph targets and animation. Animation clips are launched by name, as with the fox model from the demo on the site.
- Materials. PBR, Phong, flat and toon are available; you can write your own materials, including multi-pass ones.
- Light and image. There are shadows, including cascaded ones, HDR, tone mapping, a render graph and post-processing, including bloom and ambient occlusion.
- Other. Particles and a camera that orbits around an object are included.
Copies of a single prop cost almost nothing. Each model builds its own nodes but uses shared geometry, materials and textures, the same way sprites use a single texture. If you place several crates from one file around a level, the file is loaded once. A separate batch mode is provided for thousands of copies.
Speed without manual optimization
The main promise of the release: a scene assembled in the most obvious way should already run fast. The developers compared different rendering approaches, and the engine itself picks the one suited to the device, the browser and the specific scene. Objects with shared geometry and material are automatically merged into a single instanced draw call. Five cubes with shared geometry and material are drawn in one call; twelve animated characters from one model file are also drawn in one.
Culling of invisible objects is performed on the graphics card in a compute shader in most browsers with WebGPU. In Safari and on any iPhone and iPad it is computed by the processor for a typical scene, and it moves to the graphics card when the object batch becomes large enough. The engine recomputes only changed meshes, so a static scene puts almost no load on the processor. This is probably especially useful for interfaces where a 3D object is motionless most of the time. Each browser downloads only the backend it needs, WebGPU or WebGL2.
The batch demonstration shows 100,000 objects with shadows at 60 frames per second. The announcement does not state what hardware these figures were obtained on. To show the engine at work outside benchmarks, the team published two games on its Good Stuff experiment showcase. Nightward generates all its graphics and music in code and loads not a single image or sound file. Mach 2 runs on WebGPU and WebGL2, and can be played with a keyboard or on a phone. The team promises to post new 3D experiments there as well.
What to account for when assembling a scene
The 3D part has its own coordinate system, and those who work in 2D pixels will have to get used to it. The Y axis points up, and the unit is a meter. By default the camera draws nothing farther than 1000 units, so a scene assembled at pixel sizes will be clipped. Models may need scaling: in the fox demo the model is reduced to 0.01 of its original size.
The second nuance concerns compatibility. If the browser has chosen WebGPU but the graphics card lacks a required feature, the application will not switch to WebGL2 automatically and will throw an error on startup. The documentation describes how to check support in advance. For phones, the guide advises limiting pixel density to a value of 2: on a triple-density screen this cuts the number of drawn pixels by more than half.
The closed beta has already revealed characteristic problems. Export from Blender crashed the glTF loader, and on some Android phones shaders requested more parameters than WebGL2 permits. In total, testers sent more than 30 bug reports and feature requests, most of which made it into the release.
Where to get it and how to start
The @pixi/3d package installs together with pixi.js via npm or from a CDN and requires pixi.js version 8.23.0 or newer. The sources are in the PixiJS 3D repository on GitHub; documentation and examples are gathered on the PixiJS 3D page. There are 35 guides there, more than 100 interactive examples and three tutorials that run right in the browser editor. The introductory lesson step by step assembles a rotating cube on a floor, sets up a camera and directional light, and then loads a glTF model.
Along with the extension came a skill for AI agents; it can be connected in Claude Code, Cursor, Codex and Copilot, and it is part of the npm package. The documentation is published in the llms.txt format, convenient for language models. The developers themselves call PixiJS 3D the largest addition to PixiJS since the engine's eighth version.
Who will find it useful and where the risks are
PixiJS has long had a third-party 3D extension, Pixi3D, from an independent developer. It supports PBR and environment-map lighting, and its author reports production use on hundreds of thousands of devices, but it is compatible with PixiJS versions 5, 6 and 7. The official package targets the eighth branch, starting from 8.23.0. Studios with old projects on Pixi3D will probably first have to move them to current PixiJS, and only then switch to the new extension. No ready migration path is described in the materials.
The biggest winners, apparently, are teams whose project foundation is two-dimensional: casual browser games, playable ads, interactive landing pages and interfaces with individual 3D elements. They no longer need to keep a second renderer in the project and synchronize it with the 2D layer. For projects that need a full-fledged 3D scene with a minimum of 2D, the advantages are less obvious: the developers provide no comparisons with major web 3D engines.
The main risk follows from the status itself: the API may still change before 1.0, and code written now may have to be revised. It is separately worth checking model export from Blender and behavior on Android devices: that is exactly where the closed beta found failures, including running into WebGL2 limits on some phones.
Where would you embed a 3D view from PixiJS 3D?
- A casual browser game
- A playable ad