Image credit: USA Today Sports

A Google search for “rulebook strike zone” reveals a comical range of images for interpretations of the rulebook strike zone. Some show a batter, but don’t even draw the midpoint at what is clearly the midpoint. Old strike zone rule examples from years ago before rule changes linger as well.

Official Rule 2.00: The Strike Zone
The STRIKE ZONE is that area over home plate the upper limit of which is a horizontal line at the midpoint between the top of the shoulders and the top of the uniform pants, and the lower level is a line at the hollow beneath the kneecap. The Strike Zone shall be determined from the batter’s stance as the batter is prepared to swing at a pitched ball.

Much of this disarray is because the rulebook strike zone is too subjective, ripe for interpretation. It will need a further refined definition to serve as a universal definition for postgame analysis, and also to help remove it as one of several major roadblocks for machine systems to be implemented calling balls and strikes in a live game.

For postgame analysis, there is no standard definition of the strike zone. That’s partly because most postgame analysis is done without the knowledge of each particular batter’s stance. In the absence of the batter’s stance information, analysts use a generic, “typical” batter strike zone, but each analyst has their own idea of the dimensions and location. Or they might use data of the top and bottom, which is set by MLB stringers. But stringers are people setting a top and bottom based on their subjective assessment, or they use pre-defined values obtained at some random time that may or may not be relevant to the player at the time of batting.

Stats for catcher framing, out-of-zone swing rate, in-zone swing rate, and several others depend on defining the batter’s strike zone. So comparing Analyst A’s stats with Analyst B’s stats aren’t necessarily a direct comparison. The analyst community needs to discuss and agree on a definition of a strike zone for the average batter for postgame analysis where the batter stance is unknown.

A postgame strike zone definition is so basic and fundamental to postgame data analytics that I find it amazing that this has yet to have an industry accepted standard definition. Once defined, that definition should then also be used to define a “universal” strike zone for game play, unifying both game play and postgame analysis.

Once a universal strike zone is defined, it would be used in game play as the same size and location for all batters. As it stands now, shorter batters have the advantage of a smaller strike zone, while taller batters are disadvantaged with a larger strike zone. A batter whose stance is more upright is disadvantaged compared to a batter who crouches over. Why do we need a different-sized zone for every batter and every particular stance a batter might use? It not only doesn’t make sense, but it severely complicates the use of machines and analysts’ stats, as well as training for pitchers, batters, and umpires.

Some have said that having a variable strike zone evens things out for shorter batters, taking away the supposed physical advantage of taller batters. That’s not a good argument. It’s as bad as if they were to make pitchers who threw faster pitch farther away from the plate to make things even for slower-throwing pitchers. It also assumes that a shorter batter is somehow disadvantaged. Jose Altuve would prove that idea false.

Before joining the Houston Astros, Mike Fast wrote for Baseball Prospectus that he saw just a small amount of difference in the top of the umpire-called strike zone for taller pitchers. So it appears that umpires are already using somewhat of a universal top of a strike zone.

Imagine the increase in consistency and accuracy there would be if pitchers, batters, and umpires all trained with the exact same strike zone 100 percent of the time. In addition, postgame analysis would match the game play, and stats would be consistent between each analyst.

The above is an example of postgame analysis of the balls and strikes called using a typical batter strike zone.

It’s a wonder why analysts are using so many of their own variations of a typical batter strike zone. Perhaps the reason for some of the confusion comes from the difference between what I call the “strike zone boundary” definition as in the rulebook strike zone definition, and the actual “true strike zone” due to the width of the ball. Then that confusion is compounded by dimensions of the “called strike zone” as called by umpires and also by MLB stringer values. This “called strike zone” is even more varied than what analysts use.

Under current MLB rules, the diameter of the ball shall be between 2.86 inches and 2.94 inches. For our purposes, we will use the larger value of 2.94 inches for the baseball width.

To clarify things, let’s define the five types of strike zones:

  • Rulebook Strike Zone Boundary: This is the strike zone boundary dimensions and location drawn to the rulebook.
  • True Strike Zone: This is the strike zone boundary dimensions and location drawn to the rulebook, with the added half-ball width added to the perimeter. Because if the center of the ball lands with half its width outside the strike zone boundary, the ball’s outer edge touches the zone. This is the strike zone that determines true balls and strikes. If the center of the ball is inside this zone, it is a strike.
  • Called Strike Zone: This is the subjective strike zone to which umpires call balls and strikes.
  • Stringer Strike Zone: This is the subjective strike zone set by video stringer operators for pro games.
  • Universal Strike Zone: This is the strike zone boundary dimensions and location drawn to the rulebook for a typical 73-inch-tall player, with the added half-ball width added to the perimeter. Because if the center of the ball lands with half its width outside the strike zone boundary, the ball’s outer edge touches the zone. This is the universal strike zone used for postgame analysis when the batter height is not known. If the center of the ball is in this zone, it is a strike.

