Fill Flat PDFs with Overlay Fields

Some PDFs look like forms but do not contain usable fillable fields. They may be scanned, flattened, printed from another system, or exported as a static layout. Doqlo can still fill these PDFs when the layout is stable by placing overlay fields on top of the page.

In Doqlo Bulk Fill, overlay fields let you map CSV columns to visual positions on the PDF. Each CSV row can then produce one completed PDF using the same stable layout.

What is a flat PDF?

A flat PDF is a PDF whose visible content exists on the page, but the file does not expose usable interactive form fields. It may still look exactly like a form, but clicking on the page does not reveal fields that a PDF form tool can fill.

This often happens when a document was printed to PDF, scanned, flattened after someone else filled it, exported from another business system, or created from a design file. The page is visible and stable, but the form layer is missing, removed, or not useful for the workflow.

That is different from a supported AcroForm PDF. In a supported native AcroForm, the PDF already contains form fields such as text boxes, checkboxes, single-select dropdowns, or radio groups that Doqlo can map to CSV columns. A flat PDF does not provide that usable field structure.

XFA is a separate compatibility issue. Some XFA PDFs may look like fillable forms, but they are not the same as supported non-XFA AcroForm PDFs. If an XFA document is flattened into a stable layout, it may fit an overlay workflow, but Doqlo does not turn XFA into a native AcroForm workflow.

When overlay fields are useful

Overlay fields are useful when the PDF layout is stable and the same positions should be filled for every row. Instead of relying on a native form layer, you place text visually where it should appear.

This is a good fit when:

• the PDF looks like a form but does not have usable native fields
• the same boxes or blank spaces should be filled for every output
• the values come from CSV rows
• you need to place text on top of fixed areas
• the form is visually clear but technically flat
• the workflow needs repeated outputs from the same layout

Common examples include certificates, HR forms, training documents, internal forms, labels, fixed-layout notices, simple packing slips, forms exported from another system, and PDFs where fields were flattened before delivery.

Overlay filling is not the right answer for every PDF. It works best when the page layout is predictable. If different records need different pages, different sections, or row-specific layout changes, prepare separate workflows or make the source layout stable first.

How overlay fields work in Doqlo

The overlay workflow starts with the PDF and the CSV. The PDF supplies the fixed visual layout. The CSV supplies the changing values.

In Doqlo Bulk Fill:

1. Upload the PDF.
2. Upload the CSV.
3. Add overlay fields where text should appear on the PDF.
4. Map each overlay field to the right CSV column.
5. Preview representative rows.
6. Export a test PDF.
7. Export the full batch when the output looks correct.

During preview and export, Doqlo draws the row value at the chosen location. The underlying PDF layout stays the same. The changing values come from the selected CSV row.

Overlay fields are visual placement fields. They do not turn the original PDF into a native AcroForm form. They also do not rebuild the PDF's form structure or add native interactive fields for later editing in another PDF form tool.

Prepare the PDF and spreadsheet data

Start with a PDF that should stay the same for every output. A clean, readable PDF is easier to align than a tilted, blurry, or inconsistent scan.

Before uploading the PDF, check that the same field positions apply to every completed file. If one group of rows needs a different layout, use a separate PDF or a separate Bulk Fill workflow for that group.

Prepare the data in the spreadsheet tool your team already uses, then export the final table as CSV before uploading it to Doqlo. The data may be prepared in Excel, Google Sheets, Airtable, an internal system, or another table tool, but CSV is the upload format for this workflow.

Use one row per output PDF and one column per value. Keep the column order stable after mapping. Format dates, names, IDs, amounts, addresses, and other values before upload.

Place and map overlay fields

After the PDF and CSV are loaded, add overlay fields where text should appear. Place each field carefully on the page, then map it to the CSV column that should supply the value.

Work slowly at first. A small placement error can repeat across every exported PDF, so check alignment before running a large batch.

Long values are the common stress test. Names, addresses, descriptions, IDs, and amounts can be wider than the first row suggests. If long values overlap existing text or run outside the intended area, adjust the placement or prepare shorter source values before exporting the full batch.

Blank values should also be reviewed. A blank may be correct for some rows, but it can also indicate a missing CSV value or a field mapped to the wrong column.

Preview rows before exporting

Preview is the main safety step for overlay-based filling. Do not preview only the first row. Choose rows that represent normal data and edge cases.

Check rows with:

• long names
• long addresses
• dates
• IDs or reference numbers
• amounts
• blank values
• values near the end of the CSV

Look for alignment, spacing, and overlap. Confirm values land on the intended page and do not cover labels, lines, or existing text in a way that makes the output hard to read.

Export a test PDF before the full batch. Open it like a reviewer, recipient, or downstream system would. The test PDF is the last low-cost place to catch a layout or mapping issue.

Export completed PDFs

After preview and test export look correct, export the batch. Each selected CSV row can produce one completed PDF using the same flat PDF layout.

For batch output, Doqlo delivers the completed PDFs as an export package. Smaller exports usually start as a direct download. Larger exports may use a time-limited download link. In either case, spot-check several completed PDFs before sending files onward or importing them into another process.

If your CSV includes a header row, decide whether it should be setup-only or part of the final output.

Native fields vs overlay fields

Native AcroForm filling and overlay filling solve related but different problems.

Native AcroForm filling writes values into existing supported PDF fields. It is usually best when the PDF already has supported non-XFA fields and those fields match the data you need to fill.

Overlay filling visually places values on top of a stable PDF layout. It is useful when the PDF is flat, when the original fields are missing, or when the PDF does not provide a field in the place you need.

Some workflows can use both. A supported native form may handle the main fields, while overlay fields add row-specific text in places the original PDF did not include.

Common use cases

Overlay fields are most useful for repeated documents with stable visual layouts, such as:

• flat HR forms
• certificates
• training forms
• internal approval documents
• static notices and letters
• fixed-layout labels
• simple packing slips
• forms exported from other systems
• PDFs where fields were flattened before delivery

The shared pattern is simple: the PDF layout stays fixed, and the row data changes.

Limitations

Overlay fields require a stable layout. If the form structure changes for different rows, prepare separate workflows or stabilize the layout first.

Overlay fields place values visually. They do not create native PDF form fields, rebuild a missing form layer, or make the original PDF behave like a supported AcroForm.

Overlay fields do not find every place that should be filled for you. You choose the placement, map the CSV columns, and review the output.

If the PDF is scanned or low-quality, visual alignment may be harder. A cleaner source PDF usually gives better results.

If the PDF is XFA, it may need to be flattened or prepared before it fits an overlay workflow. Doqlo native form mapping is scoped to supported non-XFA AcroForm PDFs.

Overlay fields are not a redaction tool. Overlay fields do not remove or rewrite the underlying PDF content. They place values on top of the existing page.

Always preview representative rows and export a test PDF before running the full batch.

Next steps

If your PDF is flat but the layout is stable, start with a small Bulk Fill test. Upload the PDF, upload the CSV, place a few overlay fields, preview representative rows, and export a test PDF before running the full batch.

For related workflows, read Fill PDF Forms from Excel or CSV, PDF Mail Merge, and the Bulk Fill Overview.