What is xwOBA? Definition, Formula, and Example
xwOBA (expected weighted On-Base Average) is Statcast's quality-of-contact metric that estimates what a hitter's wOBA should be based purely on exit velocity, launch angle, and (for speed-dependent balls) sprint speed. It strips out luck, defense, and ballpark to reveal true underlying offensive skill.
What Is xwOBA?
xwOBA (expected weighted On-Base Average) is MLB's publicly available "true talent" offensive metric. It takes every batted ball a hitter puts in play, looks at the exit velocity and launch angle of that ball, and assigns it the expected wOBA value based on how similar balls have performed league-wide over the last several years. Walks and hit-by-pitches are credited at their real wOBA weights.
The result: a hitter's expected offensive output if defense, ballpark, and random variance were all removed. When a hitter's actual wOBA is much higher than xwOBA, they're overperforming (luck, weak opposing defense, hitter-friendly parks). When it's much lower, they're underperforming and due for regression upward.
xwOBA Formula
Conceptually:
xwOBA = (0.69 × uBB + 0.72 × HBP + Σ(xwOBAcon_i)) / (AB + BB – IBB + SF + HBP)
Where xwOBAcon_i is the expected wOBA value of batted ball i, looked up from a league-wide table of exit-velocity / launch-angle bins. For balls where sprint speed matters (weakly hit grounders, shallow fly balls), the lookup includes a speed adjustment.
Statcast publishes the binned xwOBAcon table; in practice you rarely calculate xwOBA by hand — you pull it from Baseball Savant or FanGraphs.
Worked Example
A hitter puts the following batted balls in play in April:
| EV (mph) | LA (°) | Outcome | xwOBA value |
|---|---|---|---|
| 102 | 27 | HR | 1.63 |
| 98 | 32 | Out (great catch) | 1.21 |
| 74 | -5 | Infield single | 0.38 |
| 88 | 18 | Out | 0.42 |
| 105 | 14 | Double | 1.05 |
Actual outcome: HR + 1B + 2B in 5 BIP = 3 hits, one HR, one 2B → strong actual wOBA.
Expected outcome: the 98 mph / 32° ball had an xwOBA of 1.21 regardless of the defensive play. Averaged across all five batted balls, his xwOBAcon is 0.938.
If this hitter kept this up over 400 batted balls and combined it with 10% walks, his xwOBA would sit around .430 — MVP territory. His actual wOBA could be .400 or .460 depending on park, defense, and luck. The xwOBA number is the more predictive.
Actual wOBA vs xwOBA: The Regression Signal
| Gap | Interpretation |
|---|---|
| Actual wOBA > xwOBA by 50+ points | Overperforming. Expect regression down. |
| Actual wOBA ≈ xwOBA (within 20) | Performance matches underlying skill. |
| Actual wOBA < xwOBA by 50+ points | Unlucky. Expect regression up. |
Front offices use this gap as a trade-market inefficiency. The hitter with a .310 actual wOBA but .370 xwOBA is the one you want. Fantasy managers use the same signal for buy-low targets.
Why xwOBA Matters in Legends Deck
Card ratings in Legends Deck are driven by xwOBA, not actual wOBA. This is deliberate. Actual results are noisy — a three-week hot streak can push wOBA 100 points above its true level. xwOBA smooths that out by measuring the *quality* of contact, not its luck-adjusted outcome.
When you see a hitter whose real-life numbers look mediocre but whose card rating is high, xwOBA is why. The math sees a true-talent MVP underneath a BABIP-unlucky surface.