Choosing a cooling approach is a facility decision, not a decorative upgrade to a miner. The useful question is how heat will move from the equipment to its final destination under the conditions the site actually experiences. Airflow, liquid circuits, access for maintenance, compatible materials, and failure handling all belong in that discussion.
This guide compares air cooling and immersion through a planning framework. It is not a construction specification or a conversion manual. Equipment changes, electrical work, fluid handling, and facility design should follow manufacturer requirements and qualified professional guidance. No universal temperature target or claimed efficiency improvement is assumed.
Draw the complete heat path
Start with a diagram that follows heat from the device to the surrounding environment or an intended heat-reuse system. Name every stage: the component interface, the transport medium, any circulation equipment, and the final heat rejection point. A cooling system is only as useful as its ability to complete that path.
The Braiins overview of mining cooling methods distinguishes air cooling, immersion, and hydro cooling. Air moves heat with ventilation; immersion transfers it into a compatible dielectric fluid; hydro designs use purpose-built liquid-cooling arrangements. These are different architectures, and a liquid-cooled product should not automatically be treated as suitable for immersion.
Understand the air-cooled operating picture
For an air-cooled project, map intake and exhaust paths before counting machines. Ask where incoming air comes from, where heated air goes, and what prevents recirculation. Include access for inspecting and maintaining filters, fans, and the surrounding space. The site layout should be evaluated under representative operating conditions rather than only when the room is empty.
Record environmental observations at meaningful locations. A room average can hide a problematic intake area or an exhaust path that affects a particular row. Keep sensor placement documented so readings remain comparable after equipment moves. These observations support a professional design review; they do not replace the manufacturer's operating limits or the relevant safety requirements.
Understand the immersion operating picture
An immersion project requires more than a tank and fluid. It needs verified compatibility among equipment, fluid, seals, cables, service procedures, and the rest of the circulation and heat-rejection system. Establish who approves each compatibility decision and where the supporting documentation is kept. Do not assume a conversion preserves warranty coverage or support eligibility.
Think through routine service before choosing the architecture. How is a device isolated, removed, inspected, and returned? What happens to fluid during maintenance? Which trained people and approved procedures are required? A plan that only describes steady operation leaves its most practical questions unanswered. Treat handling and recovery procedures as part of the design rather than afterthoughts.
Compare equivalent boundaries
Cooling comparisons can become misleading when one option includes all auxiliary equipment and another reports only miner power. Define whether the comparison includes device fans, external ventilation, pumps, heat exchangers, or other facility loads. Use the same boundary for both alternatives and state any exclusions prominently.
Also match the intended workload and operating conditions. A system that supports more hardware in a given space may be useful for a density constraint, but that is not the same claim as lower total energy use. The efficiency guide explains why a lower device J/TH figure and a better whole-site outcome are separate questions.
Build a maintenance comparison
Write a typical month of maintenance activities for each option. Include inspection, cleaning or fluid checks as applicable, service access, spare parts, documentation, and the people authorized to perform the work. Estimate effort using evidence from the proposed system rather than generic claims that one method is always simpler.
Then describe a less convenient day: a failed component, an unexpected leak, a blocked path, or a device that needs replacement. Identify what must stop, which neighboring equipment is affected, and how work resumes safely. The preferred option may depend as much on the team's ability to recover from these events as on a favorable steady-state measurement.
Avoid universal temperature rules
Different devices expose different sensors, and their labels may refer to different measurement locations. A chip temperature, inlet temperature, board reading, and fluid temperature are not interchangeable. Do not copy a threshold from an unrelated machine or assume a single green range is appropriate for an entire mixed fleet.
Build a sensor dictionary with the exact field name, unit, location where documented, supported range, and source of the operating limit. Keep warning rules separate from raw readings. The monitoring design guide describes how to show both the observed value and the rule that interprets it, including an explicit state for missing sensors.
Plan for changing conditions
A cooling design should be evaluated against the operating conditions relevant to the site, not a single favorable afternoon. Ask the design team how seasonal conditions, load changes, maintenance, and loss of a supporting component affect the system. Record the assumptions used in any capacity calculation.
Do not extrapolate linearly from one machine without checking shared constraints. A second row may alter airflow, circulation requirements, or access. An expansion can also change which component becomes the limiting factor. Plan a staged commissioning process with defined observations and review points. Scaling should be an evidence-based decision, not simply filling every remaining physical slot.
Treat heat reuse as another system
Recovering useful heat can be an interesting objective, but the recipient system has its own timing, temperature, reliability, and safety requirements. Identify who needs the heat, when they need it, and what happens when the miner stops or the recipient no longer accepts it. A theoretical heat quantity is not proof of a usable match.
Keep the mining and recipient boundaries explicit. Account for any additional equipment and operating effort required to move or use the heat. Avoid calling a project “free heating” without a complete comparison against the relevant alternative and actual constraints. Our electricity cost framework offers a way to keep energy flows and cost assumptions separate.
Create a pilot with acceptance criteria
Before a larger deployment, define a representative pilot approved for the proposed equipment. Write the measurements, operating envelope, and stop conditions in advance. Include normal operation, a controlled maintenance event, and a recovery exercise performed by qualified personnel under the appropriate procedures.
Success should mean the system satisfies the documented criteria, not merely that it runs without an obvious alarm. Record temperature behavior at supported sensors, relevant power measurements, workload output, and any deviations from the test plan. Keep failed or inconclusive results. They are valuable information for improving the design and preventing a larger commitment based on selective evidence.
Ask better questions of suppliers
Request the exact equipment variants, supported cooling configuration, compatibility documentation, maintenance requirements, warranty terms, and the conditions behind any published performance claim. Ask which parts of the complete system are included in a quotation. A tank price or miner price alone does not describe a commissioned facility.
Separate documented facts from estimates and sales projections in your comparison sheet. Where suppliers use different measurement boundaries, ask for a comparable view rather than ranking the headline figures. The ASIC hardware page provides an inventory-oriented starting point for keeping variants, firmware, and operating requirements tied to the actual devices being considered.
Choose for the whole operating lifecycle
Air cooling and immersion should be compared against the job, site, available expertise, and maintenance model. Neither is a universal shortcut to lower cost or better performance. A suitable design must move heat reliably, remain serviceable, and fit the equipment and facility requirements throughout its lifecycle.
Finish with a decision record containing the complete heat path, compatibility evidence, measurement boundary, pilot results, recovery procedures, and unresolved questions. Have the responsible professionals review the parts within their expertise. The strongest cooling choice is the one your team can explain, operate, and maintain safely—not simply the one with the most futuristic appearance.
