PigPDF
93 tools
Menu

Privacy-first PDF toolkit

PDF tools that
respect your files.

Organize, convert and inspect PDFs with clear processing information and no account required for basic tools. Supported local tools process files in your browser.

Browse all 93 toolsHow local processing works
  • No account for basic tools
  • Clear limits before processing
  • Mobile and keyboard first
Working local beta

Merge PDF

PDF
report.pdf12 pages · 3.8 MB
appendix.pdf4 pages · 1.2 MB
Browser-only processing

Covered by an automated processing egress test.

Open Merge PDF beta
Transparent statusNew file as output
93tools cataloged
8clear categories
0proofs of concept queued
5target languages

Find your route

Eight focused categories

Every tool has a stable ID, processing mode, readiness status and documented limitations.

OrganizeCombine, split and arrange pages without changing their content.13toolsConvertMove between PDF, image, office, web and text formats.19toolsEditAdd visual content, annotations and page-level changes.16toolsSecurity & metadataInspect protection, signatures and potentially sensitive data.11toolsFormsFill, inspect, validate and exchange PDF form data.8toolsOptimize & repairReduce size, improve delivery and recover compatible files.8toolsOCR & accessibilityMake scans searchable and inspect document accessibility.9toolsWorkflowCompare, batch, preflight and package document jobs.9tools

Privacy is a test, not a slogan

Know what happens before you choose a file.

Each workspace will show its processing mode, supported formats, practical limits and failure cases before a file is loaded.

Browser-only processing for supported tools, verified through automated egress tests.

  1. 01
    Declare the mode

    Browser, browser with limits, dependency or research.

  2. 02
    Test real documents

    Normal, large, encrypted, signed, damaged and edge cases.

  3. 03
    Verify network egress

    Automated tests must confirm the published behavior.

  4. 04
    Publish the limits

    Compatibility and known failures stay visible.

Clear by design

No “unlimited.” No hidden processing.

Browser memory, file structure, device performance and PDF features all matter. PigPDF will reject unsupported cases clearly instead of pretending every file can be processed.

Output policy
Always a new file
Signed PDFs
Signatures may become invalid
Failures
Encrypted, damaged or unsupported files

Good to know

Questions before files

Do PigPDF tools upload my files?

Supported local tools process files in your browser. Every published BETA or LIVE tool shows its processing mode and must pass an automated egress test. Tools that need a reviewed dependency say so before use.

Are all 93 tools available now?

No. 93 tools are working betas and the rest keep transparent readiness labels. A tool is only marked LIVE after its processing, error handling, mobile behavior, keyboard support, privacy checks and tests are complete.

What happens to signed or encrypted PDFs?

Encrypted, damaged and unsupported files are rejected by relevant local tools. Creating a new output file may invalidate existing digital signatures, so each tool will show this before processing.

Will PigPDF work offline?

PigPDF is installable as a PWA. A supported local tool can reopen offline on the same device after its route and processing assets have loaded successfully once. Browser storage can still be cleared by the user or operating system.