pdf832 B

Intentionally Corrupt — Truncated PDF

An intentionally corrupt PDF, truncated to 60% of its bytes, for testing how a PDF parser handles a damaged file. Not a valid document by design.

Error handling PDF editor testing

pdf

application/pdf

832 B

Corruption: truncated to 60% of bytes
Intentionally Corrupt: true

Binary pdf — no in-browser preview. Download it above to open in a compatible application.

Specifications

Corruption: truncated to 60% of bytes
Intentionally Corrupt: true

What is a .pdf file?

PDF (Portable Document Format) is a page-oriented format that fixes layout, fonts, and vector and raster graphics so a page renders identically anywhere. A `%PDF-` header is followed by numbered objects, a cross-reference table mapping each to a byte offset, and a trailer; edits append incremental updates rather than rewrite the file. Page content is a stream of drawing operators, so a PDF holds no words or paragraphs, only positioned glyph runs. Adobe released it in 1993 and gave it to ISO as ISO 32000-1 in 2008.

How to use this file

Use an example PDF to test text extraction, rendering, metadata parsing, AcroForm handling, and OCR pipelines — checking that extraction reconstructs reading order from glyph positions, that a scanned page yields no text, and that an incremental update leaves earlier revisions in the file.

How to use this file for testing

“Intentionally Corrupt — Truncated PDF” is a deterministic Novus Examples fixture for Error handling, PDF editor testing. Deliberately corrupt and invalid files, clearly labelled, for testing how your tool fails.

Documented properties for this file: intentionally corrupt. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Document fixtures list their internal structure (pages, fields, tracked changes, embedded objects) in the spec table. Test extractors, converters, and OCR against that known structure, and compare searchable↔scanned or format-twin companions when present.

Code examples

import pdfplumber  # pip install pdfplumber

with pdfplumber.open("truncated.pdf") as pdf:
    print(len(pdf.pages), "pages")
    print(pdf.pages[0].extract_text())