What the Heck Is CS and Why Should You Care
CS stands for Caught Stealing. It is a box score statistic that tracks how often a baserunner is tagged out while attempting to take the next base, usually second or third. It gets thrown around in fantasy baseball and sabermetric conversations, and people treat it like it tells you everything about a catcher. It does not. A low CS total does not automatically mean a catcher is bad, and a high one does not mean they are great. Context matters, and most casual readers skip it entirely. To actually understand what CS means beyond the raw number, you have to look at the catcher's role in the running game. The catcher is responsible for preventing steals through a combination of pop time, accuracy, game management, and pitch selection. Pop time measures how fast the ball gets from the catcher's hand to second base, but it is only one piece. Footwork, blocking, and the ability to field a bad throw all factor in. The secret language here is not some mystical code. It is the way catchers communicate with pitchers, call games, and set up defensive positioning without ever raising their voice. That communication is what separates a catcher who prevents runs from one who just sits there. The catchers game involves sign-calling, pitch sequencing, and arm angles that runners and their coaches try to decode. A competent catcher will vary his delivery, use check swings at the plate, and manipulate the pace of the game to disrupt a baserunner's timing. When a runner does get a good jump, the catcher has to react instantly. The stat that records the result is CS, but the decision before the throw is what actually drives that number.
I spent years watching game film and arguing with stats people who only looked at framed numbers. The first thing I learned is that CS rate alone is almost useless without context. A catcher who faces two hundred steal attempts and tags out sixty of them has a forty percent success rate against the run. Another catcher faces forty attempts and throws out ten has the exact same percentage, but his sample is tiny and his reputation will be completely different. The volume of attempts depends on the pitcher staff, the quality of the opponents, and the game situation management of the manager. You cannot read anything meaningful from the bare statistic alone. There is also the frame rate problem. Some catching coaches will point out that CS totals do not account for attempted throws that never materialize because a runner bails early on a known weak arm. A elite runner might hold lead extra long against a catcher with a slow pop time, then go anyway when the count is wrong. The manager chooses not to challenge that. The catcher never gets the chance to throw, and no CS is recorded. Meanwhile, the same runner might get picked off first or third because the catcher did not have the arm to execute. That shows up in Pickoffs and Advanced Outs but not in CS. The stat is incomplete by design, and you have to know where the gaps are. Another practical issue I ran into involves the difference between attempted and actual plays. A catchers pop time might look terrible in the stat line because he made five wild throws in one month, but those throws could have been on borderline plays where the runner beat it anyway. The difference between a CS and a safe call is often three or four inches. Umpire tendencies matter, and some regions and some umpires are more generous to runners than others. I once worked with a scout who was tracking a catcher whose CS total looked inflated compared to his league average. When I pulled the game log, half of those plays were close calls at second where the runner would likely have been safe even on a perfect throw. The catcher was getting credit for outcomes he did not control. That is why advanced metrics like Framing Runs, Zone Value, and the various arm tracking systems exist. They try to separate signal from noise.
When you want to evaluate whether a catcher is actually good at preventing the run, you look at a combination of tools. Pop time is the standard starting point, with the MLB average hovering somewhere in the high 1.9 to low 2.0 second range for elite arms. Block rate is another measurable component, along with fielding bunts and handling foul tips. Then there is the qualitative side: does the catcher dictate the pitch schedule? Does the pitching staff trust him? Is he calling a game that limits damage when the hit is on? I remember a specific situation where a catcher in the minors had a subpar pop time, around 2.08 seconds, which would normally flag him as a liability on the bases. He still ranked in the upper tier for preventing stolen bases in his league that season. What was happening was that he varied his footwork to such a degree that base runners could not get a consistent read on his release point. Runners rely on timing, and timing breaks when the mechanics shift from pitch to pitch. He also threw more from a slightly closed stance, which hides the ball longer and gives the runner less visual information. It is a small adjustment that most tracking software does not capture, but it directly impacts the run game. CS totals stayed low despite the mediocre arm number. The other side of this is equally important. Catchers with elite arms can still have poor CS numbers if they lack game awareness. I have seen catchers throw the ball with authority into the dirt or into the catcher mitt at a base rather than letting the infielder apply the tag. Throwing directly at a base when there is a force play risk or a double play possibility is a common error among younger players who are still learning when to hold the ball and when to deliver it. Those mistakes show up as passed balls, wild pitches, and yes, CS when the runner scores anyway.
Get the Full Details
For anyone trying to decode what is actually happening, I recommend looking at a few sources together rather than relying on one metric. Start with the raw CS total and compare it to the league average for catchers with similar playing time. Then look at pop time data if you can find it. Next, examine the underlying context: how many steal attempts did each team face, what was the quality of the base runners, and were there manager decisions that favored pitch outs over throws. A high CS total with a high volume of attempts and a young roster facing fast opponents is a very different story than a low CS total with minimal action against a team that rarely attempts to steal. There is also a communication layer that influences CS that most people miss. Catchers call games using a system of fingers, wrist movements, and occasional verbal signals. Runners and their coaches study these patterns obsessively. Some teams employ sign stealers who sit in the stands or use binoculars to track the catchers hand at the plate. Others use technology. When a catcher changes his sign sequence mid-game, it disrupts the opposing teams ability to predict pitch type and location. That disruption can cause hitters to swing early or take pitches outside the zone, which leads to more called strikes and fewer balls in play. Fewer balls in play means fewer opportunities for the defense to get out of inning threats, and it indirectly reduces the number of high leverage steal attempts the opposing manager will make. The catchers secret language is as much about disrupting the opponents timing as it is about the physical act of throwing someone out. If you are tracking this for fantasy purposes or for evaluating a prospect, the most useful approach is to build a small dashboard. Pull the raw CS and CSA (Caught Stealing Attempts), calculate the success rate, then cross reference with pop time and the opponents base running frequency. Add in the pitchers groundball rate and velocity because a staff that induces weak contact limits steal opportunities by nature. You will find that the correlation between pop time and actual CS prevention is not as strong as most people assume. Game management and opponent quality shift the numbers significantly.
I also learned the hard way that one bad month can skew your perception of a catcher for an entire season. A catcher might have a rough outing where he makes two errors on a steal attempt, and then people write him off. In reality, those plays might have been outlier events driven by bad hops, weather, or the runner being exceptionally fast that day. A single game does not define a catchers value in the run game. You need a reasonable sample, ideally thirty to fifty attempts, before drawing conclusions about whether the underlying skill is real or just noise. The deeper you get into this, the more you realize that CS is a surface level entry point into a much larger system. Catchers control tempo, manipulate timing, read hitters, manage pitchers, and field balls in the dirt. Every one of those skills affects the probability that a steal attempt will succeed or fail. The stat is useful, but it is only a snapshot. The real value is in understanding the mechanics behind the number and knowing when to trust it and when to dig deeper.