For example, Pitchgrader—my company that provides software to MLB and D-1 college teams to analyze and manage pitched/batted ball tracking data—uses this as a universal strike zone.

In the graphic below, the strike zone boundary is 17 inches wide, 19.76 inches bottom, and 42.61 inches top. The strike zone boundary is what you would use if creating a target for a pitcher to throw to. But the location where balls may land and touch those boundaries extends by half the width of a baseball for +1.47 inches around the perimeter. That’s the true strike zone for calling balls and strikes.

The above shows the universal strike zone used by Pitchgrader.

It seems many people try to define the strike zone for analysis based on how the umpires call the strike zone. Determining a universal strike zone based on what the typical umpire calls is a flawed approach because it’s a subjective strike zone. The same is true for using MLB stringer sz_top and sz_bot values, since they are also set by people making a subjective call of where the top and bottom of the zone was.

So using the subjective location of a ball determined by an umpire with an equally subjective strike zone boundary determined by a person manually setting stringer values is a recipe for inaccuracy, confusion, and the enigma we see now in what the strike zone actually is. The only way to determine an accurate and fair universal strike zone is to use the rulebook definition with actual body measurements of the mean average position player.

So let’s dig into how we decided to use these particular dimensions for the universal strike zone by looking at some key body measurement data.

A UCLA study lists 1,035 MLB players with heights and the average is 73.7 inches, but that includes all pitchers. However, if you exclude pitchers, this study has a mean average position player height of 72.81 inches and a median average height of 73 inches.

Anthropometric Data

Below are from a 2012 U.S. Army anthropometry study of 4,082 males. The average height of these males for the 1st percentile group was 62.99 inches, which is considerably shorter than a typical 73-inch male baseball player. For 73 inches (72.60 inches), that was the 90th percentile group in this study. So we will use the 90th percentile group.


Height is 62.99 inches for the 1st percentile and 72.60 inches for the 90th percentile (page 193).

Hollow Below Knee

Tibial height (below knee cap) is 16.06 inches for the 1st percentile and 19.76 inches for the 90th percentile (page 205).

Top of Shoulders

Acromial height (top shoulder) is 51.02 inches for 1st percentile and 59.88 inches for 90th percentile group (page 47).

Pants Top

Pants top at midpoint between waist height (belly button) and buttock height. This is 37.52 inches + (44.21 inches – 37.52 inches)/2 = 40.86 inches.

Waist height, belly button (page 223) is 37.13 inches for 1st percentile group and 44.21” for 90th percentile group.

Buttock height (page 79) is 30.71 inches for 1st percentile group and 37.52 inches for 90th percentile group.

So midpoint between the shoulders and the top of the uniform pants, from the ground is ((59.88 inches – 40.86 inches)/2) + 40.86 inches = 50.21 inches. Then we have to subtract the typical shoulder drop when in the batting stance of 7.6 inches. That puts the top of the zone at 50.21 inches – 7.6 inches = 42.61 inches.

Batting Stance Shoulder Drop

Since batters hunch over slightly in their stance, a slight bend at the waist plus slight bending of the knees lowers the shoulder height. This shoulder drop averages about 7.6 inches as noted in the following images.

Assorted batter standing vs stance ratios:

Compared to the average 73-inch MLB position player, Aaron Judge is six inches taller and Jose Altuve is seven inches shorter. If we use these two MLB batter height extremes and examine their stances, we get shoulder drops of 7.11 inches for Aaron Judge and 8.58 inches for Jose Altuve, which averages to a shoulder drop of 7.58 inches.

Stance Ratio

At Pitchgrader, we use what we call the “stance ratio,” which we define as the ratio between the player’s head height when in his batting stance divided by head height when standing normally. Then take the same ratio using the player’s shoulder instead of head. Then average the two ratios, rounding to two decimal places.

Aaron Judge: A rough measurement looks like he has a 0.91 stance ratio. Since he’s 6-foot-7 (79 inches), that would mean his shoulder lowers when in batting stance about 79 inches – (79 inches x 0.91) = 7.11 inches.

Jose Altuve: A rough measurement looks like a 0.87 stance ratio. Since he’s 5-foot-6 (66 inches), that would mean his shoulder lowers when in a batting stance about 66 inches – (66 inches x 0.87) = 8.58 inches.

Typical Analyst Zones

Examples of various analysts’ postgame analysis strike zones are as follows:

From the table above, you might be tempted to think, well, the average zone top and width seem to roughly agree, so why not use the average zone bottom? Many analysts are using a zone bottom that’s 2-5 inches higher. That’s part of the problem, as we should be defining the zone based on the actual batters and rulebook strike zone, not what analysts, stringers, or umpires guess.

