Unitree H1

• robotoverflow.com/en/robot-database/unitree-h1/55 values
• humanoid.press/database/H1-Unitree/47 values
• aparobot.com/robots/unitree-h146 values
• originofbots.com/robot/unitree-h1-by-unitree-robotics-details-specifications-rating46 values
• unitree.com/h142 values
• unitree.com/cn/h138 values
• originofbots.com/robot/unitree-h1-2-by-unitree-robotics-details-specifications-rating34 values
• robotsatlas.com/robots/unitree-h1-231 values
• humanoid-robots.io/robot/h1-by-unitree-robotics27 values
• roboatlas.ai/en-US/products/unitree-h1/h1-227 values
• humanoidapplications.com/robot/unitree-h1-h1-2/26 values
• robotsatlas.com/robots/unitree-h126 values
• humanoid.guide/product/h1-2/24 values
• robozaps.com/products/unitree-h123 values
• roboatlas.ai/en-US/products/unitree-h122 values
• biorobot.ai/en/robot/unitree-h1-219 values
• biorobot.ai/en/robot/unitree-h117 values
• humanoid-world.com/roboter/unitree-h1-2/15 values
• robotico.market/unitree/h113 values
• guijicankao.com/products/h112 values
• humanoidrecord.com/robots/unitree-h1/11 values
• humanoidmetric.com/robot/unitree-h111 values
• humanoidindex.org/robots/h111 values
• github.com/unitreerobotics9 values
• humanoid-world.com/roboter/unitree-h1/5 values
• guijicankao.com/products/unitree-h1-25 values
• unitree.com/app/h15 values
• humanoidroster.com/robots/h14 values
• unitree.com/cn/terms2 values
• unitree.com/cn/download2 values
• shop.unitree.com/products/unitree-h11 value
• humanoidmetric.com/robot/unitree-h1-21 value
• unitree.com/cn/about1 value
• support.unitree.com/main/en1 value

A value below no longer shows on the page — it was superseded, or withdrawn after review. Kept here, not deleted, with the reason it was withdrawn.

• Rated payload: 7 kg2026-09-27

  Unitree states this as an ARM load, not the robot's payload: www.unitree.com/h1 prints the row "Arm normal load" / "Peak: About 21Kg; Rated: About 7Kg" (Chinese: 手臂常规负载 / 峰值：约21Kg；额定：约7Kg), and both figures are already stored correctly under loadPerArmKg from that same vendor page. Each value withdrawn here republishes one of them as the whole robot's rated payload: roboatlas writes "Rated 7 kg / peak 21 kg per arm" on the same page as its own "21 kg General Payload"; biorobot.ai calls its 21 kg a "rated arm payload"; robotoverflow calls its 7 kg "a nominal payload of 7 kg per arm" and adds that "the base H1 has no rated arm payload"; humanoid.guide prints a bare "Strength [kg] 21" cell that names no subject at all. This field is the rated payload of the WHOLE robot, and its registry row excludes both a peak load and a per-arm value.

• Rated payload: 21 kg2026-09-27

  Unitree states this as an ARM load, not the robot's payload: www.unitree.com/h1 prints the row "Arm normal load" / "Peak: About 21Kg; Rated: About 7Kg" (Chinese: 手臂常规负载 / 峰值：约21Kg；额定：约7Kg), and both figures are already stored correctly under loadPerArmKg from that same vendor page. Each value withdrawn here republishes one of them as the whole robot's rated payload: roboatlas writes "Rated 7 kg / peak 21 kg per arm" on the same page as its own "21 kg General Payload"; biorobot.ai calls its 21 kg a "rated arm payload"; robotoverflow calls its 7 kg "a nominal payload of 7 kg per arm" and adds that "the base H1 has no rated arm payload"; humanoid.guide prints a bare "Strength [kg] 21" cell that names no subject at all. This field is the rated payload of the WHOLE robot, and its registry row excludes both a peak load and a per-arm value.

