Air-cooled vs liquid-cooled is a per-SKU form-factor fact, not an architecture fact: H100 PCIe is dual-slot air-cooled, H100 SXM is a bare module
Fields
supply/h100-pcie-air-cooled-vs-sxm-liquidNotes
THIS RECORD EXISTS TO KILL A COMMON ERROR IN POWER-DENSITY PLANNING: THE MENTAL MODEL THAT 'HOPPER IS AIR-COOLED AND BLACKWELL IS LIQUID-COOLED' IS WRONG AT THE PART LEVEL. NVIDIA's H100 datasheet form-factor row reads, verbatim and side by side: 'SXM' for H100 SXM and 'PCIe dual-slot air-cooled' for H100 PCIe. The word 'air-cooled' is attached to a specific SKU's physical form factor, in the same row as its Max TDP of 350 W, not to the Hopper architecture as a whole. So: H100 PCIe at 350 W IS air-cooled and goes in a conventional server in a conventional colo with no liquid anywhere. H100 SXM at 700 W is a bare module with no cooler, normally deployed in an HGX baseboard or DGX system, which is itself air-cooled at the node level - see supply/dgx-h100-h200-10kw-air-cooled-node, which documents a 10.2 kW max air-cooled 8-GPU node with 1105 CFM of front-to-back airflow. The H100 NVL sits between the two, typically shipped as a PCIe card with a factory cooler. THE CONSEQUENCE FOR ANY POWER-DENSITY DECISION: you cannot ask 'is this chip air-cooled or liquid-cooled'. You have to ask what the specific SKU's form factor and TDP are, then what the host chassis is, then what the facility is. A 350 W air-cooled H100 PCIe and a 700 W SXM H100 are both 'Hopper', differ by 2x in power, and can have completely different facility requirements. ALSO WORTH FLAGGING FOR POWER SIZING: NVIDIA's HGX H100/H200 datasheet publishes NO TDP and NO rack power figure at all - only the Hopper SXM datasheet gives 700 W - so anyone power-sizing an HGX baseboard must derive it from the SXM datasheet and mark it as derived rather than vendor-stated. That asymmetry between generations is itself a signal: every Blackwell platform datasheet publishes Max TDP per GPU, while the Hopper HGX datasheet publishes none, because Blackwell customers had to spec for facility integration from the start.
EXPORT CONTROL (2026-10-04, mechanism-level; sources spl-eccn-3a090-ccl, spl-bis-2026-01-advanced-computing-case-by-case): this record compares the AIR-COOLED PCIe form factor against the liquid-cooled SXM module, and the two are NOT equivalent under export control - which is the procurement point of the comparison. The PCIe H100 is the same die as the SXM part, but export status attaches to the CONTROLLABLE item, so the two ship under different ECCN treatment and different licensing analysis; a buyer cannot assume a PCIe card inherits the SXM module's clearance or vice versa. Both are 3A090-class, so the three-layer mechanism applies: US export licence (case-by-case for TPP < 21,000 and DRAM bandwidth < 6,500 GB/s parts per 91 FR 1684), the 742.6(a)(6)(iii)(A) end-user/ultimate-parent test that reaches entities outside D:5, and the surviving presumption of denial on reexports and on D:5/Macau-headquartered or -parented buyers. Recorded true for the controlled datacenter parts; the NVL variant is likewise controlled as an integrated system.
LEAD TIME: null - and for this record that is the WRONG QUESTION, which is the point worth recording. This record measures a build constraint that is not the accelerator supply chain: the lead time for a 120 kW liquid-cooled rack is set by construction, electrical service, and CDU/manifold plumbing, not by GPU allocation. Its own notes already make this argument for the colo case, so this entry only fixes the boundary: do not read a GPU lead time into a facility lead time, and do not read a facility lead time into a GPU lead time. No vendor publishes a weeks figure for either, so both stay null - probe log in source spl-negative-no-oem-publishes-lead-time. Where a real published horizon exists for the supply side it is on the accelerator record (NVIDIA's $95.2bn purchase and supply/capacity obligations substantially payable through FY2027, source spl-nvda-10k-fy2026-supply-commitments).