Add form fields by typing structured text directly into your document, and understand when this approach is the right tool for the job.
Add form fields by typing structured text directly into your document, and understand when this approach is the right tool for the job.
Use text tags to add form fields to documents by typing structured placeholders directly into the document content. Text tags are fast and precise, and they rely on exact syntax.
This page helps you choose the right next step. Each linked page below focuses on one topic, so you can get in and out quickly.
Start here if...
Choose the path that matches what you’re trying to do:
What text tags are (and are not)
Text tags are text-based field definitions that Acrobat Sign converts into form fields when the document is uploaded.
Text tags:
- Let you author fields without using visual tools.
- Are available to all tiers of service.
- Are processed automatically during upload.
Text tags are not:
- A visual editor.
- Self-validating.
- Interactive during authoring.
If a tag is malformed or unsupported, it fails silently.
When text tags are a good fit
Text tags work best when:
- You need speed or automation.
- Documents are generated programmatically.
- Layout is predictable.
- Authors are comfortable with structured syntax.
They are commonly used in:
- Templates
- Bulk workflows
- API-driven document generation
When to use visual authoring instead
Text tags are not ideal when:
- Precise layout is required.
- Non-technical users maintain documents.
- You need visual validation while authoring.
- Field behavior must be discoverable in the UI.
In these cases, visual authoring is a safer approach.
Important limitations to understand early
Before you proceed, be aware of these constraints:
- There is no authoring-time validation.
- There are no warnings or error messages.
- Syntax must be exact.
- Many failures are silent.
If this feels strict, that’s because text tags rely on precise syntax. The rest of this documentation helps you apply them confidently and correctly.
How this documentation is organized
The Text Tags documentation is intentionally split into focused pages:
- Basics and syntax — how tags are structured.
- Supported field types — what you can create.
- Examples — copy-safe patterns.
- Advanced behaviors — conditions, calculations, cloning.
- Calculated fields — the legacy expression language.
- Identity-verified data — name-based population with no UI mapping.
- Troubleshooting — why something didn’t work.
If you only read one thing
If text tags don’t behave as expected, nothing will tell you why.
That’s normal behavior.
When something fails:
- Assume a syntax issue.
- Check field names and directive order.
- Use Text tag troubleshooting early.
