The Definitive Guide toAI Data Centers
Ask the GuideAboutAccount

Chapter 5.4

Direct-to-Chip Liquid Cooling (DLC) — Architecture, Fluid & Thermal Design

DLC is the design basis where the named equipment requires liquid capture at source; single- versus two-phase, coupling architecture, coolant, flow, delta-T, pressure drop, residual-air duty, and service/redundancy choices then set the lifetime operating and capex consequences.

POWER-BOUNDDENSITY-RAMPGOODPUT

What you'll decide here

  1. Which named single- or two-phase cold-plate system has OEM, fluid, warranty, service, safety and facility-envelope evidence for the project; reported market share does not select it.
  2. How you plumb the rack: in-rack manifolds with blind-mate/floating-tray couplings vs flexible-hose dripless quick disconnects — the serviceability-vs-reliability fork that governs every node swap for the next five years.
  3. The per-chip and per-rack thermal budget—liquid-captured heat, approved-fluid properties, selected delta-T, and pressure drop across cold plate, manifold and QDs—with flow derived from the named operating point rather than a universal ratio.
  4. Coolant chemistry—the named OEM-approved base fluid, concentration, inhibitor package, water quality, wetted-material matrix, freeze/biofouling plan and warranty consequences across the secondary loop.
  5. What deliberately stays on air (NICs, DIMMs, PSUs, optics, VRMs) and how the residual ~10–20% air load is captured — because a hall that forgets the air tail strands the very racks it cooled.
The direct-to-chip loop from cold plate to facility water: flow, ΔT, and pressure budgets, the ~115/17 kW liquid/air split, and why D2C won on capex.

By 2026 the argument about whether AI racks need liquid is over. GB300 NVL72 is the principal 2026 NVIDIA rack platform — ~132–140 kW nominal, ~155 kW peak — and 2026 halls take delivery of a GB200/GB300 blend. The best-documented published heat split is still the cited HPE GB200 NVL72 record, which assigns roughly 115 kW to liquid and 17 kW to residual air (Chapter 5.2); this chapter derives from that record and scales to the rack you name. That product-specific heat split makes direct-to-chip liquid cooling (DLC) plus residual room-air removal the supported basis; Chapter 5.1 explains the wider selection envelope. Rear-door heat exchangers and air-assisted liquid (Chapter 5.3) extend a brownfield envelope only where the named product rating, airflow or room-rejection path, water conditions, service/redundancy case, and refresh tail close. For a greenfield whose selected or roadmap rack profile requires liquid capture at source, DLC and its residual-air path belong in the design basis before steel is cut. Size that basis against VR200 NVL72 as well: NVIDIA reported it in full production in August 2026, at an analyst-estimated ~190–230 kW per rack.

Once DLC is assumed, the decisions that remain are concrete. Choose two-phase and you inherit a PFAS supply-chain and liability problem. Choose flexible-hose quick disconnects over blind-mate manifolds and you trade factory-integrated reliability for field serviceability — and a different leak-risk profile. Budget the cold-plate delta-T too tight and you over-spec the CDU and the pumps; too loose and you throttle the GPUs. Each of these forks is cheaper to see before it is poured into a slab.

Cold-plate architectures: single-phase vs two-phase

A direct-to-chip cold plate is a sealed metal block — typically copper, sometimes copper-on-aluminum — pressed onto the die package through a thermal interface material (TIM), with coolant forced through internal microchannels or skived fins directly over the hot silicon. The heat path is short and the thermal resistance low: a few hundredths of a °C per watt from junction to coolant, which is what makes 1.0–2.3 kW per GPU package tractable. The first fork is whether the coolant changes phase inside the plate.

Single-phase cold plates keep the coolant liquid throughout. A water/glycol mix enters, warms by a bounded delta-T (commonly 7–12 °C), and leaves still liquid. Heat removal scales with mass flow times specific heat times delta-T — pump harder or run a wider delta-T to carry more watts. It is mechanically simple, the fluids are benign (water-based, non-PFAS), the pressure regime is well understood, and it maps cleanly onto the CDU-and-secondary-loop architecture of Chapter 5.6. The penalty is that water has finite heat capacity, so very high heat fluxes demand high flow and therefore pump energy and pressure drop.

Two-phase cold plates exploit the latent heat of vaporization: a low-boiling-point dielectric enters as liquid, boils inside the plate, and leaves as a vapor-liquid mixture. Because latent heat dwarfs sensible heat, two-phase moves enormous heat flux at low flow and a nearly isothermal plate surface — thermodynamically the superior answer for the 1.5–2.3 kW packages on the roadmap. The catch is the working fluid. The engineered dielectrics that boil at convenient temperatures are predominantly fluorochemicals — the PFAS family — and that is now a regulatory and liability exposure rather than a footnote.

