WAR Calculator (Wins Above Replacement)

WAR Calculator – Wins Above Replacement

Estimate position-player or pitcher WAR from the component values used in a FanGraphs-style summary framework.

Player type Position player WAR 6.16 Band MVP range

Example workbook is ready.

Inputs

Choose the matching WAR equation. Switching modes keeps the example values available.

Position-player WAR adds run-value components, then divides the total runs above replacement by runs per win.

runs

Runs above or below average attributable to batting. Signed values are allowed.

runs

Baserunning value relative to average; negative values reduce WAR.

runs

Defensive run value above or below average.

runs

Adjusts for the defensive position and playing time.

runs

Small league-balancing adjustment, expressed in runs.

runs

Runs added to move the baseline from average to replacement level; must be nonnegative.

runs/win

Season run environment used to convert runs above replacement into wins; must be greater than zero.

Live results

Wins Above Replacement (WAR) 6.16

A rule-of-thumb MVP-range result. Treat WAR as an estimate, not a perfectly precise ranking.

Runs above replacement57.10 runs
Runs above average36.40 runs
General WAR bandMVP range

WAR is 6.16.

Calculation breakdown

Component Model value Contribution / role
Batting runs 46.30 runs +5.00 wins before other components
Base running runs -0.60 runs -0.06 wins before other components
Fielding runs 2.20 runs +0.24 wins before other components
Positional adjustment -12.30 runs -1.33 wins before other components
League adjustment 0.80 runs +0.09 wins before other components
Replacement runs 20.70 runs +2.23 wins before other components
The signed component rows are shown as a table rather than a part-to-whole chart because positive and negative run values do not form a valid pie or donut total.

How to use this WAR calculator

What this calculator does. Wins Above Replacement (WAR) is a summary estimate of how many wins a player contributes compared with a readily available replacement-level alternative. This tool follows the compact FanGraphs-style equations commonly used to explain WAR: position-player WAR combines batting, baserunning, fielding, positional, league, and replacement run values and converts the total from runs to wins; pitcher WAR starts from the gap between league FIP and pitcher FIP, converts that gap with pitcher-specific runs per win, adds replacement level, scales by innings and leverage, and applies a league correction. WAR is useful as a broad value estimate, but it is not a scouting grade, a prediction of future performance, or a claim that two players separated by a few hundredths of a win are meaningfully different. MLB's WAR glossary definition and formula overview explains the same replacement-level concept and why different public WAR systems can differ.

When to use it. Use the position-player mode when you already have the player's component run values and want to translate them into one WAR estimate. Use pitcher mode when you have the FIP-based summary inputs used by the pitcher equation. It is also useful for checking a published component breakdown, stress-testing how a different run environment changes the final WAR, or teaching how replacement level and playing time enter the statistic.

How to calculate. The calculator opens with a ready-to-use position-player demonstration based on a well-known FanGraphs worked-example component set, and its Excel workbook is immediately available. To use your own data:

  1. Choose Calculate WAR for as either Position player or Pitcher. The results and breakdown table switch to the equation for that player type.
  2. Replace the demonstration values with your own signed decimal inputs. A period is the decimal separator; commas, scientific notation, percent signs, and mixed-unit text are rejected rather than silently reinterpreted.
  3. Read Wins Above Replacement (WAR) first, then use the secondary results and the Calculation breakdown table to see which pieces drive the total. The calculator updates live.
  4. Select Download Excel to export the current valid state as a real .xlsx workbook containing Summary, Inputs, Breakdown, and Notes sheets. Reset clears all demonstration/input data and the calculated state; after Reset, Download Excel is disabled until the active mode once again has a complete valid set of values.

Input guide – position players. Batting runs, Base running runs, Fielding runs, Positional adjustment, and League adjustment are required signed run values; examples are 46.3, -0.6, 2.2, -12.3, and 0.8 runs. Higher values increase WAR and lower or negative values reduce it. A common mistake is treating these as percentages or raw box-score counts rather than already-computed run values. Replacement runs is a required nonnegative run value, 20.7 in the example; it shifts the baseline from league average to replacement level. Runs per win is a required positive decimal in runs per win, 9.264 in the example. Increasing runs per win while holding the numerator fixed lowers WAR because more runs are needed for one win in that run environment. FanGraphs' position-player WAR methodology describes how these components are constructed before they reach the final summary equation.