• Rated payload: 21 kg2026-09-27

  Unitree states this as an ARM load, not the robot's payload: www.unitree.com/h1 prints the row "Arm normal load" / "Peak: About 21Kg; Rated: About 7Kg" (Chinese: 手臂常规负载 / 峰值：约21Kg；额定：约7Kg), and both figures are already stored correctly under loadPerArmKg from that same vendor page. Each value withdrawn here republishes one of them as the whole robot's rated payload: roboatlas writes "Rated 7 kg / peak 21 kg per arm" on the same page as its own "21 kg General Payload"; biorobot.ai calls its 21 kg a "rated arm payload"; robotoverflow calls its 7 kg "a nominal payload of 7 kg per arm" and adds that "the base H1 has no rated arm payload"; humanoid.guide prints a bare "Strength [kg] 21" cell that names no subject at all. This field is the rated payload of the WHOLE robot, and its registry row excludes both a peak load and a per-arm value.

• Rated payload: up to 21 kg2026-09-27

  Unitree states this as an ARM load, not the robot's payload: www.unitree.com/h1 prints the row "Arm normal load" / "Peak: About 21Kg; Rated: About 7Kg" (Chinese: 手臂常规负载 / 峰值：约21Kg；额定：约7Kg), and both figures are already stored correctly under loadPerArmKg from that same vendor page. Each value withdrawn here republishes one of them as the whole robot's rated payload: roboatlas writes "Rated 7 kg / peak 21 kg per arm" on the same page as its own "21 kg General Payload"; biorobot.ai calls its 21 kg a "rated arm payload"; robotoverflow calls its 7 kg "a nominal payload of 7 kg per arm" and adds that "the base H1 has no rated arm payload"; humanoid.guide prints a bare "Strength [kg] 21" cell that names no subject at all. This field is the rated payload of the WHOLE robot, and its registry row excludes both a peak load and a per-arm value.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.31 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.33 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• Walking speed: 3.3 m/s2026-09-27

  3.3 m/s is H1's MAXIMUM, not its walking speed, and the row's REJECT says so in its own words: "running / maximum / top speed, including a speed the page itself calls a record ('Moving speed of 3.3m/s(world record)' is maxSpeedMps, not walking)". Nothing is lost: 3.3 m/s is already stored under maxSpeedMps from Unitree's own page plus 12 directories, and Unitree's own "移动速度 ＜ 2m/s" (up to 2 m/s) survives here.

• SDK languages: Rust2026-09-27

  Not a language of the official SDK: GitHub's org page lists "Rust interface for unitree_sdk2 with C++ SDK2 bindings" — a third-party/wrapper repo around the C++ SDK, i.e. the row's REJECT "languages of an unrelated tool". CLAUDE.md already records RUST as a known alias hole on this exact host (it also matched "Trust center"). PYTHON and CPP survive from the vendor and two directories.

• Hand active DoF: 52026-09-27

  An OPTIONAL accessory hand's DoF, not this robot's hand DoF: robotsatlas's own sentence is "H1-2 supports OPTIONAL dexterous hands INCLUDING the Dex5-1 (5 DOF anthropomorphic) OR other ambidextrous configurations from the Unitree portfolio" — one item from a catalogue of choices, attached to no variant. The quote never says "active" either, which is the whole point of this key against handJointCount.

• Battery voltage (nominal): 67.2 V2026-09-27

  This is the MAXIMUM voltage, which the row's REJECT names word for word ("charger or max voltage"): aparobot prints the bare "67.2 V" in "a 15 Ah (0.864 kWh) battery at 67.2 V" with no "nominal" label, while Unitree's own page prints "Max Voltage 67.2V" / "最大电压67.2V" and the same number is already stored 6× under batteryMaxVoltageV. 67.2 V is also exactly 16S x 4.2 V, i.e. full charge.