Single-phase vs two-phase direct-to-chip — the cold-plate fork
AxisSingle-phase DLCTwo-phase DLC
Heat-transfer modeSensible heat; coolant stays liquidLatent heat; coolant boils in the plate
Working fluidNamed OEM-approved water or water/glycol fluid; concentration and inhibitor package are project-specificEngineered dielectric — predominantly PFAS
Flow demandDerived from liquid heat, approved-fluid properties and selected ΔT; no universal L/min/kWMuch lower; latent heat does the work
Plate surface tempRises by the selected operating ΔT inside the named product envelopeNear-isothermal at the boiling point
Pressure regimeUse the named OEM pressure-flow curve; no portable per-plate valueTwo-phase flow instability risk; harder to control
2026 status~55% in one 2026 market estimate; not a project-selection ruleNamed pilots and vendor evidence; production adoption remains gated by OEM/warranty, fluid and service evidence
Primary riskPump energy/flow at very high fluxFluid supply chain, regulation, liability
Design bands are 2026-current practitioner figures (DCD/Schneider, OCP, Dober, SemiAnalysis). Two-phase figures are pilot/early-deployment, not mature production.

In-rack plumbing: manifolds, blind-mate, and quick disconnects

Getting coolant from the rack inlet to 72 cold plates and back, while letting a technician swap a failed tray in minutes without draining the rack, is the second major fork in DLC design. Every NVL72-class rack carries a vertical pair of manifolds (a supply and a return rail, the in-rack analogue of a busbar) running the rack height. Each compute tray taps the rails through couplings. The decision is what kind of coupling, and it trades serviceability against reliability and leak risk.

Blind-mate / floating-tray couplings are integrated into the tray and the manifold so that sliding the tray home automatically engages the fluid connection — no hose to route, no fitting to hand-torque. The 'floating' geometry absorbs the mechanical tolerance stack so the connection self-aligns. This is the factory-integration path: couplings are validated at L10/L11 integration (Chapter 5.13 on the mechanical side; rack integration in Part 7), and field service becomes a slide-out/slide-in operation. The cost is rigidity — the rack and tray geometry are co-designed and far less forgiving of field improvisation.

Flexible-hose dripless quick disconnects (UQDs) put a short hose with a dry-break coupling between the tray and the manifold. The technician physically connects two halves; the dry-break valve seals both sides on disconnect so the spill is a few drops, not a stream. This is more serviceable in the messy reality of a live hall and tolerant of tolerance stack-up, but every manual connection is a potential leak point and a human-error surface, and the hoses add pressure drop and clutter. OCP has standardized UQD form factors precisely to make these field-mateable and second-source-able.

Per-chip and per-rack thermal design

The thermal budget is governed by one conservation equation: the heat a loop carries equals mass flow times specific heat times the coolant temperature rise (Q = ṁ · cp · ΔT). Everything in DLC design is a negotiation among the three terms on the right — and against a pressure-drop ceiling that the pumps and CDU must overcome.

Flow from the heat balance. Use Q = ṁ·cp·ΔT on the liquid-captured heat. For water-like properties, 1 kW at a 10 K rise requires about 1.43 L/min; recalculate with the approved fluid at its operating temperature. For the HPE GB200 NVL72's ~115 kW liquid share, water-property illustrations are about 82 L/min at 20 K, 165 L/min at 10 K, and 236 L/min at 7 K. A Dober PG25 planning illustration of roughly 1.25–2.0 L/min/kW at 7.5–12 °C is supplier guidance, not an OCP or OEM acceptance requirement. Size the manifold and CDU from the named vendor schedule or declared-fluid calculation plus the pressure and control margin. Run a wider delta-T and you cut the flow (and pump energy) for the same watts — but you raise the return-water temperature the heat-rejection plant must handle and you push the warmest cold plates closer to the throttle line.

Wide vs. tight delta-T. A wider coolant delta-T is a gift to the facility: it means less flow, smaller pipes, lower pump energy, and warmer return water that free-cooling and heat-reuse plants love (Chapter 5.7, Chapter 5.9). For the cited QCT GB200 NVL72 reference, 45 °C maximum liquid inlet and 65 °C maximum liquid return are separate limits, not a prescribed 20 K operating rise; ASHRAE W45 describes FWS supply capability. The junction budget still binds: the delta-T you can run is bounded by the supply temperature plus the cold-plate's thermal resistance, so spend the budget on a wide delta-T at a warm inlet and the last plate in a series path may sit too warm. Design teams therefore favor parallel manifold paths so every cold plate sees near-inlet coolant, and reserve series only where pressure budget forces it.

