eSign PDF Guide
Browser PDF tools vs native apps: the privacy problem nobody talks about
That 'free offline' browser tool? It's probably uploading your NDA to a server in Virginia. Here's how to tell.
Short answer
Every week someone on Reddit recommends a free browser-based PDF tool. 'Just use pdfapihub.com' or 'try ilovepdf.com, it's free.' And for casual stuff, they work fine.
Last updated 2026-04-18
The 'Offline' Lie
Every week someone on Reddit recommends a free browser-based PDF tool. 'Just use pdfapihub.com' or 'try ilovepdf.com, it's free.' And for casual stuff, they work fine. But here's what nobody mentions: most browser-based tools upload your PDF to their server to process it. Even the ones that claim to be 'client-side' often hit a server at some point for complex operations like signature flattening, form field detection, or PDF compression. You can verify this yourself. Open the browser's Network tab (F12 > Network) while using any 'free offline' PDF tool. If you see outbound requests carrying your PDF data, your document left your device. For a restaurant menu, who cares. For an NDA with a $50K penalty clause, your client's confidential financial records, or a W-9 with your Social Security number? That's a real problem.
What 'On-Device' Actually Means
A native iPhone app like eSign PDF runs entirely on your phone's processor. The PDF rendering, signature placement, form filling, AI field detection, and export all happen on your device's CPU and GPU. There is no server. There is no upload. There is no network request. You can put your phone in airplane mode and sign a 50-page contract. It works exactly the same. This isn't a marketing claim. It's an architectural fact. Browser tools need a server because browsers have limited PDF processing capabilities. Native apps don't have that limitation because they use Apple's native PDFKit and Vision frameworks directly. Your document literally cannot leave your phone because there's nowhere for it to go.
How to do it
Step 1: How to Check If a Browser Tool Is Really Offline
Open the tool in Chrome or Safari. Press F12 (or Cmd+Option+I on Mac) to open Developer Tools. Go to the Network tab. Upload a PDF and perform a signing operation. If you see POST requests to any server, your document was uploaded. If the Network tab stays empty, it's genuinely client-side.
Step 2: Ask the Right Question
The question isn't 'is this tool free?' The question is 'does my document leave my device?' For signing a pizza coupon, it doesn't matter. For signing an NDA, a lease, a tax form, or anything with sensitive information, it matters a lot.
Step 3: When Browser Tools Make Sense
Honestly? For non-sensitive documents, browser tools are fine. Quick edits, casual signatures, public documents. Use them. Save money. The privacy argument only kicks in when the document contains information you wouldn't email to a stranger.
Step 4: When You Need a Native App
NDAs, contracts with penalty clauses, tax forms (W-9, 1099), medical forms, financial documents, leases, anything with your SSN or bank details. For these, use a native app that processes on-device. eSign PDF is one option. Others exist. The key is: nothing leaves your phone.
Mistakes to avoid
- 1Trusting 'we don't store your files' claims. Even if they delete the file after processing, it still traveled across the internet and sat on their server briefly. That's a window of exposure.
- 2Assuming open-source means safe. An open-source browser tool can still make network requests. Check the Network tab, not the GitHub readme.
- 3Using browser tools on public WiFi. Even if the tool is client-side, the initial page load and any JavaScript it runs could be intercepted on unsecured networks.
- 4Thinking all native apps are private. Some native apps upload to their own cloud (Signeasy, DocuSign). Native doesn't automatically mean on-device. Check the privacy policy.
100% On-Device. Verified.
eSign PDF processes everything on your iPhone using Apple's native PDFKit and Vision APIs. No server, no cloud, no network requests. Put your phone in airplane mode and sign a contract. It works. That's the proof. For documents that matter, on-device processing isn't a feature. It's a requirement.
Learn more about eSign PDF →FAQ
Are browser PDF tools dangerous?+
Not inherently. For casual, non-sensitive documents they're fine and convenient. The risk is using them for sensitive documents (NDAs, tax forms, medical records) without realizing your file was uploaded to a third-party server.
How do I know if eSign PDF is really on-device?+
Put your phone in airplane mode. Open a PDF. Sign it. Fill it. Export it. If it all works with zero internet, it's on-device. Try the same test with any browser tool.
Is this just fear-mongering to sell an app?+
Fair question. For most people signing most documents, browser tools are fine. But if you handle client NDAs, tax documents with SSNs, or financial records professionally, on-device processing is a genuine advantage, not a scare tactic.
Related Guides
Guide
Apple Markup vs Dedicated Signing App
Apple Markup vs eSign app — Markup can't add dates, checkboxes, or reliable multi-page signatures. Here's when you need a real signing app.
Guide
How to Sign a PDF on iPhone
How to sign a PDF on iPhone in under 60 seconds. Draw, type, or import your signature. No printing, no scanning, no account needed.
Alternative
DocuSign Alternative
Looking for a DocuSign alternative? eSign PDF lets you sign and fill documents on iPhone for $19.99/year instead of $180/year. 100% offline, no account needed.