API 520 vs API 521 vs API 526: Relief System Standards Explained

If you have ever sat in a HAZOP session and heard someone say “just follow API 520” when the conversation was clearly about flare header sizing, you know exactly why this topic needs a proper breakdown. These three standards are not interchangeable. They govern different scopes, different engineering disciplines, and different project phases. Getting them confused does not just create rework it creates compliance gaps that can fail a PHA audit or, worse, contribute to an overpressure event.

This guide draws a clean line between API 520, API 521, and API 526, explains where each one applies, and gives you a working compliance checklist to carry into your next project.

What These Three API Standards Actually Cover (And Why Engineers Confuse Them)

API 520 governs the sizing and selection of pressure-relieving devices at the source. API 521 governs what happens downstream the disposal systems (flares, blowdowns, vents). API 526 is a procurement and dimensional standard for flanged steel relief valves. They address three distinct scopes and must be applied together on any full relief system design.

The confusion is understandable. All three standards appear in the same project deliverable the Pressure Relief System Design Basis and their names overlap enough to blur the boundaries. But their engineering domains are separate.

Think of it this way: API 520 answers “how big does the relief valve need to be?” API 521 answers “once it opens, where does the fluid go safely?” API 526 answers “what physical valve do I order from the vendor?” Three questions. Three documents. All required.

One without the others produces an incomplete design.

API 520 Sizing and Selection of Pressure-Relieving Devices

API 520 is published in two parts and is the primary engineering standard for overpressure protection at the equipment level. It covers the methodology for calculating the required relieving capacity for pressure vessels, heat exchangers, pumps, and piping systems exposed to credible overpressure scenarios.

The standard addresses:

• Single and multiple contingency overpressure cases
• Sizing for vapour, liquid, and two-phase flow
• The effect of superimposed and built-up backpressure on valve selection
• Conventional, balanced bellows, and pilot-operated PRV types

It does not specify valve dimensions. It does not govern the disposal system. Those are separate documents.

API 521 Pressure-Relieving and Depressuring Systems

API 521 picks up precisely where API 520 stops. Once a relieving device opens, the released fluid must go somewhere safe. API 521 defines how to design the entire downstream infrastructure: flare headers, knockout drums, seal drums, flare tips, and emergency depressurization systems.

This standard is the governing document for:

• Flare system hydraulic analysis (pressure drop, Mach number limits)
• Thermal radiation calculations from flare tips
• Blowdown drum design and emergency depressurization of pressure vessels
• Disposal of relief loads to atmosphere, closed systems, or incinerators

API 521 also addresses the selection logic for disposal methods when flaring is acceptable versus when a closed disposal system is required.

API 526 Flanged Steel Pressure Relief Valves

API 526 is the dimensional and procurement standard. It defines standard orifice sizes (designated by letters: D, E, F, G, H, J, K, L, M, N, P, Q, R, T), pressure-temperature ratings, materials of construction, end connections, and face-to-face dimensions for flanged steel pressure relief valves.

When your datasheet says “API 526 compliant valve,” it means the valve’s physical envelope, orifice area, and pressure class conform to this standard. This enables interchangeability between manufacturers; a Leser valve and an Emerson valve with the same API 526 designation are dimensionally equivalent.

What it does not do: tell you which orifice to select. That calculation belongs to API 520.

API 520 Deep Dive: Part I vs Part II Not the Same Document

API 520 Part I covers the engineering methodology for sizing pressure-relieving devices, including flow equations for vapour and liquid service and backpressure correction factors. Part II covers installation requirements inlet pressure drop limits, discharge piping design, and isolation valve requirements. Both parts are required for a compliant relief system design.

Many engineers treat API 520 as a single document. It is not. The two parts serve fundamentally different engineering functions, and referencing only Part I during detailed design is a common gap that gets flagged in third-party safety audits.

Part I Sizing and Selection (The Engineering Calculation Standard)

API 520 Part I is where the pressure relief valve sizing calculations live. It provides the governing flow equations for:

