API 570 vs 510 vs 653: Which Code Applies?
New mechanical-integrity engineers constantly mix up which API code governs which asset, and citing the wrong one in a program document undermines it. This page draws a clean line between API 570, 510, and 653 - the piping, vessel, and tank inspection codes - and explains the philosophy they share, so you reach for the right one every time. It is a comparison, not a deep dive into any single code.
API 570 vs 510 vs 653 in one line: The three codes split by asset: API 570 governs in-service process piping, API 510 governs in-service pressure vessels, and API 653 governs in-service aboveground storage tanks. All three are in-service inspection codes that share one philosophy - qualified inspectors, corrosion-rate-driven intervals, and engineering evaluation of findings - applied to different equipment with different damage mechanisms.
The Decision in One Paragraph
Identify the asset and the code follows. If it carries fluid between equipment, it is piping and you want API 570. If it is a pressure-containing vessel, you want API 510. If it is an aboveground storage tank, you want API 653. All three are strictly in-service - the design and construction of each asset is governed by its own construction code, and these three pick up once the asset is operating.
The confusion usually comes from the shared vocabulary - thickness measurement locations, corrosion rate, remaining life, not-to-exceed intervals - which appears in all three because the underlying integrity logic is the same. The vocabulary is common; the asset and its damage mechanisms are not.
Side-by-Side
The table lines up the three codes by asset and the construction code each follows in service. Use it to place a code quickly, then go to the specific code's page for the interval and program detail.
| Code | Asset | Governs |
|---|---|---|
| API 570 | Process piping | In-service inspection, rating, repair, alteration |
| API 510 | Pressure vessels | In-service inspection, rating, repair, alteration |
| API 653 | Aboveground storage tanks | In-service inspection, repair, alteration, reconstruction |
What They Share and Where They Differ
All three set intervals from corrosion rate against remaining thickness, capped by a ceiling, and all three separate the inspector who documents from the engineer who evaluates fitness-for-service. They also all increasingly draw on risk-based inspection to allocate effort, and on process history to understand exposure.
Where they differ is the damage mechanisms and the geometry. Piping under API 570 worries about dead legs, injection points, and corrosion under insulation; vessels under API 510 worry about shell and head thinning and cyclic damage; tanks under API 653 worry heavily about the bottom plate and settlement. The interval philosophy is shared; the inspection focus is asset-specific.
Pitfalls
The first pitfall is folding piping into the vessel program because the piping connects to a vessel. Piping has its own code, circuits, and damage mechanisms; riding it on the vessel schedule leaves thinning elbows and dead legs uninspected. Each asset class needs its own program under its own code.
The second is citing a construction code where an inspection code belongs, or vice versa. The construction code built the asset; API 570, 510, and 653 keep it fit for service. Mixing them in a program document confuses the reader and the auditor about what obligation you are actually meeting.
Frequently Asked Questions
Which API code covers piping, vessels, and tanks?
API 570 covers in-service process piping, API 510 covers in-service pressure vessels, and API 653 covers in-service aboveground storage tanks. All three are inspection codes that apply once the asset is operating, not during design or fabrication.
Do the three codes share the same methodology?
Largely. All set corrosion-rate-driven intervals capped by a ceiling, separate the inspecting from the evaluating role, and increasingly use risk-based inspection. They differ in the damage mechanisms and geometry specific to piping, vessels, and tanks.
Can piping be inspected under the vessel program?
No. Piping has its own code, circuits, and damage mechanisms under API 570. Folding it into a vessel program leaves piping-specific threats such as dead legs and corrosion under insulation uninspected. Each asset class needs its own program.
Sources and verification
This page references the standards, specifications, and official documentation published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- API 653, Tank Inspection, Repair, Alteration, and Reconstruction - American Petroleum Institute
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.