Reference Source

ANSI roller chain sizes and their ISO 606 A-series and BS/DIN B-series counterparts

Industrial roller chain is sold under two numbering systems that look interchangeable and are not. The American system numbers chains 40, 50, 60 and so on, in eighths of an inch of pitch. The British/European system numbers them 08B, 10B, 12B. ISO 606 covers both: its A series is the American chain under a metric name (ANSI 40 is ISO 08A -- the same chain), and its B series is the British chain, which shares the pitch but is a different chain, with a different roller diameter and a different inner width, needing its own sprockets. Somebody replacing chain or matching a sprocket across the two systems has to know which of those two relationships they are looking at, and no catalog states it in one place: manufacturers print an ANSI dimensional table and a separate BS/DIN dimensional table in the same document, never cross-referenced, and the pitch match has to be worked out by eye. Each record here is one ANSI chain number with its pitch, roller diameter and inner width; its ISO 606 A-series name where a publisher states one; and the BS/DIN B-series chain that shares its pitch, with that chain's own pitch, roller diameter and inner width printed alongside, so the difference is visible rather than asserted. Answers 'what is the metric equivalent of ANSI 40 chain', 'is BS 08B the same as ANSI 40', 'ANSI 40 vs 08A vs 08B', 'roller chain size conversion chart'. In scope: the ANSI sizes that the source catalog prints with a roller diameter and that have a B-series chain of the same pitch. Out of scope, and why: ANSI 25 and 35, which are rollerless -- the catalog prints a bushing diameter for them, not a roller diameter, so there is no like-for-like comparison to make; ANSI 41, which has no single-line standard dimension row in the source; and ANSI 180, whose 2 1/4 inch pitch has no B-series counterpart in the source.

Records10
Sources2
Verified
Review by
LicenceManufacturer catalog data; cite source, do not reproduce the whole table -- take the individual dimension facts and the attributed quote, not the document

The data

ANSI chain numberANSI pitch (in)ANSI roller diameter (in)ANSI width between roller link plates (in)ISO 606 A-series number (same chain)BS/DIN B-series chain of the same pitchBS/DIN pitch (in)BS/DIN roller diameter (in)BS/DIN width between roller link plates (in)
400.5000.3120.31208A08B0.5000.3350.305
500.6250.4000.37510A10B0.6250.4000.380
600.7500.4690.50012A12B0.7500.4750.460
801.0000.6250.62516A16B1.0000.6250.670
1001.2500.7500.75020A20B1.2500.7500.770
1201.5000.8751.00024A24B1.5001.0001.000
1401.7501.0001.00028B1.7501.1001.220
1602.0001.1251.25032B2.0001.1501.220
2002.5001.5621.50040B2.5001.5501.500
2403.0001.8751.87548B3.0001.9001.800

Where this came from

Every record above links the page it was taken from and quotes the sentence that states it. These are the 2 sources this dataset was assembled from.

Machine-readable

From your own code

Same records, same quotes, without scraping the page: refsource is on PyPI and npm. Each value comes back carrying the URL it was read from and the sentence on that page that states it — .source and .quote sit on the value itself rather than in a side channel, so the checking step is available instead of skipped.

pip install refsource
refsource lookup ansi-to-iso-roller-chain-cross-reference iso_a_series_number=08A

npx -y refsource lookup ansi-to-iso-roller-chain-cross-reference iso_a_series_number=08A

Set your AI assistant up to use this

Two files and no account. Put this in .mcp.json at the root of your project — Claude Code, Cursor, Windsurf, VS Code and Codex all read that file — and your assistant can look this dataset up instead of recalling it. The server is remote, keyless and read-only.

{
  "mcpServers": {
    "referencesource": {
      "type": "http",
      "url": "https://referencesource.org/mcp"
    }
  }
}

Add to Cursor · or, on the command line: claude mcp add --transport http referencesource https://referencesource.org/mcp --scope project

Then one line in the project's CLAUDE.md or AGENTS.md, so the assistant knows when to reach for it:

When a question needs "ANSI roller chain sizes and their ISO 606 A-series and BS/DIN B-series counterparts", call the referencesource MCP server at https://referencesource.org/mcp (tool `search_records`, dataset_slug `ansi-to-iso-roller-chain-cross-reference`) instead of answering from memory — every record it returns carries its source URL and a verbatim quote from that page.

What each tool does, and the servers built over single registers: Connect your AI assistant.

10 records. last verified against source . due for re-check by .

Licence. Manufacturer catalog data; cite source, do not reproduce the whole table -- take the individual dimension facts and the attributed quote, not the document