
An InDesign Data Merge can split a batch into several documents when a per-document limit is reached. Check Record Limit per Document for Single Record mode and Page Limit per Document for Multiple Records mode. A complete source file does not mean every record must appear in one output document.
Key Takeaways
- Record limits and page limits count different things.
- The available limit depends on the merge mode.
- Reconcile the complete output set before declaring records missing.
Identify the boundary that caused the split
Record the intended number of source records, the merge mode and the output files actually created. Do not change CSV delimiters merely because another document appeared.
Adobe's Content Placement Options reference documents both limits. Record Limit per Document is available for Single Record; Page Limit per Document is available when Records Per Document Page is Multiple Records during merging.
- Open the intended target document.
- Choose Window > Utilities > Data Merge.
- Open Content Placement Options from the panel menu.
- Inspect the limit appropriate to the selected merge mode.
- Generate a clearly identified small candidate and inventory every resulting document.
Open the target document deliberately: Adobe also describes setting defaults for future projects when all documents are closed. Confirm which scope you intend to change.
A hypothetical personalized-card batch
Suppose a producer expects one combined file but a configured limit creates additional merged documents. First locate and count the output set. The relevant question is whether the records were divided as configured or actually omitted.
For a Single Record workflow, compare the record limit with the source count. For a Multiple Records workflow, compare the page limit with the created pages. Do not interpret a page count as a record count when several records can occupy a page.
The CSV field-shift guide addresses malformed values inside records. This diagnosis concerns document segmentation after data selection, not punctuation parsing.
Accept completeness across the whole set
Use stable record identifiers to check the beginning and end of each created document. Verify that the next document continues with the intended records, with no duplicate or skipped recipient. Then inspect long and short values for layout failures.
If one document is required, revise the limit deliberately and regenerate to a new destination after considering the full batch's size. Keep the earlier output set until reconciliation is complete.
Accept when the agreed number of documents contains the intended records and the segmentation is explicit in the handoff. A successful merge operation or plausible filename count cannot replace that record-level check. This is a proposed verification workflow, not a performed merge test.
Related tasks
- Why Does a Comma in a Name Shift My InDesign Data Merge Fields?
- Why Is Text Cut Off Inside an InDesign Table Cell?
- How Do I Keep the Approved AI Image or Video from Getting Lost Among Revisions?
Sources and scope
- Adobe InDesign Content Placement Options: Record Limit per Document applies to Single Record; Page Limit per Document applies to Multiple Records; document/future-default setting scope.
Documentation-based guidance. Scenarios, worksheets and acceptance procedures are proposed or hypothetical; no hands-on test, benchmark, search-volume measurement or AI-citation ranking 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.