Generate Adobe Sign Text Tags for Microsoft Word

Generate or write your field's text tag, then:

1. Open your Microsoft Word document
2. Paste the text tag where you want it to appear. Adobe Acrobat Sign will automatically convert the raw text tag into an interactive field. (No "activation" needed.)
3. Test by dropping your Word file into Adobe Acrobat Sign, to verify fields appear and behave as expected.

Your text tagging experience depends on how where you start the signing process. When I talk about raw text tags, I am referring to 

Adobe Acrobat Online

Alert: Acrobat's online "Request e-signatures" tool no longer works with raw text tags. You can, however, import your tagged Word file as a sign template or a webform:

• Create a signing template
• Create a webform

As far as I can tell, text tagging support will continue for these options.

Adobe Acrobat Pro app

Alert: Adobe Acrobat Sign raw text tags also no longer work in the "New" experience of the app. For now, you can switch your app back to the "Classic" experience, and the text tags will work IF you have exported your Word file to PDF -- since the Word file type is also no longer compatible with the Classic experience.

The Classic experience is being discontinued in March 2026. After that, you will still have text tag support online (see Online section, above), and tagged InDesign/Acroform support (as far as I can tell). To swich to the Classic experience in Adobe Acrobat Pro:

1. Open Acrobat Pro.
2. Go to the View menu.
3. Select "Disable New Acrobat".
4. Click "Restart" when prompted to restart the application. 

In summary

Raw text tags DO work in:

• Create a signing template online (Word and PDF files work, for now)
• Create a webform online (Word and PDF files work, for now)
• The "Classic" experience in Adobe Acrobat Pro, IF you export to PDF first.

Raw text tags do NOT work in:

• Adobe Acrobat Sign's online "Request e-signatures tool"
• Adobe Acrobat Pro's "New" experience "Request e-signatures" too.

The better alternative

If you have Adobe Acrobat Pro or Adobe InDesign and you want to avoid rework and harness the full power of text tags, I strongly recommend using InDesign to create your Adobe Sign tagged PDFs instead.

Adobe Sign tagging works differently in InDesign and Acrobat Pro, so check out my Guide and Tag Generator, written specifically for the quirks of these options.

Adobe is pushing out new features all the time! Here's a great page to see what's coming next for Adobe Acrobat and the signing experience:

All Acrobat Sign text tags made for Word require {{curly brackets}} around them, to tell Adobe Acrobat Sign where the interactive field begins and ends.

You can visually set the width of a field by adding extra spaces/tabs after the closing set of brackets. For example:

{{nameMe_es_:signer1           }}

Note: Curly brackets should not be used in InDesign. For InDesign-specific guidance, check out my Guide and Generator!

*

To make a field required, put an asterisk (*) at the very front of the tag.

Example:

{{*fieldName_es_:signer1:phone}}

This is a required phone field assigned to Signer 1.

Note: Signature and initials fields are automatically required (unless they include "opt" in the field name). Don't add an asterisk to these fields--it can cause glitches.

! or :readonly

There are two ways to make a field readonly:

1. Put an exclamation mark (!) at the front of the tag, OR
2. Put :readonly at the end of the tag.

Method 1 does not let ANYONE modify the field, including the sender.

Example:

{{!fieldName_es_:checkbox}}

This is a readonly checkbox that cannot be filled by anyone.

Method 2 allows the sender/prefiller to modify the field before sending, then marks the field as readonly for the signers.

Example:

{{fieldName_es_:prefill:checkbox:readonly}}

This is a readonly checkbox that can be filled by the prefiller or sender, but will be readonly for all signers. 

Note: You can merge data into readonly fields using  Acrobat Sign APIs or the Send in Bulk via CSV feature before the document is sent for signatures.

fieldName

You can name a field whaever you want; just don't include any spaces or special characters (purely alphanumeric).

As a field naming best practice, I recommend using camel case (likeSoAndThus), but it is not a requirement.

Give each field a unique name to remember what the field is for. Use shared field names to link fields of the same name together.

_es_

This is a required element that tells Adobe Acrobat Sign the text tag is an interactive field.

"ES" stands for "EchoSign". EchoSign is the name of the company that Adobe bought up and rebranded as Adobe Sign. It's former name still lives on in the tags, though!

The role defines who is assigned to fill out a field. Here are the possible roles:

Prefill

The :prefiller role can fill out the form before they send it out for the signatures of other signers. There can be only one prefiller.

Sender

Similar to the :prefill role, the :sender role can fill out the form before they send it out for the signatures of other signers - but they also must sign the document at the beginning or end of the signing process. This role only works if  the "I need to sign First/Last” option is chosen while setting up the signature request. There can be only one sender.

