How to Edit a PDF in Your Browser: What You Can Change and What You Cannot

Understanding the mechanism removes most of the frustration, because the limitations follow directly from the design.

A browser PDF editor renders the page you are looking at into a canvas element, which is a bitmap. On top of that bitmap it maintains an editing layer: the text you type, the shapes you draw, the images you place, and the signature you add. Those objects are positioned in page coordinates and tracked separately from the rendered page.

When you save, your additions are drawn into that bitmap and the finished image is embedded into a new PDF page. The output therefore looks identical in every reader, including ones that hide annotation layers by default, because there are no annotations left to hide — the page is simply a picture.

The consequence is important: the original text is not preserved. Once a page has been through this pipeline it is an image, so its text can no longer be selected, searched, or copied — including the words you never touched. You gain reliable rendering and irreversible edits, and you lose the live text layer.

That single architectural fact explains every limitation that follows, and it also explains why the approach is so dependable: you are editing a flat bitmap, so what you see in the editor is exactly what every reader will show.

Within that model, a great deal of real work is possible, and most of it is what people actually need.

You can add text anywhere on the page: a clause, a note, a correction, a reference number. You can place an image, which covers logos, stamps, photographs, and signature graphics. You can draw rectangles, lines, and freehand marks, which handles highlighting, boxing, and callouts. You can fill in a form that was not built as an interactive form, which is one of the most common reasons people reach for a PDF editor at all.

You can also cover things up. Drawing an opaque shape over content is trivially easy and is the basis of the whiteout technique below. Be clear about what this achieves: the content is hidden from view but remains in the file, which is fine for correcting a typo and entirely unsuitable for removing confidential information. The redaction guide explains why those are different problems.

Page-level operations are handled better by dedicated tools than by a general editor. Adding a repeated overlay across every page is a watermark job, so use Add Watermark. Adding a footer sequence is a pagination job, so use Add Page Numbers. Placing a signature is its own workflow, covered in the signing guide.

Since you cannot edit existing text in place, the practical technique for corrections is to cover the old text and type new text over it. Done carefully, the result is indistinguishable from the original at normal viewing size.

The method has four steps, and each one matters. First, zoom in far enough that you can judge alignment precisely; at fit-to-window zoom, small mismatches are invisible and you will not notice the error until you print. Second, sample the actual background colour of the page rather than assuming white, because scanned and printed pages are rarely pure white. Third, draw a rectangle over the old text that is slightly larger than the text block, so no ascenders or descenders remain visible. Fourth, type the replacement using a font and size that match the surrounding text, and align its baseline with the neighbouring lines.

The most common failure is font mismatch. Helvetica and Arial are metrically compatible and are usually a safe choice for documents produced from standard office software. Times New Roman and Times are likewise close. If the original uses an unusual typeface, matching it precisely may not be possible, and in that case the honest options are to accept a visible difference or to edit the source document instead.

There is a second-order problem worth knowing about: if the document is later processed by text extraction, the covered text is still there. A whiteout on a contract does not change what a search finds. If the goal is to change what the document says in a way that survives scrutiny, you need to edit the source and re-export.

A large share of PDF editing is filling in a document that was designed to be printed and completed by hand. These are not interactive forms; they are pictures of forms, and the fields are just boxes printed on the page.

The approach is the same as any other text placement: click where the text belongs and type. The things that make the result look professional are consistent alignment, a font size that matches the printed labels, and restraint. Text that is noticeably larger than the form's own typography looks amateurish even when it is perfectly legible.

For fields that expect a tick or a cross, drawing a short pair of strokes by hand usually looks better than inserting a symbol from a font, because the weight and angle will match the document's own marks more closely. For signature fields, use the signing workflow rather than typing a name.

One thing to check before you invest effort: confirm that the form is not actually interactive. If it is, the fields will accept input directly when you click them, and typing into a real form field produces a cleaner result than overlaying text. Many government and institutional forms are genuinely interactive, and it is worth testing before assuming otherwise.

The editing model works the same way on every platform, but the input devices change what is comfortable.

On a desktop, a mouse is precise for placement and alignment, and the keyboard makes entering text fast. The one thing a mouse is poor at is freehand drawing: a mouse-drawn signature looks like a mouse-drawn signature. If the appearance of a handwritten mark matters, use a trackpad gesture, a stylus, or a touchscreen.

On a tablet or phone, the reverse is true. Drawing is natural and accurate, and placing text precisely is fiddly because your finger covers the area you are trying to position. For documents that need careful alignment, a larger screen makes the work substantially easier.

There is one browser-specific gotcha worth mentioning. Canvas-based editors need a canvas to work with, and some mobile browsers throttle or discard background tabs aggressively. If an edit session is long, save your work by exporting rather than leaving the tab open, since a discarded tab may lose unsaved changes.

PDF editing is a patch, not a rewrite, and recognising the boundary saves time.

If you are changing a few words, a date, a figure, or filling in a form, editing the PDF directly is the fastest route and produces a good result. If you are rewriting a paragraph, restructuring a section, or changing the length of the text, you are fighting the format. Every edit will require manual re-alignment, and the result will drift further from the original with each change.

In that situation the correct move is to go back to the source. If the document was created in Word, edit the Word file and export a fresh PDF. If the source is unavailable, PDF to Word gives you an editable starting point, with the caveats described in the conversion guide: layout will not survive perfectly, and you should budget time to tidy the result.

There is a middle path for documents that only need to be assembled rather than rewritten. If the change is really about what is included rather than what it says, use the page-level tools: Merge PDF to combine, Split PDF to extract, and Organize PDF to reorder or drop pages. Those operations are exact, whereas overlay editing is approximate.