Adobe Acrobat Sign's 150 transaction limit, and the price Adobe doesn't publish

The allowance

Adobe states it directly: "Acrobat Sign plans sold as user licenses include 150 transactions per user per year unless otherwise stipulated in your contract."

A transaction is counted "each time an electronic document or collection of related electronic documents is sent to one or more End Users through Acrobat Sign" — so, like most platforms, on send rather than on completion, and once per envelope regardless of how many documents it bundles.

Which plans that binds is worth being precise about, because two of them are not capped:

| Service level | Transactions per user licence per year | |---|---| | Acrobat Standard (except ETLA) | Unlimited | | Acrobat Pro (except ETLA) | Unlimited | | Acrobat Sign SMB (Small Business) | 150 | | Acrobat Sign for Business (ETLA) | 150 | | Acrobat Sign for Business (VIP) | 150 | | Acrobat Sign for Enterprise (ETLA) | 150 | | Acrobat Sign for Enterprise (VIP) | 150 |

There is a genuine oddity in that table: the dedicated e-signature products are capped and the general PDF products are not. If your signing volume is modest and you mainly need Acrobat anyway, Acrobat Standard or Pro is unlimited for e-signing. The purpose-built Acrobat Sign tiers are the ones metered at 150.

The price Adobe does not publish

Every other major platform in this category publishes a per-unit rate for going over. DocuSign lists $3.00 to $7.80 per envelope; SignNow lists $0.96 to $3.60 per invite; PandaDoc lists $2.00 to $3.50 per document.

Adobe lists nothing. The transaction-limits page says only that "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)."

So the cap is transparent and the consequence of hitting it is not. There is no published figure from which to calculate the cost of a year that runs 20% over, which means it cannot be modelled before purchase — it has to be negotiated, at a point where you have already standardised on the platform. This is the substance behind the recurring complaint that Acrobat Sign pricing requires a sales call: for volume, it genuinely does, structurally.

To be fair about it, the model Adobe points you toward — a transaction bundle with unlimited users, or a site licence — is the right shape for a team whose volume is high relative to headcount. It is the pre-purchase opacity that is the issue, not the model.

The limits that are not about volume

The same table sets per-transaction ceilings that apply regardless of how much allowance you have left:

| | Acrobat Standard | Acrobat Pro | Acrobat Sign SMB / Business | Acrobat Sign Enterprise | |---|---|---|---|---| | File size per upload | 10 MB | 10 MB | 10 MB | 10 MB | | Pages per transaction | 100 | 100 | 100 | 500 | | Signers per transaction | 10 | 25 | 25 | 25 | | KBA transactions | 0 | 0 | 0 (50 on VIP) | 50 / yr | | Phone auth transactions | 0 | 0 | 0 (50 on VIP) | 50 / yr |

Three of these bite in ordinary use. 10 MB per file is not much for a scanned document set; exceeding it produces "Upload limit exceeded." 100 pages per transaction on everything below Enterprise triggers "Acrobat Sign was unable to create your agreement because the document(s) exceeded your page limit." And knowledge-based authentication and phone authentication are zero on Acrobat Standard and Pro — the two unlimited tiers — so the plans without a volume cap are also the ones without identity verification. If you need KBA, the unlimited option is not available to you.

Throttling, separately from the allowance

Independent of the annual cap, Acrobat Sign rate-limits requests. Adobe's description: requests from the same source — "such as a user ID, IP address, or agreement ID — are limited per minute, hour, and day", and a request exceeding those limits "is rejected with an error message." It adds that in rare cases, where usage disrupts the system, "access to Acrobat Sign may be temporarily disabled."

For anyone building an integration this matters more than the annual number, because the annual allowance fails predictably at a known point while throttling fails at a threshold Adobe does not publish. Build in retries with backoff and do not batch sends tightly.

Costing a real workload

Five people sending 300 documents a month is 3,600 a year. Five Acrobat Sign user licences allow 750. The excess is 2,850 transactions — and there is no published rate to multiply it by, so unlike every other platform in this comparison the annual cost of that workload cannot be stated here at all.

That is the finding, rather than a gap in this article: the number does not exist publicly. Anyone evaluating Acrobat Sign at volume should ask for the per-transaction rate and the site-licence price in writing, early, and treat the answer as the main commercial term.

For contrast, PearSign publishes both halves of the calculation: Professional is $39 a month for 1,000 envelopes a month across the whole account with 15 team members included, and the free plan is 10 a month with no card. The 3,600-a-year workload fits inside Professional, so the answer is $468 a year and it is derivable from the pricing page before you talk to anyone.

FAQ

How many transactions does Adobe Acrobat Sign include?

150 per user licence per year, unless your contract stipulates otherwise. This applies to Acrobat Sign SMB, Acrobat Sign for Business and Acrobat Sign for Enterprise. Acrobat Standard and Acrobat Pro (except ETLA) are listed as unlimited transactions.

What counts as a transaction in Acrobat Sign?

Adobe defines it as each time an electronic document, or a collection of related electronic documents, is sent to one or more end users through Acrobat Sign. It is counted on sending, and one transaction covers the whole bundle however many files it contains.

What happens if you exceed the Acrobat Sign transaction limit?

Adobe does not publish a per-transaction overage price. Its transaction-limits page directs high-volume business and enterprise customers to speak to a sales agent about buying a volume of transactions with unlimited users, or a site licence. The cost of exceeding the allowance therefore has to be quoted rather than calculated.

Is Adobe Acrobat Sign really unlimited on Acrobat Pro?

For transactions, yes — the limits table lists Acrobat Standard and Acrobat Pro (except ETLA) as unlimited. But both are listed with zero knowledge-based authentication and zero phone authentication transactions, so the unlimited tiers do not include those identity-verification methods. Signers per transaction is also capped at 10 on Acrobat Standard.

What is the page limit on an Acrobat Sign agreement?

100 pages per transaction on Acrobat Standard, Acrobat Pro, Acrobat Sign SMB and Acrobat Sign for Business; 500 pages on Acrobat Sign for Enterprise. The limit applies to all files in the transaction merged together, and exceeding it returns "Acrobat Sign was unable to create your agreement because the document(s) exceeded your page limit."

Does Acrobat Sign rate-limit API requests?

Yes, separately from the annual transaction allowance. Adobe states that requests from the same user ID, IP address or agreement ID are limited per minute, hour and day, that requests over those limits are rejected with an error, and that access may be temporarily disabled where usage disrupts the service. The thresholds are not published, so integrations should retry with backoff.