A hitter goes 2-for-4 with two singles, while another goes 1-for-3 with a home run and a walk. Batting average prefers the first line: .500 beats .333. OPS prefers the second because it rewards both reaching base and hitting for power. That contrast explains why modern analysis usually treats OPS as the more informative snapshot, even though batting average still describes how often a player records a hit.
What batting average actually measures
Batting average is calculated by dividing hits by official at-bats. A player with 150 hits in 500 at-bats has a .300 average. The statistic is familiar, easy to calculate and tied to one of baseball’s basic outcomes: reaching safely with a hit.
Its simplicity is also its limitation. Batting average treats a single and a home run exactly the same because each counts as one hit. It also excludes walks, so it does not fully measure a hitter’s ability to avoid outs. Sacrifice flies, hit-by-pitches and other plate-appearance outcomes sit outside the formula.
Batting average therefore answers a narrow question: how often did the player get a hit in an official at-bat? It does not answer the broader question teams care about most: how much offensive value did the hitter create?
OPS explained in plain language
OPS stands for on-base plus slugging. It adds on-base percentage to slugging percentage. On-base percentage measures how often a hitter reaches through hits, walks and hit-by-pitches, while slugging percentage measures total bases per at-bat and gives extra weight to doubles, triples and home runs.
If a player has a .360 on-base percentage and a .480 slugging percentage, his OPS is .840. The figure is not a true percentage, and its two components use different denominators, so OPS is not mathematically perfect. It remains popular because one number captures two central skills: reaching base and hitting for power.
When comparing on-base percentage vs slugging, neither component should be ignored. A patient hitter can help an offence without a high batting average. A powerful hitter can create runs with extra-base hits despite frequent strikeouts. OPS combines those contributions better than average alone.
Where batting average can mislead
It gives every hit equal value
A .280 hitter whose hits are mostly singles may contribute less than a .250 hitter with many doubles and home runs. Batting average cannot distinguish between those profiles. OPS can, because extra-base hits raise slugging percentage more than singles do.
It ignores walks
Suppose two players each collect 25 hits in 100 at-bats. Both hit .250. One also draws 20 walks, while the other draws two. Their averages look identical, but the first player reaches base far more often. OPS reflects that difference through on-base percentage.
It can swing in small samples
Some batted balls find gaps, while equally well-struck balls go directly to defenders. Speed, contact quality and positioning matter, but short-term batting average can move because of where balls land. It is risky to judge a hitter from a few weeks of results.
Why OPS usually tells you more
OPS gives credit for two things directly connected to scoring runs: avoiding outs and gaining extra bases. A walk extends an inning, while an extra-base hit can move runners farther or score them immediately. Batting average captures only the hit portion of that value.
OPS is not complete. It excludes baserunning, stolen-base value and situational context. It also treats one point of on-base percentage as equal to one point of slugging, even though the values are not truly identical. More advanced metrics handle those relationships more precisely. Even so, OPS is fast, widely available and usually more revealing than batting average.
A practical head-to-head example
Imagine Player A bats .305 with a .340 on-base percentage and a .410 slugging percentage. His OPS is .750. Player B bats .265, but posts a .370 on-base percentage and a .500 slugging percentage, producing an .870 OPS.
Player A gets hits more frequently, so batting average ranks him first. Player B reaches base more often overall and does considerably more damage when he connects. For choosing the stronger offensive player, OPS points to Player B, and the components explain why.
The practical lesson is to check all three figures together. Start with batting average for hit frequency, then examine on-base percentage and slugging percentage for patience and power. OPS gives the summary, while the components reveal the player’s style.
How OPS+ improves the comparison
OPS plus, written as OPS+, adjusts a player’s OPS for league scoring levels and ballpark effects. It is scaled so that 100 represents league average. An OPS+ of 120 means the hitter performed about 20 percent better than league average after those adjustments, while an 80 indicates performance about 20 percent below average.
This matters because raw OPS is affected by context. A favourable offensive park may boost a hitter, while another player works in a pitcher-friendly environment. League offence also changes across eras. A raw .800 OPS may be outstanding in one season and merely good in another. OPS+ makes cross-team and historical comparisons more meaningful.
OPS+ still measures hitting rather than total player value. It does not include defence or baserunning, and it should not be confused with wins above replacement. At the plate, however, it is usually more informative than raw OPS and far more complete than batting average.
When batting average is still useful
Batting average has not become meaningless. It describes contact outcomes in a way OPS does not. A high-average hitter may be especially capable of handling two-strike counts, using the whole field or producing hits against difficult pitching. Average can also explain why two players with similar OPS totals have different offensive styles.
The key is not to use it alone. A .290 average looks impressive, but its value depends on whether it comes with walks and extra-base power. Conversely, a .235 hitter may still be productive if he reaches base consistently and drives the ball.
Frequently asked questions
Is OPS better than batting average?
For a quick estimate of overall hitting production, yes. OPS includes on-base ability and power, while batting average measures only hits per official at-bat. Average remains useful as one part of the player’s profile.
What is considered a good OPS?
The answer depends on the season and league environment. As a rough guide, an OPS around .800 is often strong, but OPS+ provides better context because 100 is always league average after park adjustments.
Can a player have a low batting average and a good OPS?
Yes. A hitter can compensate for fewer hits by drawing walks and producing extra-base hits. Power hitters with disciplined strike-zone control often fit this profile.
Does OPS include stolen bases?
No. OPS measures on-base percentage and slugging percentage only. Stolen bases, baserunning decisions and defence require other statistics.
Which stat should you trust?
Batting average tells you how frequently a player gets a hit. OPS tells you more about how effectively he reaches base and how much damage he does when he connects. For most head-to-head hitting comparisons, OPS is the stronger starting point, and OPS+ is better when parks or eras differ. The clearest evaluation uses batting average as supporting context rather than the final verdict.
