PDF & Documents

How to Fill Out a PDF Form on iPhone

To fill a PDF form on iPhone, open a copy in a PDF app, tap a real form field when one exists, and enter the requested information. For a scanned form without fields, an annotation tool can place visible text over the page, but that does not turn it into a structured form. Save the completed copy and reopen it outside the editing view. Check all pages and long answers before sending. Follow the recipient’s instructions if they require interactive fields, a specific portal, or a particular signing method.

Identify the kind of form

Tap an empty field in your PDF viewer. If a cursor appears, the document may contain interactive form fields. If nothing happens, the page may be a scan or a flattened layout; adding a text annotation is a different workflow from filling a built-in field.

Complete a copy

Preview on supported iPhone versions includes form-filling controls. Use actual fields where available and add text annotations only where necessary. Match the intended line length instead of shrinking every answer until it is hard to read. Check whether a checkbox is interactive before drawing a mark over it.

Use a short test answer first and reopen an exported copy. That catches a save or compatibility problem before you spend time completing a long application. Never enter private information into a test file you intend to share publicly.

Final checks

Compare the completed copy with the original page count. Make sure long answers are not clipped, check marks are visible, and dates use the requested format. If the recipient cannot see your entries, ask whether a flattened copy is acceptable. Flattening can make annotations visible in more viewers but may remove later editability, so retain the working version.

Identify the kind of form you received

A PDF can contain interactive fields, a scanned picture of a form, or ordinary page text with blank spaces. Try selecting a field before deciding that the file is broken. If it is only a scan, adding a text annotation may be appropriate for a visual submission, but a system expecting actual field data may not accept it.

Read the recipient’s instructions before changing the file’s structure. A page that looks completed to a person may still fail an automated upload that requires specific field behavior. Keep the original template and work in a separate copy.

Enter answers that survive the final view

Use a readable text size and review long answers after leaving each field. Some fields can display a scrolling answer while only part of it appears in a printed or flattened view. Shorten the answer where appropriate or follow the form’s instructions for an additional page instead of hiding essential information outside the visible area.

Check tick boxes and dates independently. A tap near a box is not proof that its state changed. Move through the complete document once after entry, including pages that initially appeared blank or optional.

Export and reopen before returning it

Save the file to a clear location and reopen the saved copy from Files. Compare the visible answers with the editing view. If the recipient requests a flattened copy, understand that this can remove interactivity; retain an editable source separately where your app supports it.

For disappearing answers, see annotations missing after sharing. For a signature area, use signing a PDF after you have checked the entered information.

Can I use white text or a white rectangle to redact information?

A covering annotation is not a guarantee that underlying information is removed. Obtain a properly redacted source or use a verified redaction workflow when sensitive data must be eliminated.

Why is the finished file too large?

A scanned background may dominate the size even if you typed only a few words. Reducing PDF size explains the difference between an image-heavy document and a text document. Do not sacrifice readability merely to meet a limit.

Sources & further reading

  • Apple · Checked Oct 1, 2026

Related Guides

Related Tools