Filling a PDF form on Android is less about picking the shiniest app and more about controlling the pipeline: input, storage, signature, flattening, and delivery. Many Android PDF tools can open a form, but only a subset reliably map keyboard input into AcroForm fields, accept a drawn signature, flatten the document so downstream recipients cannot edit the answers, and preserve field values when the file is re-sent. This guide focuses on Android behavior, not iPhone. It covers which apps work without an account, how to type accented characters safely, when a browser-based filler is better, and how to diagnose the classic failure where fields look filled on your phone but appear blank when printed or opened elsewhere.
You can handle this directly in your browser with our free pdf to word tool — nothing gets uploaded.
The practical shortlist for account-free form filling on Android includes several local-first options and one browser fallback.
When choosing, open your actual form first. A form that uses dynamic widgets, unusual field types, or JavaScript can behave very differently across apps. If a local app shows your typed values but a print preview or a second app shows blanks, the problem is likely in how the app stores values rather than in the app being "broken".
The biggest source of "garbage in the form" errors on Android is keyboard and input-method handling. Android soft keyboards can emit composed characters, alternate layouts, or plain ASCII that the PDF field may not expect. For forms that require accented characters, use this workflow:
A practical test string for diacritics is something like: José Müller Ångström Ñoño. If the phone displays it but the printed page or a second reader shows blanks, boxes, or question marks, the pipeline is losing Unicode fidelity.
On Android, the most reliable signature method is a drawn signature, not a typed signature. A typed signature looks inconsistent and does not satisfy forms that expect an ink image. Use a signature pad provided by the app, draw the signature with a steady hand, and save it as the form's signature image or widget. Keep these points in mind:
For high-stakes forms, verify the signature after flattening. A flattened document should still show the signature as part of the page content, not as an editable annotation.
Flattening converts form field values and annotations into static page content. After flattening, the recipient sees the text and signature as part of the page, not as editable fields. This is the step that prevents "the form opened and my answers disappeared" complaints from downstream users. To flatten on Android:
Not every Android PDF app can flatten. If your local app cannot flatten reliably, use a browser-based tool that offers a "flatten" or "convert to static PDF" option, or send the unfilled but completed form to a desktop tool for the final flatten step. Do not assume that saving a filled form equals flattening; saving preserves field values, while flattening bakes them into the page.
Android storage and sharing introduce subtle failure modes. To keep field values intact when you save and re-send:
When re-sending, attach the flattened PDF. If you attach the interactive version, the recipient's phone may show editable fields, and their app may render them differently or clear them if they interact with the document.
This is the most frequent Android form problem. The filled values look correct on your phone, but a print shop, a desktop viewer, or another mobile app shows blanks or missing text. The usual causes are:
Diagnose by doing three tests: open the filled PDF in a second mobile app, open it on a desktop reader, and print it to PDF or to a physical page. If all three match what you see on the fill device, the file is likely stable. If any one differs, flatten the document and re-test. If flattening does not fix it, the source app is not exporting the values correctly, and you should refill in a more capable app or in a browser-based form engine.
A browser-based filler is often the better choice when the Android app fails at a specific stage. Use a browser when:
The trade-off is that browser tools may require uploading the file to a service, so use them only for documents you are comfortable sending over the network. For sensitive forms, prefer a local app that can fill and flatten offline, and reserve browser tools for non-sensitive documents or for the final verification step when you can upload a flattened copy.
In practice, the most dependable Android workflow is: fill in a local app that supports your field types, type accented characters with a verified keyboard, draw the signature, flatten the document, save a named copy, and verify the result in a second reader before sending. When that pipeline breaks, switch to a browser-based filler for the failed stage rather than trying to force the phone app to produce output it cannot reliably create.
Related reading: add handwritten signature to pdf, add page numbers formatting, best cv resume format as pdf.
How do I type accent marks on an Android keyboard?
Long-press the base letter (e.g., 'e') to open a pop-up with accented alternatives like , , or . For devices without this feature, use a third-party keyboard app or copy-paste symbols from a character map. Ensure your PDF form uses standard Unicode fonts to display these characters correctly without falling back to default fonts.
Can I draw a signature directly in the PDF?
Yes. Use the touch-drawing tool to sign on the screen, or upload a scanned image of your signature. Position the signature within the designated signature field. If your Android device supports biometric authentication, some apps may allow you to save the signature for reuse. Ensure the line thickness is visible against the background before finalizing the form.
What does 'Flat Output' mean for my file?
Flattening merges all interactive form fields, including your text and signatures, into the static background image. This prevents others from editing your input later. Use flat output when submitting legal documents to lock data. If you need to edit fields later, save a non-flat version first, as flattening is irreversible and removes the ability to change specific text fields.
Why are my accent characters appearing as boxes?
This usually happens when the PDFs embedded font does not support the specific Unicode character. Try selecting a different font that includes extended Latin or Greek characters within the form properties. If the issue persists, the PDF may lack proper encoding; regenerate the document using a source that supports UTF-8 to ensure characters render correctly across all devices.