Skip to main content

Bulk Fill Overview

Bulk Fill works especially well when you already have an existing fillable PDF form or another stable PDF layout and need to fill it from CSV more than once.

When the PDF already contains supported native PDF form fields, native form fill is usually the cleanest path. Overlays remain available when you need flexible placement, fixed content, or fallback coverage for fields the PDF does not provide.

If you are deciding between these methods, start with Choose the right fill method.

When Bulk Fill Is A Good Fit​

Bulk Fill works best when:

  • you have an existing fillable PDF form or a closely related family of stable PDFs
  • each output document follows the same mapped structure
  • the variable content already exists in a CSV
  • you want to preview a few rows before exporting the full set

Common examples include certificates, invoices, letters, notices, internal forms, and other repeatable business documents.

Choose The Right Fill Method​

Start with native PDF form fields when the document already has them. Use overlays when the PDF needs flexible placement, fixed content, or fallback coverage. Depending on the document, you can:

  • map CSV data into supported native PDF form fields when the PDF already has a usable AcroForm layer
  • map overlay content to CSV when you need flexible placement anywhere on the page
  • add fixed overlay content that appears on every output

Read Choose the right fill method for the full comparison, then continue to Work with native PDF forms (AcroForm) if your PDF already contains supported fillable fields.

High-Level Workflow​

  1. Prepare an existing fillable PDF form or other stable PDF layout.
  2. Choose the right fill method for that PDF.
  3. Upload your CSV data and map the changing values.
  4. Preview representative rows and validate the result.
  5. Export one preview PDF or the full batch.
  6. Reuse the validated package later through the Public API if needed.

During batch export, you can also open Custom filename (optional) and add up to 3 CSV columns to each PDF filename while keeping the existing row prefix. That makes it easier to organize downstream files without losing the stable row-based naming anchor.

If you later need the Public API, the validated editor workflow can be exported as a reusable .doqlo package for API execution. If you want no-code automation instead, you can also take that validated package into Use Doqlo with Zapier or Use Doqlo with Make or Use Doqlo with n8n.

If .doqlo is new to you, read What a .doqlo project file is before you move into reuse or API details.

How This Differs From Manual Single-File Editing​

Manual editing is for one document at a time. Bulk Fill is for one configured workflow and many rows of data. Instead of typing values directly into each output, you prepare the document once, choose the right fill method, reuse the same mappings across the whole CSV, and validate the result before export.

What Bulk Fill Does Not Try To Do​

Bulk Fill is not a full PDF editor or automatic document-understanding tool. In the current product contract:

  • PDF layouts are not analyzed or repaired automatically.
  • CSV headers are not detected automatically.
  • Every CSV row is treated as exportable data.
  • If your CSV includes a header row, you must exclude it during export.
  • Bulk Fill is not intended for arbitrary one-off document design.

Start Here​

If you want the shortest path to a first successful run, start with Quickstart. If you are still deciding how the PDF should be filled, read Choose the right fill method. If you are still preparing files, read Prepare your PDF, Work with native PDF forms (AcroForm), and Prepare your CSV before you begin mapping. If you want the basic .doqlo explanation, read What a .doqlo project file is.