Glossary
What Is VoxPoser?
Last reviewed: October 2026
Short answer
VoxPoser is a published robot manipulation method (arXiv 2307.05973) from Stanford University and collaborators. A large language model writes code that calls a vision-language model to compose 3D value maps in the robot’s observation space, and a motion planner turns them into trajectories without extra training. It is third-party research; Firsthand is not affiliated.
01
What is VoxPoser, and what is a 3D value map?
VoxPoser is introduced in VoxPoser: Composable 3D Value Maps for Robotic Manipulation with Language Models (arXiv 2307.05973) by Wenlong Huang, Chen Wang, Ruohan Zhang, Yunzhu Li, Jiajun Wu and Li Fei-Fei. The project page lists Stanford University and the University of Illinois Urbana-Champaign as affiliations and CoRL 2023 (Oral) as the venue. The abstract states the aim: to synthesize robot trajectories, a dense sequence of 6-DoF end-effector waypoints, for many manipulation tasks given an open set of instructions and an open set of objects, without relying on pre-defined motion primitives.
02
Where does Firsthand fit next to VoxPoser?
Firsthand is not affiliated with the VoxPoser authors and makes no claim that any model, VoxPoser included, was trained on Firsthand data. Firsthand captures human egocentric video, not robot data: custom collection, fast and on demand, to a written spec, with depth derived from a calibrated stereo rig, 3D hand pose at 21 joints per hand and 6-DoF IMUs at 200 Hz, delivered in RLDS, LeRobot format or WebDataset under a buyer-owned commercial license. 3D value maps, voxel maps, camera calibration files, multi-view rigs, 3D labels, reward labels, success or failure labels, rollouts, planning annotations and language annotations beyond one task instruction per episode are not Firsthand deliverables.
03
How does VoxPoser work?
Per the abstract, large language models are good at inferring affordances and constraints from a free-form instruction. By using their code-writing ability, they can interact with a vision-language model to compose 3D value maps that ground that knowledge in the agent’s observation space.
The composed maps then feed a model-based planning framework that synthesizes closed-loop trajectories zero-shot, with robustness to dynamic perturbations. The paper’s example is “open the top drawer and watch out for the vase”: the drawer handle region gets high values and the area around the vase gets low values.
04
What are 3D value maps and which types exist?
The paper defines a voxel value map as a 3D grid over the robot’s observation space that guides an “entity of interest”, such as the end-effector, an object or an object part. It names five types: affordance, avoidance, end-effector velocity, end-effector rotation and gripper action maps.
The LLM fills the maps by writing Python that calls perception APIs and NumPy array operations. Per the paper, the perception stack uses the open-vocabulary detector OWL-ViT, Segment Anything and the video tracker XMEM, and the language model is GPT-4 prompted with example queries. The input is an RGB-D observation plus a language instruction.
05
How does VoxPoser turn value maps into trajectories?
The authors use simple zeroth-order optimization inside model predictive control. Only the affordance and avoidance maps drive the planner; the other maps set rotation, velocity and gripper action at each waypoint. After a 6-DoF trajectory is synthesized, the first waypoint is executed and a new trajectory is replanned at 5 Hz. Waypoints are executed by an Operational Space Controller.
Because the generated code stays the same throughout a sub-task, its output can be cached, which makes closed-loop replanning possible. The paper also shows that zero-shot trajectories can seed learning of a dynamics model from online interaction for contact-rich tasks such as doors, windows and fridges in simulation.
06
What setup and limits do the authors state?
Per the paper, the real-world setup is a Franka Emika Panda arm on a tabletop with two Azure Kinect RGB-D cameras returning observations at 20 Hz. The authors evaluate five real-world tasks and a simulated suite of 13 tasks. These are the authors’ own setups, and this page repeats none of their success rates.
The authors list four limits: VoxPoser relies on external perception modules, a general-purpose dynamics model is still needed for contact-rich tasks, the motion planner considers only end-effector trajectories, and the LLM prompts need manual engineering. The paper states an open-source implementation, linked in the sources below.
07
How does VoxPoser compare with PaLM-E, RoboBrain, GeoVLA and 3D-VLA?
The comparison table below sets VoxPoser beside four site entries. The paper cites PaLM-E in its related work and says multi-modal LLMs of that kind could be translated into VoxPoser for direct visual grounding. It does not mention RoboBrain, GeoVLA or 3D-VLA, so those rows say Not stated.
In short, VoxPoser composes value maps from LLM-written code and plans without training a new policy, while the other four entries describe trained models. This page ranks no models.
08
What data does VoxPoser need, and what does Firsthand state?
In its zero-shot form, the paper says VoxPoser needs no additional training data for each task or for the LLM. It contrasts this with robotic data that are “often of limited amount or variability”, and relies on pre-trained language and vision-language models instead.
Firsthand states human egocentric capture with stereo-derived depth, 21-joint hand pose and one task instruction per episode. Whether those streams suit VoxPoser is Not stated, and no Firsthand data is claimed to have trained or been used by VoxPoser.
09
When do you need fast, on-demand custom collection instead?
When a program needs real human egocentric demonstrations that public data does not cover. Firsthand does not build or train models. Confirm the fields on a Spec Pilot, a small fast first batch; the median from signed spec to first validated batch is 48 hours where coverage is deep, three to four weeks where thin.
10
VoxPoser at a glance, as stated in the paper and the project page
| Item | What the sources state |
|---|---|
| Paper | VoxPoser: Composable 3D Value Maps for Robotic Manipulation with Language Models (arXiv 2307.05973) |
| Venue | CoRL 2023 (Oral), per the project page |
| Core idea | An LLM writes code that composes 3D value maps via a vision-language model; a motion planner turns them into trajectories |
| Input | An RGB-D observation and a free-form language instruction |
| Output | Dense sequences of 6-DoF end-effector waypoints |
| Value map types | Affordance, avoidance, end-effector velocity, end-effector rotation, gripper action |
| Training | No additional training for the zero-shot synthesis, per the paper |
| Code | An open-source implementation is stated in the paper; linked in the sources |
| Firsthand relationship | None |
12
VoxPoser beside the PaLM-E, RoboBrain, GeoVLA and 3D-VLA entries
| Site entry | What the entry states | How VoxPoser relates (sources read) |
|---|---|---|
| PaLM-E | An embodied multimodal language model that injects images and robot state into a PaLM language model and generates text such as plans | The paper cites PaLM-E and says such multi-modal LLMs can be translated into VoxPoser for direct visual grounding |
| RoboBrain | A multimodal LLM that plans a task in steps, then predicts object affordance regions and 2D end-effector trajectories | Not stated in the sources read; both involve affordances, but VoxPoser composes 3D value maps from LLM-written code |
| GeoVLA | A point-cloud VLA framework that fuses image-language inputs with point clouds from depth maps through a diffusion action expert | Not stated in the sources read; VoxPoser plans with value maps and a motion planner, not a trained action expert |
| 3D-VLA | A 3D generative world model that predicts goal images and point clouds to guide robot control | Not stated in the sources read; VoxPoser predicts no goal images or point clouds |
13
What VoxPoser consumes beside what the Firsthand site states
| Aspect | VoxPoser (sources read) | What the Firsthand site states |
|---|---|---|
| Observation | RGB-D from two Azure Kinect cameras at 20 Hz in the authors’ real-world setup | Human egocentric video; depth derived from a calibrated stereo rig |
| Task specification | A free-form language instruction, split into sub-tasks by an LLM | One task instruction per episode |
| Hand data | Not used | 3D hand pose at 21 joints per hand |
| Value maps | Composed at run time from LLM-written code | Not a Firsthand deliverable |
| Labels | None needed for zero-shot synthesis, per the paper | Reward labels and success or failure labels are not deliverables |
14
Frequently asked questions
- What is VoxPoser?
- A published method (arXiv 2307.05973) in which a language model writes code that composes 3D value maps through a vision-language model, and a motion planner turns the maps into robot trajectories without additional training. It is third-party research.
- What are composable 3D value maps?
- Per the paper, voxel grids over the robot’s observation space that encode affordances and constraints. Types are affordance, avoidance, end-effector velocity, end-effector rotation and gripper action maps, composed by LLM-written code.
- Does VoxPoser need robot training data?
- Per the paper, not for the zero-shot synthesis: it needs no additional training data for each task or for the LLM. The authors also show optional online learning of a dynamics model for contact-rich tasks.
- Are the VoxPoser code and prompts available?
- The paper states an open-source implementation, and the project page links the authors’ materials. The GitHub repository is linked in the sources below. Check its licence before relying on it.
- Does Firsthand use VoxPoser, and can I request a custom dataset?
- Firsthand is not affiliated with the VoxPoser authors and claims no use, training or compatibility. 3D value maps, voxel maps, camera calibration files, rollouts, reward labels and success or failure labels are not Firsthand deliverables. You can request a custom dataset.
Related terms