Vision-Language-Action (VLA) Models Explained: How One Model Turns Cameras and Words Into Robot Motion
A field briefing on vision-language-action (VLA) models: how one robotics foundation model turns a camera feed and an instruction into robot motor commands.
Every few weeks another lab posts a clip of a robot folding laundry or bagging groceries on a spoken command, and the edit implies the hard part is over. It isn’t. But the architecture doing the work in most of those clips is real, it is converging across labs, and it deserves to be understood on its own terms rather than through the demo reel. That architecture is the vision-language-action model.
What is a vision-language-action (VLA) model?
A vision-language-action (VLA) model is a multimodal foundation model that takes a camera image or video of a robot’s surroundings plus a natural-language instruction, and outputs low-level robot actions directly — end-effector poses, joint commands, or discretized motor tokens that a controller can execute. One trained model maps an instruction such as “put the apple on the plate,” together with a live camera feed, onto the sequence of motor commands that accomplishes it. There is no hand-written program for “apple” or “plate.”
That is the departure worth marking. Classical robotics stacked separate, hand-engineered modules — perception, planning, motion control — and retuned them per task and per robot. A VLA collapses that pipeline into a single learned function from pixels and words to motion. The bet is that scale and pretraining buy generalization that hand-engineering never could. For how this fits into the wider shift toward machines that sense and act in the real world, see our field guide to physical AI.
How does a VLA turn a camera image and an instruction into motor commands?
Under the hood, most VLAs run in two stages. A pretrained vision-language backbone — the same class of model that captions images or answers visual questions — fuses the camera frame (itself the product of the broader robot sensor stack of cameras, depth, and proprioception) and the instruction text into a shared internal representation. An action head then decodes that representation into commands the robot can execute. The interesting engineering is in how those actions are represented, and two approaches dominate.
The first is discretization: chop each continuous action dimension into bins and treat the resulting tokens like words, predicting them autoregressively. Google DeepMind’s RT-2 pioneered this by uniformly quantizing each action dimension into 256 bins, which let the model reuse the exact machinery of a language model to “speak” actions. It is elegant, but generation is capped at the token-by-token rate.
The second is continuous trajectory generation, where a diffusion- or flow-matching “action expert” head emits a chunk of continuous motion in a single forward pass. Physical Intelligence’s π0 (pi-zero) uses flow matching and states it reaches roughly 50 Hz control — fast enough for smoother, more dexterous motion than token-by-token decoding comfortably allows.
What does “robotics foundation model” actually mean?
The phrase robotics foundation model borrows directly from the LLM playbook: instead of training a bespoke policy for each task and each robot, you pretrain one large policy on internet-scale vision-language data plus large cross-robot demonstration datasets, and expect it to generalize across tasks, objects, and even robot bodies — the way a language model generalizes across NLP tasks it was never explicitly trained on.
Keep the skepticism handy here. The analogy is aspirational at the action layer. The internet is saturated with text and images; it is not saturated with labeled robot actions. So the “foundation” in a robotics foundation model rests on far thinner action data than the phrase implies — which is exactly why data collection dominates the field.
How are VLA models trained?
The dominant recipe is imitation learning, specifically behavior cloning: collect many (image, language instruction, action) tuples and train the model to reproduce the demonstrated action given the image and the instruction. Most of those demonstrations come from humans teleoperating real robots, increasingly supplemented by simulation and egocentric human video.
Collecting that data is the bottleneck, and the field’s reference rig makes the cost concrete. Stanford’s ALOHA / Mobile ALOHA is a low-cost bimanual teleoperation platform — roughly USD 32,000 in total per the Stanford team’s own reporting, with 14-DoF arms on a mobile base producing a 16-dimensional action vector — built specifically to gather manipulation demonstrations cheaply (arXiv 2401.02117, January 2024). “Low-cost” is relative: USD 32,000 per rig, one human operator, one demonstration at a time, is nothing like scraping the web.
After large-scale pretraining, VLAs are commonly post-trained — fine-tuned on additional task-specific demonstrations, and in some cases reinforcement learning — to sharpen performance on a target robot or task. This general pattern recurs across the 2025-2026 VLA survey literature; the specifics for any single model are often thinly documented, so treat a given model’s post-training claim as provisional.
Which VLA model families matter in 2026?
The lineage is traceable and mostly public. The table below is the field’s spine; the prose after it fills in what each line contributed.
| Model / line | Organization | First announced | Distinctive trait |
|---|---|---|---|
| RT-1 | Google (Robotics at Google) | Dec 2022 | Transformer policy; tokenizes image + instruction into actions; VLA precursor |
| RT-2 | Google DeepMind | Jul 2023 | First model branded “VLA”; actions as text tokens (256 bins); 55B / 12B backbones |
| Open X-Embodiment + RT-X | DeepMind + 34 labs | Oct 2023 | 1M+ trajectories, 22 embodiments; cross-embodiment generalist |
| OpenVLA | Stanford, UC Berkeley, Google DeepMind, Toyota Research Institute | 2024 | 7B open-source; Llama-2 + DINOv2/SigLIP; LoRA-tunable |
| π0 (pi-zero) | Physical Intelligence | Oct 2024 | Flow-matching action head; ~50 Hz continuous control |
| Isaac GR00T | Nvidia | Mar 2025 | Open humanoid foundation model; dual-system (System 1/2) |
| Helix | Figure AI | Feb 2025 | Dual-system humanoid VLA; company-reported 200 Hz upper-body control |
| Gemini Robotics | Google DeepMind | Mar 2025 | Built on Gemini 2.0; on-device variant tunable with ~50 demos |
The RT lineage (Google / Google DeepMind). RT-1 (December 2022) was the precursor rather than a full VLA: a Transformer policy trained on 130,000-plus real-robot episodes spanning 700-plus tasks, collected over 17 months with a fleet of 13 Everyday Robots, reporting roughly 97% success on instructions it was trained on. RT-2 (July 2023) was the first model DeepMind explicitly branded “vision-language-action.” It co-fine-tunes a pretrained VLM on both web-scale vision-language data and robot trajectories, emitting actions as text tokens. Two variants shipped — RT-2-PaLI-X on a 55B-parameter backbone and RT-2-PaLM-E on 12B — with a smaller 5B PaLI-X built for comparison; the 55B model generalized markedly better to unseen scenarios (roughly 62-63% versus about 44% success for the 5B), while showing emergent zero-shot generalization and rudimentary step-by-step reasoning.
Open X-Embodiment (October 2023) pooled about 60 existing datasets from DeepMind and 34 academic labs into more than one million real robot trajectories across 22 robot embodiments, spanning 527 skills across 160,266 tasks. The generalist RT-1-X trained on all of it outperformed robot-specific specialist models by roughly 50% on held-out tasks — the clearest early evidence that one cross-embodiment model can beat many bespoke ones.
OpenVLA (2024) matters because it is open. It is a 7B-parameter model — a Llama-2 7B language backbone plus a fused DINOv2 + SigLIP visual encoder of about 600M parameters — trained on 970,000 episodes drawn from Open X-Embodiment, with weights and a PyTorch training pipeline released publicly and LoRA fine-tuning supported for new robots. Its headline claim is beating the far larger closed RT-2-X (55B) by 16.5 percentage points of absolute task success across 29 tasks, despite roughly 7x fewer parameters. Read that as the authors’ own benchmark figure; independent replications vary.
Nvidia Isaac GR00T is the humanoid-focused line, and it is worth its own deep dive — see our explainer on Nvidia Isaac and GR00T for the full platform picture. GR00T N1 (GTC, March 2025) was positioned as “the world’s first open humanoid robot foundation model,” built on a dual-system design: a slower VLM-based reasoning module (System 2) that plans from the instruction and scene, and a fast action module (System 1) that turns plans into continuous, real-time motor commands — framed by Nvidia as an analogue of dual-process cognition. It trains on a mix of real teleoperation, simulation, and egocentric human video plus synthetic data, and was demonstrated on humanoids including the Fourier GR-1. The line iterated fast: N1.5 (unveiled at Computex, May 2025) improved instruction-following and, per Nvidia, generated its synthetic training data in roughly 36 hours via the “GR00T-Dreams” pipeline instead of about three months of manual collection — a vendor claim, not independently confirmed. N1.6 / N1.7 (2026) followed with a new VLM backbone and roughly 20,000 hours of “EgoScale” human-video pretraining; a released nvidia/GR00T-N1.6-3B checkpoint indicates a 3B-parameter model. Nvidia has also announced GR00T N2 on a “world action model” architecture with a claimed greater-than-2x success rate over leading VLA baselines — but as of mid-2026 that is a recent, largely single-source announcement and should be treated as provisional pending independent evaluation.
The dual-system pattern is now common. Physical Intelligence’s π0 (October 2024, with a π0.5 follow-up in 2025) trained on data from 7 robot platforms and 68 tasks and demonstrated long-horizon dexterity — laundry folding, table bussing, grocery bagging. Figure AI’s Helix (February 2025) applies the same fast/slow split to full upper-body humanoid control at a company-reported 200 Hz. Google DeepMind’s Gemini Robotics family (from March 2025), built on the Gemini 2.0 backbone, added an on-device variant that Google says can be fine-tuned with as few as 50 demonstrations. Gemini Robotics 1.5 (fall 2025, arXiv 2510.03342) paired the action model with a separate embodied-reasoning model, Gemini Robotics-ER 1.5, adding a “Motion Transfer” mechanism for moving skills across robot bodies and what Google DeepMind calls “embodied thinking.” A January 2026 announcement of a Boston Dynamics partnership putting Gemini Robotics into the Atlas and Spot platforms is recent and, as of mid-2026, lower-confidence.
What are the current limits of VLA models?
This is where the demo reels quietly overpromise. The 2025-2026 survey literature converges on five hard limits.
Latency versus control frequency. Multi-billion-parameter VLM backbones are slow relative to the tens-to-hundreds of Hz that dexterous, dynamic manipulation needs. Much of the current research — layer pruning, early-exit, action chunking, and the dual-system split itself — exists specifically to close this gap.
Data scarcity and cost. Real-robot teleoperation data is expensive and slow next to internet text and images, which is why simulation, synthetic data, and human-video pretraining are used as partial substitutes. They are partial: sim-to-real and cross-embodiment transfer gaps persist.
Bounded generalization. VLAs generalize reasonably to novel objects and rephrasings within a familiar task distribution. They generalize far less well to genuinely new long-horizon tasks, contact-rich dexterous manipulation, or embodiments far from anything in training.
Safety and reliability. Multiple 2026 papers frame VLA safety — adversarial robustness, failure detection, out-of-distribution behavior — as open and actively studied, not solved. These systems lack strong formal safety guarantees and lean on empirical benchmark success rates rather than certified behavior.
Benchmark fragmentation. Almost every success-rate number above is self-reported on the authors’ own tasks and robots, which makes cross-model comparison unreliable. Standardized, independent benchmarks (RoboArena is one named effort) are only now emerging.
How big is the VLA and humanoid market, really?
Treat any single market figure with suspicion. For the same nominal year — 2025 — humanoid robot market estimates range from about USD 1.84B (Precedence Research) to USD 2.92B (MarketsandMarkets), USD 4.87-4.89B (SNS Insider / Fortune Business Insights), and USD 7.80B (Future Market Insights). That is a greater-than-fourfold spread, driven mostly by scope — hardware only versus hardware plus software and services. The honest read: directional interest is real; the dollar figure is not settled.
The operational read
VLA models are a genuine architectural shift: one model, camera and instruction in, motor commands out, pretrained rather than hand-built. The lineage from RT-1 through RT-2, Open X-Embodiment, OpenVLA, π0, and GR00T is real and largely documented. What is not yet true is the implied conclusion of the demo reels — that these systems generalize widely, run fast, and stay safe enough for open-ended deployment. As of mid-2026 they are promising, improving quickly, and still bounded by data, latency, and evaluation you should read critically. For the wider context, see our Physical & Embodied AI Foundations hub.
Frequently asked
What's the difference between a VLA model and a large language model?
An LLM maps text to text. A vision-language-action model builds on the same kind of pretrained backbone but adds a camera-image input and an action output: it maps pixels plus a natural-language instruction to low-level robot commands — end-effector poses, joint angles, or discretized motor tokens. RT-2 made the link explicit by representing actions as text-like tokens the model predicts autoregressively.
Was RT-2 the first vision-language-action model?
RT-2 (Google DeepMind, July 2023) was the first model its makers explicitly branded 'vision-language-action.' Its predecessor RT-1 (December 2022) already tokenized camera images and instructions into actions, but it was trained only on robot data, without the web-scale vision-language pretraining that defines the full VLA idea.
What is Nvidia GR00T?
GR00T (Generalist Robot 00 Technology) is Nvidia's humanoid-focused VLA family, introduced as GR00T N1 in March 2025 and positioned as an open humanoid robot foundation model. It uses a dual-system design — a slower VLM planner (System 2) and a fast action module (System 1) for real-time motor commands — and trains on teleoperation, simulation, and human video. It has iterated through N1.5 and N1.6/N1.7 with an announced N2; treat the newest versions as provisional as of mid-2026.
Are any VLA models open source?
Yes. OpenVLA (2024) released its 7B weights and PyTorch training pipeline publicly, with LoRA fine-tuning support. Nvidia has published a GR00T-N1.6-3B checkpoint, and Google DeepMind offers a Gemini Robotics On-Device variant. Fully closed, proprietary VLAs exist alongside these.
Why can't VLA models run at high control frequencies?
The vision-language backbone that gives a VLA its generalization is large — often billions of parameters — and slow relative to the tens-to-hundreds of Hz that dexterous control needs. That mismatch is why labs split models into a slow planner and a fast action module (as in GR00T and Helix) and pursue layer pruning, early-exit, and action chunking.
How is training data for VLA models collected?
Mostly by humans teleoperating real robots, one demonstration at a time, producing (image, instruction, action) tuples for behavior cloning. Stanford's ALOHA / Mobile ALOHA rig — about USD 32,000 per the team's own reporting — is a widely cited example. Simulation and egocentric human video increasingly supplement this, but real-robot data remains the expensive bottleneck.
Are VLA models reliable enough to deploy safely?
Not as a settled matter. The 2025-2026 research literature treats VLA safety — adversarial robustness, failure detection, out-of-distribution behavior — as open and actively studied. These models rely on empirical benchmark success rates rather than certified guarantees, and those benchmarks are often self-reported, so real-world reliability should be verified per deployment.