Understand transaction limits

Adobe Acrobat Sign transaction limits

Adobe Acrobat Sign limits transactions based on the service level of the sending party per the table below:

 

Transactions/ User License/ Year

File size/ Upload

Pages/ Transaction

Signers/ Transaction

KBA Transactions

Phone Auth Transactions

Acrobat Standard
(except ETLA)

Unlimited

(See below)

10 MB

100

10

0

0

Acrobat Pro
(except ETLA)

Unlimited

(See below)

10 MB

100

25

0

0

Acrobat Sign SMB
(Small Business)

150

(See below)

10 MB

100

25

0

0

Acrobat Sign for Business
(ETLA)

150

(See below)

10 MB

100

25

0

0

Acrobat Sign for Business
(VIP)

150

(See below)

10 MB

100

25

50

50

Acrobat Sign for Enterprise
(ETLA)

150

(See below)

10 MB  

500

25

50/yr 

50/yr

Acrobat Sign for Enterprise
(VIP)

150

(See below)

10 MB 

500

25

50

50

Transactions/Acrobat Sign user: A transaction occurs each time an electronic document or collection of related electronic documents is sent to one or more End Users through Acrobat Sign.

Acrobat Sign plans sold as user licenses include 150 transactions per user per year unless otherwise stipulated in your contract.

Business and enterprise-level customers who process a high volume of transactions can speak to their sales agent about buying a total volume of transactions with unlimited users (or a site license).

Refer to the Transaction Consumption article for details on how transactions are consumed.

File size/Upload: Acrobat Sign limits the size of each file uploaded.

If you attempt to upload a document outside this boundary, you get an error under the file that says, "Upload limit exceeded."

Pages/Transaction: The whole transaction (all files merged together) has a total page limit.

If you attempt to send a document that is larger than your account set limit, you get the error "Acrobat Sign was unable to create your agreement because the document(s) exceeded your page limit."

Signers/Electronic transaction: The number of people who can sign an electronic signature transaction varies for each level of service.

Single-user, multi-user for teams, and business service levels have hard caps to the total number of signers their transactions can include.

KBA transactions: Knowledge-Based Authentication (KBA) is an advanced form of signer verification that is enabled at the business and enterprise level of service.

Phone Authentication transactions: Phone Authentication transactions are an advanced form of signer verification that is enabled at the business and enterprise levels of service.

Transaction throttling

Get help faster and easier

New user?