• Vapour/gas service (critical and subcritical flow regimes)
• Liquid service (with viscosity correction factors)
• Two-phase and steam service
• Fire contingency sizing (per API 521 heat input rates)

The standard also walks through the selection logic between conventional PRVs, balanced bellows PRVs, and pilot-operated PRVs based on the backpressure effects on PRVs. If built-up backpressure exceeds 10% of the set pressure, a conventional valve is no longer appropriate Part I makes this explicit.

Relieving capacity calculation under Part I is not a simple lookup table. It requires:

1. Defining the governing overpressure scenario (blocked outlet, fire, thermal expansion, etc.)
2. Calculating the relieving conditions (pressure, temperature, fluid properties at relieving conditions not normal operating conditions)
3. Applying the appropriate flow coefficient (Kd) and backpressure correction factor (Kb or Kw)
4. Verifying the selected orifice against ASME Section VIII allowable accumulation limits

Part II Installation (The Field Engineering Standard)

Part II is where most projects cut corners. It governs:

• Inlet pressure drop to the relief valve (must not exceed 3% of set pressure for conventional valves to prevent chatter)
• Discharge piping design to avoid excessive backpressure
• The use of block valves (car-seal open requirements, interlocking requirements)
• Drain requirements for discharge piping to prevent liquid accumulation
• PRV installation orientation and support requirements

In our experience reviewing client designs, inlet pressure drop violations are the single most common non-conformance. Engineers size the valve correctly per Part I but run the inlet line too small to save on pipe rack space, creating chatter conditions that destroy the valve seat within weeks of commissioning.

Common Sizing Mistakes Engineers Make Under API 520

• Using normal operating conditions instead of relieving conditions for fluid properties
• Ignoring the Kv factor (viscosity correction) for high-viscosity liquid service
• Selecting a conventional PRV where built-up backpressure exceeds 10% of set pressure
• Omitting the combination capacity factor when a rupture disk is installed upstream
• Failing to check the selected orifice area against the next standard API 526 orifice size

Each of these errors requires a complete rework of the PRV datasheet. Catch them in FEED, not during detailed design.

API 521: The Standard That Governs Where the Pressure Goes

API 521 governs the design of pressure-relieving and depressuring systems downstream of relief devices. It covers flare and vent system design, emergency depressurization, thermal radiation from flares, and disposal method selection. Compliance with API 521 is referenced by OSHA PSM regulations and is effectively mandatory for hydrocarbon processing facilities in the US.

If API 520 is the upstream standard, API 521 is the downstream standard. Every relief load calculated under API 520 must be routed to a disposal system that API 521 governs. This is where systems engineering happens.

Flare and Vent System Design Under API 521

The flare system is not just a pipe to a flame. API 521 requires a rigorous hydraulic analysis of the entire relief header network to ensure that backpressure at each PRV inlet (under simultaneous relief scenarios) remains within acceptable limits.

Key design parameters governed by API 521:

• Maximum Mach number in relief headers (typically 0.5 at the point of highest velocity API 521 flags Mach >0.7 as a design concern)
• Knockout drum sizing to separate liquids before the flare tip
• Seal drum liquid seal depth to prevent flashback
• Flare tip velocity and heat release calculations
• Thermal radiation exclusion zones around the flare stack (per API 521 radiation intensity limits of 1.58 kW/m² at grade level for continuous flaring)

The simultaneous relief case is where most flare systems are undersized. Sizing the header for the single largest PRV load is not sufficient API 521 requires evaluating credible simultaneous relief scenarios.

Depressurization Studies and Emergency Blowdown

Emergency depressurization is a safety-critical operation for high-pressure hydrocarbon systems particularly on offshore platforms, gas processing plants, and high-pressure reactors. API 521 defines the depressurization criteria:

• Vessels containing flammable fluids should be depressurized to 50% of design pressure or 6.9 barg (100 psig), whichever is lower, within 15 minutes for fire exposure scenarios
• Blowdown drum design must account for thermal loads during rapid depressurization (Joule-Thomson cooling effects can cause brittle fracture if materials are not correctly specified)
• The standard provides guidance on emergency blowdown valve sizing and control logic