Pressure-drop budget. Pump head is divided among the selected cold-plate pressure-flow curve (including declared fittings and quick disconnects), the in-rack manifold and headers, and the secondary loop back to the CDU. Rack-level manifold pressure drop across a 72-plate parallel circuit with headers and QDs typically runs 1.5–2.5 bar. Every fitting, every hose, every reduction in channel size buys lower thermal resistance at the price of more pressure drop — and pressure drop is pump energy, which shows up in PUE. The cold-plate designer's lever — finer microchannels for lower thermal resistance — is exactly the lever that raises pressure drop, so the per-chip design is an explicit optimization of thermal resistance against pressure drop.

~55%
reported 2026 forecast for single-phase cold-plate/direct-to-chip share; PMR's published cold-plate category is broader, and market share does not select a project architecture
~1.43 L/min/kW
guide water heat-balance at 10 K: ~1.43 L/min per kW of liquid-captured heat; recalculate for the approved fluid
2025Guide heat-balance derivation using water properties at the declared design pointregister ↗
45 °C maximum liquid inlet; 65 °C maximum liquid return (separate limits)
QCT GB200 NVL72 QoolRack reference maxima: 45 °C liquid inlet and 65 °C liquid return; separate limits, not a selected operating pair
~170–235 L/min
rack-level manifold flow for NVL72 (guide water-property heat-balance band for ~115 kW at 7–10 °C design rise; Clariant PG25 ~172–246 L/min at the same rise); CDU sized ~250–300 L/min at design pressure
Use the named OEM pressure-flow curve
per-module cold-plate pressure drop, depending on plate design and flow — no vendor-published NVL72 figure
~115 / ~17 kW
NVL72 heat split — removed by liquid vs left on air per rack (~132 kW total)
$300–500/kW
direct-to-chip system capex vs ~$1,000+/kW for immersion
up to 3x
in-silicon microfluidic cooling vs cold plates (≤65% lower peak temp rise) — the forward pointer
Deep dive: coolant selection — why PG25, and the consequences of the choice

The secondary-loop coolant is a chemistry decision with mechanical consequences that ripple from the cold plate to the CDU. There is no universal single-phase coolant recipe. Select the rack-side fluid from the accelerator, cold-plate, CDU, quick-disconnect, seal, pipe, heat-exchanger, climate, water-quality, and warranty requirements. PG25 — a 25% propylene-glycol/water blend with an approved inhibitor package — is one project-specific option, not the default for every loop.

Heat transfer. Pure water has the best specific heat and lowest viscosity — thermodynamically you would run water if you could. Glycol degrades both: it raises viscosity (more pump energy, more pressure drop) and lowers specific heat (more flow for the same watts). Use only the concentration that the freeze case, material-compatibility matrix, biological-control plan, fluid supplier, and equipment warranties support.

Freeze and biofouling protection. The glycol you do add buys freeze protection for outdoor loop sections and dry coolers in cold climates, and propylene glycol (vs ethylene) is chosen for low toxicity — a leak near electronics and people is less hazardous. Biocide is non-negotiable: warm water in a closed loop is an ideal medium for biofilm that fouls microchannels and spikes pressure drop. Temperature rise and flow follow the named equipment profile, approved-fluid properties, heat load, pressure budget, and control range; a generic PG25 ratio is not an acceptance criterion.

Material compatibility. The loop is a mixed-metal system — copper cold plates, stainless or brass fittings, aluminum heat exchangers, EPDM/elastomer seals. Galvanic corrosion and incompatible elastomers are the failure modes that surface late: the wrong inhibitor package or an unmanaged pH lets dissolved copper plate out on aluminum and seals swell or embrittle. This is why fluid chemistry must follow the complete OEM-approved wetted-material and water-quality specification — it is aggressive to some metals and offers no biocide or freeze margin. The coolant is therefore a managed fluid: filtration, periodic chemistry sampling, and inhibitor top-ups are an operational line item, not a fill-and-forget. → fluid chemistry management lives with the CDU in Chapter 5.6.

What stays on air — and how it is handled

'Liquid-cooled' overstates what DLC does. It cools the high-flux components only — the GPUs, the CPUs/Grace dies, the NVLink/NVSwitch silicon, and increasingly the high-power VRMs — leaving a residual air load that a hall ignores at its peril. On a GB200 NVL72 rack, roughly 115 kW is removed by liquid and ~17 kW remains on air — about 13% of the rack. Scale the split with the rack you name: GB300-class racks run higher total power and a higher liquid duty, so an air tail sized off the GB200 record is sized for the previous generation. That tail is everything not worth a cold plate: NICs and optical transceivers, DIMMs, power-supply units, lower-power voltage regulators, the BMC, and miscellaneous board components. Optics in particular are a growing concern — pluggable transceiver power is climbing, and the optics sit at the rack's air-cooled edge precisely where airflow is now sparse.

