One Greek letter turns a king into a psalmist. The Textus Receptus names Asa, king of Judah. The critical text printed by Nestle–Aland and the United Bible Societies names Asaph, the Levite linked with a group of Psalms. Because the name closes one clause and opens the next, the change appears twice.
“Abia begat Asa; and Asa begat Josaphat.” — Matthew 1:7–8
This is not a difference in English spelling. Asa was Abijah’s son and Jehoshaphat’s father. Asaph was not.
Why editors print Asaph
Asaph has old and varied support, including Sinaiticus, Vaticanus, and early versions. Critics also call it the harder reading. A scribe who found the wrong man in a royal genealogy would have a reason to remove the final phi and restore Asa; no equally obvious reason seems to turn correct Asa into Asaph.
That account is coherent, but it asks Matthew to make the very mistake later scribes would notice. Some defend the result by supposing that he copied a faulty list. The supposition protects a rule about harder readings at the cost of the Gospel’s historical claim.
Matthew did not place an obscure name in an open slot. His pattern says that Abijah begat the disputed man and that the same man begat Jehoshaphat. First Kings 15 and First Chronicles 3 name Asa in that exact line.
An old error is still an error
Asaph need not have arisen from a deliberate change. Both names were familiar to biblical readers, their Greek forms differ by one final letter, and Asaph’s name appeared often in psalm headings. A copyist can finish a short name with the ending his memory expects. Once the error entered an early exemplar, age and geographic spread would record its success, not its truth.
The broad Greek transmission keeps Asa. So do the Old Testament sources and the sense of the genealogy. These are not three unrelated votes. They join at the historical person Matthew is naming.
Inspiration should not be used as a shortcut that saves us from looking at manuscripts. It does tell us what kind of writing lies before us: Matthew’s genealogy makes true claims about the line of Christ. The evidence then points to the reading that tells that truth.
Asa belongs in both places. Asaph is ancient enough to deserve study, but not authentic enough to enter the royal line.
The paired occurrence makes the result unusually testable. Matthew does not merely use the disputed form once, where a reader might wonder about an unknown alternate spelling. He uses it on both sides of the same genealogical link. Whatever name he wrote must be the man begotten by Abijah and the man who begot Jehoshaphat. The Old Testament answers both relations with one voice.
Nor does receiving Asa require the claim that every late copy is good or every early copy bad. A single old exemplar can pass one mistake to several descendants; a later manuscript can preserve a reading older than its parchment. Dates belong to physical witnesses, while readings have histories that reach behind them. That is why antiquity must be joined to number, variety, continuity, context, and the author’s evident claim.
The choice also sets a rule for the genealogy that follows. Historical fitness does not override manuscript evidence, but neither may a favored manuscript rule force an inspired historian into a false assertion when an old, broad, and exact reading stands before us. Asa is not a theological repair. He is the king Matthew’s sentence requires.
Sources and further reading
- 1 Kings 15:8–24; 1 Chronicles 3:10; Matthew 1:1–17.
- Bruce M. Metzger, A Textual Commentary on the Greek New Testament, note on Matthew 1:7–8.
- John William Burgon and Edward Miller, The Traditional Text of the Holy Gospels.