FormFiller

The :formfiller role only fills in assigned fields; they do not sign the form. You can have multiple sequential formfillers (formfiller1, formfiller2, formfiller3, etc.).

Signer

The :signer role fills in assigned fields and also signs the form. You can have multiple sequential signers (signer1, signer2, signer3, etc.).

Approver

The :approver role reviews the form and approves. Approvers are not required to have a signature field on the form. You can have multiple sequential approvers (approver1, approver2, etc.)

Anyone

The :anyone role permits anyone to fill in a field. The first person to fill out an anyone field locks in the response. After an :anyone field is filled by someone, no one else can change it. 

Everyone (used with :link only)

The :everyone role is unique to the :link field option. It forces each person to click the link and open it in another tab before they are allowed to submit the filled form.

:signature

Automatically required. Captures the signer's full first and last name and date signed. (Note: If you need InDesign-specific guidance, go to my Guide and Tag Generator of InDesign.)

:optsignature

This is an optional version of the signature field. A signer can skip this signature if desired.

:digitalsignature

Not currently compatible with Word (as of June 2025). This is not recorded in Adobe Sign's documentation.

:initials

Automatically required. Captures the signer's initials and date signed.

:optinitials

Creates an optional initials field. Captures the signer's initials and date signed.

:signatureblock

Includes all of the :signature information, plus email address.

Alert: If your oranization has enabled either of these preferences, then this block field will also display the user-entered title and company fields:

• "Require signers to provide their job title when e-signing," and/or  
• "Require signers to provide their company name when e-signing."

:stampimage

An optional user-uploaded stamp image. Becomes required if no other signature fields have been assigned to the stamping user.

Note: :stamp does not work on its own.

:email

A validated field that appears in the :signatureblock, if entered.

:date

A readonly field that automatically records the signing date.

Note: Adobe Acrobat Sign does not yet have a "date picker" field type, though you can have a user enter a valid date pattern using :isdate. See section "Identity Fields" for details.

:fullname

A readonly field populated automatically based on the signer's typed first and last name when they complete the :signature or :signatureblock fields.

:firstname

A readonly field populated automatically based on the signer's typed first name when they complete the :signature or :signatureblock fields.

:lastname

A readonly field populated automatically based on the signer's typed last name when they complete the :signature or :signatureblock fields.

:title

A field whose value appears in the :signatureblock, if entered.

:company

A field whose value appears in the :signatureblock, if entered.

Default single-line text fields

If no field type is included, the default field type is a simple one-line text field. You can set the width of the field by adding space before the closing brackets "}}".

Example:

{{fieldName_es_:signer1}}

This is a simple text field assigned to signer1. Note that no field type has been defined in the tag.

{{fieldName_es_:signer1                                              }}

This is a simple text field assigned to signer1 with the width set by adding extra spaces or tabs before the closing brackets "}}". Note that no field type has been defined in the tag.

