The Strike Zone Is Imperfect, but Mostly Unchanged
The strike zone doesn’t exist. Not physically, at least; it’s a rough boundary that varies based on how each umpire looks at it and how each batter stands. Catchers influence the shape, too; smooth hands can turn balls to called strikes, while cross-ups tend to do the opposite.
This year, the zone seems particularly amorphous — maybe it’s just my imagination, but I feel like I can’t turn on a broadcast without hearing about an inconsistent zone. Of course, hearing isn’t believing, and there are botched calls every year. Just because there have been some memorable ones this year doesn’t necessarily mean the overall rate of missed calls has changed. Let’s find out if it has, or if it’s merely imaginations running wild with the backdrop of fan noise.
For a rough idea of ball/strike accuracy, I went to Statcast data. For every pitch, Statcast records a top and bottom of the strike zone, as well as where the pitch crossed the plate. Armed with that data as well as some constants like the size of a baseball and the width of home plate, I measured how far out of (or into) the strike zone each pitch of the 2021 season was when it crossed the plate.
This data isn’t perfect. The top and bottom of the strike zone are approximated, and the plate isn’t a two-dimensional object, despite the fact that our data on it is represented that way. We aren’t considering framing. But we have previous years of the same data, which is great news. We can use the previous years to form a baseline, then see if this year’s data represents a meaningful change. And because we have a huge chunk of data, we can at least hope that framing comes out in the wash.
Let’s start with pitches outside the strike zone being called strikes. This year so far, a whopping 42% of pitches that missed the zone by half an inch or less have been called strikes. In the interest of getting an unbiased sample, I excluded skewed counts — 0-2, 2-0, 3-0, and 3-1 — so these aren’t gift strikes on unimportant pitches; they’re simply calls that turned pitches that were outside the strike zone into called strikes.
Disaster, right? That’s 42% of batters wrongfully denied their rightful ball. Umpiring is falling apart! Well, in the same counts last year, pitches that missed the plate by less than half of an inch were called a strike 43.5% of the time. Same same, which means we need to keep looking.
Those are pitcher’s pitches; batters understand that they’ll be victimized by those from time to time. What about when pitchers miss by slightly more? In 2021, pitches that miss the outside edge of the zone by between 0.5 and 1.5 inches have been called strikes 33.2% of the time. Aha! Those dastardly umpires. Except… in 2020, those pitches were called strikes 34.8% of the time.
Between 1.5 and 2.5 inches out of the zone, 17.4% of taken pitches have gone for called strikes this year. Last year, that number was 18.6%. Again, not much difference. Between 2.5 and 3.5 inches, umpires are calling strikes 7.4% of the time this year. Last year, they called those pitches strikes 8% of the time. We get it, we get it; pitches that just miss the zone are being called strikes at standard rates this year. Here it is in table form:
| Distance from Edge | 2020 | 2021 |
|---|---|---|
| 0-.5″ | 43.5% | 42.0% |
| .5-1.5″ | 34.8% | 33.2% |
| 1.5-2.5″ | 18.6% | 17.4% |
| 2.5-3.5″ | 8.0% | 7.4% |
Okay, we have our first finding: on pitches that are off the plate but close, umpires are calling strikes at roughly similar rates compared to last year. How about pitches that miss by more than that? They basically don’t get called strikes, but the rates are similar from year to year. Though I’m not willing to take a strong stance given the limitations of a two-dimensional strike zone with moving top and bottom, I think it’s fair to say there’s no evidence of a change here.
What about pitches in the zone being called balls? That’s a slightly trickier calculation, but I used the same rough idea. Take the pitch’s location, add in the width of the baseball, then find the nearest edge of the strike zone — the distance to that edge is how far into the strike zone the pitch was. Pitches that just clipped the zone — between 0 and 0.5 inches from the edge — have been called strikes 61.2% of the time this year. Last year, they were called strikes 62.5% of the time.
Get further into the zone, and umpires call strikes more frequently — pitches that were in the zone by between 0.5 and 1.5 inches have been called strikes 75.4% of the time this year, as compared to 76% last year. Past that, it’s less automatic than you’d think, though still fairly automatic, to the tune of an 86.8% called strike rate on pitches in the zone by between 1.5 and 2.5 inches. That compares to 88% in 2020. Here’s the same table as above, only for pitches in the zone:
| Distance to Edge | 2020 | 2021 |
|---|---|---|
| 0-.5″ | 62.5% | 61.2% |
| .5-1.5″ | 76.0% | 75.4% |
| 1.5-2.5″ | 88.0% | 86.8% |
| 2.5-3.5″ | 93.2% | 91.5% |
Umpires are calling slightly fewer strikes in every case this year; that’s the only clear trend in this data. If your baseline is what umpires have done before now, they’re doing roughly the same thing this year. That doesn’t mean that they didn’t blow a call when your favorite pitcher needed the strike, or punch out your team’s top slugger on a pitch three inches outside. It just means they were doing that last year, too.
You could imagine a different grid, though. Here’s the theoretically optimal grid, if you care most about accuracy:
| Distance to Edge | 2020 | 2021 |
|---|---|---|
| 0-.5″ | 100% | 100% |
| .5-1.5″ | 100% | 100% |
| 1.5-2.5″ | 100% | 100% |
| 2.5-3.5″ | 100% | 100% |
Bring on the robots! They’ll get this stuff right. I have two counterpoints to that — not disagreements, per se, but arguments. I think there’s value in uncertainty — I like the fact that pitches that clip the edge are strikes 60% of the time, while pitches an inch in are strikes 75% of the time. That probabilistic nature makes sense to me. Bright lines are weird! A scale of called-strike-iness is how I imagine the strike zone working, and I like that it works that way in real life.
A related concern: when you’re dealing in absolutes, slight measurement errors are important, and no system is perfect. For example, take a look at this called strike:
That missed the zone; no arguments about that. But per the data, that pitch was 4.5 inches low, the single most egregious called strike in the so-called “shadow zone” this year. It certainly doesn’t look that way to me on the video.
Part of the reason for that: the bottom of Jazz Chisholm’s strike zone gets recorded independently on every pitch, and it was 1.5 inches higher on this particular pitch than its year-long average. The bottom of his zone has varied by 6.72 inches from highest recording to lowest recording this year in 211 pitches. I’m not privy to the calculations that go into determining the top and bottom of a player’s strike zone on each pitch, but that’s a wide range, and might result in pitches that annoy us just as much as the current “missed” calls.
I doubt this article will change your feeling about umpires one way or another. If you wanted the robots already, you probably still do. If you liked the uncertainty and tradition of the current system before this year, you probably feel the same. Umpires don’t appear to be getting worse at calling balls and strikes, no matter what announcers’ eyes are telling them. The question, instead, is whether their current level of precision is the kind of strike zone you want.
Ben is a writer at FanGraphs. He can be found on Bluesky @benclemens.
“The bottom of his zone has varied by 6.72 inches from highest recording to lowest recording this year in 211 pitches.”
This is a thing I did not know. Unless the robot umps are programmed to use a fixed value for each batter, a six-inch zone of “maybe a strike” seems like it’s not really any better than human umps.
It seems like a lot. But if Chisholm varies his batting stance significantly between PAs (or between pitches) it may even be right
I’ve never given this much thought before, but is that how we want the zone to be called? Like a guy can kind of scrunch up to buy a ball?
Funny. I read the wikipedia article on the strike zone the other day (FWIW, it could be inaccurate, but I’m lazy) and it quoted the rules as saying that the zone is defined by location of “letters” and knees of the batter in his stance. So already, explicitly, I believe that this is how it works. Scrunching up likely does have an effect on the zone (though I’m guessing more for the top of the zone than the bottom since your knees can’t move that much since your shin bone is fixed?)
PS: the history of the strike zone in the 19th century is fascinating! I didn’t know that batters used to tell the pitcher the height at which to throw the ball! Nor did I know that a called “ball” is short for “no ball”. To be stupid, next time someone asks me if I think that was a ball, I’m gonna reply, “no ball” 🙂
Good point. This would be very easy to do, I think: have all the uniforms have some kind of sensor/reflector sewn in at the letters and the approximate knees. The robot umps then use them to determine the zone for each batter. If a batter wants to scrunch way up, so be it.
You could easily crouch such that your strike zone has zero size. Of course, you could do it today but i think the human ump might still wring you up.
This made me wonder about the uniformity of the position of “the letters” on jerseys. Or how a jersey must fit so that an ump knows where the top of the zone should be.
Also, do the players then wear a sensor to delineate the zone so that the robot ump knows where it is? How does that sensor not get shifted around accidentally, or even intentionally?
Getting flashbacks to my HS JV baseball days where our coach would scold us harshly if we ever said anything to umps about the balls and strikes. haha
It won’t be a sensor, the Hawkeye system is camera based computer vision. They’ll use pose estimation.
I am sure it’s a selection bias on my part, but also, don’t tell any of us who watched LAD/COL that the umps were typical (or else “typical” no longer feels acceptable)
I will answer the question you asked in the last sentence. I do not think pitches from 1.5″-2.5″ out of the zone should be called correctly only 82% of the time. It is pretty difficult to hit when there is that much uncertainty about what is a strike but I am an unabashed basher of umpires, not knowing the rules as Kulpa admitted to in the Conforto fiasco, and watching Angel Hernandez for far too many years, will put those ideas in one’s mind, and when I see Hawkeye operate in tennis and be accurate to very small increments I find it hard to imagine that it isn’t superior.
Hawkeye at least has the advantage that “in” and “out” don’t vary depending on who’s receiving the ball. At least in theory.
Tell that to Federer! (I think he has the worst success percentage on challenges, at least of the true contenders)
I don’t know why this is being compared to last year where the umps to were terrible. Even if not perfect it shouldn’t be hard to get some technology that at least makes this a improvement
Exactly. I don’t need perfect; I just need consistent.
And if you LIKE some level of slop and randomness, (A) the computers aren’t perfect, just better than the human eye, and (B) the batters aren’t perfect and will still be guessing about whether a ball is a ball or strike.
Umpires are human and therefore subject to error bars the same as anyone else. Robot umps wont be perfect either, but it will feel worse when they make a mistake, and they might be easier to tamper with! Enjoy the game for what it is, great! Stop complaining about the professional umps. They are not risking their cool job by cheating very often and they generally want to get it right. This article is nothing more than a sophisticated complaint. I hope it made you feel better, but the game is the game. I love it for what it is!
What is the errorbar on the statcast location data? If it’s about 1 inch, then we expect a ‘correct’ umpire, whatever that means, to call strike on nearly 20% pitches that statcast claims to be up to 1 inch off the plate.
The answer to the question posed in the final sentence is “NO.” And the answer to the larger question is robot umps. The sooner the better.
We don’t need any more evidence that human umpires are never going to get enough calls correct. It is a really hard job and the umps are waaaaaaaaaay better than I could ever be, but they still suck at it.
Define a fixed strike zone. x inches from ground to y inches from ground in height. Use average or median, whatever. Make it independent of the batter or stance.
Calibrate an automated system to it. Add/enhance whatever cameras needed, center field, overhead.
Maybe have plate ump relay the call, but ump cannot override.
Watch the accuracy of calls go up.
Pitchers are going to hate that. Unless they’re given an AR headset that allows them to see the box we see on TV, I think they’d rather throw relative to the batter.
Independent of the batter? So a 6’8 guy has the same zone as a 5’4 guy? That’s………one approach I guess.
A not-at-all good approach is still an approach!
Also: does this analysis take into account the nonzero diameter of the ball?
It sure does — well, I used one end of the specification band, a diameter of 2 55/64″. I don’t think the analysis would change much if I assumed the other end of the band, 2 15/16″. I assumed that the Statcast location is the center of the ball and then used the radius from there.
Good, thanks Ben. Do we know statcast precision? Your 100% table assumes statcast errors are negligible compared to the quoted off plate distances. Is that realistic?
No idea, to be honest.
Well, then I’m afraid all bets are off, and your claim that the 100% table represents an ideal situation is entirely unjustified. Lacking the statcast error bar, then for all we know, the data are consistent with the human umpires being perfect the last two years.
Oh yeah, we’re talking long-term theoretical ideals. The system is not ready yet as far as I can tell. I do know that Hawkeye in tennis has *extremely* tight tolerances.
Ok, but “long term theoretical ideals” is a far cry from “bring on the robots!”. I don’t know anything about Hawkeye, but can imagine its job is made easier by having two dimensions instead of three, and a nice bounce point to compare against a physically drawn line.
Oh yeah, I agree with you. I don’t want robot umps yet either. I particularly enjoy the uncertainty, though I know I might be alone in that. I also just don’t think it would work yet.
MLB’s Hawk-Eye Statcast system is claimed to accurate within an average of .25″ at the plate.
See Fig.6 here: https://technology.mlblogs.com/introducing-statcast-2020-hawk-eye-and-google-cloud-a5f5c20321b8
PITCHf/x and Trackman Statcast averaged 1/2″ horizontal error and 1/2″ (PITCHf/x) or 3/4″ (Trackman) error according to this study before the 2018 season :
https://tht.fangraphs.com/the-lurking-error-in-statcast-pitch-data/
Fun side note: I think it must be possible to use difference between missed ball and missed strike calls to infer the diameter of the ball.
I want the automated strike zone for many reasons. But the biggest reason, by far, is that it would obviate the utility of those damned strike zone boxes that broadcasters are superimposing on the screen. Words can’t describe how much I hate those worthless distractions. They have absolutely ruined my enjoyment of watching a game. As a result I watch at least 1/3 fewer games and fewer innings when I do watch. I curse whomever is responsible for making these annoyances full time.
Why is that a reason to have robots? Seems like we’d all be much happier if they just removed the damn box and we didn’t have to know, after every pitch, whether statcast and its unknown errorbar thinks the umpire ‘got it right’.
Agree, the box leads to increased calls for robots but it’s not there because the umpires are not accurate enough. Having robot umps does nothing to remove the boxes.
I agree that the boxes can and should be removed right now. But they aren’t being removed. I imagine the thinking behind that awful decision is that the box lets fans see if the pitch was called accurately. Once the pitches are called automatically there will be no conceivable justification to keep them.
I wonder if hitters and coaches have contemplated the significantly greater strike zone size robotic umpiring might force them to cover?
Maybe, but it will be far easier to recalibrate the robots after a season that it is to re-teach humans what a strike zone is. If it’s too big the first year, they just make it smaller for the next year.
I think we need a whole article about how a batter’s zone is calculated! This seems like a really important and hugely variable calculation!
How, may I ask, does the length of Jazz Chisholm’s leg change by 6.72 inches from AB to AB? I doubt if he is using prosthetics and nobody can vary that much unless he is virtually on his knees. This borders, or even crosses, the line of impossible.
So the zone shrinks when the pitch is in the zone, and it stretches when the pitch is out of the zone. Makes perfect sense.
Still skeptical of the premise behind the analysis in the original post, I just ran a little monte carlo simulation to see what Ben’s tables would look like when a *perfect* umpire is evaluated using finite-precision statcast data.
For simplicity I assumed a 1-dimensional strike zone and sampled the *true* pitch location from a normal distribution with mean set to the edge of the strike zone (where inner surface of the ball just grazes black of the plate). I set the standard deviation to five inches, my best guess at how precisely the typical big-league pitcher can paint the black (the results are not sensitive to this choice, other than affecting the sample size in each location bin).
I then drew simulated statcast errors from a second, independent, normal distribution with mean zero and standard deviation set to some value that represents the typical statcast errorbar. Adding these deviates to the true pitch location, I obtain simulated statcast measurements of the pitch locations.
I then calculate the rate at which statcast would say that the perfect umpire —who, by construction, calls ball or strike with 100% accuracy based on the known true pitch location—“erroneously” calls strike on balls that statcast thinks are within the same location bins from Ben’s tables.
Here is the result for a statcast errorbar of 3 inches:
#distance from edge called strike rate (by statcast with horizontal errorbar +/- 3.0 inches)
0.0″ – 0.5″ 47.2 %
0.5″ – 1.5″ 31.61 %
1.5″ – 2.5″ 28.5 %
2.5″ – 3.5″ 1.18 %
Here’s for statcast errorbar of 2 inches:
#distance from edge called strike rate (by statcast with horizontal errorbar +/- 2.0 inches)
0.0″ – 0.5″ 45.42 %
0.5″ – 1.5″ 23.39 %
1.5″ – 2.5″ 17.96 %
2.5″ – 3.5″ 0.54 %
Here’s for statcast errorbar of 1 inch:
#distance from edge called strike rate (by statcast with horizontal errorbar +/- 1.0 inches)
0.0″ – 0.5″ 40.43 %
0.5″ – 1.5″ 7.61 %
1.5″ – 2.5″ 3.0 %
2.5″ – 3.5″ 0.02 %
A couple of takeaways:
–The rates that Ben observes out to 1.5 inches are basically consistent with perfect human umpires, unless statcast has precision << 1 inch.
–If you want to groan about human umpires and call for robots as a superior alternative, your evidence is probably limited to that observed ~ 7% rate at 2.5 – 3.5 inches, where we'd expect a perfect umpire to "miss" 1% or less.
I would assume a lot of the pitches well within the zone being called balls are instances of pitchers badly missing their targets? Like: Sets up low inside, you chuck it for a strike up and out. No human ump is ever going to give you that call. And shouldn’t, imho.