A 400-foot fly ball is not a fixed thing. Hit it to straightaway center in one stadium and it dies on the warning track; hit the same ball in another and it lands ten rows deep. Pull it down the left-field line in Boston and it caroms off a 37-foot green wall for a double instead of clearing it for a homer. The ball obeyed the same physics in every case — what changed was the building it was hit into. Park factors are the tool that lets us subtract the building back out.
Every ballpark in the majors has its own dimensions, altitude, wall heights, foul-territory acreage, and weather, and each of those quietly nudges the stat line of whoever happens to play there. A park factor is a single index that says, in one number, how much a given stadium inflates or suppresses run scoring relative to a neutral baseline — so that a hitter in a launching pad and a hitter in a pitcher’s graveyard can finally be compared on the same terms.
Why no two parks play alike
Start with the obvious: dimensions. Major League outfields are not standardized the way an infield is, so the distance to the fence varies wildly from park to park and from one part of the same park to another. A short porch in right turns warning-track outs into home runs for left-handed pull hitters; a cavernous power alley swallows the same contact. Wall height matters just as much as distance — Fenway Park’s Green Monster is only a few hundred-odd feet down the line but stands roughly 37 feet tall, which converts a great many would-be home runs into doubles and a great many lazy fly balls into wall-scraping singles.
Then there is air. Coors Field in Denver sits at roughly 5,280 feet above sea level, and thin air does two things at once: it offers less resistance, so a struck ball carries noticeably farther, and it robs breaking pitches of bite, flattening the sliders and curveballs that would otherwise generate weak contact. Foul territory is the quieter lever — a park with vast foul ground hands its pitchers extra outs on pop-ups that would sail into the seats elsewhere, while a cramped park gives hitters second chances. Add weather, wind patterns, and even the time most games are played, and the result is that the same swing produces different outcomes in different zip codes.
How a park factor is computed
The core idea is older and simpler than the modern machinery around it. Take what happens in a team’s home park and compare it to what happens in its road parks, where the same hitters and pitchers are doing the comparing for you. If far more runs are scored per game at home than on the road, the home park is inflating offense; if fewer, it is suppressing it. Express that ratio as an index where 100 means perfectly neutral, anything above 100 is hitter-friendly, and anything below 100 is pitcher-friendly.
A rough, classic version of the run park factor looks like this:
That single-season ratio is far too noisy to trust on its own — one year is a small sample, and a hot or cold home schedule can swing it. So the published versions regress the estimate over multiple seasons and toward the league mean, smoothing out the luck before settling on a final index. The exact methods differ by site, which is one of several reasons WAR figures disagree across sites; the shared logic, though, is always the same: measure the gap between a park and neutral, then trust it only after several years of evidence.
Coors Field, the perennial outlier
If one stadium has defined the entire conversation, it is Coors. The combination of high altitude and large dimensions has made it, year after year and by a wide margin, the most hitter-friendly park in the major leagues — a fact stable enough that it functions as a fixed point in any park-factor discussion. The thin Denver air is so favorable to offense that the Rockies have at times stored game balls in a humidor specifically to tamp down how far they fly, an engineering intervention no other run environment has required.
The Coors effect also illustrates why raw counting stats can badly mislead. A hitter who posts gaudy numbers in Denver is not necessarily a better hitter than one with quieter numbers in a pitcher’s park — he may simply be hitting in a building that hands out free offense. There is even a documented “Coors hangover,” where hitters acclimated to flat breaking balls at altitude struggle to readjust on the road. Park factors exist precisely so that the line does not get all the credit the ballpark earned.
How OPS+, wRC+, and ERA+ bake it in
Here is the payoff, and the reason park factors matter to a casual reader at all: the “plus” stats have already done this adjustment for you. OPS+ and wRC+ take a hitter’s raw production, adjust it for his park and league, and rescale it so that 100 is exactly league average and every point above or below is a percentage point better or worse than average. ERA+ does the mirror-image job for pitchers, adjusting earned run average for park and league on the same 100-is-average scale.
Consider a clearly illustrative example. Suppose Hitter A plays half his games in a strong hitter’s park with a factor near 112 and posts an .850 OPS, while Hitter B plays in a pitcher’s park near 92 and posts a .820 OPS. The raw numbers favor A. But once each line is divided by its park environment, B’s lower OPS came against stiffer conditions, and it is entirely possible B lands with the higher OPS+ — say a 128 to A’s 118 in this hypothetical. The plus stats are how you see that flip without doing the arithmetic yourself. (Those numbers are illustrative, chosen to show the mechanism, not measurements of any real player.)
The caveats that keep you honest
Park factors are useful, not infallible, and three caveats keep them in their place. First, they are noisy: a single season’s factor bounces around, which is exactly why the trustworthy versions are multi-year and regressed. Treat any one year’s number as a soft estimate, not a measurement.
Second, they are component-specific. A park does not inflate everything uniformly — a stadium can boost home runs while simultaneously suppressing batting average on balls in play, because the same short fence that helps fly balls can pair with an outfield that turns liners into easy outs. A single overall run factor hides this; the better public sources publish separate factors for home runs, doubles, triples, and the rest. Third, factors have handedness splits: a right-field porch helps left-handed pull power far more than right-handed power, so a park can be friendly to one side of the plate and stingy to the other. A blanket index averages those effects away.
The bottom line
A ballpark is a silent participant in every plate appearance, and ignoring it is how you end up overrating a Coors slugger and underrating someone grinding out a living in a pitcher’s park. Park factors put both on neutral ground: 100 is fair, above 100 is a tailwind, below 100 is a headwind. You rarely need to compute one yourself — reach for OPS+, wRC+, and ERA+, which have already folded the building into the number — but knowing what they did, and where it gets noisy and handedness-dependent, is what separates reading a stat from understanding it.
Sources & Further Reading
- Baseball-Reference — park-adjusted stats including OPS+ and ERA+, and its published multi-year park factors.
- FanGraphs — wRC+ and component (handedness- and event-specific) park factors.
- FanGraphs Library — explainers on how park factors are calculated and regressed.