How Does DocuGenerate Count Documents and What Is Included in Every Plan?

DocuGenerate counts documents generated, not pages. A 100-page report counts as one document, the same as a one-page letter. Every plan, including the Free one, includes the same standard features: generated document links that never expire, overage handling instead of forced upgrades, and access to the PDF Generation API. If your workload is page-heavy but document-light, this counting model works in your favor.

How Document Counting Works

The unit of billing is the generated document, not the page. When you feed a template and a data set into DocuGenerate, each data item produces one document — regardless of how long that document turns out to be.

This matters if you generate long documents: reports, agreements, or certificates with many pages. Under a page-based model those would consume far more of your quota. Here, length is free.

The practical takeaway: estimate your monthly volume by counting data rows, not page count. If you generate one invoice per customer per month, your document count equals your customer count.

What Every Plan Includes

DocuGenerate states that features other tools reserve for higher tiers are standard on all plans, including the Free one. The confirmed standard features are:

• Documents, not pages — page count does not affect your quota.
• Links never expire — generated documents stay available until you delete them, rather than being purged after a retention window.
• Overage, not upgrades — if you go past your monthly volume, you are handled as overage rather than being forced onto a higher plan.
• PDF Generation API — the REST API is available on all plans, with a Quick Start Guide for developers.

The API point is worth noting: some document-generation services gate API access behind paid tiers. Here it is listed as a standard feature across plans.

What You Can Generate

The platform produces PDF documents from Word templates plus JSON or Excel data. Document types named on the site include invoices, letters, contracts, agreements, certificates, and proposals.

The workflow is:

1. Prepare a Word template with merge tags where dynamic text should appear.
2. Provide the data as JSON or an Excel file.
3. Generate — for each data item, the merge tags are replaced with actual values and a document is produced.

Templates can be uploaded in DOCX, DOC, ODT, TXT, or SQL format; data in JSON, XLSX, XLS, ODS, or CSV. Merge tags are auto-detected after upload, and delimiters can be changed from the default [Name] style to something custom like «Name» or {Name}. Templates support more than plain text: images, tables, lists, conditions, and QR codes can all be driven by merge tags.

You can generate through the web app, no-code integrations (Zapier, Make, n8n, Pipedream, and others), or the API.

Choosing Based on Your Volume

The counting model favors you when documents are long and few. It works against you only if you generate many short documents — in that case, your quota is consumed by row count, not by output size.

Two conditions to check before committing:

• Is your volume row-based or page-based? If you produce a small number of very long documents, the document-based count is a clear advantage.
• Do you need API access or permanent links? Both are standard here, so you do not need to compare tiers for them.

Pricing figures and the specific monthly document limits per plan are not covered in the available material — check the pricing page for current numbers before deciding.