Free Online PDF Tools
Every operation runs on your machine, not ours
Merge, split, convert, edit and secure PDF documents in the browser. Nothing you drop here is uploaded - the files are read by JavaScript on your own computer, the work happens on your own processor, and the result is handed straight back to you. There is no queue, no temporary copy on a server, and nothing for us to delete an hour later because there was never anything to delete.
No tool matches that. Try the category chips above, or tell us what you were looking for on the contact page - the build order is decided by what people actually ask for.
39 of these 39 tools are live right now, each one built on the same engine rather than bolted together from whatever library happened to be free that week. Every one of them shares the same architecture, and that architecture is the reason this page exists rather than another wrapper around somebody else's conversion API.
Why These Tools Do Not Upload Your Files
Almost every free PDF site works the same way. You choose a file, the browser posts it to a server, a worker process runs a command line utility on it, and a download link comes back. It works, it is cheap to build, and it means a stranger's machine held your document. For a birthday party invitation nobody cares. For a signed contract, a payroll export, a medical scan, or a supplier price list, that is a data transfer you did not intend to make and cannot audit.
The tools on this page do the work in your browser instead. The file is opened with the File API, parsed in memory by a PDF library running as JavaScript on your own processor, and written back out as a Blob your browser downloads from itself. There is no request carrying your document, because there is no server-side step to send it to. You can verify that claim without trusting us: open your browser's network panel, run any tool here, and count the requests. The only one you will find is the small call that counts your operation against the free allowance, and it carries a tool name and nothing else.
What this architecture costs, honestly
Client-side processing is not free of trade-offs, and any site that pretends otherwise is selling something:
Your machine sets the ceiling. A 400 page merge on a six year old laptop takes longer than it would on a server with 32 cores. The upside is that you are never queued behind three hundred other people at nine in the morning.
Memory is real. A browser tab holds the source files and the output at the same time. That is why there are batch limits, and why they are higher on an account: they are shaped by what a browser can actually survive, not by an arbitrary paywall.
Some operations genuinely need a server. Anything that requires a full office document engine or a heavyweight machine learning model is honestly hard to do in a browser. Where a tool cannot be done properly on your machine, we would rather say so on its page than ship something that produces a mangled file.
JavaScript is required. There is no no-script fallback that could work, because the fallback would be an upload, and the upload is the thing we removed.
The offline test. Open any live tool, let the page finish loading, then disconnect from the network entirely and use it. The file still processes and the download still works. That is not a demonstration of resilience, it is proof of where the processing happens.
Free Allowances and What an Account Changes
Running these tools costs us almost nothing per operation, which is exactly why the allowance exists in the form it does. We are not metering compute, we are metering the one thing that has value here: the audience. The numbers are small, deliberately public, and identical on every tool in the suite.
Tier
Operations
Files per batch
Batch size
Anonymous visitor
1 per 12 hours
20
100 MB
Free account
2 per 12 hours
20
100 MB
Premium
Unlimited
100
500 MB
An operation is one run of one tool, however many files went into it. Merging forty documents into one is a single operation, not forty. The window is a fixed 12 hours that opens on your first run, so the counter on the tool page always shows you exactly when it resets rather than making you guess.
Anonymous visitors are counted by network address, because that is the only identifier that survives a private browsing window. If you share an office connection with forty colleagues, you share the anonymous allowance with them too, and the fix is fifteen seconds of registration rather than an argument with a firewall.
Who These Tools Were Built For
CartHacker is a publication for people running online stores, and this suite exists because the same document problems keep appearing in that work. Supplier invoices arrive as twelve separate scans that need to be one file before accounting will look at them. Product photography needs to reach a printer as a paginated document rather than a folder of images. A signed distribution agreement needs its metadata stripped before it goes to a third party, because the Author field still says the name of a lawyer at the other company.
None of that justifies a monthly subscription to a desktop suite, and none of it should require handing a contract to a free website with an unclear privacy policy. That is the entire brief.
If you need something that is not here yet
The build order is set by what people actually ask for. Tools marked Soon have a page, a specification and a place in the queue, and the fastest way to move one up that queue is to say so.
Free CartHacker tools
Free speed test and trust badges for Shopify and WooCommerce stores
Find the apps that slow your store down, by name and in milliseconds, then answer shoppers' doubts with trust badges under Add to cart. Both are free, with no card and no access to your store admin.