Direct-to-Chip vs Immersion Cooling: An Engineering Comparison for AI Data Centers

Every AI facility planning discussion lands on the same fork: direct-to-chip cold plates or full immersion. Both move heat with liquid, and both outperform air by an order of magnitude, yet they differ in almost everything that determines project success: how much of the server they cool, what the building must provide, how technicians service hardware, and what the fluid loop demands from its pumps. Vendor comparisons tend to favor whichever architecture the vendor sells. This guide compares the two on engineering terms, with the numbers that decide real projects and the pump and fluid-loop implications that most comparisons skip.

How Each Architecture Moves Heat

Direct-to-chip: targeted capture

Direct-to-chip cooling mounts sealed cold plates on the highest heat-flux components, the CPUs and GPUs, and circulates water-glycol coolant through microchannels inside the plates at roughly 0.5 to 2 LPM per plate. Thermal resistance between the die and the coolant drops to 0.02 to 0.10°C/W, ten to twenty times better than an air heatsink. The loop runs through a coolant distribution unit that isolates the technology-side coolant from facility water and holds flow, temperature, and pressure at setpoint. Heat capture covers 60 to 80 percent of rack load; memory, power conversion, and storage still reject their heat to air, so the hall keeps a reduced air-cooling layer alongside the liquid loop.

Immersion: whole-server capture

Immersion removes the boundary entirely by submerging the server boards in dielectric fluid. Single-phase systems pump the fluid through a heat exchanger and back to the tank. Two-phase systems let the fluid boil on the hot components and condense on a coil above, moving heat through phase change with minimal pumping. Heat capture approaches 98 percent of IT load, server fans come out, and rack-equivalent densities reach 100 to 250 kW per tank. The trade is operational: servers require immersion-rated variants, maintenance involves lifting wet hardware out of fluid, and the facility gains a fluid management program it never had before.

Direct-to-chip cold plate versus immersion cooling architecture comparison

Head-to-Head: The Numbers That Decide Projects

CriterionDirect-to-chipSingle-phase immersionTwo-phase immersion
Practical rack density60 to 120 kW50 to 150 kW100 to 250+ kW
Heat capture share60 to 80%~98%~98%
Typical PUE1.05 to 1.151.02 to 1.101.01 to 1.08
Server modificationCold plates on standard chassisImmersion-rated hardwareImmersion-rated, sealed-tank qualified
Service workflowStandard rack hot-swap with quick disconnectsTank access, fluid handling, drying proceduresSealed tank, fluid loss control, specialist procedures
CoolantWater-glycol, 20 to 35%Dielectric hydrocarbonEngineered boiling fluid
Retrofit fitStrong, rack-by-rack rolloutWeak, dedicated pods or greenfieldWeakest, purpose-built facilities


The Four Decision Axes

Density trajectory

Current-generation GPU racks run 40 to 120 kW, squarely inside direct-to-chip territory and a key reason OEM-recommended configurations for flagship AI systems ship with cold plates. Roadmaps pointing beyond 150 kW per rack strengthen the immersion case. Match the architecture to where your density will be in five years, with the caveat that a hybrid path lets you defer the extreme end.

Retrofit or greenfield

Direct-to-chip enters an existing hall row by row using standard racks, standard chassis, and a CDU per row or per rack. Immersion tanks bring floor loading, spill containment, fire strategy, and electrical rework that make them a poor retrofit and a strong greenfield choice. Most announced AI capacity through 2026 sits in existing or conventional-shell buildings, which explains why cold plate deployments dominate current installations.

Operations model

Cold plate maintenance looks like the maintenance teams already do: quick disconnects, hot-swap, familiar rack workflows. Immersion changes the operating culture around fluid cleanliness, compatibility testing, and lifting procedures. An architecture that matches the team you have will outrun a theoretically superior one that matches nobody on site.

Standards and warranty

Direct-to-chip rides mature standards work, including OCP ACS interface specifications and broad OEM cold plate options with intact warranties. Immersion hardware certification is improving yet remains vendor-specific, and warranty terms for submerged operation require case-by-case confirmation.

What Each Architecture Demands from Pumps and Fluid Loops

This is the comparison layer most articles omit, and the layer where failures actually happen.

Direct-to-chip: a precision water-glycol loop

The technology cooling loop is a high-resistance circuit: cold plate microchannels, quick disconnects, and manifold networks stack pressure drop at moderate flow. Pumps run continuously at variable speed inside the CDU in N+1 arrangements, must hold stable pressure as filters load, and cannot leak into a data hall. Glycol viscosity at low temperature demands curve derating. Seal-less magnetic drive circulation pumps with stainless wetted paths fit this duty directly, as detailed in the AI data center liquid cooling pump selection guide; the MDW vortex magnetic pump covers the stable low-flow, zero-leakage requirement, and its forward/reverse capability simplifies loop filling and purging.

Magnetic drive pump in a direct-to-chip cooling loop diagram

Single-phase immersion: dielectric circulation

Tank circulation pumps handle engineered dielectric fluids with low lubricity and specific material compatibility requirements. Leak containment matters less for electronics risk, since the fluid itself is non-conductive, and more for fluid cost and housekeeping. Seal materials and bearing construction must be confirmed against the exact fluid chemistry.

Two-phase immersion: minimal pumping

