Edit a PDF in your browser:the edits never leave your tab
When you edit a PDF in your browser, the work happens on your own machine, not on a server. This page explains exactly how that works, and where your file does and doesn't go.
Drop PDF here
or click to browse
Max 50MB
Your browser does the real work
Most online tools are a thin front end over a server. You upload a file, a remote machine edits it, and it sends the result back, so every change makes a round trip. A browser-based editor flips that. The code that reads the PDF, measures fonts, and rewrites the page runs inside your browser tab using JavaScript and WebAssembly. The same kind of fast, low-level code a desktop app uses, downloaded as part of the page.
So when you click a line of text and start typing, nothing is being sent anywhere. Your browser already has the page loaded, it edits it in place, and the result is built on your machine. That's why edits feel instant. There's no network hop between pressing a key and seeing the change.
The one moment your file touches a server
To be precise about privacy: there is exactly one point where your file leaves your device. When you first drop a PDF in, we copy it to temporary storage so the first page renders reliably across every device and browser. That copy is automatically deleted after two hours.
After that first render, the editing is all local. Your keystrokes, the font measurements, the color sampling, the undo history, the final rewritten file: none of it is sent back to a server. The clean line between "a brief copy for hosting" and "your edits stay on your machine" is the whole point of doing it in the browser.
Private because of how it's built, not a promise
Plenty of tools claim privacy. Here it falls out of the architecture. Because the edit runs in your browser, your sensitive content (the numbers on an invoice, the clauses in a contract, the details on a form) never has to travel to us to be changed. We can't read what we never receive.
That makes a browser editor a good fit for documents you'd rather not hand to a third party at all: legal paperwork, medical forms, financial statements, anything with personal data. The file gets edited where it already lives, in front of you, and the result downloads straight back to your device.
Under the hood, answered
What's a browser PDF editor?+
A PDF editor where the actual editing happens inside your browser tab, using JavaScript and WebAssembly, instead of on a remote server. Edits show up instantly, and your file doesn't make a round trip to the cloud each time you change a character.
Does the file ever leave my computer?+
Briefly. We upload it to temporary cloud storage so we can render the first page reliably across devices, and that copy is auto-deleted after 2 hours. All keystrokes, font measurements, and layout work happen in your browser; those never get sent anywhere.
Why a browser PDF editor instead of a desktop app?+
There is nothing to install and nothing to update, and it runs on locked-down work laptops, Chromebooks, and whatever browser you happen to be in front of. The trade-off: very large documents (500+ pages) run slower than in a native app. For most documents you'll never notice.
Which browsers does it work on?+
Any modern Chromium-based browser (Chrome, Edge, Brave, Arc), plus Firefox and Safari. We test on the latest two versions of each. Internet Explorer is not supported.
Edit a PDF in your browser
Open the editor and drop a PDF in. The work happens locally, keystroke by keystroke.
Edit a PDF now