API 2000 is the reference engineers reach for when they need to know how big a tank's vents must be, but the standard is a sizing methodology, not a single number. It breaks the required venting capacity into distinct contributions - the flow from pumping liquid in and out, the flow from the tank breathing as temperature changes, and the far larger flow of the fire-exposure case - and adds the relevant ones together. This guide walks through how each contribution is computed and combined so you can see where the numbers on a vent-sizing spreadsheet come from.
Tank Vent Sizing (API 2000) in one line: Tank vent sizing per API 2000 is calculated by summing the venting demands the tank can experience. Normal venting adds the maximum pump-in and pump-out flows to the thermal in- and out-breathing caused by temperature changes, giving the required normal venting capacity in a flow unit such as standard cubic feet of air per hour. Emergency venting is sized separately for the fire-exposure case, using the heat a fire would put into the tank's wetted area to compute a much larger relief flow. The vents are then selected to pass the governing requirement.
Normal venting sizing starts with the flows the tank creates in ordinary service, and there are two sources. The first is liquid movement. When liquid is pumped in at the maximum fill rate, it displaces an equal volume of vapor that must vent out, so the out-breathing demand from pumping equals the maximum pump-in rate expressed as a vapor volume. When liquid is pumped out at the maximum rate, an equal volume of air or blanket gas must vent in to replace it, so the in-breathing demand from pumping equals the maximum pump-out rate. These two are the pumping contributions to out-breathing and in-breathing respectively.
The second source is temperature. As ambient conditions change, the vapor space and its contents expand and contract even when no liquid is moving. A rising temperature expands the vapor and drives out-breathing; a falling temperature contracts it and, together with any vapor condensation, drives in-breathing. API 2000 provides a way to estimate these thermal in- and out-breathing rates from the tank's size, based on how quickly conditions can change. Notably, thermal in-breathing can be the larger of the two thermal effects, because a sudden cooling - a rainstorm on a hot tank, for instance - can pull a strong vacuum demand.
The required normal venting capacity is then the sum of the relevant flows for each direction. Out-breathing capacity must cover pump-in-driven venting plus thermal out-breathing occurring together; in-breathing capacity must cover pump-out-driven venting plus thermal in-breathing together. The vent is sized so it can pass whichever direction's combined demand is larger without letting the tank pressure or vacuum exceed its limits. Everything is converted to a common basis - typically an equivalent volume of air at standard conditions - so the different contributions can be added and compared to a vent's rated capacity.
Emergency venting is a separate calculation because it addresses a scenario that dwarfs normal breathing: an external fire heating the tank. The physics is that fire delivers heat into the portion of the tank shell wetted by liquid, that heat boils the liquid, and the vapor generated must be vented or the tank will over-pressure. So the calculation begins with the wetted surface area - the area of shell in contact with liquid up to a height the standard defines - because that is the area through which fire drives heat into the contents.
From the wetted area, API 2000 provides a heat-input relationship that gives the rate of heat the fire is assumed to deliver, generally with the heat input per unit area falling off as the wetted area grows larger. That heat input is then converted into a vapor generation rate using the latent heat of the stored liquid, and the vapor rate is expressed as an equivalent airflow at standard conditions so it can be matched to a vent's rating. The result is the required emergency relief capacity, and because a fire boils liquid far faster than pumping or weather ever moves vapor, this figure is typically far larger than the normal venting requirement.
Certain credits can reduce the fire-case requirement where they genuinely apply. Adequate insulation on the tank slows the heat that reaches the liquid and lowers the required relief; proper drainage that carries burning liquid away from the tank and prompt firefighting can also be recognized in some cases. These credits must reflect real, maintained provisions, not hopeful assumptions, because the emergency vent is the last barrier against rupture in a fire. The emergency requirement is computed on its own and does not add to the normal venting number - the tank must simply be able to pass whichever scenario governs, and the vents are selected accordingly.
A vent-sizing calculation ends with required capacities and selected devices, but those numbers are only protective if the tank actually operates within the assumptions behind them. The normal venting figure, for instance, is tied to the maximum pump-in and pump-out rates the engineer assumed. If a tank is later filled faster than that - a bigger pump, a changed transfer plan - the real breathing demand can exceed what the normal vent was sized to pass, and the tank pressure will climb beyond the intended band during fills. Knowing the true fill and draw rates is therefore part of trusting the sizing.
A cloud SCADA such as Merobix makes those operating rates visible. By trending the tank level over time, the platform effectively shows the actual fill and draw rates every transfer achieves, and by trending tank pressure and vacuum it shows whether the vents are keeping the tank within its limits at those rates. Merobix reads level, flow, and pressure from the field over Modbus, DNP3, OPC UA, and MQTT, so the assumptions in a vent-sizing spreadsheet can be checked against what the tank really does rather than accepted on faith.
For an operator managing many tanks, this closes the loop between a static calculation and live operation. The system can flag a transfer whose rate exceeds the value the vents were sized for, or a tank whose pressure repeatedly approaches its limit during fills, both of which are signs that the operating reality has outgrown the sizing basis. Vent sizing is done once on paper, but keeping it valid is an ongoing operations task, and continuous monitoring of the rates and pressures involved is how field operations confirm the vents remain adequate as the tank's service changes.
Normal venting per API 2000 combines two sources. The pumping contribution comes from the maximum fill rate, which drives out-breathing, and the maximum draw rate, which drives in-breathing. The thermal contribution comes from temperature changes that expand or contract the vapor space. Out-breathing and in-breathing are each sized for their pumping plus thermal demand occurring together, converted to a common flow basis.
Because it is sized for a fire boiling the tank's contents, which generates vapor far faster than pumping or weather ever move it. The fire-case calculation starts from the tank's wetted surface area, applies an assumed heat input, and converts the resulting boil-off into a required relief flow. That flow is typically far larger than the normal breathing demand, which is why emergency relief uses big, dedicated devices.
No, they are evaluated as separate scenarios. Normal venting sizing covers routine pumping and thermal breathing, and emergency venting sizing covers the fire-exposure case; the tank must be able to relieve whichever scenario governs rather than the sum of both. In practice normal breathing is handled by the everyday vent and the fire case by dedicated emergency devices, each meeting its own required capacity.
Primary references from the standards bodies and regulators that define this topic:
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.