Stringer Zones

So what emerges is a possibility as to why some analysts use the top and bottom of the zone that they use. It looks like they possibly used a simple mean average of the stringer values. That would not be a valid “typical batter” because it values the 60-inch and 83-inch height extremes of players the same as the majority of the typical 73-inch batters.

It seems as though analysts also might have chosen the dimensions they use in order to somewhat agree with what the stringers average values are, and what the umpire’s typical called strike zone is. I also can’t see a reason to justify a zone width other than 19.94 inches when the plate is always 17 inches wide and ball is always 2.94 inches in diameter. Their zone top seems to be almost arbitrarily chosen. The zone bottom they use seems to follow how umpires tend to call the bottom of the zone, but it’s not the true bottom of the zone.

Universal Strike Zone Definition

Based on the analysis of the anthropometric data of the average MLB position player, while staying true to the rulebook strike zone definition, the universal strike zone should be defined as below:

Universal Strike Zone Bottom: 18.29 inches

Based on anthropometric data, there can be little argument against using tibial height of 19.76 inches minus 1.47 inches for half a ball width = 18.29 inches for the bottom of the universal strike zone.

Universal Strike Zone Width: 19.94 inches

The width of the zone should be indisputable. The plate is 17 inches wide, and the maximum allowable tolerance for a baseball is 2.94 inches. So half of a ball width on each side of the plate produces a universal strike zone width of 19.94 inches.

Universal Strike Zone Height: 44.08 inches

Based on the anthropometric study cited, the top of the strike zone boundary would be 42.61 inches, which accounts for the reduction of height by the average amount of waist and leg bending when in the batting stance. Then you still have to add 1.47 inches for half a ball width for the universal strike zone top for 44.08 inches.

With the wide range of postgame strike zone dimensions and locations used by various analysts, the stats for catcher framing, O-swing, Z-swing, and others that depend on defining the strike zone, it’s like comparing apples to baseballs. They don’t match up.

The universal strike zone definition is so basic and fundamental to postgame data analytics that it requires an industry accepted standard definition. That definition should then be used for game play as a universal strike zone for all batters, unifying both game play and analysis.

Wayne Boyle is an electronics and software engineer with a career spanning 30 years. He is the founder of Pitchgrader, which makes advanced software used by top D1 & MLB teams for Pro level baseball 3D analysis/simulation/projection, and actionable meaning for pitched and batted ball tracking data for player development and scouting.

