react-three-fiber
A React renderer for Three.js
README
@react-three/fiber
Build your scene declaratively with re-usable, self-contained components that react to state, are readily interactive and can participate in React's ecosystem.
- ```bash
- npm install three @types/three @react-three/fiber
- ```
Does it have limitations?
None. Everything that works in Threejs will work here without exception.
Is it slower than plain Threejs?
No. There is no overhead. Components render outside of React. It outperforms Threejs in scale due to Reacts scheduling abilities.
Can it keep up with frequent feature updates to Threejs?
What does it look like?
Let's make a re-usable component that has its own state, reacts to user-input and participates in the render-loop. (live demo). |
- ```jsx
- import { createRoot } from 'react-dom/client'
- import React, { useRef, useState } from 'react'
- import { Canvas, useFrame } from '@react-three/fiber'
- function Box(props) {
- // This reference gives us direct access to the THREE.Mesh object
- const ref = useRef()
- // Hold state for hovered and clicked events
- const [hovered, hover] = useState(false)
- const [clicked, click] = useState(false)
- // Subscribe this component to the render-loop, rotate the mesh every frame
- useFrame((state, delta) => (ref.current.rotation.x += 0.01))
- // Return the view, these are regular Threejs elements expressed in JSX
- return (
- <mesh
- {...props}
- ref={ref}
- scale={clicked ? 1.5 : 1}
- onClick={(event) => click(!clicked)}
- onPointerOver={(event) => hover(true)}
- onPointerOut={(event) => hover(false)}>
- <boxGeometry args={[1, 1, 1]} />
- <meshStandardMaterial color={hovered ? 'hotpink' : 'orange'} />
- </mesh>
- )
- }
- createRoot(document.getElementById('root')).render(
- <Canvas>
- <ambientLight />
- <pointLight position={[10, 10, 10]} />
- <Box position={[-1.2, 0, 0]} />
- <Box position={[1.2, 0, 0]} />
- </Canvas>,
- )
- ```
Show TypeScript example
- ```bash
- npm install @types/three
- ```
- ```tsx
- import * as THREE from 'three'
- import { createRoot } from 'react-dom/client'
- import React, { useRef, useState } from 'react'
- import { Canvas, useFrame, ThreeElements } from '@react-three/fiber'
- function Box(props: ThreeElements['mesh']) {
- const ref = useRef<THREE.Mesh>(null!)
- const [hovered, hover] = useState(false)
- const [clicked, click] = useState(false)
- useFrame((state, delta) => (ref.current.rotation.x += 0.01))
- return (
- <mesh
- {...props}
- ref={ref}
- scale={clicked ? 1.5 : 1}
- onClick={(event) => click(!clicked)}
- onPointerOver={(event) => hover(true)}
- onPointerOut={(event) => hover(false)}>
- <boxGeometry args={[1, 1, 1]} />
- <meshStandardMaterial color={hovered ? 'hotpink' : 'orange'} />
- </mesh>
- )
- }
- createRoot(document.getElementById('root') as HTMLElement).render(
- <Canvas>
- <ambientLight />
- <pointLight position={[10, 10, 10]} />
- <Box position={[-1.2, 0, 0]} />
- <Box position={[1.2, 0, 0]} />
- </Canvas>,
- )
- ```
Live demo: https://codesandbox.io/s/icy-tree-brnsm?file=/src/App.tsx
Show React Native example
This example relies on react 18 and uses expo-cli, but you can create a bare project with their template or with the react-native CLI.
- ```bash
- # Install expo-cli, this will create our app
- npm install expo-cli -g
- # Create app and cd into it
- expo init my-app
- cd my-app
- # Install dependencies
- npm install three @react-three/fiber@beta react@rc
- # Start
- expo start
- ```
Some configuration may be required to tell the Metro bundler about your assets if you use useLoader or Drei abstractions like useGLTF and useTexture:
- ```js
- // metro.config.js
- module.exports = {
- resolver: {
- sourceExts: ['js', 'jsx', 'json', 'ts', 'tsx', 'cjs'],
- assetExts: ['glb', 'png', 'jpg'],
- },
- }
- ```
- ```tsx
- import React, { useRef, useState } from 'react'
- import { Canvas, useFrame } from '@react-three/fiber/native'
- function Box(props) {
- const mesh = useRef(null)
- const [hovered, setHover] = useState(false)
- const [active, setActive] = useState(false)
- useFrame((state, delta) => (mesh.current.rotation.x += 0.01))
- return (
- <mesh
- {...props}
- ref={mesh}
- scale={active ? 1.5 : 1}
- onClick={(event) => setActive(!active)}
- onPointerOver={(event) => setHover(true)}
- onPointerOut={(event) => setHover(false)}>
- <boxGeometry args={[1, 1, 1]} />
- <meshStandardMaterial color={hovered ? 'hotpink' : 'orange'} />
- </mesh>
- )
- }
- export default function App() {
- return (
- <Canvas>
- <ambientLight />
- <pointLight position={[10, 10, 10]} />
- <Box position={[-1.2, 0, 0]} />
- <Box position={[1.2, 0, 0]} />
- </Canvas>
- )
- }
- ```
Documentation, tutorials, examples
Visit docs.pmnd.rs
First steps
You need to be versed in both React and Threejs before rushing into this. If you are unsure about React consult the official React docs, especially the section about hooks. As for Threejs, make sure you at least glance over the following links:
1. Make sure you have a basic grasp of Threejs. Keep that site open.
2. When you know what a scene is, a camera, mesh, geometry, material, fork the demo above.
3. Look up the JSX elements that you see (mesh, ambientLight, etc), _all_ threejs exports are native to three-fiber.
4. Try changing some values, scroll through our API to see what the various settings and hooks do.
Some helpful material:
- Threejs-docs and examples
- Discover Threejs, especially the Tips and Tricks chapter for best practices
- Bruno Simons Threejs Jouney, arguably the best learning resource, now includes a full R3F chapter
Ecosystem
There is a vibrant and extensive eco system around three-fiber, full of libraries, helpers and abstractions.
- [@react-three/drei](https://github.com/pmndrs/drei) – useful helpers, this is an eco system in itself
- [@react-three/gltfjsx](https://github.com/pmndrs/gltfjsx) – turns GLTFs into JSX components
- [@react-three/postprocessing](https://github.com/pmndrs/react-postprocessing) – post-processing effects
- [@react-three/flex](https://github.com/pmndrs/react-three-flex) – flexbox for react-three-fiber
- [@react-three/xr](https://github.com/pmndrs/react-xr) – VR/AR controllers and events
- [@react-three/csg](https://github.com/pmndrs/react-three-csg) – constructive solid geometry
- [@react-three/rapier](https://github.com/pmndrs/react-three-rapier) – 3D physics using Rapier
- [@react-three/cannon](https://github.com/pmndrs/use-cannon) – 3D physics using Cannon
- [@react-three/p2](https://github.com/pmndrs/use-p2) – 2D physics using P2
- [@react-three/a11y](https://github.com/pmndrs/react-three-a11y) – real a11y for your scene
- [@react-three/gpu-pathtracer](https://github.com/pmndrs/react-three-gpu-pathtracer) – realistic path tracing
- [create-r3f-app next](https://github.com/pmndrs/react-three-next) – nextjs starter
- [lamina](https://github.com/pmndrs/lamina) – layer based shader materials
- [zustand](https://github.com/pmndrs/zustand) – flux based state management
- [jotai](https://github.com/pmndrs/jotai) – atoms based state management
- [valtio](https://github.com/pmndrs/valtio) – proxy based state management
- [react-spring](https://github.com/pmndrs/react-spring) – a spring-physics-based animation library
- [framer-motion-3d](https://www.framer.com/docs/three-introduction/) – framer motion, a popular animation library
- [use-gesture](https://github.com/pmndrs/react-use-gesture) – mouse/touch gestures
- [leva](https://github.com/pmndrs/leva) – create GUI controls in seconds
- [maath](https://github.com/pmndrs/maath) – a kitchen sink for math helpers
- [miniplex](https://github.com/hmans/miniplex) – ECS (entity management system)
- [composer-suite](https://github.com/hmans/composer-suite) – composing shaders, particles, effects and game mechanics
How to contribute
If you like this project, please consider helping out. All contributions are welcome as well as donations to Opencollective, or in cryptoBTC: 36fuguTPxGCNnYZSRdgdh6Ea94brCAjMbH, ETH: 0x6E3f79Ea1d0dcedeb33D3fC6c34d2B1f156F2682.
Backers
Thank you to all our backers! 🙏
Contributors
This project exists thanks to all the people who contribute.