React Three Fiber is taking a major step toward next-generation browser-based 3D graphics. The project's v10.0.0-alpha.6 release, published on October 17, 2026, makes Three.js WebGPURenderer the default renderer for the upcoming major version. The change moves the React-based 3D framework toward WebGPU and Three.js Shading Language (TSL), while introducing migration considerations for developers who rely on traditional WebGL and GLSL workflows.
The update is significant because React Three Fiber is widely used to build interactive 3D experiences with React. Instead of manually managing a Three.js scene, developers can create and control 3D objects through React components, hooks and application state. By changing the default rendering architecture in v10, the project is aligning its development direction with the newer graphics capabilities being introduced across the Three.js ecosystem.
WebGPU Becomes the Default Renderer in React Three Fiber v10
One of the biggest changes in v10.0.0-alpha.6 is that the standard Canvas import now uses WebGPURenderer. In earlier alpha versions, developers could opt into the newer renderer separately. The project has now decided to make it the default for v10, describing the major-version transition as the appropriate point to move away from a WebGL-only default.
This does not mean that every application must run on a browser with native WebGPU support. The new renderer can use WebGPU where available and fall back to a WebGL 2 backend when necessary. This gives developers a route to adopt the new rendering architecture while retaining compatibility with browsers that do not yet provide WebGPU.
Custom GLSL Projects May Need a Different Import
The change has an important consequence for existing projects. Applications that depend on custom GLSL shaders, ShaderMaterial or libraries built around the traditional WebGL renderer may need to use the legacy entry point. The release notes direct developers to import Canvas from @react-three/fiber/legacy when they need to preserve the older WebGL-based workflow.
This distinction matters because the new renderer is designed around node materials and TSL rather than treating traditional GLSL workflows as its primary path. Developers who have built custom shader systems or integrated third-party graphics libraries should test their projects before upgrading. A simple package update may not be enough if their rendering code depends on older renderer-specific features.
TSL Gets a More Central Role
React Three Fiber v10 is also expanding its integration with Three.js Shading Language. TSL provides a node-based approach to creating shader logic, allowing developers to build rendering effects through a more structured system. The project is providing React-friendly hooks for managing uniforms, nodes, buffers, GPU storage and rendering pipelines.
In the alpha 6 release, the TSL-related hooks have been moved into the separate @react-three/tsl package. The new @react-three/fiber/extension entry point also provides shared functionality for libraries that need to work across different renderer configurations. These changes are intended to make the architecture easier to extend while giving developers more explicit control over GPU-related resources.
What Happens to the Old WebGL Renderer?
The traditional renderer is not being removed from the project. Developers who need the older WebGL workflow can use the @react-three/fiber/legacy entry point. This is particularly relevant for applications with existing GLSL shaders or dependencies that have not been updated for the newer renderer.
The release notes also explain that the previous @react-three/fiber/webgpu entry point is now redundant because WebGPU has become the default in the v10 alpha line. It remains available temporarily but is marked for removal in the first beta. Developers following the alpha releases should therefore pay attention to import changes as the package moves toward its beta and stable milestones.
Should Developers Upgrade Now?
Developers should treat v10.0.0-alpha.6 as a pre-release for testing and migration planning rather than an automatic upgrade recommendation for production applications. Teams using the stable v9 series can continue with their existing renderer while evaluating the new architecture in a separate branch or test project.
Before migrating, developers should review custom shader code, third-party rendering libraries, renderer-specific configuration and post-processing workflows. They should also verify browser compatibility and test performance on the actual devices their users rely on. The WebGL 2 fallback helps broaden compatibility, but it does not guarantee that every older shader or renderer integration will work without changes.
A Major Direction Change for React-Based 3D Development
React Three Fiber's move toward WebGPU is more than a renderer setting change. It signals a broader architectural direction for React-based 3D applications, with TSL, node materials and GPU resource management becoming increasingly important parts of the development workflow.
For developers starting new experimental projects, the v10 alpha provides an opportunity to explore this approach early. For production applications built around GLSL and WebGL, the legacy renderer offers a migration path while the ecosystem adapts. The next important milestone will be the progress from alpha releases toward a stable v10 version, when developers can make more confident decisions about adopting the new default.
