ScopeThe rule and version used here
This page applies the 2026 Official Baseball Rules issued by the Office of the Commissioner of Baseball, especially Rules 5.05(b)(3), 5.06(b)(3)(B) and (D), 6.01(c), and 6.01(g). The rulebook says it governs Major League Baseball and leagues in MLB's professional development league system.
The 2026 edition is the effective book for the 2026 MLB season. Its published summary of 2026 changes does not identify a change to Rules 5.05(b)(3), 6.01(c), or 6.01(g). NCAA, NFHS, Little League, international federations, and local competitions publish separate codes; this page does not present the MLB wording as universal baseball law.
TriggerThe test is whether a fielder hindered the swing
MLB defines defensive interference as an act by a fielder that hinders or prevents a batter from hitting a pitch. Rule 6.01(c) is commonly called “catcher interference,” but its text covers the catcher or any fielder.
Bat-to-mitt contact during the attempt to hit is strong evidence and the usual example. The rule is nevertheless framed around hindrance, not around a required object, an intentional act, or a minimum amount of contact. The umpire judges the timing and effect: a catcher setting up too close or reaching forward can interfere even though the catcher was only trying to receive the pitch.
TimingBefore delivery and after the swing are different questions
The protected act is the batter's opportunity to hit the pitch. The 2026 Rule 5.05(b)(3) Comment expressly says contact before the pitcher delivers the ball is not interference under this rule: the umpire calls “Time,” and the pitcher and batter start over.
Later contact can belong to the offensive-interference rules instead. Under Rule 6.03(a)(3), a batter who steps out or makes another movement that hinders the catcher's fielding or throwing can be out. A purely unintentional backswing that strikes the catcher or ball after a missed swing is treated under the Rule 6.03 Comment as a strike, with a dead ball and no runner advance—not as catcher interference. “The bat touched the catcher” is therefore not enough; the replay must show when and which player's action caused the hindrance.
Ordinary penaltyBatter to first; other runners do not all move automatically
If the interference penalty is applied, Rules 5.05(b)(3) and 6.01(c) entitle the batter to first without liability to be put out, provided the batter advances to and touches first. A runner advances one base without liability when forced by that award under Rule 5.06(b)(3)(B).
That means a runner on first is forced to second; runners on first and second are forced to second and third; and with the bases loaded, the runner from third scores. But with first base empty, a runner on second or third is not advanced merely because the batter receives first. A separate protection applies to a runner who was attempting to steal when the batter was interfered with.
Delayed enforcementWhy the umpire lets the action finish
Rule 6.01(c) deliberately preserves a potentially better result for the offense. When a play follows the interference, the umpire allows the action to continue. The call is enforced only after the play's result is known.
This is a delayed decision, not a rule that makes the interference disappear as soon as the ball is hit. A caught fly, an out at a base, runs scored, and extra bases all remain relevant because the offensive manager may prefer that live-ball result. If no play follows, there is no alternative result to select and the interference award is applied.
Automatic resultSometimes the play stands without a choice
The manager does not always receive an option. The final sentence of Rule 6.01(c) says the play proceeds without reference to the interference when both tests are met:
- The batter reaches first on a hit, error, walk, hit by pitch, or otherwise.
- Every other runner advances at least one base.
If there are runners, check each one separately. A runner who reaches the next base and is then retired trying for an additional base has still satisfied the one-base part of the test. The Rule 6.01(c) Comment also treats a missed next base as reached for deciding whether this automatic provision applies; ordinary appeal consequences can still matter. If either test fails, move to the manager's option.
Manager's optionThe choice is the whole play or the penalty
When action followed but the automatic-result test was not met, the offensive manager may decline the interference penalty and accept the actual play. Rule 6.01(c) requires that election immediately at the end of the play.
The manager cannot mix outcomes—for example, keep a run from the play, erase an out, and also place the batter on first. Accepting the play keeps its result. Accepting the penalty awards the batter first, advances runners who are forced or separately protected as stealers, and removes the unsupported results of the play.
Runner stealingA stealing runner receives a separate one-base award
Rule 5.06(b)(3)(D) entitles a runner to advance one base without liability when that runner was attempting to steal and the batter was interfered with by the catcher or another fielder. This protection does not depend on the batter's first-base award creating a force.
For example, with first base empty, a runner attempting to steal third from second is awarded third when the interference penalty is applied. A runner merely taking a secondary lead or advancing only because the ball was put in play is not automatically a “runner attempting to steal”; that factual judgment matters.
Steal of homeA squeeze or steal from third has an immediate dead-ball rule
MLB Rule 6.01(g) is the important exception to the ordinary delayed-option process. It applies when a runner on third is trying to score by a squeeze play or steal and the catcher or another fielder either:
- Steps on or in front of home plate without possession of the ball; or
- Touches the batter or the batter's bat.
The ball is dead, the pitcher is charged with a balk, and the batter is awarded first for the interference. The balk award advances each runner one base, so the runner trying to score from third is awarded home. Because the ball is dead under this provision, the offense does not wait to compare a later batted-ball result under the ordinary Rule 6.01(c) option.
Decision pathHow to rule the play in order
- Identify the protected moment. Did a catcher or other fielder hinder the batter's attempt to hit a delivered pitch?
- Separate later contact. Pre-delivery contact, batter interference with a throw, and an unintentional backswing use different rulings.
- Check third base. If a runner was trying to score on a squeeze or steal and Rule 6.01(g)'s conduct occurred, call the ball dead and apply that special penalty.
- Let an ordinary play finish. Preserve the offense's possible benefit under Rule 6.01(c).
- Apply the automatic-result test. Did the batter reach first and every runner advance at least one base? If yes, the play stands.
- If not, obtain the immediate election. The offensive manager chooses the complete play or the interference penalty.
- Place runners under the chosen result. On the penalty, award forced runners and any runner who was attempting to steal; do not advance everyone by assumption.
Worked case 1The bat clips the mitt and the batter misses
Situation: with no runners, the catcher reaches forward; the swinging bat contacts the mitt, and the batter misses the pitch.
MLB OBR 2026 ruling: award the batter first under Rules 5.05(b)(3) and 6.01(c). There is no useful batted-ball play to preserve. The decisive fact is that the fielder hindered the batter while the batter was trying to hit the delivered pitch.
Worked case 2A single advances every runner one base
Situation: runner on first. The bat clips the mitt, but the batter singles; the batter reaches first and the runner reaches second.
MLB OBR 2026 ruling: the play stands automatically. Both parts of Rule 6.01(c)'s final-sentence test are satisfied. This is not a manager declining the penalty; the rule proceeds without reference to the interference.
Worked case 3A sacrifice fly may be better than the award
Situation: runner on third, one out. Catcher interference occurs, but the batter's fly is caught and the runner legally scores after the catch.
MLB OBR 2026 ruling: this is one of the rulebook's own examples of the manager's option. The manager may accept the run and the batter's out, or apply the interference penalty, place the batter on first, and return the runner to third. The options cannot be combined.
Worked case 4An unforced runner who was stealing is protected
Situation: runner on second attempts to steal third. The catcher interferes with the batter's swing, and no advantageous play follows.
MLB OBR 2026 ruling: award the batter first under Rule 6.01(c) and the stealing runner third under Rule 5.06(b)(3)(D). The runner's award comes from the steal provision, not from a force created by the batter going to first.
Worked case 5A runner on third does not always score
Situation: runners on first and third. The catcher interferes with a swing; the runner on third was not trying to steal home, and no play follows.
MLB OBR 2026 ruling: batter to first, runner from first to second because forced, runner on third remains at third. Rule 6.01(g) does not apply without a squeeze or attempted steal of home, and ordinary catcher interference does not award every runner one base.
Worked case 6The catcher moves in front on a squeeze
Situation: the runner from third breaks for home on a squeeze. Before possessing the ball, the catcher steps in front of home plate and contacts the batter's bat.
MLB OBR 2026 ruling: Rule 6.01(g) makes the ball dead, charges the pitcher with a balk, awards the batter first, and awards the runner home. The decisive facts are the attempt to score from third and the fielder's position or contact specified by the special rule.
ReplayThe interference judgment is not an MLB challenge category
MLB's current published list of reviewable calls includes such matters as force and tag plays, hit by pitch, home-plate collisions, and double-play interference. It does not list catcher interference. The judgment whether the catcher hindered the batter is therefore not itself a manager-challenge category under that published list.
A separate reviewable event within the continuing play can still be reviewed—for example, a force or tag call. MLB's replay guidance says that when review changes a call, a manager whose later strategic choice was influenced by the incorrect call may reaffirm or change that decision. That matters if a reviewed component changes whether taking the play is preferable.
ScoringPlate appearance, no at-bat, and an error
When the batter is awarded first for interference, MLB Rule 9.02(a)(1)(D) records no time at bat, while Rule 9.02(a)(15) separately records the award. Rule 9.22 includes that award in total plate appearances. The batter receives no hit.
Rule 9.12(c) charges one error to the fielder who committed the interference when the umpire awards one or more bases, regardless of how many bases are awarded. Rule 9.16 treats a defensive-interference penalty as a fielding chance for earned-run reconstruction; a batter-runner who reaches first on catcher's interference is not an earned run if that runner later scores. If the offense instead takes the live-ball play, score the accepted play rather than the rejected award.
Common mistakesSix claims the MLB rule does not support
- “The ball is always dead immediately.” Ordinary Rule 6.01(c) action is allowed to finish; the squeeze/steal-of-home rule is immediately dead.
- “The manager always chooses.” There is no choice when the batter reaches first and every runner advances at least one base; the play stands automatically.
- “Every runner gets one base.” On the ordinary penalty, other runners advance only if forced or if attempting to steal.
- “It must be intentional.” Rules 5.05(b)(3) and 6.01(c) contain no intent requirement.
- “Any bat-catcher contact is catcher interference.” Pre-delivery contact, batter interference, and unintentional backswing contact have different rulings.
- “Video can always fix it.” Catcher interference is not included in MLB's published list of manager-challenge categories.
Competition limitsDo not transfer this ruling blindly
Professional, college, high-school, youth, and international baseball can use different rule numbers, terminology, option procedures, and special competition regulations. The MLB book itself notes that amateur and non-professional organizations may modify specifications for their needs.
For a game outside MLB's professional rules family, identify the appointed code and current season before applying this decision path. This page deliberately does not claim an unverified NCAA, NFHS, Little League, WBSC, or tournament variation.
Official referencesGoverning-body sources and effective version
- Office of the Commissioner of Baseball — Official Baseball Rules, 2026 Edition: Rules 5.05(b)(3), 5.06(b)(3), 6.01(c), 6.01(g), 6.03(a), 9.02, 9.12(c), 9.16, and 9.22
- Major League Baseball — Catcher Interference glossary, current 2026 explanation
- Major League Baseball — Replay Review glossary, current 2026 reviewable-call list
Checked on 26 August 2026 against MLB's 2026 Official Baseball Rules and current MLB rules pages. The 2026 rulebook governs MLB and its professional development league system; competition regulations and other baseball codes may supplement or replace this baseline.