
The instructions describe two different workflows. Native Bulk create supports up to 249 variations using a spreadsheet you prepare. The Bulk Create and Generate add-on documents up to 99 variations and requires its own generated CSV template. Choose the route before building the data file.
Identify the interface in front of you
Check whether you entered Bulk create from Edit page or opened Bulk Create and Generate through Add-ons. Similar names do not make their CSV setup interchangeable.
Imagine a hypothetical local-events organizer preparing 120 venue cards. A tutorial for the add-on suggests a 99-variation ceiling, while the organizer sees a native Bulk create panel. Splitting the job immediately is unnecessary until the actual route and its requirements are identified.
Adobe documents native Bulk create and the Bulk Create and Generate add-on separately. Neither documented ceiling guarantees that a poorly mapped dataset will create usable pages.
Prepare data for the chosen route
For native Bulk create, create spreadsheet headers for changing text or visual elements and a row for each variation, then save CSV. Upload it from Edit page, Bulk create. Connect each selected element to the corresponding column and inspect Manage & preview before Create pages.
For the add-on, generate and download its CSV template first. Adobe explicitly says it does not provide a way to manually set up that template and upload an arbitrary existing CSV. Fill the supplied structure rather than forcing a native-workflow sheet into it.
Do not change linked placeholder strings casually after configuring the add-on. A Photoshop dataset header mismatch is another example of a data binding breaking when its identifiers no longer match, although its file format differs.
Pilot a meaningful sample
Before creating the full venue set, use a few rows containing a long location name, punctuation, an absent optional value and representative images. Confirm that the connected element receives the intended column.
Check the first, last and exceptional rows. A successful page-generation action does not prove that all images match their captions. Retain the clean template and dataset independently, following the same principle as preserving a Photoshop template during dataset export.
Accept the batch by records
For the 120-card scenario, acceptance means the chosen route supports the planned count, every source record maps to the expected page and the demanding rows remain legible. Keep a record-to-page checklist.
If the intended workflow cannot accommodate the full job, divide it into named batches without duplicating or skipping records. InDesign Data Merge's record and document boundaries also need explicit batch accounting.
When an import fails, verify the interface and CSV origin before rewriting the whole spreadsheet. Report generation and visual quality separately; the documented maximum is a capacity boundary, not a quality score.
Related tasks
- Photoshop Variable Data Sets Fail: Match the File to the Template
- Apply Data Set or Export Data Sets as Files? Preserve Your Photoshop Template
- Why Did My InDesign Data Merge Split the Batch into Several Documents?
Sources and scope
- Adobe: Create designs in bulk: Native Bulk create uses manually prepared CSV, explicit element-column connection and up to 249 variations.
- Adobe: Bulk create and generate designs using add-on: Add-on-generated CSV template, up to 99 variations and automatic foreground/background image layer order.
Documentation-based guidance. Examples are hypothetical and acceptance checks are proposed; no installed-application test is claimed.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. This is documentation-based guidance with proposed examples, not a claim of hands-on testing or an independent product review. Report a correction.
Cover: AI-generated conceptual editorial illustration; not a real application screenshot, observed output or before-and-after test.