
Please Support the Bible Translation Work of the Updated American Standard Version (UASV)
$5.00
![]() |
![]() |
![]() |
The Amsterdam Database of New Testament Conjectures is valuable precisely because it gathers a large body of proposed emendations into one searchable scholarly environment, but its value must be understood in documentary terms. A database of conjectures is not a treasury of recoverable apostolic readings. It is a record of scholarly proposals, many of which arose from perceived difficulty, stylistic discomfort, grammatical tension, historical uncertainty, or dissatisfaction with the printed Greek text at a given stage in the history of editing. The distinction is essential. A conjecture has no right to stand in the text merely because it is clever, elegant, or capable of producing smoother sense. In New Testament textual criticism, the text must be restored from the documentary evidence preserved in Greek manuscripts, ancient versions, and patristic citations, with priority given to early, textually disciplined witnesses. The autographic text was inspired, as indicated by Second Timothy 3:16 and Second Peter 1:20-21, but no doctrinal authority attaches to a modern conjecture that lacks transmissional support.
The Nature of a New Testament Conjecture
A conjecture, in the strict textual sense, is a proposed reading that is not preserved in the extant documentary tradition. It is an editorial reconstruction introduced because an editor believes every known reading is corrupt or inadequate. That definition separates conjecture from ordinary textual variation. When John 1:18 has “only-begotten god” in early Alexandrian witnesses and “only-begotten Son” in other witnesses, the issue is not conjectural, because both readings stand within the manuscript tradition. When Mark 16:9-20 is absent from Codex Sinaiticus and Codex Vaticanus but present in many later manuscripts, the question is not conjectural, because the longer ending exists in manuscripts. When John 7:53–8:11 is absent from the earliest and strongest witnesses but present in later and movable forms, the matter is still documentary, not conjectural. The critic evaluates evidence; he does not invent a new text.
This is why conjectural emendation must occupy only the most restricted place in New Testament study. The New Testament differs from many classical works because its textual base is abundant, early, and geographically broad. The discipline does not face a situation where the entire tradition rests on one late medieval copy. The New Testament is preserved in papyri, majuscules, minuscules, lectionaries, early translations, and patristic citations. A conjecture that ignores this abundance is not a restoration of the apostolic text but a substitution of editorial preference for transmitted evidence.
![]() |
![]() |
![]() |
The Database as a Record of Reception, Not an Authority for Adoption
The Amsterdam Database should be treated as a documentary history of conjectural activity. It records what scholars have proposed, where they proposed it, and how such proposals entered or failed to enter later discussion. This is useful because conjectures reveal where readers have felt tension in the text. A dense cluster of conjectures at a verse can indicate that the verse has been repeatedly perceived as difficult. Yet difficulty is not corruption. Romans 9:5 is difficult because punctuation and syntax affect interpretation, but the problem is not solved by inventing words. James 4:5 is difficult because its wording and scriptural allusion require careful grammatical analysis, but difficulty does not authorize textual replacement. First Peter 3:19-20 is difficult because it requires close attention to grammar and context, not because the transmitted wording has failed.
The database therefore helps the textual critic identify the history of scholarly dissatisfaction. It does not supply warrant to move a conjecture into the printed text. A catalog of proposals is not equivalent to a catalog of readings. A reading belongs to textual criticism when it is transmitted. A conjecture belongs to the history of interpretation and editing until documentary evidence gives it standing. If later manuscript evidence is discovered supporting a formerly conjectural proposal, the proposal ceases to be strictly conjectural at that point and becomes a variant reading subject to ordinary documentary evaluation.
![]() |
![]() |
![]() |
Documentary Priority and the Limits of Internal Reasoning
The documentary method begins with witnesses, not with editorial imagination. Early papyri, high-quality majuscules, coherent textual relationships, and demonstrable scribal habits provide the foundation. Internal evidence has a role, but it cannot overrule strong external support. The principle is simple: a reading that explains the rise of other readings deserves consideration, but only within the bounds of the manuscript tradition. A conjecture has no transmissional pathway unless the critic can show how the alleged original disappeared from every known witness while derivative readings survived everywhere. Such a claim requires more than grammatical discomfort; it requires an extraordinary account of total documentary loss.
The relationship between Papyrus 75 and Codex Vaticanus illustrates why conjecture is rarely necessary. Papyrus 75, dated 175–225 C.E., and Codex Vaticanus, dated 300–330 C.E., preserve a remarkably close textual relationship in Luke and John. Their agreement demonstrates that a disciplined Alexandrian textual stream reaches back into the second and early third centuries. This is not a late ecclesiastical reconstruction. It is a real line of transmission. When such witnesses preserve a difficult reading, the difficulty must first be explained as part of the transmitted text rather than treated as a defect requiring conjectural repair.
![]() |
![]() |
![]() |
The Alexandrian Tradition as a Control Against Speculation
The superiority of the Alexandrian text-type lies in its early attestation, restraint, and relative freedom from harmonizing expansion. This does not mean every Alexandrian reading is automatically original. It means that Alexandrian witnesses, especially the early papyri and Codex Vaticanus, form a primary control against later expansion and editorial smoothing. When Papyrus 66, dated 125–150 C.E., preserves a Johannine text that is already close to the form later represented by strong Alexandrian witnesses, the critic has evidence of stability, not chaos. When Papyrus 75 aligns with Vaticanus across substantial portions of Luke and John, conjecture loses force because documentary continuity is present.
This matters when evaluating conjectures. A conjectural reading that makes a verse smoother than the Alexandrian text must be viewed with suspicion. Scribes often smoothed grammar, expanded titles, clarified subjects, harmonized parallel passages, and supplied liturgical or explanatory material. They did not normally preserve rougher readings everywhere while eliminating the smoother original from all witnesses. If the extant text is difficult but well supported by early Alexandrian evidence, the burden rests heavily on the conjecture, and that burden is almost never met.
![]() |
![]() |
![]() |
Examples That Clarify the Difference Between Variants and Conjectures
Several major New Testament passages show why documentary evaluation must precede conjectural thinking. Mark 16:9-20 is absent from Codex Sinaiticus and Codex Vaticanus and displays vocabulary and stylistic features that distinguish it from the preceding Gospel narrative. Yet its existence in later manuscripts means it is a secondary textual addition, not a conjectural invention by modern editors. John 7:53–8:11 appears in different locations in the manuscript tradition and is absent from the earliest and best witnesses, but again the issue is documentary. Acts 8:37 is absent from the earliest Greek witnesses and appears in later tradition as an expanded baptismal confession. First John 5:7 contains the famous Trinitarian expansion in late Latin-influenced transmission, but its evaluation depends on manuscript history, not conjecture.
These examples demonstrate that the New Testament critic already has enough evidence to identify many secondary readings without creating new ones. The task is restoration, not reinvention. Even where the text is difficult, the critic must ask whether the difficulty arises from authorial style, Semitic influence, compressed syntax, rhetorical emphasis, or scribal transmission within attested readings. A conjecture that bypasses those questions short-circuits the discipline.
![]() |
![]() |
![]() |
Scriptural Grounding for Textual Restraint
The New Testament itself supports careful attention to written words. Matthew 5:18 records Jesus’ affirmation that not the smallest letter would pass from the Law until fulfillment. While that statement concerns the Law, it establishes the seriousness with which Scripture is to be treated at the level of written expression. Luke 1:1-4 shows concern for orderly written transmission and accurate instruction. John 20:30-31 identifies the written Gospel as the means by which readers come to believe that Jesus is the Christ, the Son of God. First Corinthians 15:3-4 shows Paul transmitting received apostolic content with precision concerning Christ’s death, burial, and resurrection. Revelation 22:18-19 warns against adding to or taking away from the words of the prophecy. These passages do not teach a mechanical theory of manuscript copying, but they do require reverence for the transmitted wording of Scripture and resistance to unnecessary alteration.
The Holy Spirit inspired the Scriptures through the prophets and apostles, as Second Peter 1:20-21 teaches. That inspiration attaches to the original writings, not to every scribal copy and not to later conjectural proposals. The critic therefore honors the Spirit-inspired Word by seeking the text through evidence rather than by creating readings that no known witness preserves. The documentary method is not skepticism. It is disciplined respect for the way the text has actually been transmitted.
![]() |
![]() |
![]() |
Why the New Testament Does Not Need Regular Conjectural Repair
The argument against regular New Testament conjecture rests on the character of the evidence. The Greek manuscript tradition is extensive. The early papyri are close in date to the autographs when compared with the manuscript situation of most ancient literature. Majuscule witnesses such as Codex Vaticanus, Codex Sinaiticus, Codex Alexandrinus, and Codex Ephraemi Rescriptus preserve large portions of the text. Versions such as the Old Latin, Syriac, Coptic, Gothic, Armenian, and Georgian traditions provide early translational evidence. Patristic citations, though requiring caution, often show how passages were read in specific regions and periods.
This evidence does not remove every difficulty, but it gives the critic a real transmissional field. The article on the transmission of the New Testament text rightly belongs in this discussion because the text was preserved through copying, comparison, correction, and continued use. Scribal errors occurred, but the multiplicity of witnesses allows those errors to be identified. A singular blunder in one manuscript can be isolated. A regional expansion can be detected. A harmonization can be compared with parallel passages. A liturgical addition can be recognized when absent from early witnesses and present in later ecclesiastical forms. Conjecture becomes unnecessary when evidence supplies the means of correction.
![]() |
![]() |
![]() |
The Problem of Total Loss
Every conjectural emendation must face the problem of total loss. If a proposed reading is original but absent from all known Greek manuscripts, all known versions, and all known patristic citations, then the critic must explain how that original vanished without trace. In a narrow and late manuscript tradition, such an argument can occasionally be considered. In the New Testament, the argument is far weaker because the evidence is not narrow. The tradition is multiform, geographically distributed, and early. A reading known in Egypt, Caesarea, Rome, Antioch, or North Africa had pathways for survival through Greek copying, translation, and citation. Total loss across all channels requires an exceptional explanation.
This is especially important in passages where conjectures are proposed because a phrase appears abrupt. Abruptness is not proof of corruption. Paul writes compressed arguments, as in Romans 5:12-21. John uses simple vocabulary with deep theological density, as in John 1:1-18. Mark’s style can be rapid and vivid, as in Mark 1:12-13. James employs sharp ethical exhortation, as in James 4:1-10. Revelation contains Semitic influence, prophetic symbolism, and unusual grammar, as in Revelation 1:4 and Revelation 13:18. The critic must not force every author into classical smoothness and then declare the transmitted text corrupt when it resists that standard.
![]() |
![]() |
![]() |
Scribal Habits and the Evaluation of Proposed Emendations
Scribal habits provide a necessary control. Scribes accidentally omitted words through homoioteleuton, repeated words through dittography, confused similar letters, harmonized Gospel parallels, expanded divine titles, clarified pronouns, and adjusted grammar. These habits are visible in manuscripts. They can explain many variants without conjecture. For example, when a later manuscript expands “Jesus” to “the Lord Jesus Christ,” the expansion follows a known reverential and clarifying tendency. When a Gospel passage is adjusted to match a parallel in Matthew, Mark, or Luke, harmonization provides a concrete explanation. When a short Alexandrian reading stands against a longer Byzantine expansion, documentary and scribal evidence often converge.
A conjecture must be tested against these observable habits. If the conjecture requires scribes everywhere to have made the same unlikely alteration independently, it fails. If it requires a difficult reading to have replaced a smoother reading in every line of transmission, it fails. If it exists only because an editor dislikes the author’s grammar, it fails. If it solves a perceived theological tension by changing the wording without evidence, it fails. Textual criticism is not a tool for making Scripture conform to later expectations. It is a discipline for restoring what the authors wrote.
![]() |
![]() |
![]() |
The Role of the Byzantine and Western Traditions
The Byzantine and Western traditions must not be dismissed, but they must be evaluated according to documentary quality and transmissional history. The Byzantine tradition often preserves the ecclesiastical text that became dominant in the medieval period. Its numerical strength reflects later copying history, not automatic originality. The Western tradition, especially in witnesses such as Codex Bezae, preserves striking readings, expansions, paraphrastic tendencies, and distinctive forms, particularly in Acts. These traditions can preserve original readings in specific places, but they cannot override earlier and stronger evidence merely by age of later popularity or by vividness of wording.
The Amsterdam Database is useful here because some conjectures arise from the same impulse visible in Western expansion: a desire to make the text more explanatory, dramatic, or explicit. The documentary critic must distinguish between a reading that entered transmission early and a conjecture that never entered transmission at all. A Western reading can be examined as evidence. A Byzantine reading can be examined as evidence. A conjecture without documentary support remains outside the evidential field.
![]() |
![]() |
![]() |
Printed Editions and the History of Conjectural Interest
The history of printed Greek New Testament editions explains why conjectures accumulated. Early editors worked with limited manuscript access. Erasmus published his first Greek New Testament in 1516 C.E. using a small group of late manuscripts. Later editors inherited and modified printed forms, sometimes with insufficient documentary breadth. As more manuscripts became known, especially early uncials and papyri, the need for conjecture diminished. The move from the Textus Receptus toward documentary criticism was not an abandonment of Scripture but a recovery of earlier evidence. The history of New Testament textual criticism demonstrates that progress came through manuscripts, not through conjectural brilliance.
This historical point must govern how the Amsterdam Database is used. A conjecture proposed before the full weight of papyri and major uncials was known cannot be treated as though it arose in the same evidential environment available today. Some older conjectures were attempts to solve problems created by dependence on late printed forms. Once earlier manuscripts are brought into view, the conjectural solution loses force. The database preserves those proposals as part of scholarly history, but documentary criticism decides whether the text requires them. In the overwhelming majority of New Testament cases, it does not.
![]() |
![]() |
![]() |
Conjectural Emendation and the Apparatus
A conjecture may have a place in an apparatus as a record of scholarly proposal, but it should not enter the main text without documentary support. The main text should represent the best recoverable wording from extant evidence. An apparatus can record rejected proposals, historical conjectures, and interpretive alternatives. This distinction protects readers from confusing speculation with text. It also allows scholars to study conjectural history without granting conjecture equal standing with manuscript readings.
The difference is practical. A pastor, translator, or teacher using a Greek text needs to know whether a reading is attested by Papyrus 75, Codex Vaticanus, Codex Sinaiticus, Codex Alexandrinus, a group of minuscules, an early version, or a church father. That information helps determine whether the reading belongs to transmission. A conjecture with no such support should be clearly marked as conjecture. It must not be presented as a recovered apostolic word. To do so would blur the boundary between evidence and invention.
![]() |
![]() |
![]() |
The Amsterdam Database and Responsible Scholarly Use
The responsible use of the Amsterdam Database begins with classification. The critic must ask whether the entry is a true conjecture, an editorial alternative, a punctuation proposal, a proposed transposition, a spelling adjustment, or a reading later found in documentary evidence. Not every proposal has the same textual significance. A punctuation decision can affect interpretation without changing the Greek letters. A transposition can rearrange words while preserving vocabulary. A substitution introduces a different word. An omission removes transmitted wording. An addition supplies wording not preserved. Each kind of proposal must be evaluated differently.
The database also helps identify repeated scholarly pressure points. If many conjectures cluster around a passage, the critic should examine why. The reason can be grammatical difficulty, perceived historical tension, theological discomfort, or the influence of earlier printed editions. Yet the existence of a pressure point does not establish corruption. It establishes that the passage deserves close grammatical, contextual, and documentary examination. The critic must then return to the manuscripts. The database points to questions; it does not answer them authoritatively.
![]() |
![]() |
![]() |
Textual Certainty and the Rejection of Skeptical Overreach
The presence of thousands of conjectures does not imply that the New Testament text is uncertain. It implies that many scholars have proposed many changes. The number of proposals is not evidence of textual instability. The same principle applies to the nature of textual variants in the New Testament. A high count of variants reflects the abundance of manuscripts. It does not mean every word is doubtful. Most variants are spelling differences, word order changes, minor omissions, harmonizations, or expansions that do not affect doctrine. The significant variants are relatively few, and they are handled by evidence.
Skeptical presentations often confuse the existence of variation with the absence of recoverability. The documentary record shows the opposite. Because there are many witnesses, the critic can compare them. Because early witnesses exist, the critic is not confined to late medieval forms. Because scribal habits are observable, the critic can explain how many secondary readings arose. Because textual families can be studied, readings can be weighed genealogically and geographically. Conjecture is weakest precisely where manuscript evidence is strongest.
![]() |
![]() |
![]() |
Theological Integrity and the Textual Task
The textual critic must not use conjecture to protect doctrine, soften doctrine, or reshape doctrine. The doctrine must arise from the text, not from editorial reconstruction. John 1:1 identifies the Word as God. John 20:28 records Thomas addressing the resurrected Jesus as his Lord and his God. Colossians 1:15-20 presents the Son’s preeminence in creation and reconciliation. Hebrews 1:3 describes the Son as the exact representation of God’s nature. These teachings do not rest on conjectural emendation. They rest on transmitted text. Likewise, the resurrection of Jesus rests on documentary testimony in passages such as First Corinthians 15:3-8, Luke 24:1-49, John 20:1-31, and Acts 2:22-36. The textual critic has no need to invent readings to sustain Christian doctrine.
This point is vital because conjecture can tempt editors in two opposite directions. One editor can propose a reading that removes theological difficulty. Another can propose a reading that strengthens a preferred doctrine. Both procedures are wrong. The text must not be altered to fit theology. The inspired wording must be restored from evidence. Where the manuscripts give certainty, the critic should speak with certainty. Where variants require careful evaluation, the critic should present the evidence. Where no documentary support exists, conjecture must remain outside the text.
![]() |
![]() |
![]() |
Practical Criteria for Evaluating a Proposed Emendation
A proposed emendation must first be tested by documentary absence. If any Greek manuscript, ancient version, or credible patristic citation preserves the reading, the proposal is no longer a pure conjecture and must be evaluated as a variant. If no witness preserves it, the critic must ask whether the transmitted readings are genuinely impossible or merely difficult. Genuine impossibility is rare. Difficult syntax, abrupt transitions, unusual vocabulary, and theological density do not equal corruption. The critic must then ask whether known scribal habits explain the extant readings. If ordinary scribal tendencies explain the variation, conjecture is unnecessary.
The critic must also test whether the conjecture explains the total manuscript situation better than the extant readings do. A conjecture that explains one difficulty while creating several transmissional impossibilities is unacceptable. For example, a conjecture that smooths grammar but requires every known textual stream to have lost the same original word lacks documentary plausibility. A conjecture that produces elegant Greek but contradicts the author’s known style is likewise weak. A conjecture that depends on modern discomfort with Semitic influence in Revelation or compressed Pauline syntax confuses editorial taste with textual evidence.
![]() |
![]() |
![]() |
The Place of the Database in Conservative Textual Study
The Amsterdam Database can serve conservative textual study when it is used as a warning against speculative excess and as a map of prior scholarly discussion. It shows how easily conjectural thinking multiplies. One proposed change invites another. A difficult clause becomes a site for repeated experimentation. The history of conjectures demonstrates that brilliance is not the same as evidence. Many conjectures solve one problem by creating another. Some are grammatically attractive but documentarily baseless. Others are ingenious but unnecessary once early manuscripts are considered.
The conservative documentary approach therefore receives the database as a tool, not a judge. It can help locate passages that have drawn conjectural attention. It can help trace the history of editorial proposals. It can help distinguish genuine variants from unsupported reconstructions. It can also strengthen confidence in the transmitted text by showing that conjecture, when tested against the evidence, rarely improves upon the manuscript tradition. The restored New Testament text is not built from conjectures. It is built from witnesses.
![]() |
![]() |
![]() |
The Final Standard: Manuscript Evidence Before Editorial Ingenuity
The final standard in evaluating proposed emendations is not whether a conjecture produces a smooth reading, a striking reading, or a reading favored by a scholar. The final standard is whether the proposed wording belongs to the transmissional evidence. The early papyri, the great majuscules, the versions, and patristic citations provide the field in which restoration occurs. The uncial manuscripts are especially important because they preserve large sections of the Greek text in forms earlier than the medieval manuscript majority. When their evidence aligns with early papyri, the case for documentary stability becomes strong.
The Amsterdam Database of New Testament Conjectures therefore has a legitimate place in textual scholarship, but that place is subordinate. It preserves the history of proposals; it does not determine the text. It assists investigation; it does not authorize alteration. It records conjectural imagination; it does not replace manuscript evidence. A proposed emendation must remain outside the main text unless documentary support brings it into the field of evidence. The New Testament text was transmitted through real manuscripts, and its restoration must proceed by real manuscripts. That is the safeguard against both skeptical instability and editorial overconfidence.
![]() |
![]() |
![]() |
You May Also Enjoy
The Sahidic Coptic Version and Early Alexandrian Readings: Supporting Evidence for the Critical Text




























































Leave a Reply