No compromises.
Your browser receives permission to read the PDF you select. PDFup does not browse other files on your device, and no account is required to begin a task.
JavaScript, Web Workers, WebAssembly, and PDF libraries perform supported operations on your device. Processing speed and file-size capacity therefore depend on your browser, memory, and hardware.
The tool creates a new output file for you to download. Keep the original until you have opened and checked the result, especially after security, repair, or layout operations.
Local document processing does not mean the website makes no network requests at all. The site still loads application assets and may use analytics described in our Privacy Policy. The important distinction is that the PDF contents selected for supported browser-based tools do not need to be sent to PDFup's servers for processing.
PDFup provides focused tools for merging, splitting, organizing, converting, signing, printing, securing, and inspecting PDF files. Dedicated pages explain what each operation does, when to use it, and how it differs from similar workflows.
The project also publishes PDF guides for users who need more than a button: task comparisons, step-by-step instructions, limitations, privacy considerations, and recommended next steps.
PDFup is not a document hosting, backup, collaboration, identity-verification, or certificate-issuing service. Locally processed files are not stored for later retrieval, so users are responsible for keeping their own originals and outputs.
Some PDF standards and complex files are not supported equally by every browser or library. A successful download should always be opened and checked before the original is deleted or the result is used in an important workflow.
PDFup combines its own interface and workflow logic with established open-source PDF and browser technologies. Dependency updates, browser changes, and unusual PDF structures can affect results, so the project is tested and improved over time rather than presented as a perfect replacement for every desktop publishing application.
Tool pages are written to describe the actual task rather than hide limitations behind generic marketing language. When two tools sound similar—such as merging files versus stitching pages into one page—the site explains the difference and links users to the more appropriate workflow.
If you find a reproducible problem, contact us with the tool URL, browser name and version, operating system, the steps that caused the issue, and any visible error message. Do not email confidential documents, passwords, private keys, or personal records. A synthetic or redacted sample is safer when a sample is necessary.
Read what site-level analytics and third-party services may collect, and how local PDF processing differs from website telemetry, in the Privacy Policy.
Users must have permission to process their documents and should review important output. The full usage conditions are in the Terms and Conditions.
PDFup uses open-source components with their own licenses. Project licensing information and required notices are available on the Licensing page.
To provide the most comprehensive PDF toolbox that respects your privacy and never asks for payment. We believe essential document tools should be accessible to everyone, everywhere, without barriers.
In an era where data is a commodity, we take a different approach. All processing for pdfup tools happens locally in your browser. This means your files never touch our servers, we never see your documents, and we don't track what you do. Your documents remain completely and unequivocally private. It's not just a feature; it's our foundation.
No waiting for uploads or downloads to a server. By processing files directly in your browser using modern web technologies like WebAssembly, we offer unparalleled speed for all our tools.
No trials, no subscriptions, no hidden fees, and no "premium" features held hostage. We believe powerful PDF tools should be a public utility, not a profit center.
Start using any tool immediately. We don't need your email, a password, or any personal information. Your workflow should be frictionless and anonymous.
Built with transparency in mind. We leverage incredible open-source libraries like PDF-lib and PDF.js, and believe in the community-driven effort to make powerful tools accessible to everyone.
Choose a task, keep your source file, and review the generated PDF before using it. If you need help deciding, start with the tool directory or read a workflow guide.
Explore All Tools