You start with a template and mark the variable parts with {{placeholder}} tokens, for example {{name}}, {{event}} or {{id}}. Then you supply the data: paste a CSV whose first row is the header of field names and where every following row is one document’s values, or switch to the editable table and type the same thing. The tool scans the template for tokens, lists the detected fields, and highlights in amber any token that does not match a column. For each data row it replaces the tokens with that row’s values to build a finished document, and the live preview lets you page through the results one at a time so you can check the merge before generating in bulk.

There are three bundles. A ZIP contains one file per data row in your chosen format — plain text (.txt), Markdown (.md), or styled HTML (.html), where Markdown is rendered to a clean, self-contained HTML document. Filenames come from a pattern you control, using any {{field}} plus {{_index}} for the row number; illegal characters are stripped and any clashes get -2, -3 and so on. A combined text file concatenates every document with clear separators into a single download. A combined PDF lays out each merged document as its own paginated section. All three are assembled on your device with lazily-loaded libraries, so the export still involves no upload.

The Bulk Document Generator is 100% client-side. The template you write, the data you paste, the merge itself and the ZIP, combined file and PDF are all built in the page — there is no server round-trip and no CDN, and not a single name, address or row is sent anywhere. That makes it suitable for sensitive mail-merge such as payroll letters, medical or legal notices and customer lists that cannot be put through a cloud document service. Close the tab and nothing is kept; the tool works offline once cached.

Matching between template tokens and data fields is case-insensitive, so {{First Name}} finds a “First Name” column. Any token that has no matching column is highlighted in amber in the detected-fields list, called out in a warning, and intentionally left in the merged document as {{token}} so it is obvious in the preview instead of producing a blank. Always review the merged preview and page through a few rows before generating in bulk, and for rich formatting write the template in Markdown and export HTML, which is rendered with a clean stylesheet.