OPS adds on-base percentage (OBP) to slugging percentage (SLG) and produces a single number that correlates well with run scoring — but that addition hides which half of the equation a player actually delivers. Two hitters at .900 OPS can generate runs through completely different mechanisms, and those mechanisms determine where they belong in a batting order, how they perform against left-handed pitching, and whether they complement or duplicate the hitters around them.
What OPS Actually Measures
OBP measures how often a batter reaches base — hits, walks, and hit-by-pitches divided by plate appearances (minus intentional walks and sacrifice hits, per the MLB glossary). SLG measures total bases per at-bat: singles count once, doubles twice, triples three times, home runs four times. Adding them together is arithmetically convenient but statistically impure — OBP is per plate appearance while SLG is per at-bat, so the denominators don't match. The sum still correlates strongly with runs, which is why it persists, but it treats a point of OBP and a point of SLG as equivalent when they are not.
A player who posts a .420 OBP and a .480 SLG reaches .900 OPS through patience and contact. A player who posts a .340 OBP and a .560 SLG reaches the same .900 through raw power. Strip away the composite number and you have two different hitters.
The Lineup Construction Problem
Batting order construction depends on sequencing. A high-OBP hitter creates baserunners; a high-SLG hitter drives them in. Placing two power-heavy .900 OPS hitters back-to-back in spots three and four accomplishes less than pairing a high-OBP hitter in front of a high-SLG hitter — the power bat has more runners to score.
This is not theoretical. Research on run-expectancy tables at Baseball Reference shows that the value of a home run scales with baserunner state. A solo shot scores one run regardless of lineup construction. A three-run homer requires two runners on base, which requires OBP earlier in the order.
Speed compounds the OBP effect. A .400 OBP hitter who steals bases at a high success rate (roughly 75% or better is the break-even threshold in most run-expectancy models) advances into scoring position without requiring a hit, putting additional pressure on defenses and pitchers. That same stolen-base threat is irrelevant if the hitter's .900 OPS is slugging-driven — a player with a .340 OBP simply reaches base too infrequently to run.
Worked Example: Two .900 OPS Seasons
Consider two hypothetical stat lines across 550 plate appearances:
Player A — OBP-driven:
- 155 hits, 75 walks, 4 HBP, 3 SF, 520 at-bats
- Singles: 110, Doubles: 35, Triples: 7, HR: 3 → Total bases: 110 + 70 + 21 + 12 = 213
- OBP: (155 + 75 + 4) ÷ (520 + 75 + 4 + 3) = 234 ÷ 602 = .389
- SLG: 213 ÷ 520 = .410
- OPS: .389 + .410 = .799 (adjusted to reach .900 for illustration — bump HR to 18, total bases to 249)
- Revised SLG: 249 ÷ 520 = .479; OPS: .389 + .479 = .868 — close enough to illustrate the split
Player B — SLG-driven:
- 135 hits, 45 walks, 2 HBP, 3 SF, 520 at-bats
- Singles: 70, Doubles: 28, Triples: 2, HR: 35 → Total bases: 70 + 56 + 6 + 140 = 272
- OBP: (135 + 45 + 2) ÷ (520 + 45 + 2 + 3) = 182 ÷ 570 = .319
- SLG: 272 ÷ 520 = .523
- OPS: .319 + .523 = .842
Neither line hits exactly .900, but the ratio tells the story: Player A reaches base roughly 7 points more per opportunity while Player B generates 44 more total bases per 520 at-bats. Player A bats leadoff or second and sets the table. Player B bats third or fourth and clears it. Dropping Player B into the leadoff spot wastes his power because the bases behind him are empty; moving Player A to cleanup wastes his OBP because he rarely drives in runs on his own.
You can run either stat line through the OPS calculator to confirm the arithmetic and test how changing walk rates or isolated power shifts the composite number.
Why OPS+ Doesn't Fully Solve This
OPS+ (park- and league-adjusted OPS, scaled to 100) normalizes for context but still collapses the two components. A 130 OPS+ tells you a hitter is 30% above league average; it does not tell you whether that advantage comes from getting on base or hitting for power. For lineup purposes, the component split remains the essential question.
wRC+ (weighted Runs Created Plus, available at FanGraphs) weights OBP more heavily than SLG because research shows on-base events are slightly more valuable per unit than slugging events. That weighting is why a high-OBP player often outperforms his OPS rank in wRC+ — the composite metric undervalues his actual run contribution.
Platoon and Park Factors
The OBP/SLG split also drives platoon decisions. Power hitters tend to show larger platoon splits — a right-handed slugger may carry a .560 SLG against lefties and a .430 against righties. A high-OBP contact hitter's splits are typically narrower because walk rates don't fluctuate as dramatically with pitcher handedness. A manager relying solely on OPS when setting a platoon will miss this asymmetry.
Park factors interact differently with each component too. A pitcher's park suppresses SLG more than OBP — fly balls die at the warning track while walks remain walks. A player with a .900 OPS built on power will see that number deflate more in Petco Park than a player whose .900 is OBP-driven.
This same logic applies across sports whenever a composite metric bundles different skills — similar to how yards per attempt isolates QB efficiency rather than letting volume obscure decision-making quality.
Frequently asked questions
What is a good OPS in MLB?
League-average OPS in recent MLB seasons has ranged from roughly .720 to .740. An OPS above .800 is considered above average, above .900 is excellent, and above 1.000 is elite — but those thresholds shift with league-wide offensive environment, so OPS+ (indexed to 100 = league average) is more stable for cross-era comparisons.
Does OPS predict runs better than batting average?
Yes. OPS correlates more strongly with team run scoring than batting average because it captures both the frequency of reaching base and the value of extra-base hits. Batting average treats all hits equally and ignores walks entirely.
Why is OBP weighted more heavily in advanced metrics like wRC+?
Run-expectancy research shows that an additional point of OBP is worth slightly more than an additional point of SLG because getting on base is a prerequisite for scoring. wRC+ applies those empirically derived weights rather than the 1:1 addition OPS uses.
Can two players with identical OPS have different values to a team?
Yes, and the difference can be significant. The player whose OPS is OBP-driven creates more baserunner opportunities for teammates behind him; the SLG-driven player drives in more runs when runners are already on. The same composite number represents different lineup functions.
How does park factor affect OPS components differently?
Pitcher-friendly parks suppress fly-ball distance more than they suppress walk rates, so SLG drops more than OBP in those environments. A power hitter's OPS will be more sensitive to park context than a contact/walk hitter's OPS, which matters when comparing players across different home parks.
Informational only, not professional advice.