This is not a calculation you estimate. A dynamic simulation (typically in HYSYS or equivalent) is required to accurately model vessel wall temperatures during blowdown.

API 521 and Its Relationship to OSHA PSM Requirements

Process Safety Management under OSHA 29 CFR 1910.119 requires that pressure relief systems be designed in accordance with recognized and generally accepted good engineering practices (RAGAGEP). API 521 is explicitly cited as RAGAGEP for relief system disposal design.

This means non-compliance with API 521 is not just a technical gap, it is a PSM compliance gap that carries regulatory enforcement risk. During a PSM audit, expect the auditor to request:

• The flare system design basis referencing API 521
• Documentation of the simultaneous relief case analysis
• Evidence that flare radiation calculations were performed per API 521 methodology

API 526: The Procurement and Dimensional Standard

API 526 defines standard orifice designations, face-to-face dimensions, pressure-temperature ratings, and materials for flanged steel pressure relief valves. It enables interchangeability between manufacturers. It does not govern valve sizing (API 520) or system design (API 521), but it is referenced in PRV datasheets and vendor RFQs for procurement compliance.

API 526 is the standard that actually shows up on the purchase order. Once the engineering is done under API 520, the result is an orifice letter designation and a set pressure. API 526 translates that into a purchasable valve.

What API 526 Standardizes (and What It Does Not)

API 526 defines:

• Standard orifice designations (D through T) with corresponding effective orifice areas
• Face-to-face dimensions for flanged connections (ensuring physical interchangeability between vendors)
• Pressure-temperature ratings per material group and flange class
• Body and bonnet materials (carbon steel, stainless steel, chrome-moly alloys)
• End connection types (raised face, ring type joint)
• Spring-loaded PRV inlet and outlet flange classes from 150# to 2500#

What API 526 does not standardize: the flow coefficient (Kd), the valve performance under backpressure, or the installation requirements. Those belong to API 520.

Orifice Designation, Pressure-Temperature Ratings, and Materials

The orifice letter system in API 526 is the universal language between process engineers and PRV vendors. When a datasheet specifies a “J orifice,” every compliant manufacturer knows the effective area is 0.110 in² (71.0 mm²).

Orifice	Effective Area (in²)	Effective Area (mm²)
D	0.110	71.0
E	0.196	126.5
F	0.307	198.1
G	0.503	324.5
H	0.785	506.5
J	1.287	830.3
K	1.838	1185.8
L	2.853	1840.6
M	3.600	2322.6
N	4.340	2799.9
P	6.380	4116.1
Q	11.050	7129.0
R	16.000	10322.6
T	26.000	16774.2

This standardization is what makes global PRV procurement possible. Without API 526, every valve would be a custom fabrication.

When API 526 Applies vs When It Doesn’t

API 526 applies to spring-loaded, flanged steel pressure relief valves in refining, petrochemical, and gas processing service. It does not apply to:

• Screwed (threaded) relief valves (commonly used in utility systems below 2″ nominal size)
• Rupture disks these are governed by ASME Section VIII Division 1, Mandatory Appendix 11
• Pilot-operated PRVs (covered under API 520 for sizing, but API 526 does not cover pilot-operated valve dimensions)
• Safety valves in steam boiler service (ASME Section I governs those)

If your application falls outside these boundaries, confirm the applicable standard before issuing the PRV datasheet.

API 520 vs API 521 vs API 526: Side-by-Side Comparison

Parameter	API 520 Part I	API 520 Part II	API 521	API 526
Primary Scope	PRV sizing & selection	PRV installation	Relief disposal systems	PRV dimensions & procurement
Engineering Phase	FEED / Detailed Design	Detailed Design / Construction	FEED / Detailed Design	Procurement
Governs	Relieving capacity, orifice area	Inlet/outlet piping, block valves	Flare, vent, blowdown systems	Physical valve envelope
Key Output	Required orifice area (in²)	Piping layout compliance	Flare system design basis	PRV datasheet / PO spec
Related Standards	ASME Sec. VIII	ASME B31.3	OSHA PSM / API 521	API 520
Applies to Rupture Disks?	Yes (combination sizing)	Yes (installation)	No	No
Mandatory for PSM?	Yes	Yes	Yes	Referenced

