The first time I uploaded a client's asylum application to a free PDF tool, I didn't think twice about it. I needed to merge three documents into one filing. The tool was free, it was fast, and it worked. I closed the tab and moved on.
It took me about six months to start thinking about where those files actually went.
Here is what I know now that I wish I had known then. Once a file leaves your machine for a free web tool, you cannot prove what happened to it. No log to audit, no receipt, no way back. For a recipe PDF that is fine. For a torture survivor's medical evidence, that uncertainty is the whole problem.
I was working as a solicitor at a small refugee law firm in Australia. Small, meaning underresourced, underfunded, and perpetually outmatched. We took on cases against the government, representing people seeking protection in Australia. Refugees fleeing persecution and war. People held in immigration detention whose case files included medical evidence of physical and psychological injuries, and in some cases, abuse reports documenting assaults by correctional facility officers against detainees. The kinds of cases where the stakes are someone's freedom, safety, or life, and the other side has unlimited resources to fight you.
The document load was relentless. Every tribunal hearing, every Federal Court filing, every matter that crept toward the High Court came with hundreds of pages. Medical reports documenting torture injuries. Statutory declarations. Country condition evidence. Tribunal submissions. Ministerial intervention requests. All of it needed merging, splitting, compressing, and organising into court books with precise page numbering.
In 2021, the Taliban retook Afghanistan. The firm was suddenly processing humanitarian refugee visas for people evacuating the country. Identity documents, visa applications, and personal details for individuals who had worked with Western governments and organisations. If any of that information reached the wrong hands, those people and their families could be killed. We were merging and compressing these files under impossible deadlines.
I was doing this multiple times a week. And every time, I faced the same choice that every professional who works with PDFs faces.
Pay Adobe $30 a month. Or upload your files to a website.
That's it. Those are the two options the PDF industry has decided you get.
Let me explain why both of them failed me, and why I think they're failing you too.
Adobe Acrobat is the default answer to any PDF question. It has been the default for decades. And for decades, Adobe has known that most people who buy Acrobat use about 5% of its features. Merge. Split. Compress. Maybe convert an image. That's it.
For those four operations, Adobe Acrobat Standard runs about $14.99 a month on an annual plan. Want Pro? Around $19.99 a month, also annual. That is a recurring bill for a tool you probably open twice a week to combine some files.
And if you decide a monthly bill for merge-and-compress is not a reasonable expense, good luck cancelling. The FTC sued Adobe in 2024 over their cancellation process. The complaint described hidden early termination fees buried in fine print and a cancellation flow designed to be as difficult and confusing as possible. That is not a fringe allegation. It is a federal enforcement action against one of the largest software companies in the world.
At the law firm, we couldn't justify it. Legal aid budgets don't have room for per-seat software subscriptions that cost more than some of our clients' weekly food budgets. We needed a PDF merge tool with no subscription, no recurring drain on grant money.
So we looked at the free alternatives. iLovePDF, around $5 to $9 a month if you pay. Smallpdf, roughly $9 a month on an annual plan. PDF24. Dozens of sites with friendly names and clean interfaces, all promising the same thing for nothing.
They all work the same way. You upload your files. Their servers process them. You download the result.
I remember the moment it clicked. I was merging documents for a refugee's protection visa application. The file contained medical evidence of injuries sustained in detention, names of correctional officers involved in an assault, and a statutory declaration describing what had happened. I dragged it into a browser tab, watched the upload progress bar fill, and thought: "Where is this going?"
I didn't know. I still don't. The privacy policies on most of these sites are vague at best. They say files are "deleted after processing" or "not stored permanently." But there's no way to verify that. No way to audit it. No way to know if the file was cached, logged, backed up, or processed through a third-party pipeline.
For most people merging a recipe collection or a school project, this probably doesn't matter. But I was handling protection visa applications for refugees. Medical evidence of torture. Abuse reports that named specific officers in correctional facilities. Evacuation documents for people fleeing the Taliban. Documents that, if leaked, could get people killed. "It's probably fine" is not an acceptable risk assessment when someone's life depends on your judgment.
We needed an offline PDF tool. Something that processed files locally on the machine and never touched the internet. And we needed it to not cost $30 a month.
We looked at other desktop tools. Most of them looked like they hadn't been updated since Windows XP. Bad UX, clunky interfaces, and half of them were just thin wrappers around command-line utilities. Almost none of them supported WebP images, which was becoming a real problem as more and more evidence and screenshots came in that format.
Nothing fit.
The PDF industry has split into two business models, and both are broken for the same reason. They're designed around extracting revenue, not solving problems.
Think of it like plumbing. You don't pay a monthly subscription to use your kitchen tap. You don't upload your water to someone else's pipes for processing. The infrastructure sits in your house, it works when you need it, and you paid for it once. PDF tools should work the same way. They're file utilities. They should behave like utilities.
Instead, the industry built two extraction machines. One charges you monthly for the privilege of merging two files on your own computer. The other processes your files for "free" on servers you don't control, monetising the data or attention you give them in the process.
Neither model considers that some documents should never leave the machine they're on.
So I built my own tool.
It started as an internal project. Something I needed for work. A desktop app that does four things: merge, split, compress, and convert PDFs. Everything processes locally. No internet connection required. No data sent anywhere. No tracking. No account. No sign-up.
I chose Tauri as the framework, which uses Rust on the backend. Rust gave me the performance characteristics I needed for handling large document sets and the memory safety guarantees that matter when you're processing sensitive files. The frontend is React and TypeScript. The whole thing is small, opens fast, and does exactly what it is supposed to do.
I called it ReamPDF.
One of the first things I added beyond the basics was native WebP to PDF support in the Convert feature. WebP is Google's image format, and it's everywhere now. Screenshots from Chrome, images downloaded from the web, exports from design tools. Try feeding a WebP file to most PDF converters and they'll reject it. You have to convert the WebP to PNG or JPEG first, then convert that to PDF. Two steps for something that should take one.
With ReamPDF, you drag in your WebP files, hit convert, and you get a PDF. I kept running into this exact friction in my own work, so I fixed it. It turns out this is one of the features people mention most.
After I left the law firm, I spent time polishing it. I added eight themes, because I was tired of utility software that looks like it was designed in a government procurement meeting. You can switch between light and dark modes, or use something like Dracula or Nord if you spend long hours in the app. Sounds minor. When you are preparing documents at midnight, the interface matters.
I put it on the Microsoft Store for $9.99 USD. One-time purchase. No subscription. No recurring charges. No trials that expire.
The math is simple. ReamPDF is $9.99 once, on Windows and macOS, with every file processed locally and nothing uploaded. Adobe Acrobat Standard is about $14.99 a month, so you cover the price of ReamPDF in under three weeks. Everything after that, for the life of the tool, is the saving.
That price was a deliberate choice. Merge, split, compress, and convert are not operations that require ongoing cloud infrastructure. They don't need continuous development sprints or server farms. They're computations that run on your processor, using your memory, on your machine. Charging a monthly fee for local PDF processing is a business model choice, not a technical necessity.
There's a version of this piece where I'd walk you through the "transformation" of using the product. But this isn't a supplement or a course. It's a utility. The transformation is instant. You download it, merge your first PDF, and realise in about 30 seconds that you never needed to be paying $30 a month for this. You never needed to be uploading your files to anyone's server.
The feeling most people describe is not excitement. It's mild irritation. A quiet "why was I putting up with that?"
I want to be clear about what privacy means in this context, because it has become one of those words that companies throw around without meaning it.
ReamPDF has no network calls. None. It doesn't phone home. It doesn't check for updates by pinging a server. It doesn't send analytics. It doesn't sync to a cloud. There is no account system. There is no telemetry. Your files go in, your files come out, and nothing is transmitted anywhere.
This wasn't bolted on after the fact as a marketing angle. It was the original design constraint. When you're building a privacy PDF tool for a law firm that handles cases for asylum seekers and abuse survivors, "we take privacy seriously" isn't a tagline. It's an architectural requirement that shapes every decision from the first line of code.
I think about those late nights before tribunal hearings. Merging 300 pages of evidence and submissions at 2am, getting the page numbering right, compressing the final PDF to squeeze under the electronic filing limit. Running it through some website because we didn't have the budget for an Adobe Acrobat alternative and hoping nobody malicious was on the other end.
That's the specific frustration this tool was built to solve. Not for a hypothetical user persona. For me, at that desk, with those files.
If you handle sensitive documents in your work, whether that's legal files, financial records, medical information, or client contracts, you already know the discomfort of uploading them to a website you found through a Google search. You know the quiet calculation of "is this worth the risk?" every time you need to combine two PDFs.
You're not the person who should be paying $30 a month to merge two files. You're not the person who should be uploading client contracts to a website with a cute name and no real privacy policy. You're someone who takes your work seriously, and your tools should reflect that.
ReamPDF is $9.99 USD on the Microsoft Store. One time. It runs on Windows 10 and 11 and on macOS. Nothing else, no Linux build, no web version. Available on the Microsoft Store and Mac App Store. No subscription. No account. No data leaves your machine. Learn more at torpenhow.ai.
The short version: an industry built two broken models for PDF tools, one that charges you monthly for basic operations and another that processes your files on servers you don't control. A human rights law firm needed something better, so we built it. ReamPDF runs on your machine, handles everything locally, supports formats other tools ignore, and costs $9.99 once. Your files stay yours.
For a recipe collection or a school handout, fine. For sensitive documents it is a real risk. The hosted versions of these tools process your file on their servers, so the document leaves your machine. Their policies say files get deleted after processing, but you cannot audit caching, logs, or third-party pipelines. The only way to remove that uncertainty is to never send the file off your machine, which is what an offline tool that processes locally does.
Any tool that processes on your own device rather than a server qualifies. PDF24 ships a desktop app, and ReamPDF is built around this from the start. ReamPDF makes no network calls at all: no account, no cloud sync. Your files go in and come out without anything being transmitted anywhere. That matters most for legal, medical, and financial documents you should not be uploading to a site you found through a search.
Adobe Acrobat is subscription only, roughly $14.99 per month for Standard and $19.99 for Pro on annual billing (Adobe public pricing, verified June 2026). ReamPDF is a one-time purchase at $9.99 with no recurring charges and no trial that expires. It handles merge, split, compress, and convert, which covers what most people actually open Acrobat for, and it runs fully offline on Windows and macOS.
Most PDF converters reject WebP and force you to save it as PNG or JPEG first, then convert that to PDF. ReamPDF added native WebP to PDF support in its Convert feature, so you drag the WebP files in and get a PDF in one step. WebP shows up constantly now in Chrome screenshots and web exports, which is why this turns out to be one of the features people mention most.
In 2024 the FTC filed an enforcement complaint that described hidden early-termination fees buried in fine print and a cancellation flow built to be hard to finish. It is an allegation in a federal action against one of the largest software companies in the world, not a final verdict. It is one reason a lot of professionals now go looking for a one-time-purchase PDF tool that has no cancellation maze attached.
ReamPDF runs on both Windows 10 and 11 and macOS. It is built on Tauri with a Rust backend for fast, memory-safe handling of large document sets. Because every operation runs locally, the same guarantee holds on both platforms: your files stay on your machine, with no upload and no account. The price is the same $9.99 one-time purchase either way.