platen-document
platen-document is a standalone local Python document-processing SDK copied
from PDFNest's proven local OCR V2 engine.
The 0.1.x releases are parity-focused. They are intentionally not an OCR-quality redesign and do not change the current detector, structure heuristics, rendering, or validation contracts.
Included capabilities
- native PDF text extraction and conservative native/scanned routing;
- local Tesseract OCR with explicit languages and the current bounded AUTO policy;
- canonical word, line, block, reading-order, provenance, and validation results;
- structured-document extraction with the current bounded headings, lists, and simple-table behavior;
- Markdown rendering;
- searchable-PDF rendering with invisible text and independent validation;
- query-based and typed region-based Highlight, Underline, and Strikeout markup; and
- local capability inspection through
DocumentProcessor.capabilities()orplaten-document doctor.
Minimal usage
from platen_document import DocumentProcessor
processor = DocumentProcessor()
ocr_result = processor.extract_text("document.pdf")
structured = processor.extract_document("document.pdf")
markdown = processor.to_markdown(structured)
processor.make_searchable_pdf("scanned.pdf", "scanned-searchable.pdf")
Application adapters that need to preserve the canonical searchable-PDF profile can use the public profile enum and pass an already extracted result to the render step, avoiding a second OCR pass:
from platen_document import DocumentProcessor, OCRProfile
processor = DocumentProcessor()
result = processor.extract_text("scanned.pdf", profile=OCRProfile.SEARCHABLE_PDF_V2)
processor.make_searchable_pdf(
"scanned.pdf",
"scanned-searchable.pdf",
result=result,
job_id="optional-diagnostic-correlation",
)
extract_text also accepts the copied worker's routing_policy plus optional
cooperative cancellation_check, page_timeout_seconds, and
page_progress_callback controls. These are thin engine controls for an
application adapter; the SDK still does not own application jobs or storage.
The default routing policy preserves validated native text when appropriate.
An application adapter with a historical OCR-only contract may opt into
routing_policy="FORCE_OCR"; this selects the OCR route without changing the
default behavior of existing consumers.
The package can process local files without PDFNest backend, PostgreSQL, Redis, Dramatiq, frontend, HTTP services, authentication, billing, or application storage.
Region-based markup
DocumentProcessor.apply_markup_regions accepts typed, one-based page regions
in the existing visible CropBox-relative PDF-point coordinate space. Manual
regions annotate directly without OCR. OCR-aware regions can reuse a public
DocumentResult to avoid a second extraction pass, or perform one public
extract_text pass when no result is supplied. Per-region colors, cooperative
cancellation, and real annotation progress are supported. See
the region markup API guide for the full coordinate,
password, result, and overlap contract.
Version 0.1.1 fixed native rotated-page region selection without changing the public visible-region API or OCR/scanned geometry behavior. Version 0.1.2 extends that same coordinate contract to manual region annotation: the visible input rectangle is mapped exactly once into canonical PDF coordinates at the PyMuPDF writer boundary. Native PyMuPDF word boxes remain in unrotated PDF coordinates; OCR boxes remain in their existing visible space.
Configuration and system dependencies
Python dependencies are declared in pyproject.toml. The runtime expects a
system Tesseract installation and discovers its executable, tessdata
directory, and installed language packs. It never installs operating-system
packages or downloads OCR models.
from platen_document import DocumentProcessor, EngineConfiguration
processor = DocumentProcessor(EngineConfiguration(
tesseract_binary="/usr/bin/tesseract",
tessdata_dir="/usr/share/tesseract-ocr/5/tessdata",
))
The encoded OCR raster normally carries the configured DPI as PNG metadata. An adapter that must reproduce a historical OCR input contract can opt into the neutral public compatibility policy without changing rendered pixels:
from platen_document import (
DocumentProcessor,
EngineConfiguration,
RasterDpiMetadataPolicy,
)
processor = DocumentProcessor(EngineConfiguration(
raster_dpi=144,
raster_dpi_metadata_policy=RasterDpiMetadataPolicy.OMIT_DPI,
))
EMBED_DPI is the default. OMIT_DPI changes only the DPI metadata in the
encoded OCR image; it does not change raster dimensions, page geometry, or
the Tesseract language/routing policy. This option is intended for a
consumer-specific compatibility adapter, not for a product-wide environment
switch.
The copied engine retains its known tessdata fallback behavior, including
fallback from a stale TESSDATA_PREFIX when a known local system directory is
available.
Diagnostics
platen-document doctor
The doctor output contains safe local capability metadata only. It does not know about PDFNest users, guests, quotas, jobs, queues, storage providers, or secrets.
Boundary and current PDFNest consumer status
PDFNest authentication, anonymous ownership, quotas, rate limits, durable job
orchestration, storage policy, cleanup, product routes, and UI remain outside
this package. The following PDFNest consumers now have independent,
consumer-specific internal|sdk execution boundaries:
- OCR Text V2 (
OCR_TEXT_ENGINE); - Searchable PDF V2 (
SEARCHABLE_PDF_ENGINE); - Document Extraction V2 (
DOCUMENT_EXTRACTION_ENGINE); - PDF-to-Markdown V2 (
PDF_TO_MARKDOWN_ENGINE); - OCR-aware Highlight/Underline/Strikeout (
OCR_MARKUP_ENGINE); and - General Editor OCR (
EDITOR_OCR_ENGINE).
Each selector defaults to internal; sdk is an explicit opt-in. The frozen
PDFNest implementation remains available as the default and configuration-only
rollback/reference path; there is no implicit runtime fallback from a selected
SDK engine. PDF-to-Word OCR fallback and Studio OCR/document paths remain
internal-only and are not migrated.
Registry delivery remains separately classified
DOCUMENT_SDK_REGISTRY_DEPENDENCY_DELIVERY_BLOCKED_EXTERNAL; no package has
been published to a public registry.
Metadata
Release files for platen-document 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| platen_document-0.1.2.tar.gz | 79.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| platen_document-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 157.8 kB
Release files / platen_document-0.1.2.tar.gz
| Download URL | platen_document-0.1.2.tar.gz |
|---|---|
| Size | 79.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
32db230ddb05f2f6b4c63d12b4c9a07a52e48737eabbbde6f1d93bd3960c9d2d
|
|
BLAKE2b-256 checksum How to use checksums |
e4b501879ae0c437151b2927ea3c1aa5be2a9559d776960a64711720fd260f62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency logRelease files / platen_document-0.1.2-py3-none-any.whl
| Download URL | platen_document-0.1.2-py3-none-any.whl |
|---|---|
| Size | 78.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
53306c7d047e6f336b6b93486ecc5b51dede537d93839b70a768dbd401858c30
|
|
BLAKE2b-256 checksum How to use checksums |
2efb80219f383d977664eae3630abc27afcd53163d39cddfc3fce5908ec07c70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 7, 2026.
Transparency log