• Handheld controller: Yes2026-09-27

  "Remote Control Connection" is a TUTORIAL-VIDEO TITLE, not a statement about what ships with the robot: on www.unitree.com/app/h1 it is one bullet of the "H1/H1-2 Tutorial videos" list (beside "Calibration", "Posture & Movement", "Packing"). The key's ACCEPT is "true when a handheld controller comes with it".

• Generation: second2026-09-27

  The quote is about a different robot generation than the one it is stored on: "Unitree H1-2 is the second generation of the full-size Unitree humanoid" — H1-2 is the second, so H1 (this robot) is the FIRST. scope=robot, so no variant column can rescue it.

• Payload per arm: 21 kg2026-09-27

  exclusive family "load": the same quote on the same page proves ratedLoadKg more specifically

• Designed in: China2026-09-24

  exclusive family "country": the same quote proves manufacturingCountryCodes, which the quote names more specifically — "Produced in Hangzhou, Zhejiang, China." states where it is made, not where it was designed

• Vulnerability disclosure link: https://security.unitree.com2026-09-24

  the source page is unitree.com/cn/go2/battery — the Go2 quadruped's battery page, not an H1 page; it is excluded from discovery as of 2026-09-24 and will never be re-fetched, so this statement can no longer be re-verified

• API docs link: https://support.unitree.com/main/zh2026-09-24

  the source page is unitree.com/cn/go2/battery — the Go2 quadruped's battery page, not an H1 page; it is excluded from discovery as of 2026-09-24 and will never be re-fetched, so this statement can no longer be re-verified

• Available from: 20242026-09-24

  exclusive family "eventdate": the same quote on the same page proves announcedAt more specifically

• Available from: 20232026-09-24

  exclusive family "eventdate": the same quote on the same page proves announcedAt more specifically

• Reduction ratio: 1892026-09-24

  the pinned gate no longer accepts this quote for reductionRatio

• Hand active DoF: 72026-09-24

  exclusive family "handdof": the same quote on the same page proves handJointCount more specifically

• Robot OS: Ubuntu 20.042026-09-24

  today's gate rejects this quote (text:concept-not-in-quote)

• Fall recovery: Yes2026-09-24

  today's gate rejects this quote (bool:concept-not-in-quote)

• Fall recovery: Yes2026-09-24

  today's gate rejects this quote (bool:concept-not-in-quote)

• Price from (USD): $90,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $90,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $150,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $128,9002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $150,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $90,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $112,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $66,7702026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $94,9052026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $90,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Price from (USD): $90,0002026-09-23

  audit cleanup: price-basis — 'Typical research price: ~$90,000' — 'Typical' and '~'; a street price, not a list price.

• Robot OS: N/A2026-09-23

  audit cleanup: null-marker — humanoid.guide's H1-2 spec table prints 'Operating system | N/A' in the same column style as 'Ingress protection | N/A' and 'Latency glass to action | N/A' — N/A is that directory's not-published marker, stored as the literal OS name. registry robotOs ACCEPT: 'the robot's operating system as printed'. A null marker is not an OS; UX rule 1 forbids rendering an empty field. Two real OS statements su

• Wi-Fi: Wi-Fi2026-09-23

  audit cleanup: cross-product — The quote 'Wi-Fi' matches (letters+digits) 'WIFI' inside a Go1 quadruped firmware-update guide: '连接狗的WIFI("Unitree_Go1******")' = connect to the DOG's WiFi, at 192.168.12.1:8080/update_firmware. Nothing on that page concerns H1. registry wifiStandard ACCEPT: 'Wi-Fi standard (plain WIFI only if no version)' — for THIS robot. Four WIFI statements survive from real H1 connectivity rows.

• Founded: 2,0162026-09-23

  audit cleanup: subject-mismatch — Same, from unitree.com/h1's footer 'Copyright © 2016 - 2025 Yushu Technology Co., Ltd.'. The correct-evidence twin survives (id 6ab361a141bba468e469da0e).

