About CrispPDF
A privacy-first PDF toolkit built for people who just need to get things done. 40 free tools. No accounts. No watermarks. No ads.
Our mission
PDF tools shouldn't cost money or require an account. Every existing solution is either slow, ad-stuffed, or hides basic features behind a paywall. You shouldn't need to create an account to merge two PDFs or compress one for an email attachment.
CrispPDF runs primarily in your browser. Your files stay on your device. We don't see them, we don't store them, we don't log them. Privacy isn't a feature we charge for — it's the default behaviour of the system.
How it works — in detail
CrispPDF has two processing paths. Most tools run entirely in your browser. A few unavoidable cases use a stateless edge function. Here's exactly what happens at each step.
Path A — Browser-only (30 of 40 tools)
1. You pick a file
Drag a PDF into the upload zone or tap to browse. Your browser reads the file from your device — nothing is uploaded yet. The file picker also accepts paste-from-clipboard and folder drops for batch operations.
2. Your browser does the work
For 30 of CrispPDF's 40 tools, the entire operation runs in your browser using WebAssembly libraries like pdf-lib, pdf.js, and Tesseract.js. Your CPU merges, splits, compresses, or signs — your file never crosses the network.
3. You download the result
The processed PDF is generated as a Blob inside your browser and offered as a direct download. There is no server-side storage to clean up, no email link, no expiring URL. Close the tab and every trace is gone.
Path B — Server-assisted (10 of 40 tools)
Encrypted in transit
For the 10 tools that need server power (OCR on large scans, Office conversion, HTML to PDF), your file travels over HTTPS to an isolated edge function in the nearest region — typically under 100 ms away.
Processed in memory
The edge function reads your file into RAM, runs the conversion or OCR, and writes the result to the HTTP response. No disk write, no database insert, no S3 bucket. The whole lifecycle is a single request-response.
Discarded immediately
When the response finishes streaming, the memory buffer is garbage-collected. There are no backups, no logs of file contents, and no admin dashboard where anyone could view what you processed.
The technical stack, briefly:
Browser tools use pdf-lib for structure edits, pdf.js for rendering and text extraction, Tesseract.js for in-browser OCR, and Web Workers to keep the UI responsive on large files. Server tools run on Cloudflare Workers and Edge Functions written in TypeScript with zero state between requests.
What we stand for
Privacy by architecture
We can't see your files because the code that would let us see them doesn't exist. This isn't a policy — it's the system design.
Speed by physics
Local processing is faster than a round trip to any server. A 50-page merge that takes 8 seconds on a competitor finishes in under 1 second here.
Free by default
Free tools, no signup, no watermarks, no daily limits, no ads. We do not believe basic PDF operations should ever cost money.
By the numbers
About CrispPDF — frequently asked
Common questions about who we are, how we operate, and what makes CrispPDF different.
Who built CrispPDF and why?
CrispPDF is built by a small independent team frustrated with bloated, ad-stuffed, paywalled PDF tools. We wanted a single place where any PDF operation is one click away, runs in seconds, costs nothing, and doesn't demand a signup. So we built it.
Is CrispPDF really free, or is there a paywall I'll hit?
All 40 tools are free with no daily limits, no file count caps, no premium tier, and no feature locked behind payment. There is no Pro plan. The only rate-limiting is a soft throttle to prevent automated abuse — normal use will never trigger it.
How does CrispPDF make money if everything is free?
It doesn't, yet. CrispPDF is currently funded out of pocket by the founders. Future revenue may come from an optional API for developers and a self-hosted version for businesses with compliance requirements. The free consumer tools will always stay free.
Why is processing in my browser safer than on a server?
Because your file physically never leaves your device. A server-based tool, even with the best policies, requires you to trust the operator's logs, backups, employees, and legal jurisdiction. Browser-based tools eliminate all of that by design — there is nothing on our side to leak, subpoena, or breach.
Why are some tools still server-based then?
OCR on large scanned documents, Office (DOCX/XLSX/PPTX) conversion, and HTML-to-PDF rendering require either heavy WebAssembly that would crash low-end devices or native libraries (LibreOffice, Chromium) that cannot run in a browser. We use a stateless edge function only when in-browser processing is impossible or impractical.
What happens to my file after I close the tab?
Nothing — there is nothing to clean up. Browser tools held your file in tab memory, which the browser releases on close. Server tools processed your file in RAM during a single HTTP request and released that memory the moment the response finished, long before you closed the tab.
Is CrispPDF open source?
Parts of the stack are: we contribute back to pdf-lib, pdf.js, and Tesseract.js where we find bugs. The CrispPDF application code is not currently open source, but we publish a clear privacy policy, a security disclosure process, and our infrastructure layout so you can verify the privacy claims.
How is CrispPDF different from Smallpdf or iLovePDF?
Three differences: (1) every tool is free with no daily limits — they paywall most features. (2) 30 of 40 tools run entirely in your browser — their tools upload everything to their servers. (3) No accounts, no watermarks, no upsells. The trade-off: we don't have a desktop app or team collaboration features.
Does CrispPDF work without an internet connection?
Partially. Once a tool page has loaded, the browser-based tools continue to work even if you lose connectivity, because the processing code is already in your tab. Server-based tools (OCR, Office conversion) need an active connection. We're exploring a PWA version with full offline mode.
Where is CrispPDF hosted?
Static pages are served from a global CDN with edge locations in 200+ cities. The server-only tools run on edge functions in the region closest to you. There is no central database of user files because user files never reach our infrastructure for the 30 browser tools.
Can I use CrispPDF for commercial work?
Yes. CrispPDF tools are free to use for personal, educational, and commercial purposes. There are no restrictions on the output files. Some advanced features (bulk API, white-label) are planned as paid tiers, but every existing consumer tool remains free for any use.
How can I trust your privacy claims?
Open your browser's DevTools network tab while using any browser-based tool — you'll see no upload requests at all. For server tools, the request is single-shot with no follow-up calls. Our privacy policy is plain English, our infrastructure choices are documented, and the architecture itself makes data retention impossible for most operations.
Looking for tool-specific answers? Browse the full FAQ →
Have a question or suggestion?
Email us at hello@crisppdf.com
Contact us →