The annotation toolkit is more capable than most users stumble onto. Firefox's built-in viewer lets you place free text anywhere on a page, choosing color and font size before you drop it, according to Mozilla Support. Notes and highlights are both supported. Freehand drawing comes with controls for color, stroke thickness, and opacity giving more precision than a basic marker. Downloading the annotated file saves a copy with all markings preserved.

Form-filling is where the browser-native approach earns its keep. Firefox handles interactive PDF forms text fields, checkboxes, and radio buttons and a completed form downloads locally with the entered data intact, Mozilla confirms. For anyone who regularly deals with government forms, HR paperwork, or rental applications, that removes the need to pull in a separate app. Fill in the fields, download, done.

PDFs open directly in Firefox without being saved to disk first, and edits are preserved in a downloaded copy rather than uploaded anywhere, per Mozilla Support. That matters for users handling sensitive documents nothing passes through a third-party server. One practical note on file handling: if a PDF won't open in the browser, it may be hosted with an incorrect MIME type, and downloading the file first usually resolves the problem, Mozilla notes.

Firefox does let you add a signature to a PDF. That's where the feature description ends and the important warning begins.

Mozilla's support documentation is unambiguous: signatures added using the Firefox PDF viewer are not legally binding e-signatures. They are simple annotations and provide no authentication or verification, per Mozilla Support. Placing a signature image on a PDF in Firefox is legally no different from drawing a squiggle with the ink tool. For anything requiring a compliant e-signature a lease, a contractor invoice, a legal filing DocuSign, Adobe Sign, or an equivalent platform is still required.

The signature caveat also points to a broader category of things Firefox simply doesn't do. Mozilla's documentation covers annotation layers placed on top of existing PDFs. There is no documented support for editing body text within an existing document, rearranging or deleting pages, merging multiple documents, redacting content, or creating new interactive form fields from scratch.

That's a meaningful boundary. Consider the difference between receiving a contract and needing to fill in your name, date, and initials before returning it versus receiving one and needing to delete a clause, reorder sections, or add a new field. The first is annotation work. The second is structural editing. Firefox handles the first. It doesn't document support for the second.

The same logic applies to redaction. Highlighting text in yellow to draw attention to a passage is annotation; permanently removing text so it cannot be recovered is a structural operation requiring a dedicated tool. For any workflow where that distinction matters legal, HR, compliance Firefox is the wrong instrument.

The practical rule: if you're marking up a PDF, Firefox is likely enough. If you're restructuring one, it isn't.

For most everyday PDF interactions, Firefox covers the ground without additional software. Reviewing a contract and leaving comments before returning it for a proper signature, completing a government form, marking up a draft for a colleague, adding an informal sign-off on an internal document these are exactly the use cases Mozilla's documentation is built around.

Worth being specific about who that actually covers. Someone reviewing academic papers and adding margin notes: covered. A freelancer filling out a client onboarding form: covered. An employee marking up a policy draft before a meeting: covered. A property manager needing tenants to sign a legally binding lease: not covered, at least not for the signature step.

Users who still need a dedicated tool are those whose work involves document assembly, verified signatures, redaction, or building structured forms from scratch. For that category, tools like Adobe Acrobat or PDF-XChange offer capabilities Firefox doesn't document. The distinction isn't about Firefox falling short it's about knowing which tool fits which job.

Firefox's PDF capabilities run on PDF.js, Mozilla's open-source rendering and editing engine. Mozilla keeps a public meta tracker on Bugzilla for PDF.js updates, tagged with version-specific keywords including firefox150, per Bugzilla. The tracker was opened to consolidate PDF.js update tracking into a single bug rather than filing new dependencies each release cycle, according to the same source.

That development cadence explains something important about how these features actually ship. The annotation tools, form-filling support, drawing controls, and signature placement in Firefox today aren't the product of a single version's feature push. Each update to the in-tree PDF.js copy can carry dozens of individual commits touching editor behavior, color handling, font sizing, ink mode, and annotation layer management, as individual Bugzilla update records show.

The feature set is mature and has been iterated on steadily. What's documented now reflects a tool that has had time to stabilize, not a first-pass experiment worth knowing when deciding how much to rely on it.

It also means the signature limitation is almost certainly a deliberate design choice rather than an oversight. Mozilla has had ample opportunity to build authentication into the signature tool and has chosen not to, documenting the limitation explicitly instead. That's a signal about how this boundary is likely to evolve or not.

For the tasks Mozilla documents, Firefox's built-in PDF editor removes the need for a separate app across a wide range of common workflows. Annotation, form-filling, free text placement, freehand drawing, and informal signature placement are all handled directly in the browser, with edits saved locally rather than sent anywhere.

The signature warning is the one place where getting this wrong has real consequences. A visual sign-off on an informal internal document is fine. Treating that annotation as a verified signature in any context where authentication or legal compliance matters is a risk Mozilla's own documentation flags explicitly and one worth taking seriously.

For legal signatures, page-level editing, document merging, or redaction, Firefox doesn't document support, and dedicated tools remain the right call. For everything else, Firefox probably handles it already and has been doing so quietly for longer than most users realize.