Browsers and devices
For the most reliable experience, use a current version of Chrome or Edge on a desktop or laptop with JavaScript, site storage and sufficient free memory enabled.
Ordinary PDF editing may work in current Firefox and Safari versions, but Word conversion is more sensitive to WebAssembly, SharedArrayBuffer, cross-origin isolation, storage and memory support. If it fails, retry in current Chrome or Edge.
Embedded browsers inside social-media, email or messaging apps are not supported. Mobile and tablet use is not currently recommended for precise field positioning.
Supported files and best results
| Feature | Supported | Important limits |
|---|---|---|
| Open documents | Standard PDF and modern Word .docx | Legacy .doc, ODT, RTF and Google Docs links are not directly supported. |
| Add images | PNG and JPEG | Large images increase browser memory use and export size. |
| Existing form controls | Standard PDF AcroForms | Dynamic XFA and unusual scripted forms may not work. |
| Export | Standard interactive PDF form controls | Appearance and behavior vary among PDF readers. |
Best results come from digitally generated PDFs with selectable text, clean conventional form layouts, standard page sizes and orientations, and Word documents using commonly available fonts.
Automatic field placement
Auto-place examines selectable text and simple visible form structure. It can identify likely labels, blank lines, table cells, dates, checkbox marks and printed choices.
It does not perform OCR. Image-only scans usually need OCR in another tool first. Automatic suggestions can miss a field or choose the wrong size or type, so review every field before export.
Word conversion
Modern .docx files are converted locally with a browser-based LibreOffice engine. Layout is preserved as closely as possible, but font substitution, line wrapping, pagination, Word-specific fields, tracked changes and complex objects can produce differences.
The first conversion may require a large engine download and more memory than normal PDF editing. Private browsing, aggressive storage clearing and blocked browser storage can interfere with the local conversion handoff or recovery.
Text and image editing uses overlays
Text and image changes are applied as page overlays. This is useful for visual correction and repositioning, but it does not necessarily alter or delete the original underlying PDF object.
This is not secure redaction. Do not rely on a covering box, replacement text or visual removal to erase confidential information. Use a dedicated redaction product instead.
Signed, encrypted and special PDFs
Password-protected or encrypted files, dynamic XFA forms, PDF portfolios, damaged files, complex scripts and unusual embedded content may not open or export correctly.
Editing a digitally signed PDF normally invalidates the signature. Create Fillable does not verify identities, create digital signatures, scan documents for malware or sanitize active content. Open only documents you trust.
Export and PDF-reader compatibility
Create Fillable exports standard interactive PDF form controls and performs a local structural check before download. PDF readers can still differ in appearance and behavior.
Test the exported file in the reader your recipients will use. Adobe Acrobat Reader generally provides the fullest form support; macOS Preview and browser viewers may display or handle some controls differently.
Create Fillable does not guarantee PDF/UA, WCAG or jurisdiction-specific accessibility compliance. Review field labels, keyboard order and assistive-technology behavior when accessibility is required.
Performance and file complexity
All document processing occurs on your device, so speed and practical file capacity depend on browser memory, hardware, page count and document complexity. Very large, damaged or highly complex files can time out or fail.
If a file fails, save a fresh copy from its source application, reduce unnecessary pages or images, close memory-intensive tabs, and retry in a current Chrome or Edge desktop browser.
Still stuck? Contact support with the error message and a description of the source file—without sending confidential contents.