:multiline(#)

This field type permits multiple lines. You can set the number of visible lines (field height) by putting the number of lines in parenthesis. You can set the width of the field by adding spaces or tabs before the closing brackets "}}".

Examples:

{{fieldName_es_:signer1:multiline(3)}}

This is a three-lines-tall text field assigned to signer1.

{{fieldName_es_:signer1:multiline(3)                   }}

This is a three-lines-tall text field assigned to signer1 with the field width increased by adding spaces or tabs before the closing brackets "}}".

:curr

Permits US and UK currency formats, including prefixes and commas:

:curr(country=us)

:curr(country=uk)

:isemail

Warns the user when they enter an invalid email address pattern.

:isdate

Permits you to set a user-entered date with popup alert if they don't enter the date in your designated pattern.

Example: 

{{nameMe_es_:prefill:isdate(format=dd/mm/yy)}}

:phone

Permits US phone numbers formats (5555555555, 555-555-5555, (555) 555-5555, etc.).

:phone(country=uk)

Permits UK phone number formats.

:ssn

Permits social security number patters 123456789 and 123-45-6789.

:zip

Permits 5-digit (12345) US ZIP codes.

:zip4

Permits US ZIP codes with the additional 4-digit delivery code (12345-6789).

:num

Limits user input to numerical characters (numbers only).

:num()

Limits user input to a number range (<, <=, >,>=, or a combination the highest and lowest permitted numbers in the range). Examples:

• :num(>10)  Permits a user to enter a number larger than 10.
• :num(<10)  Permits a user to enter a number smaller than 10.
• :num(>=10)  Permits a user to enter a number larger than or equal to 10.
• :num(<=10)  Permits a user to enter a number smaller than or equal to 10.
• :num(>1,<10)  Permits a user to enter a number larger than 1 and smaller than 10 (i.e., digits 2-9 are allowed).
• :num(>=1,<=10)  Permits a user to enter a number larger than or equal to 1 and smaller than or equal to 10 (i.e., digits 1-10 are allowed).

Attention: Each text tag can only include on validation directive. One the first validation rule will be applied, if more than one is added to a text tag (additional ones will be ignored).

:custom(regexp="^.{3}$")

You can write your own custom RegEx validations, too! In this example from Adobe's text tagging guide, the regular expression requires three characters to be entered in a row.

:custom(regexp="^.{3}$",msg="Not a match for three characters in a row!")

In this example (also from Adobe's text tagging guide), the same RegEx runs and if the criteria are not met, a custom message is displayed ("Not a match for three characters in a row!").

Additional specifications for creating compatible RegEx strings, as discussed on Adobe's text tagging guide:

• Case insensitivity is not supported ("?i" and "?-a")
• Per Adobe's text tagging guide: The backslash character that is part of regexp constructs such as "\w", must always be escaped with a backslash (i.e., "\\w").
• To search for a backslash, use \\\\.
• The regular expression string begins and ends with the double-quotes (") character.
• If a double-quotes character will be a part of the string that the recipient is expected to enter, the validation string can match the double-quote by escaping it with a backslash: \"

Adobe recommends this website as a helpful reference for the syntax of regular expressions that are compatible with Adobe Sign.

:checkbox

Adds an unchecked checkbox.

:checkbox:checked

Adds a pre-checked checkbox.

:radio

There are several ways to add radio button groups to your Word form:

Method 1

{{nameThisRadioGroup01_es_:signer1:radio(Sunny)}}

{{nameThisRadioGroup01_es_:signer1:radio(Raining)}}

{{nameThisRadioGroup01_es_:signer1:radio(Snowing)}}

In this example, this is a set of three radio buttons all grouped under the group name "nameThisRadioGroup01", with button options Sunny, Raining, Snowing added in parenthesis at the end.

Method 2

{{(Sunny)nameThisRadioGroup02_es_:signer1}}

{{(Raining)nameThisRadioGroup02_es_:signer1}}

{{(Snowing)nameThisRadioGroup02_es_:signer1}}

In this example, the radio button names are added via parenthesis at the front of the tag (Sunny, Raining, Overcast). They are all grouped under the name nameThisRadioGroup02.

:label(“Custom label”)

You can add a custom visual label to the right of each radio button option using this feature. It works with both methods outlined above:

Method 1

{{nameThisRadioGroup01_es_:signer1:radio(Sunny):label("Sunny")}}

{{nameThisRadioGroup01_es_:signer1:radio(Raining):label("Raining")}}

{{nameThisRadioGroup01_es_:signer1:radio(Snowing):label("Snowing")}}

Method 2

{{(Sunny)nameThisRadioGroup02_es_:signer1:label("Sunny")}}

{{(Raining)nameThisRadioGroup02_es_:signer1:label("Raining")}}

{{(Snowing)nameThisRadioGroup02_es_:signer1:label("Snowing")}}

:dropdown(options="option1,option2,option3")

Creates a multi-option dropdown menu. Options should be listed in parenthesis. 

Example:

{{nameMe_es_:signer1:dropdown(options="Cotton candy,Elephant ears,Corndogs”)}}

This is a dropdown menu assigned to signer1 with three options: Cotton candy, Elephant ears, and Corndogs.

:attachment

This tag creates a file upload button that supports the following file types:

• Doc types: PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, RTF
• Image types: JPG, JPEG, PNG, GIF, BMP, TIF, TIFF
• Other file types: ZIP, CSV, XML

Note: Make sure to test this feature; it should support the listed file types and permit files up to 25mb in size, but the results are a little unpredictable. For instance, a photo uploaded from a smartphone might be rejected.

Accessibility warning: This button is not visible to screenreading software, so it's basically invisible to your visually impaired users. Consider your audience's needs before using this tag.

:inlineimage(#)

This tag creates a button to take a photo or upload a picture that displays inline in the form (example: Driver’s license). The form sender can download image after the signature workflow is complete.

Set the height by entering the number of lines in parentheses next. Set the width by adding extra spaces or tabs before the closing brackets "}}".

Issue: If the image is dimensions do not match your anticipated image upload dimensions, the uploaded images may display with distortion (squished horizontally or vertically).

Solution: Test this feature with both iPhone and Android phone cameras to make sure uploaded images don’t get vertically distorted by the field's dimensions.

:link("http://www.URLgoesHere.com")

This tag creates a clickable link you can require your participants to view before they submit the form.

To require an individual participant to click it before they can submit the form, assign it to their role (e.g., signer1).

To require everyone to click it before they can submit the form, assign it to the unique role :everyone. This role only works with the :link tag.

:transactionid

You can have Adobe Sign automatically capture the transaction ID in the form when signing is complete, if that unique identifier is useful to you. This is a readonly field type.

:repeat

Makes the field automatically repeat in the exact same spot on each page thereafter. When the field is filled, all other repeat instances are also filled.

:string(maxlen=#)

Use this rule to limit the number of alphanumeric characters a user can enter into a text field (alphanumeric is the default).

:string(char=alpha,maxlen=#)

Use this rule to limit the number of alpha-only characters a user can enter into a text field.

:string(char=num,maxlen=#)

Use this rule to limit the number of numeric-only characters a user can enter into a text field.

:default("Sample field value here")

Add this rule to any text field to set the default value. You can put the default value in single or double quotes - it doesn't matter.

:font(name=FontName, color=green, size=14)

You can set the font, the color, and the size of your field values. (Note: I have only tested this with single and multiline text fields; it may also work with other field types.)

Example:

nameMe_es_:signer1:font(name=Arial, color=#000000, size=12)

This text field is completed by Signer1, and the value's font is Arial, color is black, size is 12pt.

Supported fonts:

• Lato
• Roboto
• Slabo 13px
• Source Serif Pro
• Source Sans Pro
• Source Code Pro
• OR you can use the name of any font that appears within the existing document (Adobe Sign can tap into the embedded fonts you used to design your form)

Supported colors:

• Black (default if no color defined)
• Blue
• Cyan
• Darkgray
• Gray
• Green
• Lightgray
• Magenta
• Orange
• Pink
• Red
• Yellow
• White
• Or enter it as a hex code (i.e., #000000)

Size is entered in points (i.e., 14pt)

The font settings tag has not been added to the tag generator yet.

:tooltip("Custom tooltip text here")

Adds custom guidance text when your user hovers their mouse over the field.

I have yet to test this tag type in Word. I'm working on it, though!

I have yet to test this tag type in Word. I'm working on it, though!

I have yet to test this feature in Word. I'm working on it, though!

I have yet to test this feature in Word. I'm working on it, though!

The following text tags appear in Adobe's documentation, but they are not supported in InDesign PDFs (and this incompatibility is not recorded in Adobe Sign's documentation):

• :digitalsignature
• More will be added as I identify them.

I have also confirmed you cannot use bracketed text tagging AND interactive InDesign fields in the same document. Adobe Acrobat Sign will ignore the bracketed text tags if interactive InDesign fields are present in a form (this is not recorded in Adobe Sign's documentation). You must use one or the other.

AI is great at hallucinating imaginary Adobe Sign tags. Here are a few that I've tested and ruled out:

• :admin
• :bordercolor
• :capitalize
• :certifiedrecipient
• :color
• :datetime
• :datesigned
• :delegator
• :fontsize
• :lowercase
• :signerdate
• :toggle
• :password
• :uppercase
• :validation (and any derivatives thereof)
• :width("Pixels")

Adobe Sign tags are robust when used the way they were intended: As raw text tags in documents (such as those made in Word). The fuller range of text tags is available in Adobe's official guide:

https://helpx.adobe.com/sign/using/text-tag.html

If you discover a tag that works in Word that I did not list in my guide, please let me know! I am eager to keep things up-to-date. Thanks! :)

Adobe Sign's interface is somewhat accessible for your signers IF you have followed InDesign accessibility best practices to produce the PDF.

However.

As of my testing in June 2025, the final signed PDF's user-entered values are not tagged. This means your visually impaired signers will not be able to read their own form values in their signed form, using screenreading software. If you expect your signers to use assistive technology and/or you are a state or federal government agency, this is critical.

For a truly equitable experience, all users should be able to read what they signed, in full, after signing is complete.

Adobe documents this discrepancy here:

"Note: Acrobat Sign can not create an accessible PDF from a source document that is not already accessible. Acrobat Sign only ensures that existing tagging is preserved and that any content entered into a form field is tagged appropriately. It's beyond the scope of Acrobat Sign to produce a tagged document from a source document that isn't tagged when uploaded."

However, Adobe's own InDesign product does not provide a way to tag user-entered values during design or export. User-entered text is, by nature, added by the Adobe Sign system AFTER the PDF is filled and signed via Adobe Sign features, so there is no current workaround. (If you find one, let me know.)

I sincerely hope Adobe is able to fix Adobe Acrobat Sign's PDF output process in time for the oncoming 2026 federal WCAG 2.1 mandate for state and federal governments. In the meantime, this is a critical consideration when you are choosing which signing solution to use with your audience.

I will update if/when this issue is resolved.