Input guide – pitchers. Pitcher-specific runs per win is a required positive decimal, such as 9.7, used to turn the FIP gap into a wins-per-nine rate. League FIP and FIP are required finite decimals such as 4.20 and 3.25; a lower pitcher FIP relative to league FIP raises the above-average term. Replacement level is a required nonnegative wins-per-nine allowance such as 0.12. Innings pitched is required and nonnegative; 180 IP scales a per-nine result over 20 nine-inning units. Leverage multiplier for relievers is required and must be positive; 1.00 means no additional leverage scaling. League correction is a required signed WAR value such as -0.12 and is applied at the end. Do not paste ERA, winning percentage, or a leverage index into a field expecting a different unit.

Output guide. Wins Above Replacement (WAR) is the primary estimated win value and may be negative. In position-player mode, Runs above replacement is the exact numerator before division by Runs per win, and Runs above average is the sum of the five average-relative components before replacement runs. In pitcher mode, the first secondary output becomes WAR before league correction, while the second is Wins per 9 above replacement. General WAR band and the header Band pill apply a broad rule-of-thumb category to the numerical WAR; these labels are interpretive, not additional calculations. The header Player type and WAR pills simply repeat the active mode and primary value for scanning. In the table, Component names the equation term, Model value shows its current numeric value and unit, and Contribution / role explains how that term enters the equation. The table is a transparent calculation aid, not a separate model.

Worked example. The first-open position-player values are 46.3 batting runs, -0.6 baserunning runs, 2.2 fielding runs, -12.3 positional runs, 0.8 league-adjustment runs, and 20.7 replacement runs. Their total is 57.1 runs above replacement. Dividing 57.1 by 9.264 runs per win gives 6.163... WAR, displayed as 6.16. The pre-replacement sum is 36.4 runs above average. On the broad interpretive scale used here, a value of at least 6 falls in the MVP range; because WAR is an estimate, the band is more useful than over-interpreting the second decimal place.

Learn more. For the pitcher branch, FanGraphs' pitcher WAR methodology explains why FIP, pitcher-specific runs per win, innings, replacement level, leverage, and a final league correction are used. It also emphasizes that the detailed public calculation has additional upstream steps; this calculator intentionally starts from the already-prepared summary inputs shown in the form.

How the formulas work

Position player: WAR = (Batting runs + Base running runs + Fielding runs + Positional adjustment + League adjustment + Replacement runs) ÷ Runs per win.

Pitcher: WAR = [((League FIP – FIP) ÷ Pitcher-specific runs per win + Replacement level) × (Innings pitched ÷ 9) × Leverage multiplier] + League correction.

The formulas look compact because the difficult work is upstream. Batting runs, fielding runs, positional adjustments, FIP, run-environment conversions, and league corrections are themselves derived statistics. Public WAR implementations therefore do not always agree. FanGraphs' WAR overview and interpretation guidance notes that WAR is best read as an estimate and that the broad range matters more than tiny decimal differences.

Interpreting WAR responsibly

A WAR near zero suggests performance close to a replacement-level alternative in the chosen framework; negative WAR means the model values the player's contribution below that baseline. Roughly 2 WAR is often associated with an average full-season regular or starter, while larger positive values indicate progressively more value above replacement. The calculator's broad labels are intentionally coarse: under 1 is replacement/bench range, 1 – 2 is role-player range, 2 – 3 is solid-starter range, 3 – 4 is good-player range, 4 – 5 is All-Star range, 5 – 6 is superstar range, and 6 or more is MVP range.

Comparisons are most meaningful when the underlying components come from the same WAR provider and season context. Mixing a runs-per-win value from one run environment with component values derived under another methodology can create a mathematically valid but conceptually inconsistent result. The same issue applies to pitcher inputs: the FIP and league FIP should be comparable, and leverage or league correction terms should come from the same framework. Use the table and exported workbook to retain those assumptions alongside the final number.