Adobe Document Generation API Pricing and the Word Template Alternatives That Publish a Price

The pricing page at developer.adobe.com lists two boxes. The first is the Free Tier: "500 free Document Transactions per month" with "Access to all 15+ PDF Services including PDF Extract, PDF Accessibility Auto-Tag API, and Document Generation." The second is a paid plan with no price, described as "Volume and multi-product discounts" and "Scalable for high volume needs", and a Contact sales button.

The sales FAQ fills in the mechanics. You buy through an Enterprise Term License Agreement (ETLA) or a Value Incentive Plan (VIP), and "There is minimum threshold needs to be met for the Enterprise Agreement with Adobe PDF Services API." The same FAQ says the service does not support HIPAA covered data, which rules it out for patient letters and claims documents at US healthcare companies before price even comes up.

Two things buyers go looking for no longer exist. The AWS Marketplace listing, which once let teams pay per call on their AWS bill, only accepted billing addresses in a list of countries that does not include the United States, and Adobe announced on 10 May 2023 that it would sunset the listing. There is also no self serve card upgrade on the pricing page, and developers on Adobe's forum report that calls past the 500th in a month simply do not process until a contract is in place. Our Adobe PDF Services API pricing breakdown covers the same free tier from the conversion side, where the per page rules differ.

Adobe licenses every PDF Services API by the Document Transaction. For Document Generation its licensing page says a generate call consumes one transaction, and its limits page gives the worked example: "Generating a fifteen-page PDF Document from a two-page Microsoft Word template and 1MB JSON file consumes one Document Transaction." The general rule for most other operations is one transaction for up to 50 pages, and Adobe does not say whether a generated document past 50 pages counts twice. If your documents run long, get that answer in writing.

The transactions add up faster than the document count in two ways:

• Every follow up step is another transaction. Combining the generated contract with a terms PDF, compressing it, or applying an electronic seal each consume their own, per 50 pages. A generate then combine pipeline doubles the meter.
• The 500 free transactions are one pool. If another team in the same Adobe organization runs PDF Extract on inbound invoices, both jobs draw from the same 500.

Those two rules are why the free tier covers a pilot but rarely a production workload. A US insurance agency sending 400 renewal packets a month, each generated and then combined with a policy form, uses 800 transactions and is over the limit in the third week.

Adobe publishes no paid price, so the only figures in circulation are what developers relayed from sales calls on Adobe's own forum. In May and June 2023, two developers wrote that the minimum purchase was 500,000 transactions a year at $0.05 each, or $25,000, and one added that the 501st free transaction in a month simply does not process. In October 2024 another developer on a later thread reported being quoted about $55,000 or more a year under an ETLA. None of this is Adobe's published pricing, and your quote may differ.

If the $25,000 floor is close to what you are offered, the arithmetic is simple. 500,000 transactions a year is about 41,700 a month. A company generating 5,000 documents a month would use 60,000 of them, so it pays for eight times the capacity it needs, and the effective price is about $0.42 per document. At 40,000 documents a month the same contract works out to the list $0.05, which is where Adobe's model makes sense.

For comparison, 5,000 documents a month costs $49 on SitePDF's Starter API plan ($288 a year billed yearly), $164 on Docmosis Professional at three pages each, and €95 on Carbone Essential Plus. The document generation API comparison lays out the rest of the market by how each vendor meters.

The storage line is the one that surprises finance and compliance teams. Adobe returns a link that dies in an hour and deletes the asset within a day, so the system that must prove what a customer was sent on a given date has to be built separately. SitePDF returns a hosted link and keeps an archive copy for 90 days, one year or three years depending on the plan, which is the part of the job most template tools leave to you.

If your templates live in Word and the people who maintain them are not developers, the like for like alternatives are the two template engines that print a rate card.

Docmosis (US dollars, pricing dated 1 June 2026) meters pages, defined as "The total number of pages in all documents successfully generated in one calendar month." Its cloud plans step from 4,000 to 500,000 pages: Professional costs $49, $99, $164, $239, $339, $469, $649, $899 and $1,249 a month, Business $64 to $1,524, Enterprise $78 to $1,799, and above 1,000,000 pages is a quote. There are "No overage charges; No blocking at Quota": after two months over, you are asked to upgrade. Templates are ordinary Word or LibreOffice files, output can be PDF, DOCX, ODT, RTF, HTML or text, processing runs in US, EU or Australian regions, and generated documents are deleted immediately. For self hosting, Tornado and Docmosis-Java cost $3,795 to $17,145 once with unlimited documents, plus optional yearly renewals of $1,518 to $6,858.

Carbone meters documents, not pages, with up to 1 MB of merged data per document, and prices in euros excluding VAT even for US visitors: Essential €29 for 1,000 a month, Essential Plus €95 for 5,000, Advanced €159 for 20,000, Advanced Plus €295 for 100,000 and Advanced Ultra €595 for 500,000, with extra documents billed at the end of the period rather than blocked. It accepts DOCX, XLSX, PPTX, ODT and HTML templates. Its cloud is hosted with European providers and generated files are available for one hour and can be downloaded once. On premise licenses start at €1,500 a year for one server and 12,000 documents.

The honest summary: at a few thousand short documents a month, Carbone is the cheapest published option, and Docmosis is the one with a US region and no blocking. If your documents run long, Docmosis's page meter works against you, and a per document meter wins.

A Word template engine exists so that a paralegal or an operations manager can edit the template. If developers already own the templates, or the documents are generated from your application's data (invoices, statements, usage reports, certificates), an HTML template rendered by a PDF API usually costs less and does more:

• Charts and tables render as they do in the browser. Adobe's tags support line, column and pie charts; an HTML page can render any JavaScript chart library, and the render waits for it with a wait_for selector.
• The same template serves the web view and the PDF. The statement the customer sees in the app is the one they download.
• One published price per document, no page meter and no contract: $49 for 10,000 a month, $99 for 50,000, $299 for 250,000.
• A hosted link and an archive copy with a timestamp, so you can show what a document said on the day it was sent.

The migration is mechanical. Export one generated Word document to HTML as a starting layout, rebuild it with print CSS (@page for margins, break-inside: avoid on table rows), replace the Adobe tags with your template language's placeholders, and render both versions side by side for a week before switching. Our guide to generating PDF invoices from HTML walks through the print CSS for multi page tables.

Adobe wins in four situations, and we would not argue against it in any of them. First, your company already has an Adobe ETLA: adding PDF Services to an existing enterprise agreement can make the marginal cost small, and procurement is already done. Second, business users must edit the templates in Word: the Document Generation Tagger add-in builds tags from your JSON model inside Word, which no HTML workflow matches. Third, you need DOCX output that recipients edit afterwards, such as draft contracts. Fourth, you want Adobe Sign tags placed in the same template, so the generated agreement goes straight to signature.

If none of those apply and you generate a few thousand documents a month, the published prices above are the ones to compare. For the rest of the rendering market, our PDF API pricing comparison prices the rendering services at the same volumes, and the Adobe PDF Services API alternatives page covers the conversion side of Adobe's platform.