Edit PDFs on Windows, no installer needed

On Windows 10 and 11, Edge is the default PDF handler unless another app grabbed the file type. As a reader it is good: highlight, draw with the pen, fill in real form fields, drop a text box, read the page aloud.

The wall is the same one Preview hits on the Mac. Edge cannot change a word that is already printed on the page. Its Add text tool floats a new box over the document rather than opening the text underneath. It also will not delete a page, reorder pages, or merge two files. For anything past markup you need something else, and that is usually where the search for an editor starts.

Windows ships a virtual printer. Press Control P in any app, choose Microsoft Print to PDF, and you get a PDF of whatever was on the page. For turning a web page, an email or a spreadsheet into a PDF it is the fastest thing on the machine.

Running an existing PDF back through it changes nothing you wanted changed. You get a fresh copy of the same pages, minus the form fields and clickable links, with the wrong sentence still sitting there. Plenty of people try this first and conclude PDFs are simply not editable.

Acrobat wants an installer and an administrator password. On a corporate or school Windows machine you have neither, the Microsoft Store is often switched off too, and the answer to a software request is a ticket and a two week wait.

A web page needs none of that. No install, no admin rights, no license key, no software inventory entry, and nothing left on the disk when you close the tab. It behaves the same on a locked-down Dell issued by IT as on your own laptop at home.

When the PDF came out of a Word document you still own, going back to the source is the cleanest route every time. Edit the .docx, then use Save as PDF or Export, Create PDF/XPS. Nothing is guessed because nothing is being reverse engineered.

Opening the PDF in Word is a different thing and it is worth knowing what it does. Word rebuilds a brand new document from the PDF, and Microsoft says up front that the result may not look like the original. In practice tables split, columns collapse, spacing shifts, headers become floating text boxes and line breaks land in odd places. Fine for a plain one-column letter. Painful for anything designed. Editing the PDF directly avoids the rebuild entirely.

Open FileHook in Edge, Chrome, Firefox or Brave. Drag the PDF onto the upload card, or click it and browse to the file. Click the line you want changed and type over it. The rest of the toolbar sits down the side: add text, whiteout, form fields, signatures, highlights, shapes, images, links, and page moves. Click Download when the document reads the way it should. Everything is built in the tab, so there is no upload wait and no queue.

Edge and Chrome both default to C:\Users\yourname\Downloads and pop a downloads flyout at the top right. Two things to watch on a work machine. Some organisations redirect the Downloads folder into OneDrive, so the edited PDF syncs to the company cloud the moment it saves. And some browser policies force a Save As prompt instead of a silent download. Neither breaks anything, but if you are editing something you would rather keep local, check where Downloads actually points first.

Edge, Chrome, Brave, Opera and Vivaldi are all Chromium underneath, and Firefox implements the same file APIs. There is no plugin, no ActiveX leftover, and no browser that gets a better version. The only real requirement is a browser that has been updated in the last year or two. Windows 10 and Windows 11 make no difference at all, because the work happens inside the browser rather than in the OS.

For a plain edit, nothing leaves it. The PDF is read into the browser tab from your own drive, the changes happen there, and the finished file is assembled there too. No account, no email, and no analytics on what your document says. The one deliberate exception is the Share button, which uploads the finished PDF so someone can open a link, and an anonymous share deletes itself after two hours. Free use runs to 10 finished files a day across every tool here, resetting at midnight UTC, with a 50 MB ceiling per file. Honest limit: because your own PC renders the pages, an old machine with 8 GB of shared memory takes its time on a large scanned document.