InsertBase

Embed the ISO 1832 Insert Decoder

Add the InsertBase ISO 1832 turning-insert decoder to your own engineering site, blog or forum post with a single iframe. Free to use; an attribution link back to InsertBase is appreciated.

One line of code

Copy this snippet into your page HTML where you want the decoder to appear:

<iframe src="https://insertbase.com/tools/iso-1832-decoder/embed/" width="100%" height="720" frameborder="0" title="ISO 1832 insert decoder"></iframe>

Live preview

This is exactly what your readers will see:

Sizing and behaviour

  • Width — keep width="100%"; the tool is responsive down to phone screens.
  • Height — 560–720 px works for most layouts. Results expand downward, so a taller frame avoids an inner scrollbar on large decodes.
  • Theme — the embed ships one light theme designed to sit neutrally on any site. There are no cookies, no trackers and no ads inside the frame.
  • Decoding runs locally — every lookup is computed in the reader's browser from the published ISO 1832 code tables; no data leaves their machine.

What it decodes

Any standard ISO 1832 turning-insert designation — shape, clearance angle, tolerance class, fixing type, inscribed circle, thickness, nose radius, cutting edge length and hand. Brand suffixes after the dash (chipbreaker and grade codes) are flagged for catalogue verification rather than guessed. For deeper reading on the designation system, link your readers to the full decoder page or the ISO 1832 designation walkthrough.

Attribution

The embed already carries a small "InsertBase" credit line. If you write about the tool, a plain link to insertbase.com/tools/iso-1832-decoder/ is all we ask. No permission needed, no registration, no API key.

If you prefer a visual credit, this small badge is free to reuse with a link back:

Verified by InsertBase

<a href="https://insertbase.com/"><img src="https://insertbase.com/badge.svg" alt="Verified by InsertBase" width="220" height="36"></a>

Questions

Spotted a designation the decoder mishandles? Corrections are welcome — see the editorial & correction policy, or write to [email protected].