Headset standards: read SHIS, EC, ZS and IS as separate interfaces
Decode upper and lower headset references without confusing nominal head-tube codes, bearing dimensions and fork interfaces.
Published 11 October 2026 · OpenBikeFit
Headset reference · not to scale
Two interfaces. Not one diameter.
Declared code example: upper ZS44/28.6 | lower EC44/40. Families and nominal identifiers, not measured tolerances.
Upper /28.6: steerer reference. Lower /40: crown-race-seat family. Neither supplies the complete bearing dimensions.
Upper and lower support arrangements can differ. No frame/fork/headset replacement is approved.
On this page
Free blank worksheet
Keep the named reference questions
Use controlled supplementary paper notes. There are no dedicated headset fields or compatibility verdicts.
Open toolBegin with the exact frame and fork
A headset name is useful only when it belongs to an identified receiving system. Start with the frame model, generation, size and configuration, then record the fork and the installed headset independently. A specification for an original complete bicycle is not automatically a record of what remains installed today. A family name on a top cover is also not enough to establish every hidden component. Preserve the source and date of each declaration instead of merging them into a single apparently complete specification.
This guide helps read those declarations before asking a replacement question. It does not instruct you to loosen the stem, remove the fork, press cups or expose hidden surfaces to obtain a number. Use exact documentation and an existing controlled technical record first. If a reference cannot be identified non-invasively, leave it unresolved for a qualified mechanic. A blank row is more useful than a plausible number borrowed from a similar-looking bicycle because it keeps the missing evidence visible.
EC and ZS still have separate cups
The EC and ZS labels distinguish where a cup supports the bearing relative to the head tube. External-cup arrangements support the bearing outside the tube; zero-stack arrangements locate it within or near the end of the tube using a separate cup. The term zero stack does not promise zero assembly height. Keep the arrangement at each end separate. A bicycle can have one family above and another below, so do not duplicate an upper label into the lower row merely for symmetry.
The useful question is which interface a statement describes. A cup specification concerns its receiving frame arrangement; a bearing specification concerns the bearing and its seats. Neither describes stem-clamp engagement. An exposed outside diameter on a cover is a fourth kind of observation. Recording all of them under the generic heading headset diameter destroys their distinctions. Use explicit quantity names even if that makes the record longer, and keep an uncertain support arrangement as unknown rather than inferring it from the cover shape.
IS describes the frame bearing support
An integrated arrangement places the bearing against a shaped support belonging to the frame instead of a separate pressed cup of the EC or ZS kind. That distinction does not mean every component of the assembled headset is integrated into the frame. The upper cover, compression interface and fork-side reference remain independently identified parts or surfaces. Do not confuse an integrated frame bearing seat with an integrated race at the fork crown: they are at different locations and answer different questions.
The code family gives a starting description, not every contact detail. Preserve exact bearing and frame instructions rather than assuming that a familiar family determines all angles, seals or routing. This page deliberately avoids a catalogue of universal replacements. A manufacturer-specific statement can support the named assembly in its own scope without becoming permission to exchange parts between brands. Similar terminology across two sources is a reason to compare their definitions, not a reason to discard the more detailed one.
Read the upper and lower code in order
Consider the declared example ZS44/28.6 | EC44/40. Treat the vertical bar here as our separator between upper and lower records. The letters describe different support families. The nominal 44 identifiers belong to the head-tube interface family. After the upper slash, 28.6 identifies the upper steerer reference; after the lower slash, 40 identifies the crown-race-seat family. They are not two measurements of the same bearing. Keeping the two rows prevents a lower fork-seat label from being read as the upper stem-clamping diameter.
This is a code-reading example, not a specified assembly for your bicycle. It does not establish actual fits, tolerances, contact geometry or frame permission. Threaded systems also require their own thread declarations; do not delete those details to make a source resemble a threadless example. If a retailer presents only one half of the code, the other half remains unknown. Do not complete it by guessing from a photograph, a wheel size, the material of the frame or the word tapered.
Keep code and measurement in separate columns
Nominal identifiers organise interface families; they are not a machining drawing. Park Tool explicitly distinguishes its whole-millimetre SHIS identifiers from exact measurements. Record the original code unchanged beside any separately established observation, its endpoints, method and precision. Never subtract a nominal family number from an instrument reading and call the difference a clearance, interference or allowable tolerance. Those conclusions need an exact applicable specification and qualified physical verification.
A conflicting record should retain both statements. For example, a fictional worksheet might contain an upper family label in one source and an unidentified observed ring diameter in another. That is not yet a contradiction between comparable quantities because the ring may not be the receiving surface. First identify the surface and state. Do not average the numbers, round one to the nearest family or silently substitute the original-build declaration for the installed observation. Missing identity is a substantive limitation, even when the numbers look close.
Preserve details outside the short code
The complete receiving question includes the frame and fork variant, bearing identity, upper and lower contact surfaces, covers, seals and any product-specific routing arrangement. A compact identifier cannot inspect wear, damage, seating or present installation. Record which questions are not checked. A code match may narrow a documentation search; it does not certify the assembly or tell you to reuse an existing ring. This distinction remains necessary when all the familiar numbers agree.
Keep installation authority separate from reference learning. This article supplies no pressing procedure, preload amount, bolt sequence, lubricant, torque or adapter plan. An unexplained difference is not an instruction to modify a component. Exact current frame, fork and headset documentation governs permitted arrangements, with qualified inspection where needed. The browser can preserve the question but cannot examine the hidden interfaces. Do not label a completed reference record as a safe-to-ride verdict or a handling improvement.
Continue from family to the actual interfaces
Next identify the bearing dimensions and its named contact angles. Then separate the crown race from the fork seat, and finally identify the upper and lower external stack endpoints. The existing fork-length and stem/spacer guides cover their narrower geometry questions; this journey does not replace them. The free blank worksheet has general reference spaces rather than a dedicated SHIS form, so use clearly named supplementary paper notes instead of writing a headset code into an unrelated frame-length field.
Practical questions
Frequently asked questions
Does ZS mean there is no external headset height?
No. The support arrangement and its source-defined upper/lower external stack are separate.
Does the lower /40 describe my upper stem-clamping diameter?
No. In the declared example it belongs to the lower crown-race-seat family; the upper steerer reference is separate.
Can I use a SHIS code as a tolerance?
No. A nominal identifier is not an exact measurement, clearance or manufacturing limit.
Does a complete matching code approve a replacement?
No. Exact interfaces, component permissions and qualified physical checks remain independent.