Which Standard Applies to Your Project Phase?

• Concept / FEED: API 521 (establish relief philosophy, disposal routes, flare system sizing basis), API 520 Part I (initial PRV sizing for relief load calculations)
• Detailed Design: API 520 Part I (finalized PRV datasheets), API 520 Part II (piping design), API 521 (finalized flare system hydraulic model)
• Procurement: API 526 (PRV specification, vendor RFQ, dimensional compliance)
• Construction / Commissioning: API 520 Part II (installation verification), API 521 (blowdown system testing)

Can These Standards Be Used Simultaneously?

Yes and they must be. A complete relief system design references all three. API 520 sizes the device, API 521 designs the disposal path, and API 526 specifies the physical valve. Omitting any one of them creates a documentation gap that will surface during a safety audit, PHA review, or vendor pre-qualification assessment.

Compliance Checklist: Applying All Three Standards Correctly

A compliant relief system design requires API 520 Part I and II for PRV sizing and installation, API 521 for flare and disposal system design, and API 526 for valve procurement specifications. Each standard applies at a different project phase. Gaps in any one of the three create PSM compliance risk and potential rework during safety audits.

Use this checklist on your next project to avoid the most common compliance gaps.

Engineering Design Phase Checklist

API 520 Part I:

• Overpressure scenarios identified and ranked per credibility (HAZOP or What-If basis)
• Relieving conditions (P, T, fluid properties) established at relieving pressure, not operating pressure
• Sizing completed for vapour, liquid, or two-phase service as applicable
• Backpressure type (superimposed vs. built-up) evaluated and PRV type selected accordingly
• Combination capacity factor applied where rupture disk is upstream of PRV
• Required orifice area cross-referenced to next larger API 526 standard orifice

API 521:

• Relief disposal philosophy documented (flare vs. vent vs. closed system)
• Simultaneous relief case identified and total flare load calculated
• Flare header hydraulic model completed (pressure drop, Mach number verified)
• Knockout drum sized for liquid dropout under maximum relief load
• Thermal radiation exclusion zones calculated and plot plan reviewed
• Emergency depressurization criteria checked against API 521 (50% DP or 6.9 barg in 15 min)

Procurement Phase Checklist

API 526:

• PRV datasheet references API 526 for dimensional compliance
• Orifice letter designation confirmed from API 520 sizing output
• Inlet and outlet flange class specified per API 526 pressure-temperature table
• Material group selected per process fluid and temperature range
• Vendor documents requested: API 526 compliance certificate, dimensional drawing, Kd value

Installation and Commissioning Checklist

API 520 Part II:

• Inlet pressure drop verified to be below 3% of set pressure (piping isometric reviewed)
• Discharge piping routed to avoid liquid accumulation (drain points confirmed)
• Block valves (if installed) car-sealed open and interlocking logic reviewed
• PRV orientation confirmed (vertical inlet, as required)
• Cold differential test pressure (CDTP) calculated and stamped on PRV nameplate

Conclusion Knowing Which Standard to Apply Is Half the Engineering Problem

Most relief system errors do not originate from bad calculations. They originate from applying the wrong standard to the wrong scope, or skipping one standard entirely because it “did not seem relevant.” Comparing API 520 vs API 521 vs API 526 is not an academic exercise; it is the foundation of every compliant pressure relief system design in the hydrocarbon processing industry.

Apply API 520 to size and select your relief devices. Apply API 521 to design a safe disposal path for every relief load. Apply API 526 to procure a dimensionally standardized valve that any certified vendor can supply and any inspector can verify. And cross-check all three against your ASME Section VIII vessel ratings and OSHA PSM documentation at every project gate review.

If your team needs a structured review of your existing relief system design basis, or support building one from the ground up, our pressure relief and process safety engineers are available to assess your documentation and close the gaps before your next audit.