Embed private PDF tools in your product
Add compress, merge, convert, OCR and redaction to your app, with one difference from the usual PDF API: the files are processed in your user's browser and never reach a server.
Your app
Compress PDF
Drop a file. It never leaves this browser.
Why embed this instead of a PDF API
The usual way to add PDF features is to send your users' files to a server. This is the opposite: the same tools, running where the file already is.
Files never leave the browser
Every PDF feature you add the normal way means shipping your users’ files to a server, yours or a vendor’s. Embed this instead and the files stay on the device. Nothing to receive, nothing to store, nothing to breach.
A compliance win, not a liability
No document egress means no new subprocessor and no regulated files at rest because of your PDF feature. The privacy story that sells your product gets stronger, not weaker.
No servers to run or scale
The heavy lifting happens on your users’ machines, so a spike in usage is their CPU, not your bill. No conversion workers to provision, no per-file server cost, no queue to babysit.
Drop it into what you already have
It is a client-side toolkit, so it fits into a web app, an internal portal, or an Electron desktop build without a backend rewrite. Expose one tool or twenty.
The no-upload claim is not marketing you have to trust: the proof page shows how anyone can verify it from the browser's own network panel, or by going offline mid-task.
A few lines, and it runs in the browser
Drop in the tools you need. Because processing happens on your user's device, there is no upload endpoint to build, secure or scale.
- No backend and no conversion workers
- Pick one tool or the whole toolkit
- Your UI, your domain
<!-- add the tools to any page -->
<script src="https://embed.pdfmergely.com/v1.js"></script>
<div id="compress"></div>
<script>
PDFMergely.mount('#compress', { tool: 'compress' })
// the file is processed here. nothing is uploaded.
</script>Illustrative only. The exact API is shaped with each early partner.
Ways to work together
Embed / SDK
Add specific tools to your web app. The processing runs in your user’s browser; you control the UI and where it lives.
White-label
The toolkit under your brand, on your domain. Same private, in-browser engine, presented as part of your product.
Custom & desktop
A specific set of tools, an offline desktop build, or a tailored integration. Tell us the shape and we will scope it.
The free site stays free
To be clear about the model: everything on pdfmergely.com is free for everyone, forever, including commercial use. We do not monetise the people who use the tools. This page is the other side of that: if you want to build the same private, in-browser engine into your product, that is a licence, and that is what keeps the public tools free for the rest of the internet.
Have a product to build this into?
Tell us what you're building and which tools you need. A real person answers, with the way to embed it and terms that fit your scope.
or email partnership@pdfmergely.com
Frequently asked questions
What exactly can we embed?+
The same in-browser engine that powers the public tools: compress, merge, split, convert (to and from Word, Excel, images), OCR, redact, watermark, protect and the rest. You choose which tools to expose and where they sit in your product. We are onboarding the first partners now, so the integration is shaped with you rather than handed over as a fixed black box.
Do our users’ files get uploaded anywhere?+
No. That is the entire point. Every operation runs as WebAssembly inside your user’s own browser tab. Their documents never reach our servers, and they never reach yours either unless you deliberately send them. There is no upload endpoint in the path at all.
How does this help our GDPR or HIPAA posture?+
Because documents are never transmitted or stored, embedding the tools does not add a data processor or a new place where regulated files sit at rest. It is architecture, not a certificate: we give you a design that keeps files on the device, which is far easier to reason about in a review than a vendor that receives and holds your users’ documents. Your own compliance team still owns the final assessment.
Is the public pdfmergely.com still free?+
Yes, and it always will be. Every tool on the website stays free for everyone, including commercial use, with no accounts and no paid tier. This offering is different: it is for companies that want to build that same engine into their own product. The internet keeps the free tools; businesses licence the technology.
How is it priced?+
It depends on scope: which tools, expected volume, and whether you want a straight SDK embed or a white-label build. We are working out terms individually with early partners rather than publishing a rate card yet. Write to partnership@pdfmergely.com with a sentence about your product and we will come back with options.
Can we white-label it or run it on our own domain?+
That is one of the models on the table. Since the engine runs client-side, serving it from your own domain under your own brand is a natural fit. Tell us what you need and we will scope it.