Two requisitions land on the same desk. One asks for an API 600 gate valve — “NPS 8, Class 300, API 600”. The other asks for an API 6D gate valve — “NPS 8, Class 300, API 6D”. Both will be quoted, both will look like gate valves, and only one of them may actually be acceptable for the service the buyer had in mind.
The confusion is understandable, because these two standards are not rivals. An API 600 gate valve and an API 6D gate valve can come out of the same mould; the standards answer different questions.
API 600 answers: how should a steel gate valve be designed, dimensioned and assembled? API 6D answers: is this valve, as a complete product, qualified for pipeline and piping service?
A valve can be built to API 600 dimensions and still fail an API 6D purchase requirement, and an API 6D gate valve will usually follow API 600 dimensional conventions. That overlap is exactly why the distinction gets lost.
Scope of each standard: API 600 gate valve versus API 6D
| API 600 | API 6D | |
| Title | Steel Gate Valves — Flanged and Butt-welding Ends, Bolted Bonnets | Specification for Pipeline and Piping Valves |
| Valve types covered | Gate valves only | Gate, ball, check, plug and other quarter-turn or pipeline valves |
| Typical size range | NPS 2 to NPS 48 (DN 50 to DN 1200) | NPS 2 upward; large diameter pipeline sizes included |
| Pressure classes | Class 150 to Class 2500, per ASME B16.34 | Class 150 to Class 2500 and above by agreement |
| Nature of the document | Design, material and dimensional requirement | Full product specification: design, qualification, testing, documentation, marking |
| Governing dimensional references | ASME B16.5 / B16.47 flanges, ASME B16.10 face-to-face, ASME B16.25 butt-weld ends | Often the same references, plus pipeline-specific requirements |
| Pressure testing | Referenced to API 598 | Testing is a mandatory part of the specification, with defined acceptance |
The practical reading: for an API 600 gate valve, the standard tells a manufacturer how to make the component. API 6D tells the buyer what evidence and behaviour they may demand from the finished valve.
Seven differences that show up in a purchase order
- Documentation depth.API 6D requires a defined documentation package — material traceability, inspection and test records, and marking tied to the specific valve. An API 600 valve can be delivered with far less paperwork unless the purchaser writes the requirement in. If you need an EN 10204 3.1 or 3.2 certificate, say so in the requisition; it is not automatic.
- Testing regime.API 6D makes pressure testing and the acceptance criteria part of the product definition and adds a functional or operating test dimension. For an API 600 gate valve, testing follows API 598, which is thorough for shell and seat integrity but narrower in scope. See our breakdown of API 598 and ISO 5208 testing for what each test actually proves.
- Fire-safe expectation.For pipeline and hydrocarbon service, fire-safe qualification to API 607 or API 6FA is commonly specified. API 600 itself does not require it. If the valve is going near hydrocarbons in a populated area, this belongs in the specification either way.
- Double block and bleed and cavity relief.API 6D addresses DBB arrangement, drain and vent connections, and pressure relief of the body cavity for double-seated designs. These features are purchasable under API 600 too, but they must be requested explicitly.
- Quality control requirements.API 6D carries structured requirements on the manufacturer’s quality system, non-conformance handling and traceability of components. This is the part that buyers rarely see and quietly benefit from when a problem appears two years later.
- Marking and monogram.If a valve carries an API monogram, that is a statement about a licensed quality programme, not just about conforming dimensions. A valve that is “designed and manufactured in accordance with API 600” is not the same as a monogrammed valve, and the two must never be described as equivalent in a quotation or on a nameplate.
- Cost and lead time.Expect API 6D valves to cost more for the same size and class than an API 600 gate valve, and to take longer to produce. The delta is not in the castings or the machining — it is in the traceability, the inspection hold points, the paperwork and the risk the manufacturer carries.
Which one does your line actually need?
Use this as a first filter:
- Crude, product, gas transmission and gathering lines, pump and compressor stations→ API 6D. The service expectation, the documentation requirement and often the fire-safe requirement all point there.
- General plant piping, utility lines, steam headers, water and cooling systems→ an API 600 gate valve is normally sufficient, subject to the project specification.
- Anywhere the buyer’s own specification already exists→ follow it. Most EPC and operator specifications name the governing standard, and adding a second one creates conflict rather than safety.
- Where a client insists on API 6D features but the line is ordinary plant piping→ request the specific features (testing, DBB, fire-safe, documentation) rather than switching standards wholesale. It is usually cheaper and better targeted.
How to remove the ambiguity from a requisition
The failure mode is not a wrong standard; it is an underspecified one. Four lines fix most of it:
- Name the standard and revision, e.g. “API 600 (current edition)” or “API 6D (current edition)”.
- State the valve’s intended service in one sentence — medium, temperature, pressure, sour or sweet, continuous or intermittent.
- List the required documentation level explicitly, including whether a third-party witness is required.
- State the required leakage acceptance criteria rather than leaving it to the manufacturer’s default.
That last point is where the most expensive disputes start. “Zero leakage” means different things to a factory running a soft-seated test and to a pipeline operator reviewing a metal-seated test certificate.
Frequently asked questions
Can an API 600 gate valve be used in pipeline service? It can, if the purchaser specifies the pipeline-related requirements — testing, documentation, fire-safe qualification, DBB and cavity relief. What it cannot do is claim API 6D compliance without being built and documented to that specification.
Is an API 6D gate valve always better? It is better documented and better qualified, which is not free. On a cooling water line, an API 600 gate valve does the same job and the extra cost buys nothing. Choose on service criticality, not on the prestige of the standard number.
Does API 6D cover ball valves as well? Yes. API 6D covers pipeline ball, gate, check and plug valves. API 600 is gate valves only.
What if the manufacturer holds an API licence for one but not the other?
That is a real and common situation. Ask for the licence scope in writing and check the scope covers the valve type and size you are buying. Licence scope is narrow, and “we are API certified” without a scope document is not an answer.
Is it acceptable to mix the two — API 600 body dimensions with API 6D testing?
Yes, and it is common practice, provided the purchase order says so clearly and the face-to-face dimension still matches the piping drawing.
Reviewed by our engineering team. Last updated 2026-09-14.
We build API 600 and API 6D gate valves and can supply either the standard product or a project-specific package with third-party inspection. Send your line list and we will tell you which standard your service actually calls for — including when the answer is the cheaper one.
