OneMorePoint

T-Shirt Size to Story Points Converter

Free tool
T-shirt size
MappingYour team's own agreement - edit any value
3

M3 points

  • This mapping is a team-level agreement, not a fact - the default (1, 2, 3, 5, 8, 13) is a starting point, not a standard.
  • A mapping this loose is fine for roadmap-level rounding, but it reintroduces some of the precision debate t-shirt sizing exists to avoid - don't rely on it for sprint-ready story points.

Size sprint-ready stories with real points instead.

Why there's no universal conversion

There is no standard mapping from t-shirt sizes to story points, for the same reason there's no standard conversion from points to hours: both scales are relative to a specific team's own calibration, not universal units. This tool ships with a common default (XS=1, S=2, M=3, L=5, XL=8, XXL=13, following the usual Fibonacci-ish gaps) because most teams start somewhere close to it - but it's a starting point to edit, not an answer to look up.

When a mapping is genuinely useful

Teams that use t-shirt sizing for early, roadmap-level sizing sometimes need a rough points-equivalent later - for a burndown chart, for comparing roadmap items to sprint-level stories, or for a stakeholder used to seeing a number. A mapping makes that translation possible, as long as everyone remembers it's an approximation layered on top of an already-rough estimate, not a precise conversion.

The honest limitation

Converting a t-shirt size to points doesn't add precision that wasn't there - an XL converted to "8 points" is still exactly as rough as the XL vote that produced it. Using the converted number as if it carries the same confidence as a real Scrum Poker vote quietly reintroduces the false precision t-shirt sizing was chosen to avoid in the first place.

Frequently asked questions

There isn't one - both scales are relative to a team's own calibration. This tool ships a common default (XS=1, S=2, M=3, L=5, XL=8, XXL=13) as an editable starting point, not an official answer.