Forty Stripes, and Not Exceed: The Limit on Lashes
'The judge shall cause him to lie down, and to be beaten before his face, according to his fault, by a certain number... Forty stripes he may give him, and not exceed.' Deuteronomy 25:2-3 places a hard ceiling on judicial punishment — not for the offender's comfort, but, as the verse itself says, 'lest... thy brother should seem vile unto thee.' Centuries later, Paul would count among his sufferings 'forty stripes save one' (2 Corinthians 11:24), the thirty-nine-stripe tradition built on this very limit — while Jeremiah's beating by Pashur, with no judge, no count, and no cap (Jeremiah 20:2), shows what this commandment exists to prevent.
By a Certain Number, Before His Face
Two verses, read together, describe a single scene: a guilty man, a judge, and a number. Deuteronomy 25:2 places the punishment under the judge's direct supervision — "the judge shall cause him to lie down, and to be beaten before his face, according to his fault, by a certain number." Not an angry crowd, not a private grudge settled in the dark. A judgment, executed in the open, counted.
Then comes the limit: "Forty stripes he may give him, and not exceed." And then comes the reason — not procedural tidiness, but a person: "lest, if he should exceed, and beat him above these with many stripes, then thy brother should seem vile unto thee." The cap exists to protect something in the eyes of the one watching, not only in the body of the one being struck. Punishment that has no ceiling eventually teaches the community that the person receiving it is worthless — and Deuteronomy 25:3 refuses to let that lesson be taught. The word is the same word as #135's "thy brother" (Leviticus 19:17): even under judgment, even guilty, he does not stop being a brother.
Forty Stripes Save One
Centuries later, the apostle Paul listed this exact punishment among the things his body had carried: "Of the Jews five times received I forty stripes save one" (2 Corinthians 11:24). "Forty stripes save one" — thirty-nine. Jewish tradition read Deuteronomy 25:3's "not exceed" as a command demanding its own margin: count to thirty-nine, never forty, so that a miscount under pressure could never become the very transgression the law was written to prevent. The limit did not trust itself to be applied exactly at its edge. It built in room to fail safely.
Paul received this discipline five times over — from the same system that, on its own terms, was bound by Deuteronomy 25:3 even when administering it to him. Whatever judgment his synagogue communities reached about him, the number thirty-nine was itself a kind of testimony: a law still operating as Deuteronomy 25:3 intended, even at its sharpest edge.
What the Limit Was Meant to Prevent
Scripture also shows what punishment looks like once it forgets Deuteronomy 25:2's "certain number." When the prophet Jeremiah delivered a message the priest Pashur did not want to hear, Jeremiah 20:2 records the response: "Then Pashur smote Jeremiah, and put him in the stocks." No judge presiding. No count. No limit named, because none was intended — the point was not correction but silencing.
Set beside each other, the two scenes define the commandment by contrast. Deuteronomy 25:2-3 describes punishment that remains, even at its harshest, an act of justice: supervised, numbered, capped, and bounded by the dignity of "thy brother." Pashur's stocks describe punishment that has become something else entirely — an act of power with no court, no count, and no brother in view at all. The forty-stripe limit is not a loophole for cruelty. It is the line cruelty has to cross before it can call itself justice.
Key Figures
Study Questions
Deuteronomy 25:2-3 bounds punishment by a number and a witness so that even a guilty man remains 'thy brother' — a limit Paul's body bore, and Jeremiah's beating shows the absence of.
Open Deuteronomy 25:2 in Torah Reader