Glossary
What Is a Diffusion Policy in Robot Learning?
Last reviewed: October 2026
Short answer
A diffusion policy is a robot policy that generates actions by iterative denoising. Instead of outputting one action directly, it starts from random noise and, conditioned on what the robot observes, removes noise over steps to produce a sequence of future actions. The original paper frames this as a conditional denoising diffusion process on robot action space.
01
Why it matters
Diffusion is a published design for a robot policy’s action head, from the original Diffusion Policy paper to the diffusion transformer module in GR00T N1. The head turns observations into motion, so the labels attached to training data, such as wrist motion and hand pose, matter to the teams training it.
02
How Firsthand handles it
Firsthand does not train diffusion policies and does not deliver robot actions. It captures 3D hand pose, wrist trajectories, contact events and discrete action segments at recording time, in the same session as the egocentric video and depth, collected fast, on demand and to a written spec, and delivered in RLDS, LeRobot format or WebDataset with a buyer-owned commercial license.
03
What is a diffusion policy in robot learning?
The original paper (arXiv 2303.04137) represents a robot’s visuomotor policy as “a conditional denoising diffusion process.” Instead of directly outputting an action, the policy infers an action-score gradient, conditioned on visual observations, for K denoising iterations. The paper credits this with expressing multimodal action distributions, handling high-dimensional outputs such as a sequence of future actions, and stable training.
Every technical statement here comes from that paper and the GR00T N1 paper (arXiv 2503.14734), both under Sources.
04
How does a diffusion action head generate actions?
The original paper starts from Gaussian noise and runs K denoising iterations, each conditioned on the observations, until a noise-free action sequence remains. The policy predicts a block of future actions, executes part of it, then replans, which the paper calls receding horizon control.
GR00T N1 puts the idea in a transformer. A diffusion transformer processes the robot’s proprioceptive state and noised actions, cross-attends to image and text tokens, and outputs denoised motor actions. The paper reports that K = 4 inference steps worked well across all embodiments.
05
How is a diffusion policy different from flow matching and action chunking?
Diffusion describes the generative process: noise refined into actions. Flow matching is the training objective; GR00T N1 states its diffusion transformer is trained with action flow-matching and samples actions through iterative denoising. Action chunking is the output: a block of consecutive actions. GR00T N1 uses chunks of H = 16.
The terms overlap in practice and none fixes the other. This page does not rank them, and the cited passages report no ablation between them.
06
What training data does a diffusion policy need?
The original paper trains from demonstrations, with data collected by single and multiple users. It notes that its approach inherits a limit of behavior cloning, suboptimal performance with inadequate demonstration data, and that idle actions are common in teleoperation. The data is therefore observations paired with actions.
Video alone carries no actions. For human video GR00T N1 states: “in the absence of ground-truth actions, we extract learned latent actions and use them as flow-matching targets.”
07
How does egocentric human video fit diffusion-policy pretraining?
GR00T N1 organizes its training data as a pyramid. It states that human egocentric video from open datasets forms the base, described as first-person views of hand-object interactions without explicit action labels.
This page makes no claim that any dataset improves a diffusion policy. Neither cited source reports Firsthand data in training.
08
How do you request custom data for diffusion-policy training?
This site states that Firsthand captures 3D hand pose, wrist trajectories, contact events and discrete action segments, each with a start time, end time, verb and noun, at recording time in the same session as the egocentric video and depth. Collection is fast, on demand and to a written spec.
The site states a median of 48 hours to the first validated batch where coverage is deep, and three to four weeks where contributors must be recruited first, both from the signed spec. Delivery is in RLDS, LeRobot format or WebDataset under a buyer-owned commercial license. Name the labels and format you need in the spec, and build training targets on your side.
09
What does this site not state about diffusion policies?
It does not state that Firsthand trains or evaluates diffusion policies, delivers robot actions or teleoperation data, ships a diffusion-ready export, recommends denoising steps, or shows results from Firsthand data. The K = 4 and H = 16 figures belong to GR00T N1, not to Firsthand.
10
Diffusion policy, a diffusion transformer with flow matching, and direct regression, compared on attributes the cited papers state
| Attribute | Diffusion Policy (arXiv 2303.04137) | GR00T N1 action module (arXiv 2503.14734) | Direct regression (explicit policy) |
|---|---|---|---|
| How actions are produced | Starts from Gaussian noise and runs K denoising iterations conditioned on observations | Starts from random noise and iterates denoising; K = 4 inference steps with forward Euler integration | Maps observation directly to action in one forward pass, per the Diffusion Policy paper |
| Training signal | A noise-prediction network is asked to predict the noise added to a data sample | Flow-matching loss approximating the denoising vector field | A direct regression loss |
| Multimodal action distributions | Expressed, per the paper | Not stated in the passages cited | Not suitable for multimodal demonstrated behavior, per the Diffusion Policy paper |
| Network | CNN-based and time-series diffusion transformer variants | A variant of DiT that cross-attends to vision-language tokens | Not stated |
| Cost | Higher computational cost and inference latency than simpler methods such as LSTM-GMM | 63.9 ms to sample a chunk of 16 actions on an L40 GPU in bf16 | Efficient inference, one forward pass |
12
Firsthand fields and their relation to diffusion-policy training
| Firsthand field | What the site states | Diffusion-policy target export |
|---|---|---|
| 3D hand pose (hand_joints) | Per-joint 3D position of the fingers and hand, captured at recording time | Not stated |
| Wrist trajectories | The position and orientation of the wrist over time, captured at recording time | Not stated |
| Action segments (action_segments) | A discrete span with a start time, end time, verb and noun, annotated on the footage | Not stated |
| Contact events (contact_events) | When and where a hand or tool made contact with an object | Not stated |
| Robot joint or gripper commands | Not part of the stated Firsthand fields | Not delivered |
13
Claims on this page and where each comes from
| Claim | Status |
|---|---|
| Policy as a conditional denoising diffusion process; K denoising iterations; receding horizon control | Stated by the Diffusion Policy paper (arXiv 2303.04137) |
| Diffusion transformer action module; K = 4 inference steps; chunks of H = 16 | Stated by GR00T N1 (arXiv 2503.14734) |
| Human egocentric video forms the base of the data pyramid; latent actions as targets | Stated by GR00T N1 (arXiv 2503.14734) |
| Wrist trajectories, hand pose, action segments and contact events captured at recording time | Stated by this site |
| Delivery in RLDS, LeRobot format or WebDataset, buyer-owned commercial license | Stated by this site |
| Median 48 hours (deep coverage) or three to four weeks (thin) from signed spec | Stated by this site |
| Diffusion-ready export, recommended denoising steps, or improvement results | Not stated |
14
Frequently asked questions
- What is a diffusion policy in robot learning?
- A robot policy that generates actions by iterative denoising. It starts from random noise and, conditioned on observations, produces a sequence of future actions. The original paper calls it a conditional denoising diffusion process on robot action space.
- What is a diffusion action head?
- The part of a policy that generates actions by denoising. In GR00T N1 it is a diffusion transformer, the System 1 action module, which cross-attends to the vision-language model output tokens.
- What is a diffusion transformer robot policy?
- A policy whose denoising network is a transformer. The original paper proposes a time-series diffusion transformer variant, and GR00T N1 uses a variant of DiT conditioned on the denoising step.
- Is a diffusion policy the same as flow matching?
- No. Diffusion describes the denoising process; flow matching is a training objective. GR00T N1 trains its diffusion transformer with action flow-matching.
- Can a diffusion policy learn from egocentric human video?
- In the cited work, GR00T N1 places human egocentric video at the base of its training data and uses learned latent actions where ground-truth actions are missing. The original paper trains from demonstrations.
- Does Firsthand train diffusion policies or deliver robot actions?
- No. Firsthand captures 3D hand pose, wrist trajectories, contact events and discrete action segments at recording time. A buyer builds the targets and trains the policy in their own pipeline.
- How do I get a custom dataset for diffusion-policy training fast?
- Write the labels and delivery format into a skill spec. The site states a median of 48 hours to the first validated batch where coverage is deep, and three to four weeks where contributors must be recruited first, both from the signed spec.
Related terms