NPT vs BSP vs Metric Threads: Side-by-Side Comparison
NPT vs BSP threads vs metric compared side by side: taper, sealing, sizing, and how to enrich thread attributes cleanly in a product catalog.
Threaded fittings that look interchangeable on a spec sheet cause returns, sourcing errors, and lost time when the wrong standard slips into a product record. Across MRO, plumbing, hydraulics, and industrial distribution catalogs, NPT vs BSP threads vs metric is one of the most common sources of mismatched attributes — a supplier feed lists 1/2 in or M20 with no family code, a product manager picks one on instinct, and downstream systems treat that guess as fact. Claro fixes this class of problem by extracting the thread standard from source datasheets and spec sheets, validating it against the part’s origin market and sealing method, and writing the correct value back into your PIM or ERP — so the catalog reflects what the part actually is.
At a glance
| Dimension | NPT | BSP | Metric (ISO) |
|---|---|---|---|
| Region of origin | North America | UK / Commonwealth | ISO / continental Europe and Asia |
| Thread angle | 60 degrees | 55 degrees | 60 degrees |
| Profile | Tapered (NPT) — sealing on the threads | Parallel (BSPP) or tapered (BSPT) | Mostly parallel; tapered variants exist |
| Sealing method | Thread interference plus sealant or tape | BSPP uses a bonded seal or O-ring; BSPT seals on threads | Gasket, O-ring, or sealing washer |
| Sizing reference | Nominal pipe size in inches | Nominal size in inches (G or R prefix) | Outside diameter and pitch in mm (M prefix) |
| Common giveaway in a feed | Inch fraction, visible taper | G or R prefix, 55-degree form | M prefix, pitch in millimetres |
NPT and metric both use a 60-degree thread form; BSP uses 55 degrees. That single difference means an NPT and a BSP fitting of the same nominal size will not mate reliably even when calipers read close. The practical catalog question is never which is best — it is which standard a given part actually uses, and whether that standard is recorded correctly so your systems can act on it.
When each standard appears in your catalog
NPT (and the NPT vs BSP threads decision)
NPT (National Pipe Taper) dominates North American plumbing, pneumatics, and process piping. The taper means the thread tightens and seals as it is driven, usually with PTFE tape or pipe dope. If your catalog serves US and Canadian trades, NPT is your default, and the NPT vs BSP threads decision usually comes down to destination market and the mating equipment already in the field. Record it as NPT — or NPTF for the dryseal variant — plus the nominal pipe size. When supplier feeds omit the family and only carry the fraction size, Claro’s enrichment layer identifies the gap and resolves it from the source datasheet rather than guessing.
BSP
BSP (British Standard Pipe) is the Commonwealth and much of Asia-Pacific standard, split into parallel (BSPP, marked G) and tapered (BSPT, marked R). BSPP relies on a bonded seal or O-ring at the face rather than on the threads, so sealing behaviour differs fundamentally from BSPT even though both carry the BSP family label. A furniture importer sourcing UK-made gas struts or a hydraulics distributor handling European machinery will see BSP throughout their supplier feeds. Capture the G or R designation explicitly — 1/2 BSP alone hides whether the part seals on the face or on the taper, and that ambiguity drives fit-for-purpose returns.
Metric (ISO)
Metric threads (M series) are defined by outside diameter and pitch in millimetres, most common in European and Asian machinery, automotive, and general fasteners. A CPG packaging-line operator or an OEM-parts reseller will lean metric. Sealing is handled by a washer, gasket, or O-ring rather than the thread form. Record both diameter and pitch (M20 x 1.5), because the same diameter ships in coarse and fine pitches that are not interchangeable and must be stored as separate, discrete attribute fields.
Before and after: messy vs trusted thread data
The table below shows what thread records look like when they arrive from a typical supplier feed versus how they look after Claro enriches and validates them against source documentation.
| Before — raw supplier feed | After — Claro-enriched record |
|---|---|
| Size: '1/2 in' — no standard family | Standard: NPT | Size: 1/2 in | TPI: 14 | Gender: Male | Seal: taper + PTFE |
| Description: 'BSP fitting 3/4' — no G or R | Standard: BSPP (G) | Size: 3/4 in | Seal: bonded face seal |
| Thread: 'M20' — pitch missing | Standard: Metric ISO | OD: 20 mm | Pitch: 1.5 mm (fine) | Seal: sealing washer |
| Free-text: 'half-inch pipe thread' | Standard: NPT | Size: 1/2 in | TPI: 14 | flagged for human review |
| Multiple fields merged: '1/2 NPT Male' | Parsed into: Standard, Size, TPI, Gender — separate queryable attributes |
Structured thread attributes become filterable facets, reliable match keys for deduplication, and citable facts for AI shopping assistants. Claro identifies the gaps, resolves the correct value from source documents, and writes each attribute back into your existing PIM or ERP — with full provenance so you can always see where the value came from.
Recording thread data cleanly
For catalog and PIM records, split the thread into discrete, queryable attributes instead of one free-text string:
- 1Standard familyNPT, NPTF, BSPP (G), BSPT (R), or Metric (M).
- 2Nominal sizeInches for pipe standards, millimetres for metric.
- 3Pitch or TPIThreads per inch for inch standards, pitch in mm for metric.
- 4Gender and sealMale or female, and the sealing method (taper, bonded seal, O-ring, washer).
Teams that need to normalize these fields across thousands of supplier SKUs — or onboard a new range without breaking existing records — standardize the extraction step rather than cleaning by hand. The identify thread diameter and pitch playbook walks through how to do this systematically.
Related
Tool
Thread Size Cross-Reference
Look up and compare thread designations across NPT, BSP, and metric in one place.
Playbook
Identify Thread Diameter and Pitch
Step-by-step process for measuring and recording thread specs from physical parts or datasheets.
Comparison
NEMA vs IP Ratings
Another spec family where the standard, not just the number, drives correct catalog data.
Glossary
What Is Unit of Measure (UOM)?
Why inch-versus-millimetre handling matters across an industrial catalog.
Guide
58 Fields in a Complete Product Record
Where thread attributes fit in a complete, AI-ready product record.
Guide
Fill Missing Attributes With Provenance
How to enrich blank thread and spec fields without guessing.
FAQ
Are NPT and BSP threads interchangeable?
No. NPT uses a 60-degree thread angle and BSP uses 55 degrees, so even at the same nominal size they will not seal reliably and can cross-thread or leak. Use a dedicated adapter when joining the two families, and record each part’s standard separately so your catalog never implies they match.
How can I tell NPT from BSP on a fitting?
NPT threads are tapered and sized by nominal inch fractions. BSP is marked with a G (parallel) or R (tapered) designation and uses the 55-degree form. If the part is unmarked, a thread gauge that checks both the pitch and the angle is the reliable way to confirm; visual taper alone is not enough.
Is metric the same as BSP because both can be parallel?
No. A parallel thread is not a standard on its own. BSPP is defined in inches with a 55-degree form, while metric (M) threads are defined by diameter and pitch in millimetres with a 60-degree form. They are not interchangeable, so store the standard family explicitly rather than just noting that a thread is parallel.
What should a product record capture for a threaded part?
Capture the standard family, nominal size, pitch or threads per inch, gender, and sealing method as separate fields. Splitting them out makes the data filterable, usable as match keys for deduplication, and citable by AI shopping assistants, rather than locked in one ambiguous free-text string.
My supplier feed only lists the size with no standard. What do I do?
Treat the standard family as missing and flag it for enrichment instead of inferring it from the size. The correct family usually comes from the source datasheet, the manufacturer’s series, or the destination market. Recording a guessed standard is riskier than leaving it blank, because downstream systems read it as fact. Claro identifies these gaps across a supplier feed and enriches each record from source documents, writing the validated value back into your PIM or ERP.
How does Claro help when thread attributes arrive inconsistently across supplier feeds?
Claro resolves identity across supplier SKUs, extracts the thread standard family from datasheets and spec PDFs, and validates the enriched value before writing it back into your existing PIM or ERP. That means thread attributes become filterable facets and reliable match keys, not free-text noise that causes returns and sourcing errors downstream.
Claro
Stop maintaining this by hand
Claro keeps product and supplier data trusted as catalogs change — matching, deduplication, enrichment, and validated write-back into the systems you already run.
Book a demo