How to choose an online PDF editor
· 7 minute read
Eight things worth checking before you trust a website with a document, each with a way to test it yourself in under a minute — and when to use nothing online at all.
Search for a PDF editor and you get a hundred sites describing themselves in the same four words: fast, simple, secure, free. None of those can be checked, which is exactly why every site uses them. Here is a list of things that can be checked, and how to check each one in about a minute.
1. Does it say whether your file is uploaded?
This is the first question, and most sites answer it nowhere. Many PDF operations — merging, splitting, rotating, compressing, watermarking, page numbers — can run entirely inside your browser, on your own machine. Plenty of sites upload anyway, not out of malice but because server-side code is easier to build and easier to meter.
How to test it: load the page, turn off your internet, then use the tool. If it still works, nothing was uploaded. If it hangs, your document went to somebody else’s computer. That one test tells you more than any privacy policy.
2. How many steps before you can do the thing?
Count them. A well-made tool is three: open the page, add the file, press the button. A badly made one asks you to create an account, then a project, then upload, then wait in a queue, then dismiss an upsell before it hands over the result.
Steps are not only friction. Every account is a copy of your email address on somebody’s server, and every queue is your document sitting on a disk waiting its turn.
3. Does it ask for an account it does not need?
Merging two PDFs does not require knowing who you are. A site demanding an account for that is collecting addresses rather than solving a problem, and the tool is the bait.
There are two honest reasons to ask. One is a paid feature, which has to be attached to whoever paid. The other is something worth having a name against — removing the password from a document, say. Everything else is list-building.
4. Is there a watermark, and when do you find out?
The worst pattern in this category is to let you do the whole job, then stamp the output and offer to remove the stamp for money. You have already spent the time, which is the point of doing it in that order.
How to test it: run one small real job all the way to a downloaded file before trusting a site with anything that matters. A good tool tells you about a limit before you start rather than after.
5. Can you see the result before you commit to it?
Compression especially. A tool that hands you a file without showing you what it did is asking you to forward a possibly-degraded document on trust. Check that you can see the output — and check it at 200% zoom on a page with small print, because compression damage is invisible at normal size and obvious close up.
6. Does "editing" mean editing, or drawing on top?
Most tools calling themselves editors place a new text box over the page. That is genuinely useful for filling in forms and signing things, and useless for changing a word in an existing sentence: the new text will not match the font, and the old word is still underneath where anyone can select it.
How to test it: change one word in an existing paragraph, save, reopen, and select that line. If you can copy out both the old word and the new one, it was an overlay.
7. Does it work on the device you actually have?
A lot of PDF sites are unusable on a phone: controls sized for a mouse, drag targets too small for a finger, a layout assuming a wide window. If you will need this on a phone, test it on the phone rather than on the laptop you are reading this on.
8. What does it cost, and can you find out before you start?
Look for the price on a page of its own, in numbers, without having to create an account to see it. Then check what happens when you stop paying — whether the files you already made stay yours, and whether anything you produced becomes inaccessible.
When to use nothing online at all
Some documents should not go near a website, including one that processes locally — because the safest version of this decision does not depend on you having run the test correctly.
- Anything under an obligation you did not write yourself: medical records, client files under privilege, documents covered by a contract that names where they may be processed.
- Redaction of anything genuinely sensitive. Removing text properly means deleting the underlying content, not drawing a black rectangle over it — and the failure is invisible, because the page looks redacted while the text can still be copied out. This has embarrassed law firms and governments repeatedly.
- Anything that would matter if it leaked and that you cannot verify was processed on your own machine.
For everything else — which is most things — a browser tool doing the work on your own device is genuinely fine, and often better than desktop software you have to keep updated.
Where we do not fit
It would be dishonest to publish a checklist without saying where our own tool fails it. Loopdraw has no desktop application, nothing for teams, no shared workspace and no approval workflow. Very large documents are slower here than in native software, because the work happens on your device rather than on a server farm. If you need a hundred documents processed on a schedule, this is the wrong tool and an API is the right one.
What it is built for is one person, one document, done now — without installing anything, without an account, and without the file leaving the machine. That is a narrower promise than most sites make, and it is the one we can actually keep.