Boiling and condensation move the heat, so pump duty shrinks to makeup, filtration, and condensate handling. The engineering burden shifts to sealed-tank integrity and fluid loss control, particularly as the industry transitions away from PFAS-class fluids.

Efficiency Claims Deserve a Second Look

Published PUE figures favor immersion, and part of that advantage is real: removing server fans eliminates a genuine energy draw. Part of it is accounting. Fan energy disappears from the IT side of the PUE calculation and shifts the boundary, which flatters the architecture in a side-by-side comparison. Procurement-grade evaluation pairs PUE with water usage effectiveness and with the temperature grade of the rejected heat. Direct-to-chip loops running warm water unlock long free-cooling seasons and practical heat reuse at useful temperatures. Immersion loops reject heat at similar or higher grades with lower transport energy. The architecture with the lower PUE on a datasheet is not automatically the one with the lower annual energy bill at your site, climate, and load profile.

Heat rejection deserves the same scrutiny regardless of architecture. Liquid cooling transports heat; it does not destroy it. Dry coolers, cooling towers, or a heat reuse offtake must still absorb every kilowatt the loop collects, and a facility that plans the in-row technology carefully while leaving heat rejection as an afterthought ends up with an efficient loop connected to an undersized plant.

The Hybrid Reality

Large operators rarely choose one architecture for everything. A common layout keeps general compute on air, moves AI racks onto direct-to-chip rows, and reserves immersion pods for the densest training clusters. This staged path builds liquid cooling capability progressively, keeps procurement flexible across hardware generations, and spreads capital over time. The mixed environment also sets the pump agenda: each zone runs its own loop chemistry and hydraulic profile, so circulation equipment gets specified per zone against local pressure drop and fluid data, with no single pump duty covering the whole hall. Planning the shared infrastructure, facility water temperatures, heat rejection capacity, and spare CDU capacity, matters more than picking a winner between the two architectures.

Decision Checklist

  1. Peak rack density today and the credible five-year roadmap, per rack, not room average.
  2. Building constraints: floor loading, containment, piping routes, and available facility water temperatures.
  3. Operations capability: the maintenance team and workflows that will actually service the hardware.
  4. Hardware plan: OEM cold plate availability and warranty terms versus immersion-rated variants.
  5. Fluid program: glycol loop chemistry or dielectric lifecycle management, including end-of-life handling.
  6. Pump and loop engineering: pressure drop budgets, redundancy model, and leak containment for the chosen architecture.

Aulank Pump manufactures seal-less vortex magnetic drive circulation pumps for direct-to-chip technology loops and CDU duty, with zero-leakage containment and media ratings from −196°C to +400°C. Send us your loop flow and pressure drop data, and our engineering team will return a matched pump with the sizing calculation. Contact us for support on your liquid cooling project.

FAQ

What is the main difference between direct-to-chip and immersion cooling?

Direct-to-chip mounts cold plates on the CPUs and GPUs and circulates water-glycol coolant through them, capturing 60 to 80 percent of rack heat while the rest stays on air. Immersion submerges the entire server in dielectric fluid, capturing nearly all IT heat and eliminating server fans. The first keeps standard racks and service workflows; the second maximizes density and efficiency at the cost of a new operating model.

Which is more energy efficient, direct-to-chip or immersion cooling?

Immersion posts lower PUE figures, typically 1.02 to 1.10 versus 1.05 to 1.15 for direct-to-chip, partly because removing server fans shifts the energy accounting boundary. Real annual energy cost depends on climate, load profile, and heat rejection strategy, so PUE should be evaluated alongside WUE and rejected-heat temperature rather than taken as a standalone verdict.

Can direct-to-chip cooling handle current AI rack densities?

Yes. Direct-to-chip serves 60 to 120 kW per rack comfortably, which covers current flagship GPU systems including OEM-recommended configurations for the latest AI platforms. Roadmaps beyond roughly 150 kW per rack are where immersion gains the advantage.

Is immersion cooling suitable for retrofitting an existing data center?

Rarely as a simple upgrade. Immersion tanks bring floor loading, spill containment, fire strategy, and electrical rework, plus new fluid handling procedures, which makes immersion strongest in greenfield builds or dedicated pods. Direct-to-chip is the practical retrofit path, deployable rack by rack in standard enclosures.

What is the difference between single-phase and two-phase immersion?

Single-phase keeps the dielectric fluid liquid and pumps it through a heat exchanger, offering simpler management at 50 to 150 kW per tank. Two-phase lets the fluid boil on components and condense above, reaching 100 to 250+ kW with minimal pumping, at the cost of sealed-tank complexity, fluid loss control, and regulatory questions around boiling fluid chemistries.

What pumps do liquid cooling architectures use?

Direct-to-chip technology loops need seal-less circulation pumps holding stable pressure against cold plate microchannel resistance in continuous variable-speed duty. Single-phase immersion needs dielectric-compatible circulation pumps matched to fluid chemistry. Two-phase immersion needs only light-duty makeup and condensate pumps since phase change moves the heat.

Should a data center choose one liquid cooling architecture for everything?

Most large deployments run hybrid: air for general compute, direct-to-chip for AI racks, and immersion pods for the densest training clusters. The staged approach builds capability progressively and spreads capital. Shared infrastructure planning, facility water temperatures, heat rejection, and spare CDU capacity, matters more than declaring a single winner.

Contents