About PDFChamp
PDFChamp is a collection of browser-based tools for common PDF, image, form, OCR and print-preparation tasks.
What the project is for
The project focuses on useful, inspectable transformations without making a selected document travel to a remote conversion service. It currently provides 62 tools across ten categories. Each tool documents its accepted input, output and important trade-offs below the working interface.
What “in your browser” means
Local file processing and a completely network-free application are different claims. This is the boundary implemented by the current codebase:
| Area | Current behavior |
|---|---|
| Selected documents | Tool components read File objects in the browser. PDF and image operations do not send the selected file to a processing endpoint. |
| Downloads | Results are built as bytes or browser Blob objects and handed to the browser’s download flow. |
| Network access | The site and tool code must load first. OCR also fetches Tesseract language data from jsDelivr when that language is first used. |
| Offline use | A previously opened tool may continue to work when its required code and assets are already available. This is not a blanket offline guarantee. |
| Limits | Most tools are constrained by available device memory. Code to PDF separately rejects source files larger than 1.5 MB each. |
Limits worth knowing
Browser processing does not make every operation lossless. Several tools deliberately rasterise pages, which removes native text and interactive structures. Table, bank-statement and OCR output is inferred and must be checked against the source. Whiteout and Redact PDF’s Cover mode only hide content visually; Wipe mode is the destructive redaction path. Sign PDF adds a visual signature image, not a certificate-backed digital signature. Password permission flags depend on the PDF reader honoring them.
Testing and maintenance
Product behavior is checked in the repository with Playwright end-to-end suites grouped by tool category. Those tests exercise real browser controls and inspect downloaded output for properties such as page counts, dimensions, form data and text-layer behavior. The production build also generates and prerenders indexable pages, then runs a technical SEO/content gate. Page freshness metadata is derived from repository history rather than a manually invented date. Documentation changes are reviewed against the matching component controls and these automated contracts.
Browse and contact
Browse the complete tool list, read the privacy policy for analytics and storage details, or use the contact page to report a reproducible bug or documentation mismatch.
Open-source components
The PDF, rendering, OCR, spreadsheet and image libraries used by the application are listed with their licenses on the attributions page.