ozone-fiber

📣 @react-three/rapier v2 has been released, which adds support for @react-three/fiber v9 and react v19. If you are using react v18, you will need to use @react-three/rapier v1 and @react-three/fiber v8.

For contributions, please read the 🪧 Contribution Guide.


For available APIs, see 🧩 API Docs

---

react-three/rapier (or r3/rapier) is a wrapper library around the Rapier (https://rapier.rs/docs/user_guides/javascript) WASM-based physics engine, designed to slot seamlessly into a react-three/fiber pipeline.

The goal of this library to is to provide a fast physics engine with minimal friction and small, straight forward API.

Basic Usage

``tsx
import { Box, Torus } from "@react-three/drei";
import { Canvas } from "@react-three/fiber";
import { Physics, RigidBody, CuboidCollider } from "@react-three/rapier";

const App = () => {
return (











);
};
`

---




📝 Readme note

Below follows a guide on core concepts for react-three/rapier.
For full API outline and documentation, see 🧩 API Docs.

---




Readme Topics

- The Physics Component
- The RigidBody Component
- Automatic Colliders
- Collider Components
- 🖼 Collider Examples
- Instanced Meshes
- Debug
- Moving things around, and applying forces
- Collision Events
- Configuring collision and solver groups
- Contact force events
- Sensors
- 🖼 Sensors Example
- Configuring Time Step Size
- Joints
- Fixed Joint
- Spherical Joint
- Revolute Joint
- Prismatic Joint
- Rope Joint
- Spring Joint
- 🖼 Joints Example
- Advanced hooks usage
- Physics Hooks (Collision Filtering)
- Manual stepping
- On-demand rendering
- Snapshots

---

The Physics Component

The component is the root component of your physics world. It is responsible for creating the physics world and managing the simulation. It relies on lazily initiating Rapier and needs to be wrapped in .

🧩 See PhysicsProps docs for available props.

`tsx
const Scene = () => {
return (



...



);
};
`

The RigidBody Component

The component is used to add a mesh into the physics world. You use it by wrapping one or more meshes and setting desired props. By default, this will automatically generate Colliders based on the shape of the wrapped meshes (see Automatic colliders).

🧩 See RigidBodyProps docs for available props.

`tsx
const RigidBodyMesh = () => (



);
`

Automatic Colliders

RigidBodies generate automatic colliders by default for all meshes that it contains. You can control the default collider by setting the colliders prop on a , or change it globally by setting colliders on . Setting colliders={false} disables auto-generation.

Supported values:

- "cuboid", creates a CuboidCollider based on the bounding box of the mesh
- "ball", creates a SphereCollider based on the bounding sphere of the mesh
- "trimesh", creates a TrimeshCollider based on the mesh's geometry
- "hull", creates a ConvexHullCollider based on the mesh's geometry
- false, disables auto-generation

Generate ConvexHull colliders for all meshes in a RigidBody by default:

`tsx
const Scene = () => (








);
`

Turn off automatic collider generation globally, but apply auto generation locally:

`tsx
const Scene = () => (

{/ Use an automatic CuboidCollider for all meshes inside this RigidBody /}




{/ Use an automatic BallCollider for all meshes inside this RigidBody /}




);
`

Collider Components

You can also create Colliders by hand and add them to a RigidBody to create compound colliders. This is useful for creating more complex shapes, for creating simplified shapes for performance reasons, or for detecting collisions on specific parts of a mesh.

🧩 See ColliderProps docs for available props.

`tsx
const Scene = () => (<>
{/ Make a compound shape with two custom BallColliders /}






{/* Make a compound shape with two custom BallColliders, an automatic BallCollider,
Two automatic MeshColliders, based on two different shape types */}












<>)
`

RigidBodies work inside other transformed objects as well. Simulation runs in world space and is transformed to the objects local space, so that things act as you'd expect.

> Note It's always best to create RigidBodies where the center of gravity is in the center of the object, otherwise you might get some unexpected behavior during simulation interpolation.

`tsx
import { Box } from "@react-three/drei";
import { RigidBody, CuboidCollider } from "@react-three/rapier";

const Scene = () => (






);
`

If part of our meshes are invisible and you want to include them in the collider creation, use the includeInvisible flag.

`tsx





`

$3




Instanced Meshes

Instanced meshes can also be used and have automatic colliders generated from their mesh.

By wrapping exactly one Three.InstancedMesh in , each instance will be attached to an individual RigidBody.

🧩 See InstancedRigidBodiesProps docs for available props.

`tsx
import { InstancedRigidBodies, RapierRigidBody } from "@react-three/rapier";

const COUNT = 1000;

const Scene = () => {
const rigidBodies = useRef(null);

useEffect(() => {
if (!rigidBodies.current) {
return;
}

// You can access individual instanced by their index
rigidBodies.current[40].applyImpulse({ x: 0, y: 10, z: 0 }, true);
rigidBodies.current.at(100).applyImpulse({ x: 0, y: 10, z: 0 }, true);

// Or update all instances
rigidBodies.current.forEach((api) => {
api.applyImpulse({ x: 0, y: 10, z: 0 }, true);
});
}, []);

// We can set the initial positions, and rotations, and scales, of
// the instances by providing an array of InstancedRigidBodyProps
// which is the same as RigidBodyProps, but with an additional "key" prop.
const instances = useMemo(() => {
const instances: InstancedRigidBodyProps[] = [];

for (let i = 0; i < COUNT; i++) {
instances.push({
key: "instance_" + Math.random(),
position: [Math.random() 10, Math.random() 10, Math.random() * 10],
rotation: [Math.random(), Math.random(), Math.random()]
});
}

return instances;
}, []);

return (
ref={rigidBodies}
instances={instances}
colliders="ball"
>


);
};
`

We can also create compound shapes for instanced meshes by providing an array of Colliders in the colliderNodes prop.

`tsx
import {
InstancedRigidBodies,
BoxCollider,
SphereCollider
} from "@react-three/rapier";
const COUNT = 500;

const Scene = () => {
const instances = useMemo(() => {
const instances: InstancedRigidBodyProps[] = [];

for (let i = 0; i < COUNT; i++) {
instances.push({
key: "instance_" + Math.random(),
position: [Math.random() 10, Math.random() 10, Math.random() * 10],
rotation: [Math.random(), Math.random(), Math.random()]
});
}

return instances;
}, []);

return (
instances={instances}
colliders="ball"
colliderNodes={[
,

]}
>


);
};
`

Debug

Set the debug prop on to see live representations of all colliders in a scene, using the live debug buffer from the physics engine.

`tsx
import { Box, Sphere } from "@react-three/drei";
import { RigidBody } from "@react-three/rapier";

const Scene = () => {
return (








);
};
`

Moving things around, and applying forces

You can access the instance for a RigidBody by storing its ref. This allows you to perform any operation on the underlying physics object directly.

r3/rapier exposes a RapierRigidBody and RapierCollider as aliases for rapiers underlying base objects.

For all available methods, see the Rapier docs.

`tsx
import { RigidBody, RapierRigidBody } from "@react-three/rapier";

const Scene = () => {
const rigidBody = useRef(null);

useEffect(() => {
if (rigidBody.current) {
// A one-off "push"
rigidBody.current.applyImpulse({ x: 0, y: 10, z: 0 }, true);

// A continuous force
rigidBody.current.addForce({ x: 0, y: 10, z: 0 }, true);

// A one-off torque rotation
rigidBody.current.applyTorqueImpulse({ x: 0, y: 10, z: 0 }, true);

// A continuous torque
rigidBody.current.addTorque({ x: 0, y: 10, z: 0 }, true);
}
}, []);

return (






);
};
`

Rapier's API returns quaternions and vectors that are not compatible with Three.js, r3/rapier therefore exposes some helper functions (vec3, quat, euler) for quick type conversions. These helper functions can also be used as a shorthand for creating new objects.

`tsx
import { RapierRigidBody, quat, vec3, euler } from "@react-three/rapier";

const Scene = () => {
const rigidBody = useRef(null);

useEffect(() => {
if (rigidBody.current) {
const position = vec3(rigidBody.current.translation());
const quaternion = quat(rigidBody.current.rotation());
const eulerRot = euler().setFromQuaternion(
quat(rigidBody.current.rotation())
);

// While Rapier's return types need conversion, setting values can be done directly with Three.js types
rigidBody.current.setTranslation(position, true);
rigidBody.current.setRotation(quaternion, true);
rigidBody.current.setAngvel({ x: 0, y: 2, z: 0 }, true);
}
}, []);

return (






);
};
`

Collision Events

You can subscribe to collision and state events on a RigidBody:

🧩 See onCollisionEnter / onCollisionExit docs for more information.

`tsx
const RigidBottle = () => {
const [isAsleep, setIsAsleep] = useState(false);

return (
colliders="hull"
onSleep={() => setIsAsleep(true)}
onWake={() => setIsAsleep(false)}
name="Bally McBallFace"
onCollisionEnter={({ manifold, target, other }) => {
console.log(
"Collision at world position ",
manifold.solverContactPoint(0)
);

if (other.rigidBodyObject) {
console.log(
// this rigid body's Object3D
target.rigidBodyObject.name,
" collided with ",
// the other rigid body's Object3D
other.rigidBodyObject.name
);
}
}}
>




);
};
`

You may also subscribe to collision events on individual Colliders:

`tsx
onCollisionEnter={(payload) => {
/ ... /
}}
onCollisionExit={(payload) => {
/ ... /
}}
/>
`

The payload object for all collision callbacks contains the following properties:

- target
CollisionTarget of the object firing the event.
- other
CollisionTarget of the other object involved in the event.
- manifold (onCollisionEnter only)
The contact manifold generated by the collision event.
- flipped (onCollisionEnter only)
true if the data in the manifold is flipped.

A CollisionTarget is an object containing references to objects involved in a collision event. It has the following properties:

- rigidBody (if exists): Rapier.RigidBody
- rigidBodyObject (if exists): Three.Object3D
- collider: Rapier.Collider
- colliderObject: Three.Object3D

$3

Both as well as all collider components allow you to configure collisionsGroups and solverGroups properties that configures which groups the colliders are in, and what other groups they should interact with in potential collision and solving events (you will find more details on this in the Rapier documentation.)

Since these are set as bitmasks and bitmasks can get a bit unwieldy to generate, this library provides a helper called interactionGroups that can be used to generate bitmasks from numbers and arrays of groups, where groups are identified using numbers from 0 to 15.

The first argument is the group, or an array of groups, that the collider is a member of; the second argument is the group, or an array of groups, that the collider should interact with.

Here the collider is in group 0, and interacts with colliders from groups 0, 1 and 2:

`tsx

`

This collider is in multiple groups, but only interacts with colliders from a single group:

`tsx

`

When the second argument is omitted, the collider will interact with all groups:

`tsx

`

> Note Please remember that in Rapier, for a collision (or solving) event to occur, both colliders involved in the event must match the related interaction groups -- a one-way match will be ignored.

> Note By default, colliders are members of all groups, and will interact with all other groups.

Contact force events

Contact force events are triggered on and any collider components when two objects collider.

`tsx
colliders="ball"
onContactForce={(payload) => {
console.log(The total force generated was: ${payload.totalForce});
}}
>




`

The payload for the contact force event contains the following properties:

- target
CollisionTarget of the object firing the event
- other
CollisionTarget of the other object involved in the event
- totalForce
The sum of all the forces between the two colliders
- totalForceMagnitude
The sum of the magnitudes of each force between the two colliders
- maxForceDirection
The magnitude of the largest force at a contact point of this contact pair
- maxForceMagnitude
The world-space (unit) direction of the force with strongest magnitude

More information about each property can be found in the rapier TempContactForceEvent API documentation.

You can also add the onContactForce event to any collider.

`tsx
onContactForce={(payload) => {
/ ... /
}}
/>
`

Sensors

A Collider can be set to be a sensor, which means that it will not generate any contact points, and will not be affected by forces. This is useful for detecting when a collider enters or leaves another collider, without affecting the other collider.

To detect when a collider enters or leaves another collider, you can use the onIntersectionEnter and onIntersectionExit events on the collider.

🧩 See onIntersectionEnter / onIntersectionExit docs for more information.

`tsx



args={[5, 5, 1]}
sensor
onIntersectionEnter={() => console.log("Goal!")}
/>

`

$3

Configuring Time Step Size

By default, will simulate the physics world at a fixed rate of 60 frames per second. This can be changed by setting the timeStep prop on :

`tsx
{/ ... /}
`

The timeStep prop may also be set to "vary", which will cause the simulation's time step to adjust to every frame's frame delta:

`tsx
{/ ... /}
`

> Note This is useful for games that run at variable frame rates, but may cause instability in the simulation. It also prevents the physics simulation from being fully deterministic. Please use with care!

Joints

Joints can be made between two RigidBodies to provide a way to restrict a motion of a body in relation to another.

> Read more about joints in Rapier: https://rapier.rs/docs/user_guides/javascript/joints

Joints are available in r3/rapier as hooks.

There are 6 different joint types available:

- Fixed (two bodies are fixed together)
- Spherical (two bodies are connected by a ball and socket, for things like arms or chains)
- Revolute (two bodies are connected by a hinge, for things like doors or wheels)
- Prismatic (two bodies are connected by a sliding joint, for things like pistons or sliders)
- Rope (limits the max distance between two bodies)
- Spring (applies a force proportional to the distance between two bodies)

Each joint hook returns a RefObject containing the raw reference to the joint instance.

`tsx
const WheelJoint = ({ bodyA, bodyB }) => {
const joint = useRevoluteJoint(bodyA, bodyB, [
[0, 0, 0],
[0, 0, 0],
[0, 0, 0]
]);

useFrame(() => {
if (joint.current) {
joint.current.configureMotorVelocity(10, 2);
}
}, []);

return null;
};
`

$3

A fixed joint ensures that two rigid-bodies don't move relative to each other. Fixed joints are characterized by one local frame (represented by an isometry) on each rigid-body. The fixed-joint makes these frames coincide in world-space.

🧩 See FixedJoint docs for available options.

`tsx
const JointedThing = () => {
const bodyA = useRef(null);
const bodyB = useRef(null);

const joint = useFixedJoint(bodyA, bodyB, [
// Position of the joint in bodyA's local space
[0, 0, 0],
// Orientation of the joint in bodyA's local space
[0, 0, 0, 1],
// Position of the joint in bodyB's local space
[0, 0, 0],
// Orientation of the joint in bodyB's local space
[0, 0, 0, 1]
]);

return (








);
};
`

$3

The spherical joint ensures that two points on the local-spaces of two rigid-bodies always coincide (it prevents any relative translational motion at this points).

🧩 See SphericalJoint docs for available options.

`tsx
const JointedThing = () => {
const bodyA = useRef(null);
const bodyB = useRef(null);

const joint = useSphericalJoint(bodyA, bodyB, [
// Position of the joint in bodyA's local space
[0, 0, 0],
// Position of the joint in bodyB's local space
[0, 0, 0]
]);

return (








);
};
`

$3

The revolute joint prevents any relative movement between two rigid-bodies, except for relative rotations along one axis. This is typically used to simulate wheels, fans, etc.

🧩 See RevoluteJoint docs for available options.

`tsx
const JointedThing = () => {
const bodyA = useRef(null);
const bodyB = useRef(null);

const joint = useRevoluteJoint(bodyA, bodyB, [
// Position of the joint in bodyA's local space
[0, 0, 0],
// Position of the joint in bodyB's local space
[0, 0, 0],
// Axis of the joint, expressed in the local-space of
// the rigid-bodies it is attached to. Cannot be [0,0,0].
[0, 1, 0]
]);

return (








);
};
`

$3

The prismatic joint prevents any relative movement between two rigid-bodies, except for relative translations along one axis.

🧩 See PrismaticJoint docs for available options.

`tsx
const JointedThing = () => {
const bodyA = useRef(null);
const bodyB = useRef(null);

const joint = usePrismaticJoint(bodyA, bodyB, [
// Position of the joint in bodyA's local space
[0, 0, 0],
// Position of the joint in bodyB's local space
[0, 0, 0],
// Axis of the joint, expressed in the local-space of
// the rigid-bodies it is attached to. Cannot be [0,0,0].
[0, 1, 0]
]);

return (








);
};
`

$3

The rope joint limits the max distance between two bodies.

🧩 See RopeJoint docs for available options.

`tsx
const JointedThing = () => {
const bodyA = useRef(null);
const bodyB = useRef(null);

const joint = useRopeJoint(bodyA, bodyB, [
// Position of the joint in bodyA's local space
[0, 0, 0],
// Position of the joint in bodyB's local space
[0, 0, 0],
// The max distance between the two bodies / length of the rope
1
]);

return (








);
};
`

$3

The spring joint applies a force proportional to the distance between two bodies.

🧩 See SpringJoint docs for available options.

`tsx
const JointedThing = () => {
const bodyA = useRef(null);
const bodyB = useRef(null);

const mass = 1;
const springRestLength = 0;
const stiffness = 1.0e3;
const criticalDamping = 2.0 Math.sqrt(stiffness mass);
const dampingRatio = props.jointNum / (props.total / 2);
const damping = dampingRatio * criticalDamping;

const joint = useSpringJoint(bodyA, bodyB, [
// Position of the joint in bodyA's local space
[0, 0, 0],
// Position of the joint in bodyB's local space
[0, 0, 0],
// Spring rest length
springRestLength,
// Spring stiffness
stiffness,
// Spring damping
damping
]);

return (








);
};
`

$3

Advanced hooks usage

Advanced users might need granular access to the physics loop and direct access to the world instance. This can be done by using the following hooks:

- useRapier
Gives you access to the world, direct access to rapier, and more.
🧩 See useRapier docs for more information.
- useBeforePhysicsStep
Allows you to run code before the physics simulation is stepped.
🧩 See useBeforePhysicsStep docs for more information.
- useAfterPhysicsStep
Allows you to run code after the physics simulation is stepped.
🧩 See useAfterPhysicsStep docs for more information.

$3

You can implement advanced collision behaviors like one-way platforms by using physics hooks. These hooks allow you to filter collision and intersection pairs during the physics step.

r3/rapier provides two hooks for collision filtering:
- useFilterContactPair - Filter collision pairs and control solver behavior
- useFilterIntersectionPair - Filter intersection pairs for sensors

#### Filter Contact Pairs

useFilterContactPair allows you to control how collisions are processed. The callback should return:
- SolverFlags.COMPUTE_IMPULSE (1) - Process the collision normally
- SolverFlags.EMPTY (0) - Ignore the collision
- null - Let other hooks decide, or use default behavior

#### Filter Intersection Pairs

useFilterIntersectionPair controls which sensor intersections are detected. The callback should return:
- true - Allow the intersection to be detected
- false - Block the intersection

If multiple hooks are registered:
- For contact pairs, the first hook that returns non-null wins
- For intersection pairs, the first hook that returns false blocks the intersection

Important: To avoid Rust aliasing errors, you cannot access rigid body properties (like translation() or linvel()) directly during the physics step. Instead, cache the needed state before the step using useBeforePhysicsStep.

🧩 See useFilterContactPair docs and useFilterIntersectionPair docs for more information.

`tsx
import {
useRapier,
useBeforePhysicsStep,
useFilterContactPair
} from "@react-three/rapier";

const OneWayPlatform = () => {
const platformRef = useRef(null);
const ballRef = useRef(null);
const colliderRef = useRef(null);

// Cache for storing body states before physics step
const bodyStateCache = useRef(new Map());

const { rapier } = useRapier();

// Cache body states BEFORE the physics step
useBeforePhysicsStep(() => {
if (platformRef.current && ballRef.current) {
const ballPos = ballRef.current.translation();
const ballVel = ballRef.current.linvel();

bodyStateCache.current.set(ballRef.current.handle, {
position: ballPos,
velocity: ballVel
});
}
});

// Filter collisions using cached data
useFilterContactPair((collider1, collider2, body1, body2) => {
const ballState = bodyStateCache.current.get(body1);
if (!ballState) return null; // Let other hooks or default behavior handle it

// Allow collision only if ball is moving down and above platform
if (ballState.velocity.y < 0 && ballState.position.y > 0) {
return rapier.SolverFlags.COMPUTE_IMPULSE; // Process collision
}
return rapier.SolverFlags.EMPTY; // Ignore collision
});

useEffect(() => {
// Enable active hooks on the collider (required for filtering)
colliderRef.current?.setActiveHooks(rapier.ActiveHooks.FILTER_CONTACT_PAIRS);
}, []);

return (
<>







);
};
`

$3

You can manually step the physics simulation by calling the step method from the useRapier hook.

`tsx
const { step } = useRapier();

step(1 / 60);
`

$3

By default @react-three/rapier will update the physics simulation when a frame renders. This is fine for most cases, but if you want to only render the scene when things have changed, you need to run the physics simulation independently from the render loop.

- See https://docs.pmnd.rs/react-three-fiber/advanced/scaling-performance#on-demand-rendering, for info on on-demand rendering in @react-tree/fiber.

Setting will make the physics simulation run in it's own requestAnimationFrame loop, and call invalidate on the canvas only when there are active (moving) bodies.

`tsx

...

`

Snapshots


The world can be serialized as a Uint8Array using world.takeSnapshot(), see Rapier's docs on Serialization for more info.

The snapshot can be used to construct a new world. In r3/rapier, you need to replace the world with this snapshot.

> [!NOTE]
> This only works if the snapshotted world is identical to the restored one. If objects, or the order of creation of objects vary, expect RigidBodies to scramble.

`tsx
import { useRapier } from '@react-three/rapier';

const SnapshottingComponent = () => {
const { world, setWorld, rapier } = useRapier();
const worldSnapshot = useRef();

// Store the snapshot
const takeSnapshot = () => {
const snapshot = world.takeSnapshot()
worldSnapshot.current = snapshot
}

// Create a new World from the snapshot, and replace the current one
const restoreSnapshot = () => {
setWorld(rapier.World.restoreSnapshot(worldSnapshot.current))
}

return <>
...
...
...
...
...

}
``