Fill PDF forms made simpler, in your browser

A fillable PDF stores named fields inside the document. Those fields can hold text, checkbox states, list choices, or radio-button selections. This tool reads supported fields from an AcroForm PDF and presents controls for entering their values. After filling them, you can save a copy that remains editable or flatten the fields into the page appearance. The output is a new PDF, so your original blank form remains available for another use.

The distinction between a real field and a printed box matters. A scanned application form may look exactly like a fillable form while containing only a picture of lines and labels. This tool cannot create fields merely because boxes appear on the page. If the file has no supported fields, it reports that fact. For a simple visible note on a noninteractive page, the add-text tool is a separate option; it does not turn that page into a structured form either.

Add one PDF and wait for its fields to appear. Read each field name and enter the requested value. Use checkboxes and choices where the source form provides them. Read-only fields are shown but cannot be changed. Leave flattening off if the recipient needs to continue editing the form. Select it only when you want the current field appearances incorporated into the page. Process the document and inspect the generated preview before downloading.

After saving, reopen the downloaded copy in a PDF reader. Check that every visible answer is present, that long text fits, and that selected choices correspond to the intended labels. The tool verifies saved field values for editable output and checks that flattened output no longer contains form fields. Those checks catch structural problems, but they cannot know whether a date, account number, or answer is the one you meant to enter.

The supported types are text fields, checkboxes, dropdowns, option lists, and radio groups in ordinary AcroForm documents. Text fields may be single-line or multiline according to their source definition. Lists use the options supplied by the form, including multiple selections when the field allows them. The source field's length limit is respected, with an additional maximum of five thousand characters for a text field. The document can contain at most one hundred fields.

The tool rejects unsupported field types rather than pretending the form was completed fully. Signature fields and XFA forms are not supported. A PDF containing a button or another unsupported field can therefore be rejected even if some text boxes seem ordinary. This protects against an incomplete workflow that silently omits an important part of the form. Ask the issuer for a standard fillable version when the file relies on features this tool cannot handle.

The file may be a scan, a flattened form, or a digital page with boxes drawn as normal graphics. None of those necessarily includes named interactive fields. A document may also use XFA, a different form technology that this tool does not support. Seeing a blank line on screen is not enough to establish which kind of document you have. The tool reads the actual field structure before offering controls.

If you need to type a small amount of visible information into a static page, you can use the add-text tool and check the placement carefully. If the recipient requires structured fields, validation, or a specific official submission workflow, obtain the correct form version instead. Adding visible text is not equivalent to completing an interactive application, and flattening an existing document cannot create missing fields.

The tool can embed a supporting font when the entered values require characters outside basic ASCII, including common Simplified Chinese characters. This helps the saved appearance display independently of a viewer's default font. Font resources are loaded from this site; your selected form and typed values are not uploaded to generate that appearance. The source field's geometry still controls where the text can be drawn.

Check the actual result for uncommon characters, long names, and small fields. A font cannot make a narrow box wide enough for every answer. If the issuer designed a short field for a fixed-length identifier, do not force a long explanation into it. A multiline field may accommodate a paragraph, while a single-line field is intended for a short value. Reopen the saved PDF and confirm both the characters and their visible fit before sending it.

Flattening takes the current field appearances and places them into the page content, then removes the interactive fields. The recipient normally sees the completed answers without being able to click the original form controls. This can be useful for a final reading copy or a workflow that has difficulty displaying field appearances consistently. Keep an editable copy as well if you may need to revise the answers later.

Flattening is not a password, a digital signature, or protection against all editing. A PDF editor can still modify ordinary page content. It also does not certify who filled the form or prove that the document is unchanged. Choose it for presentation behavior, not as a substitute for an authentication or integrity requirement. If the recipient expects editable fields or automated data import, sending a flattened copy may make their process harder.

A field's stored value and its visible appearance are related but separate parts of a PDF form. Some viewers rely on appearance information that another application did not update correctly. This tool regenerates supported field appearances before saving, then provides a preview of the generated result. That reduces a common cause of invisible answers, but different readers and unusual source documents can still behave differently.

Open the downloaded copy, rather than the original file or an old browser tab with a similar name. Check a second reader if the answers appear missing. A flattened copy may be suitable when the recipient only needs the visible final answers, but confirm their requirements first. If the form has official calculations, submission buttons, or specialized validation, use the issuer's supported workflow rather than treating a visually filled page as proof of a valid submission.

No. This tool does not execute embedded form scripts, automatic calculations, or issuer-specific validation logic. A field that normally computes a total in a desktop reader may remain unchanged here. Read-only calculated fields cannot be edited through the controls. A visually complete page can therefore still be unsuitable for a process that depends on those calculations or on a submit button.

Review instructions supplied with the form. If they require a particular reader, a validation step, or an online submission process, follow that workflow. For a simple contact sheet or checklist without scripted behavior, entering and saving supported values may be sufficient. For a calculation-heavy form, use an application that implements its required behavior and verify totals independently. This tool is a field filler, not a replacement for every PDF form runtime.

Use an unencrypted PDF no larger than 30 MB, with one to one hundred pages and no more than one hundred supported fields. Damaged documents, XFA forms, and unsupported fields produce an error. Processing runs in your browser. The site loads code and, when needed, font resources, but the selected PDF is not sent to a document-conversion API. Clear the file when finished, and remember that downloaded copies remain in your download folder.

Check every required answer, long text near field edges, checkbox meaning, and the distinction between a blank choice and a deliberate negative answer. If you flattened the form, confirm that the visible answers are correct before discarding any editable copy. Use an unambiguous filename for the completed version so it cannot be confused with the blank original. Saving a file here does not send it to the form issuer; you still choose how and where to deliver it.

Choose a tool for the next step and review each output.

• Add visible text to static pages