You need to be logged in to comment. Login or Subscribe
I find your logic in favor of a universal strike zone unpersuasive. The point of the strike zone when it was adopted was to force the pitcher to provide pitches that a hitter has a reasonably decent chance to hit. Calling a strike on a tall player for a pitch that would have been at the knees for an average-sized hitter but for him is particularly low and calling a strike on a shorter player for a pitch high up on an average-sized hitter doesn't seem to be unfair... rather the opposite in fact. While a universal strike zone may make analysis and robotic umps easier, I do not think that makes it more fair.
Robert Hacking
Watching Justin Verlander (for example) get a strike call on a ball 6 inches off the plate isn't fair today. A computerize system won't be perfect but it will be more consistent.
Yes, agreed, but we have some technical issues to resolve before a Robo zone can be used. One of those issues is defining a Universal Strike Zone.
Alan Waxman
JSSHARO, I agree with you. I don't get what a universal strike zone buys us when it comes to the top and bottom of the zone. Plus I've come to accept that the strike zone's variability is one of the quirks of the game.
It buys us consistency and fairness.
The bottom of the zone for Altuve is roughly 18.66” - 2.94”/2 = 17.19”. The bottom of the zone for Judge is roughly 21.06” - 2.94”/2 = 19.59”. So it’s about a 2.4” difference in the bottom of the zone for these players now, not counting their stance ratio. The Universal Strike Zone bottom is 18.29” , so Altuve would have his zone bottom raised by 1.1” , and Judge lowered by 1.3”. For the batters, this isn’t much to have the bottom adjusted by less than 1.5” , roughly less than half a baseball width, but it would be a big advantage for post game analytics and the Robo zone.
"For the batters, this isn't much to have the bottom adjusted... but it would be a big advantage for post game analytics and the Robo zone." Well then why don't we get cracking on it. I know when I'm watching Jose Altuve or Aaron Judge bat I'm thinking "Man, it's pretty cool watching some of the best players in baseball perform an almost superhuman task, but what I REALLY want to see are pundits discussing consistent postgame analytics."
Stats and metrics are a large part of how you help players reach their full potential and win more games. Stats tell you what happened, Metrics in proper context tell you why and what to adjust.
As always, thanks for the comments. Every article I write is meant to stir a discussion to see and understand different point of views. As for fairness, an inconsistent strike zone isn’t fair to the pitcher or batter. For advance scouting reports, having to analyze a particular umpire’s called zone so that you can match up with a pitcher that is more favorable to his zone is something that shouldn’t be needed either. The umpire is then a part of the game, instead of just ensuring that the strike zone and rules are followed.
Jonathan Corriveau
What rule states that the CENTER of the ball must be in the strike zone to be determined a strike? I was under the impression that a strike should be called if ANY part of the ball enters the strike zone. If so, the width of the strike zone would be 22.88 inches.
No, it’s clearly 19.94” , look at the strike zone graphic to understand.
You don't actually address his question which is why you're calibrating the graphic to the center of the ball when, as far as I can tell it's a strike if any part of the ball catches the plate. So the "called strike" area should be closer to the actual width of the ball.
The location of where a ball lands is always based on it’s center. From the center it’s always 1.47” to the outer edge of the ball. So 1.47” + 17” + 1.47” = 19.94” is the strike zone width.
Jonathan Corriveau
where in the rules does it state that the location of where a ball lands is always based on it's center. Little League/Babe Ruth League/High School (NFHS), and NCAA rules all clearly state that if ANY part of the ball enters the strike zone, the pitch is a strike.
Thanks Jonathan, your questions are the type that are a big reason why I wrote the article. There is too much misunderstanding about the strike zone and how it should be measured. The way that the location of a ball is described is always by X/Y coordinates. That X/Y coordinate is where it lands in the horizontal/vertical space above the home plate and is always the center of the ball. There is no debate on this, it is absolute. This is how you determine if any part of the ball touched the strike zone by where it lands and how wide the ball is. It is absolute just the same as that the home plate is always 17” wide, and a ball is always 2.86” to 2.94” wide. Take a closer look at the strike zone graphic in the article, and read the text as well to understand.
Jonathan Corriveau
According to the official MLB rulebook, under definitions of terms (page 149): "A STRIKE is a legal pitch when so called by the umpire, which: (b) Is not struck at, if any part of the ball passes through any part of the strike zone;" So, theoretically, if one stitch of the baseball (the outer edge of the baseball) passes through the strike zone, the pitch is a strike. Hence, the strike zone should be 22.88 inches wide, should it not?
Thanks again Jonathan. I think your questions help to show where people misunderstand the strike zone and why. You quoted the rule OK, But the width of the strike zone is absolutely 19.94” . It is 100% not 22.88”. I think the problem is you’re not understanding how the location of the ball is determined. It is absolutely not determined by the edge of the ball. It is 100% for sure determined by the center of the ball. Even without machine messurement, nobody manually charts a plate appearance by placing a dot on the chart where the edge of the ball was. It is always where the center of the ball was.
Jonathan Corriveau
Perhaps nobody charts a plate appearance by placing a dot on the chart where the edge of the ball is; but an umpire certainly does not judge a strike by where the center of the ball is located. To do so would contradict the rule as written. By rule, a strike is clearly determined by the edge of the ball, hence the phrase "any part of the ball." Your diagram seems to infer that, in order for a pitch to be determined to be a strike, half the ball must fall within the strike zone. I contend that the misunderstanding is not with the strike zone, but with what constitutes a strike.
Aw, c'mon. One of the joys of watching Rickey Henderson hit was his flagrant manipulation of stance to try to get walks. We would have never gotten to watch that with these rules.
Rickey Henderson was a joy to watch anyway. If he took any advantage he was allowed then I tip my cap to him, great player. That doesn’t mean that the enigma of a strike zone we have now is a good thing.
I think I mentioned this in another column on this topic, but wouldn't a more fair option be that players have their strike zone calibrated via some sensors at the rulebook defined points? Have them wear it for some significant number of at-bats, the camera and computer tracks it and uses the information to identify where to set their individual top and bottom of the zone. That info is fed to the robo ump and when they bat it uses that defined strike zone. If we're going to replace the umpire why do away with that human fallibility and replace it with another?
Yes, but as I wrote in the “Robo Zone: It’s not so simple” BP article, you’re introducing another machine that has it’s own tolerance and reliabiliity issues and limitations. When a simple solution of a Universal Strike Zone would only change the tallest and shortest player’s strike zone bottom by less than half a ball width.
And for the record, I don’t think we should ever remove the Umpire. We need to give the Umpire better tools, training, and a better defined strike zone, to help them make better calls.

Baseball Prospectus uses cookies on this website. They help us to understand how you use our website, which allows us to provide an improved browsing experience. Cookies are stored locally on your computer or mobile device and not by BP. To accept cookies continue browsing as normal. You will see this message only once. Privacy Policy

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. See the BP Cookie Policy for more information. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.