• IP rating: N/A2026-09-23

  audit cleanup: null-marker — In context the quote is humanoid.press's heading 'WHAT IS NOT PUBLISHED' followed by its bullet '- IP rating' (next bullets: '- Payload per arm', '- Thermal management details'). It is an explicit statement that Unitree has NOT published an IP rating, stored as the IP rating. Exact inversion of the source's meaning.

• IP rating: N/A2026-09-23

  audit cleanup: null-marker — In context the quote is humanoid.press's heading 'WHAT IS NOT PUBLISHED' followed by its bullet '- IP rating' (next bullets: '- Payload per arm', '- Thermal management details'). It is an explicit statement that Unitree has NOT published an IP rating, stored as the IP rating. Exact inversion of the source's meaning.

• Arm length: 338 mm2026-09-23

  audit cleanup: subject-mismatch — Same row on the English page (unitree.com/h1). Same reasoning.

• Arm length: 338 mm2026-09-23

  audit cleanup: subject-mismatch — Same row on the English page (unitree.com/h1). Same reasoning.

• Arm length: 338 mm2026-09-23

  audit cleanup: subject-mismatch — Same row on the English page (unitree.com/h1). Same reasoning.

• Leg length: 400 mm2026-09-23

  audit cleanup: subject-mismatch — Same row, English page.

• Leg length: 400 mm2026-09-23

  audit cleanup: subject-mismatch — Same row, English page.

• Leg length: 400 mm2026-09-23

  audit cleanup: subject-mismatch — Same row, English page.

• Peak payload: ~21 kg2026-09-23

  audit cleanup: subject-mismatch — Unitree's own two-column H1 / H1-2 table: 'Arm normal load | / | Peak: About 21Kg; Rated: About 7Kg'. Two defects: (a) registry limitingLoadKg NOT 'a value per arm … this key is the WHOLE robot (use loadPerArmKg)'; (b) the H1 column is '/', so 21 kg belongs to the H1-2 column, and the statement carries variantId=null. Close together with its CN twin T1 — otherwise the identical value stays live.

• Peak payload: ~21 kg2026-09-23

  audit cleanup: subject-mismatch — Unitree's own two-column H1 / H1-2 table: 'Arm normal load | / | Peak: About 21Kg; Rated: About 7Kg'. Two defects: (a) registry limitingLoadKg NOT 'a value per arm … this key is the WHOLE robot (use loadPerArmKg)'; (b) the H1 column is '/', so 21 kg belongs to the H1-2 column, and the statement carries variantId=null. Close together with its CN twin T1 — otherwise the identical value stays live.

• Logo: https://cdn.prod.website-files.com/67e2a642c1cc92a3140c2707/67e6e5a19082776d20e74805_Unitree%5B1%5D.svg2026-09-23

  audit cleanup: third-party-url — humanoid-robots.io's Webflow CDN copy. All three H1 logo statements are directory re-hosts, so Robot.logoUrl goes NULL for H1. Organization.logoUrl is unaffected: store.ts writes 'logoUrl: d.columns.logoUrl ?? org.logoUrl'.

• Logo: https://humanoid.guide/wp-content/uploads/2026/02/Unitree-logo-humanoid-guide.webp2026-09-23

  audit cleanup: third-party-url — humanoid-robots.io's Webflow CDN copy. All three H1 logo statements are directory re-hosts, so Robot.logoUrl goes NULL for H1. Organization.logoUrl is unaffected: store.ts writes 'logoUrl: d.columns.logoUrl ?? org.logoUrl'.

• Logo: https://cdn.prod.website-files.com/68835962f272eff6d5e9270e/6923c6cf9ad3d806d19879b5_Unitree%20Robotics.svg2026-09-23

  audit cleanup: third-party-url — humanoid-robots.io's Webflow CDN copy. All three H1 logo statements are directory re-hosts, so Robot.logoUrl goes NULL for H1. Organization.logoUrl is unaffected: store.ts writes 'logoUrl: d.columns.logoUrl ?? org.logoUrl'.