Help Center
Create a fillable PDF form
Normalize a supported source, add or detect real interactive fields, preview the form and export a genuine AcroForm PDF.
Create Fillable PDF turns a supported document into a PDF form workspace. It preserves a native PDF where possible, converts supported Office or image sources to a canonical PDF when required, exposes existing supported fields, and lets you add, configure, preview and export real interactive AcroForm fields.
Before you start
A signed-in ALTABRIG account is required. Keep the original source and inspect conversion warnings before placing fields.
| Plan | Shared actions | Effective input | Transcribe | Priority |
|---|---|---|---|---|
| Guest Free | Processing denied | — | — | — |
| Registered Free | 5 credits / rolling 24 hours | 30 MB/action | Uses the shared action pool | standard |
| Pro | Unlimited standard actions | 104.8576 MB/action | Uses the shared action pool | priority |
| Pro Plus | Unlimited standard actions | 104.8576 MB/action | Uses the shared action pool | highest |
PowerPoint files are not supported in this version. PPT and PPTX must not be uploaded to this version.
Best for
- Applications, questionnaires and intake forms.
- Inspection sheets and handover records.
- Consent or acknowledgement forms prepared for later completion.
- Existing printable forms that need interactive fields.
How to use it
- Sign in and choose a supported source file.
- Review the canonical PDF, page count, conversion warnings and existing fields.
- Add text, multiline text, checkbox, radio, dropdown, date or signature fields.
- Position fields on the correct page and edit supported properties.
- Optionally run automatic field detection, then review every proposal.
- Preview representative values and required-field behavior.
- Export the interactive PDF and test it in compatible PDF software.
Important options
Date fields export as interoperable text fields with a YYYY-MM-DD hint; no proprietary date picker is promised. A signature field is a genuine PDF signature field, but signing occurs later in compatible software. Existing field names are preserved to avoid breaking integrations. Automatic detection can use digital layout or OCR evidence and can miss or over-suggest fields.
Processing and queue
What you receive
You receive a separate interactive PDF containing the configured field widgets. The source remains separate. Conversion and detection warnings remain review evidence rather than guarantees.
What to check before relying on the result
Test every page, field name, field type, option list, required flag, default value, date hint and signature workflow. Save and reopen a completed test copy in the PDF software your recipients will use.
Limitations
- PPT and PPTX are unsupported.
- Automatic detection can produce false positives or miss fields.
- Office/image conversion can change layout and must be reviewed.
- The tool does not decide which fields are legally required.
- A signature field does not itself create or validate a cryptographic signature.
Privacy and file handling
Normalization and detection use temporary processing. Export is a direct operation rather than a queued stage. Result and metadata handling follow current retention authority.
| Plan | Result | Metadata |
|---|---|---|
| Guest Free | Not retained | Not retained |
| Registered Free | Not retained | Not retained |
| Pro | Not retained | Not retained |
| Pro Plus | Not retained | Not retained |
Troubleshooting
If a file is rejected, confirm the exact extension and integrity. A PowerPoint rejection is intentional. If conversion warnings appear, inspect every affected page. If detection finds nothing, add fields manually. If export fails, preserve the workspace and correct invalid or duplicate field configuration before trying again.
Examples
- Convert a DOCX application into a fillable PDF.
- Add required checkboxes and a signature field to an existing PDF.
- Convert a scanned PNG form, then manually correct OCR field suggestions.