{
  "id": "punched-card",
  "title": "Punched Card",
  "lang": "en",
  "source_lang": "en",
  "summary": "A punched card is a physical medium that represents data or instructions through patterns of holes, historically used in automated machinery, business data processing, and computing.",
  "category": "computer-science",
  "subcategory": "hardware",
  "type": "concept",
  "aliases": [
    "Punch card",
    "Hollerith card"
  ],
  "generated_at": "2026-11-03",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/punched-card/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/punched-card/",
      "json": "https://aiwiki.page/zh/punched-card.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "A punched card is a sheet of stiff paper or thin cardboard in which holes at predefined positions represent data or instructions. Machines read the pattern mechanically, electrically, or optically. Punched cards were used to control textile machinery before becoming a major medium for statistical tabulation, business recordkeeping, and input to computers. Their significance lies both in storing machine-readable information outside a machine and in allowing that information to be rearranged, duplicated, and processed automatically."
    },
    {
      "heading": "Origins and historical development",
      "text": "Textile machinery and programmable control\n\nThe use of perforated material to control machinery predates electronic computing. Eighteenth-century textile inventors developed mechanisms using perforated paper and cards to select threads during weaving. In the early nineteenth century, Joseph-Marie Jacquard brought together and improved earlier techniques in the Jacquard mechanism, which used linked punched cards to control the selection of warp threads.\n\nEach card specified part of a woven pattern. Changing the card sequence changed the pattern without requiring the loom's mechanism to be rebuilt. These cards were control media rather than business records, but they established an influential principle: a machine's actions could be directed by externally encoded instructions.\n\nCharles Babbage incorporated punched-card control into his design for the Analytical Engine in the nineteenth century. The design distinguished cards specifying operations from cards identifying variables. The complete engine was not built in his lifetime, but its proposed use of cards was an important connection between automated weaving and general-purpose computation.\n\nStatistical tabulation and business processing\n\nHerman Hollerith developed punched-card equipment for statistical processing in the late nineteenth century. His system was used in the 1890 United States census. Holes represented attributes of individuals, and electrical contacts detected the holes to operate counting mechanisms.\n\nHollerith's business became one of the companies combined in 1911 to form the Computing-Tabulating-Recording Company, renamed International Business Machines in 1924. Punched-card systems subsequently became widely used for payroll, accounting, insurance, inventory, and government statistics.\n\nThese installations often operated without a general-purpose electronic computer. Different machines punched cards, sorted them, compared records, and accumulated totals. This arrangement became known as unit record processing, because an individual card commonly represented one person, transaction, account, or other record.\n\nElectronic computing\n\nPunched cards became a major input medium for electronic computers in the mid-twentieth century. Existing card files and equipment helped organizations move from electromechanical tabulation to electronic data processing.\n\nCards could hold programs, numerical input, transaction records, and control instructions. They remained common in mainframe environments through the 1960s and 1970s, although the timing of their replacement varied by organization and application. Interactive terminals, magnetic tape, and disks gradually displaced them in routine computing."
    },
    {
      "heading": "Physical form and information encoding",
      "text": "The 80-column card\n\nThe best-known computer punched card is IBM's 80-column card, introduced in 1928. Its nominal dimensions are 7⅜ by 3¼ inches, approximately 187.3 by 82.6 millimetres. It has 80 columns and 12 possible punching positions in each column. The rows are conventionally designated 12, 11, 0, and then 1 through 9.\n\nIn common alphanumeric encodings, a column represents one character:\n\n- A digit is usually represented by one punch in its numbered row.\n- A letter is typically represented by a combination of a zone punch and a digit-row punch.\n- Punctuation and special characters use additional combinations, which vary by code and equipment.\n\nThus, a standard card commonly holds 80 characters. Although its layout contains \\(80 \\times 12 = 960\\) possible hole positions, this does not make its usual character capacity equivalent to 960 independently usable bits. Capacity depends on the encoding and on which punch combinations the equipment accepts. Some applications used binary formats that exploited the card differently.\n\nCard codes were not identical to later character encodings such as ASCII. Readers and computer interfaces interpreted or translated the physical punch patterns according to the applicable code.\n\nMany cards carried printed column numbers, field labels, or form layouts. Keypunch equipment could also print characters along the top edge, allowing an operator to inspect the contents without decoding holes by eye.\n\nRecords, fields, and sequence\n\nBusiness cards were commonly divided into fixed-width fields. For example, designated columns might contain an employee number, department, hours worked, and wage rate. Correct interpretation depended on knowing the card layout.\n\nA collection of cards was called a deck. The order of a deck could itself carry information, especially when it contained a program or a sequence of transactions. Sequence numbers were often punched into reserved columns so that a deck could be restored after being dropped or mixed.\n\nCards were not necessarily individual records in every application. A record could span several cards, and a card could instead contain an instruction, a fragment of text, or specially encoded numerical data."
    },
    {
      "heading": "Creating, reading, and processing cards",
      "text": "A keypunch produced holes as an operator entered information from a keyboard or source document. Specialized equipment could also punch cards automatically from machine-generated data.\n\nVerification was an important part of data preparation. In a common workflow, another operator re-entered the source information at a verifier, which compared the keystrokes with the existing punches and signalled discrepancies. Verification reduced transcription errors but could not establish that the source information itself was correct.\n\nReading methods included:\n\n- Mechanical sensing: pins or similar mechanisms detected openings.\n- Electrical contact sensing: brushes or contacts completed a circuit through a hole.\n- Optical sensing: light passing through holes was detected by photosensitive components.\n\nCards were usually fed through a reader one at a time. Some readers processed large decks at hundreds or more than a thousand cards per minute, depending on the equipment.\n\nA tabulating machine could accumulate values and print results. Sorters distributed cards into pockets according to a selected column or punch position. Repeated sorting passes could arrange records by a multicolumn key, using procedures related to radix sort. Collators compared card streams, helping to merge files or match transactions with master records.\n\nThese systems could perform substantial administrative work, but their operations depended on the machinery and its setup. A deck was a physical representation of records, not automatically a database with the querying, integrity constraints, or concurrent access associated with later software systems."
    },
    {
      "heading": "Punched cards in programming",
      "text": "In card-based programming, a programmer commonly prepared a deck containing source code. The deck was read into a computer, translated by a compiler or assembler, and executed, often alongside control cards and input data.\n\nThis workflow was closely associated with batch processing. Users submitted jobs to an operations staff or input station and received printed output later. An error might require replacing a card and resubmitting the job, making turnaround time an important practical constraint.\n\nCard dimensions influenced programming-language conventions. Traditional fixed-form Fortran, for example, used columns 1–5 for statement labels, column 6 for continuation, and columns 7–72 for statement text. Columns 73–80 were commonly available for sequence identification. Such conventions were retained in software after physical cards ceased to be the normal input medium.\n\nA deck did not always contain source code. Cards could also hold machine-readable binary information, object programs, or commands interpreted by an operating system. The distinction between program, data, and job-control cards depended on the surrounding system."
    },
    {
      "heading": "Other formats and related media",
      "text": "The 80-column format was influential but not universal. Earlier Hollerith cards had different layouts. Remington Rand equipment used 90-column cards with round holes, while IBM introduced a smaller 96-column format for its System/3 in 1969. Physical dimensions, hole shapes, encodings, and reading equipment differed among systems.\n\nSome cards combined punched information with other media. An aperture card, for example, incorporated a window holding a microfilm image, while punched fields could identify or index the document.\n\nPunched cards should be distinguished from punched tape, which stores hole patterns along a continuous strip. Cards support convenient handling and rearrangement of separate records; tape provides a continuous sequence. Edge-notched cards are another distinct technology: notches along their edges allow manual selection, rather than ordinary reading by a punched-card machine."
    },
    {
      "heading": "Advantages, limitations, and legacy",
      "text": "Punched cards offered a reusable, machine-readable medium that could be handled without electrical power. Individual records could be inspected, replaced, duplicated, or physically rearranged. A deck also provided a tangible input copy that could be stored and rerun.\n\nTheir limitations were substantial:\n\n- Low storage density: large files required extensive cabinet and floor space.\n- Sequential access: finding or processing records generally required feeding cards through equipment or physically locating them.\n- Mechanical vulnerability: bends, tears, moisture, static electricity, and wear could interfere with feeding or reading.\n- Order dependence: a mixed deck could become unusable unless its sequence could be reconstructed.\n- Difficult correction: an unwanted hole could not ordinarily be erased, so replacement was the normal remedy.\n- Labor-intensive preparation: punching, verification, transport, and filing required significant work.\n\nPunched-card ballots also appeared in elections. Incompletely detached pieces of card, known as chads, could complicate machine reading and interpretation. Such problems reflected the interaction between ballot design, punching equipment, physical material, and counting procedures.\n\nCards' most enduring influence is visible in computing conventions: fixed-width records, column-oriented input formats, batch job submission, and the familiar 80-column text width. The physical medium largely disappeared from ordinary computing, while some of the formats and workflows built around it persisted."
    }
  ],
  "links": [
    "computer",
    "charles-babbage",
    "population-census",
    "ibm",
    "mainframe-computer",
    "bit",
    "character-encoding",
    "ascii",
    "tabulating-machine",
    "database",
    "source-code",
    "compiler",
    "programming-language",
    "fortran",
    "operating-system"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}