The fork here is how you capture the air tail. Three patterns dominate. In-rack air-to-liquid: a small rear-door or in-chassis air-to-liquid heat exchanger rejects the residual air load back into the same liquid loop, so the rack exhausts neutral air and the hall needs no separate air plant — the cleanest answer, and the one that makes a 'zero-air-to-room' rack possible. Hybrid containment: the hall keeps a reduced CRAH/in-row air system sized only for the ~10–20% air tail, with hot/cold-aisle containment, which is simpler to retrofit but reintroduces an air plant and its PUE. Facility air: simplest and worst — let the tail dump into the room and handle it with the building's air system, acceptable only at low rack counts. A hall that sizes liquid for 115 kW and forgets the 17 kW air tail will thermally throttle on the optics and DIMMs while the GPUs run cold — stranding the rack it just spent $300–500/kW to liquid-cool. → containment strategy for hybrid halls in Chapter 5.3; the optics thermal problem resurfaces in Chapter 8.10.

What gets liquid, what stays on air — and why
ComponentCooling pathRationale
GPU / accelerator packageLiquid (cold plate)Highest flux (1.0–2.3 kW); over the air cliff
CPU / Grace dieLiquid (cold plate)High flux; co-located on the tray
NVSwitch / NVLink siliconLiquid (cold plate)Dense interconnect silicon, significant draw
High-power VRMsLiquid (increasingly)Power-delivery losses now warrant a plate
NICs / optical transceiversAirLower flux but rising; sit at the rack edge
DIMMs / memoryAir (often)Distributed, lower flux; hard to cold-plate
PSUs / BMC / miscAirModest power; not worth the plumbing
Representative NVL72-class split; exact allocation varies by vendor and generation. Air tail ~10–20% of rack power.

Forward pointer: in-silicon microfluidics

Cold plates have a hard physical limit: no matter how good the plate, heat must still conduct from the junction, through the package, across the TIM, and into the plate before the coolant ever sees it. That stacked thermal resistance — and especially the TIM — is what caps the flux a cold plate can handle. The next step removes the intermediary entirely: etch the coolant channels into the silicon itself.

In-chip (direct-to-silicon) microfluidics routes coolant through microscopic channels — each roughly a hair's width — cut directly into the die or the backside of the package, so liquid flows over the hotspots inside the chip rather than across an external plate. Microsoft's 2025 prototype, using AI-designed, leaf-vein-inspired channel networks, reported up to 3x better heat removal than state-of-the-art cold plates and up to 65% lower peak temperature rise. The rationale is pure thermal resistance: collapsing the conduction path from junction to coolant is the only way to keep pace with 3D-stacked dies and the projected 2–3 kW packages behind them, where a cold plate simply runs out of room. Treat it as a roadmap signal rather than a 2026 production technology. The rack-power ramp pushing toward it is dated: VR200 NVL72 was in full production as of 26 August 2026 at an analyst-estimated ~190–230 kW per rack, and Rubin Ultra Kyber is the 2027 roadmap step at ~600 kW. The full consolidated cooling roadmap, including immersion's role and the 600 kW–1 MW rack generation, lives in Chapter 16.2.

DLC sits in the middle of Part 5's cooling stack. The density wall that forces it is in Chapter 5.1; the air regime it replaces in Chapter 5.2; the RDHx/AALC bridge for brownfields in Chapter 5.3; immersion's parallel single-/two-phase story and the PFAS reckoning in Chapter 5.5. The secondary loop that feeds these cold plates — CDUs, fluid chemistry, dew-point margin — is Chapter 5.6; the facility water loop and warm-water strategy Chapter 5.7; heat rejection Chapter 5.8; heat reuse Chapter 5.9; retrofitting air halls to liquid Chapter 5.10; reliability, leak detection and commissioning Chapter 5.11; and the mechanical/pressure-system engineering of the piping Chapter 5.13. The archetype decision that made DLC mandatory is framed in Chapter 1.1; the in-silicon microfluidics roadmap in Chapter 16.2; and the optics thermal tail in Chapter 8.10.
Cite this chapter
Fehn, J. (2026). Direct-to-Chip Liquid Cooling (DLC) — Architecture, Fluid & Thermal Design (Chapter 5.4). The Definitive Guide to AI Data Centers. https://aidatacenterguide.com/part-5-cooling-and-thermal-management/5-4-direct-to-chip-liquid-cooling-dlc-the-2026-default (accessed 2026-08-28).
@misc{aidc-5-4,
  author       = {Fehn, Jacob},
  title        = {Direct-to-Chip Liquid Cooling (DLC) — Architecture, Fluid & Thermal Design (Chapter 5.4)},
  howpublished = {The Definitive Guide to AI Data Centers},
  year         = {2026},
  url          = {https://aidatacenterguide.com/part-5-cooling-and-thermal-management/5-4-direct-to-chip-liquid-cooling-dlc-the-2026-default},
  note         = {Accessed 2026-08-28}
}
Spotted an error? Suggest an edit