What file formats does DocuGenerate support for templates and data?

Updated

DocuGenerate accepts DOCX, DOC, ODT, TXT, or SQL files as templates, and JSON, XLSX, XLS, ODS, or CSV files as data. You upload a Word-style template containing merge tags, supply the matching data, and DocuGenerate produces one PDF document per data item by replacing each tag with its value. This applies across the web app, no-code integrations, and the REST API.

Template formats

Format Notes
DOCX Standard Word format, the most common choice
DOC Legacy Word format
ODT OpenDocument text
TXT Plain text
SQL Accepted as a template input

Templates are ordinary files you own and can download at any time. You design them in the document editor you already use rather than a proprietary builder.

Data formats

Format Notes
JSON Typical for API and developer workflows
XLSX Excel workbook
XLS Legacy Excel format
ODS OpenDocument spreadsheet
CSV Plain comma-separated values

Each row or data item in the file generates one document. A 100-page output still counts as a single document, because DocuGenerate counts documents rather than pages.

How tags and delimiters work

  1. Prepare the template — insert tags where dynamic text should appear, for example [Name].
  2. Upload the template — merge tags are detected automatically from the template content, so you don't declare them manually.
  3. Adjust delimiters if needed — you can switch from [Name] to a custom style such as «Name» or {Name}.
  4. Provide the data — upload an Excel/CSV/ODS file or send JSON.
  5. Generate — each data item produces a PDF with tags replaced by actual values.

Tags aren't limited to plain text: images, tables, lists, conditions, and QR codes can all be driven by merge tags.

Practical notes

  • Matching formats: your data file and template are independent — you can pair a DOCX template with CSV data, or an ODT template with JSON.
  • Delimiter conflicts: if your template text legitimately contains square brackets, switch to a custom delimiter to avoid false tag detection.
  • Choosing a data format: CSV and XLSX suit manual, spreadsheet-driven runs; JSON fits API and integration pipelines where data comes from another system.

For current plan limits and pricing, check the pricing page, since generation allowances are tied to your plan rather than to file format.