[Zero Moment Point (ZMP)] excels at ensuring quasi-static stability because it constrains the Center of Pressure (CoP) to remain strictly within the support polygon. For example, Honda's ASIMO and other flat-footed humanoids rely on ZMP-based walking to guarantee that the foot never rolls or tips, achieving a mathematically provable stability margin at the cost of slow, energetically inefficient gaits that require large feet and flat ground.
Difference
Zero Moment Point vs Capture Point for Dynamic Balance

Introduction
A technical comparison of stability criteria for bipedal locomotion, framing the trade-off between quasi-static safety and dynamic fall prevention.
[Capture Point (CP)] takes a fundamentally different approach by focusing on dynamic fall prevention. Instead of enforcing a strict CoP constraint, CP calculates the point on the ground where the robot must step to arrest its linear momentum and bring itself to a complete stop. This results in more natural, human-like locomotion that can handle significant pushes, but it abandons the continuous stability guarantee of ZMP in favor of discrete, reactive step planning.
The key trade-off: If your priority is provable, continuous stability for predictable, flat-floor environments and you can accept slower speeds, choose ZMP-based controllers. If you prioritize dynamic disturbance rejection, faster walking speeds, and locomotion on uneven terrain, choose Capture Point stepping strategies. Consider ZMP for industrial humanoids in structured settings; choose CP when your robot must navigate the real world.
Head-to-Head Feature Comparison
Direct comparison of key metrics and features for Zero Moment Point (ZMP) and Capture Point (CP) stability criteria.
| Metric | Zero Moment Point (ZMP) | Capture Point (CP) |
|---|---|---|
Max. Stable Locomotion Speed | ~0.8 m/s (Quasi-static) |
|
Terrain Assumption | Flat, rigid ground plane | Uneven, stepping stones |
Control Objective | Maintain CoP within support polygon | Drive CP to desired foothold |
Disturbance Recovery Strategy | Ankle torque / hip strategy | Step adjustment / N-step capture |
Computational Cost per Cycle | < 1 ms (QP/LP solvable) | ~5 ms (Iterative optimization) |
Flat-Footed Walking Stability | ||
Running/Gapless Motion Support | ||
Requires Pre-Planned Footsteps |
TL;DR Summary
A quick-reference guide to the core strengths and trade-offs of ZMP stability criteria versus Capture Point stepping strategies for humanoid dynamic balance.
ZMP: Guaranteed Stability on Flat Ground
Mathematically proven stability: Ensures the robot is dynamically balanced as long as the ZMP remains strictly within the support polygon. This provides a hard safety guarantee for quasi-static walking. Matters most for industrial humanoids performing precise, slow manipulation tasks on known, rigid surfaces where a fall cannot be tolerated.
ZMP: Mature, Real-Time Optimization
Predictable computational load: ZMP-based walking pattern generation is typically solved via Quadratic Programming (QP) with a well-defined preview control horizon. This allows for deterministic real-time performance on embedded hardware. Matters for safety-certified systems where execution timing must be guaranteed and validated.
ZMP: Constrained to Flat-Footed, Slow Gaits
Inherently limits agility: The ZMP criterion breaks down when the support polygon shrinks to a point (running) or vanishes entirely (jumping). It forces a flat-footed, quasi-static motion, limiting the robot's ability to recover from large pushes or traverse rough terrain. This makes it a poor fit for highly dynamic locomotion.
Capture Point: Enables Dynamic Stepping Recovery
Directly models fall prevention: The Capture Point is the point on the ground where the robot must step to bring its Center of Mass to a complete stop. This provides an actionable metric for reactive stepping, enabling robust push recovery and walking over uneven terrain. Matters for humanoids operating in unstructured, human-centric environments.
Capture Point: Supports Agile, Non-Periodic Gaits
Decouples stability from a flat foot: Unlike ZMP, the Capture Point concept naturally extends to running, jumping, and walking with a non-flat foot. It focuses on the instantaneous capturability of the state, making it the superior framework for generating highly dynamic and aperiodic maneuvers.
Capture Point: Higher Computational & Sensing Demands
Requires precise state estimation: Effective Capture Point control depends on an accurate, low-latency estimate of the Center of Mass velocity. This demands high-quality sensor fusion (e.g., Factor Graph Optimization) and more complex whole-body controllers, increasing the software complexity and computational cost compared to a simple ZMP preview controller.
Performance and Computational Benchmarks
Direct comparison of key metrics and features for dynamic balance controllers.
| Metric | Zero Moment Point (ZMP) | Capture Point (CP) |
|---|---|---|
Stability Criterion | Static/Dynamic (ZMP in support polygon) | Dynamic (CP outside support polygon triggers step) |
Suitable Gait Type | Quasi-static, flat-footed walking | Dynamic walking, running, push recovery |
Computational Cost per Cycle | ~1-5 ms (QP solver) | ~0.1-0.5 ms (Analytical) |
Requires Pre-Planned Footsteps | ||
Handles Large External Pushes | ||
Energy Efficiency Focus | High (minimizes jerk) | Moderate (prioritizes fall prevention) |
Typical Control Frequency | 200-1000 Hz | 100-500 Hz |
Zero Moment Point (ZMP): Pros and Cons
A direct comparison of Zero Moment Point (ZMP) stability criteria against Capture Point (CP) stepping strategies for humanoid balance. Use this to determine which metric aligns with your robot's locomotion style.
Guaranteed Stability for Flat-Footed Walking
Mathematically proven stability: ZMP ensures the Center of Pressure (CoP) stays strictly within the support polygon. This provides a deterministic stability guarantee for quasi-static walking on flat terrain, making it the gold standard for industrial humanoids like Honda's ASIMO where a fall is unacceptable. The constraint is explicit and verifiable in real-time.
Mature Toolchain and Real-Time Solvability
Low computational overhead: ZMP-based walking pattern generation can be solved efficiently using preview control or Linear Inverted Pendulum Model (LIPM) cart-table models. This allows for 1 kHz+ real-time control loops on embedded hardware. The extensive literature and proven implementations reduce integration risk for teams moving from simulation to hardware.
Inherently Conservative for Dynamic Motions
Restricts agility: ZMP requires the CoP to remain strictly inside the support polygon. This constraint breaks down during dynamic gaits like running or jumping where the foot is not flat on the ground. For highly dynamic locomotion, ZMP acts as an artificial limiter, preventing the natural under-actuated phases that Capture Point strategies exploit for energy efficiency and speed.
Fragile on Uneven or Unstructured Terrain
Assumes a known, flat ground plane: ZMP calculation relies on accurate force/torque sensing at the ankles and a known support polygon. On rough terrain, stairs, or deformable surfaces, the support polygon shrinks or becomes ill-defined. This leads to overly conservative or incorrect stability margins, often causing the robot to freeze or fall when a Capture Point step would have recovered balance.
When to Choose ZMP vs Capture Point
Zero Moment Point for Quasi-Static Walking
Strengths: ZMP is the gold standard for flat-footed, slow-speed locomotion. By constraining the ZMP to remain strictly within the support polygon, you mathematically guarantee stability at every instant. This makes it ideal for industrial humanoids performing precise, predictable tasks.
Verdict: Choose ZMP when your robot moves slowly on flat ground, carries heavy payloads, or requires mathematically provable stability for safety certification. It's the conservative, reliable choice.
Capture Point for Quasi-Static Walking
Weaknesses: CP is overkill for slow walking. Its predictive nature adds computational complexity without benefit when the robot's center of mass velocity is low. The stepping strategy is unnecessary when the robot isn't at risk of falling.
Verdict: Avoid CP for quasi-static tasks. The extra complexity doesn't justify the marginal safety gain.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Technical Deep Dive: Mathematical Foundations
A rigorous comparison of the mathematical underpinnings of Zero Moment Point (ZMP) and Capture Point (CP) for ensuring dynamic balance in humanoid robots. We dissect the equations, assumptions, and real-time control implications for CTOs and lead engineers.
ZMP is a point on the ground, while CP is a point on the ground projection of the Center of Mass (CoM). The Zero Moment Point is derived from the Newton-Euler equations, representing the point where the net ground reaction force's horizontal moment is zero. It's a stability condition: if the ZMP stays within the support polygon, the foot won't rotate. Capture Point, derived from the Linear Inverted Pendulum Model (LIPM), is the point on the ground where the robot must step to bring its CoM to a complete stop. It's a target for foot placement. ZMP answers 'Am I stable now?', while CP answers 'Where must I step to become stable?'.
Verdict
A data-driven comparison to help CTOs choose the right stability metric for their humanoid's locomotion strategy.
Zero Moment Point (ZMP) excels as a stability criterion for quasi-static, flat-footed walking because it provides a mathematically rigorous, real-time check against tipping. For example, Honda's ASIMO and early HRP-series robots used ZMP-based control to achieve reliable, albeit slow, locomotion with a typical walking speed of 0.5–1.0 km/h. The primary advantage is its deterministic guarantee: if the ZMP stays strictly within the support polygon, the robot's foot will not rotate about its edge. This makes it the gold standard for applications requiring absolute safety and predictability, such as navigating crowded human environments or carrying delicate payloads where any dynamic tilting is unacceptable.
Capture Point (CP) takes a fundamentally different approach by focusing on step-to-step recovery rather than continuous constraint satisfaction. Instead of preventing the center of mass from ever leaving a safe zone, CP calculates the exact point on the ground where a robot must step to arrest a fall. This results in a trade-off: CP enables highly dynamic, human-like gaits with walking speeds exceeding 3.0 km/h and robust push recovery, as demonstrated by Boston Dynamics' Atlas and the DARPA Robotics Challenge. However, it sacrifices the static guarantee of ZMP, relying instead on the controller's ability to accurately place a foot at the calculated capture point within a single step cycle.
The key trade-off: If your priority is provably safe, slow, and predictable motion on known, flat surfaces—such as for an industrial inspection humanoid—choose a ZMP-based controller. If you prioritize dynamic agility, rough-terrain traversal, and robust push recovery for a humanoid operating in unstructured environments, choose a Capture Point stepping strategy. For many modern humanoids, a hybrid approach is emerging: use ZMP for slow, precise manipulation tasks and switch to a CP-based stepping controller when external disturbances or dynamic commands are detected.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us