Skip to main content
V
vsomsap
January 13, 2026
Question

“This agreement has form fields that are not supported” error blocks image upload in Acrobat Sign

  • January 13, 2026
  • 1 reply
  • 242 views

Hello Adobe Community,

I am experiencing a recurring issue with Adobe Acrobat Sign when using an Image / Attachment field in an agreement.

During the Prepare Document (Step 2/3) stage, I add an Image (or Attachment) field to allow recipients to upload a photo as part of the signing process. However, when recipients attempt to sign the document, they encounter the following error:
Server error
Error message: “This agreement has form fields that are not supported”

Once this error appears, the recipient is unable to upload the image and cannot proceed with completing the agreement.


Key details:

  • The issue happens with multiple recipients (not user-specific)

  • It occurs intermittently but frequently

  • Most reports come from recipients accessing the agreement via a web browser or mobile device

  • Reloading the page does not resolve the issue

I would appreciate clarification on:

  • Which form fields are considered “not supported” in Acrobat Sign agreements

  • Whether Image or Attachment fields have known limitations during the signing stage

  • If this issue is related to browser type, mobile devices, file size, or account-level settings

  • Recommended alternatives or best practices for collecting images from recipients during e-signing

Thank you very much for your help.
Any guidance from Adobe staff or the community would be greatly appreciated.

1 reply

Souvik Sadhu
Community Manager
Souvik SadhuCommunity Manager
Community Manager
January 13, 2026

Hi @vsomsap,

 

Hope you are doing well. Sorry for your experience with using Acrobat Sign.

 

Let's understand why this happens:

Acrobat Sign supports only a subset of PDF form field types for agreements.
When the PDF contains form fields outside the supported subset, the Adobe Sign engine cannot reliably place signature and image upload elements.

 

When an image upload is added (for example, via the File Attachment / File Upload form field), Acrobat Sign tries to map it into the input workflow. If Acrobat Sign detects unsupported or non-standard form fields, it throws the error you saw and disables the image upload control.

This happens even if the unsupported fields are not used.

 

Acrobat Sign does not support a few field types, including push button fields, generic button widgets, “File upload” fields not created by Acrobat Sign, Acrobat “Rich Media” or “Movie” buttons, and custom widget types (e.g., JavaScript buttons).

Image upload in the signing page is implemented by Acrobat Sign’s own file block widget. If the PDF already contains incompatible widget types, Sign disables or blocks its rendering.

 

 

To fix it, if you find any unsupported button/widget:

1. Delete that field

2. Replace it with an appropriately supported form field:

    • For signatures → use Signature Field

    • For initials → use Initials Field

    • For text → use Text Field

    • For attachments → let Acrobat Sign provide the upload widget, do not add your own

Let us know if this helps.

 

Additionally, if you require guidance on field-specific issues, you can upload the agreement here or share it as a private message, and we'll respond with further findings.

To send a private message, click on my profile name and then select the blue "Send Message" button.

 

Look forward to hearing from you.


Regards,
Souvik.

V
vsomsapAuthor
January 13, 2026

Thank you for the explanation.

To clarify, the image/upload field was created directly using Adobe Acrobat, not from any third-party tool. However, the same error still occurs and recipients are still unable to upload images during the signing process.

If this approach is not supported, could you please advise on how to allow recipients to upload images as part of the agreement?

Specifically: Should we avoid adding upload fields in the PDF entirely? Are there alternative supported workflows for collecting images from signers?

Your guidance on the correct and supported way to collect images from counterparties would be greatly appreciated.

Thank you in advance for your support.

Meenakshi_Negi
Meenakshi_Negi
Legend
January 14, 2026

Hi vsomsap,

 

Thank you for the information and the screenshots.

 

If you are adding form fields while sending the document for signature, the issue should not occur. However, we would like to check the document you are using. There might be a hidden field in the form that is creating this error. 

Please share the form you are using. Also, share a short video showing how you add form fields and send it for signature. It will help us to understand what might be causing this behaviour.

 

Please test to see if the issue occurs with the image field only. You may resend the document to your alternate email address for testing. In that document, do not add the image field and see if you can sign the document without receiving the error.

 

Let us know how it goes.

 

Thanks,

Meenakshi

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices