Gravity Forms
+ Document Packet

The Gravity Forms Document Packet add-on turns a form entry and the files people upload with it into one tidy, combined PDF. It starts the packet with the entry's own generated summary (from our built-in template, or any file you map), then appends the entry's uploaded files in the order you choose — uploaded PDFs are added page-for-page, and images (JPG, PNG, WEBP and HEIC) are placed one per page, scaled to fit. The result is a single document you can file, email or print, instead of a form entry plus a scattering of separate attachments.

Build the packet automatically when the form is submitted, on demand from a Build packet button on the entry, or for many entries at once with a bulk action on the entries list. Shape it with an optional cover page (with a title and sub-title built from merge tags), a table of contents, a PDF bookmark (outline) for each source document, and page numbering that runs across the whole packet — then name the file with a pattern such as {form_title}-entry-{entry_id}. This is the piece that Gravity PDF and the other PDF add-ons leave out: they render a PDF from the entry's data, but they do not fold the entry's uploaded files into the same document.

Deliver the finished packet however suits your workflow: attach it to any Gravity Forms notification, keep it on the entry in a protected folder reachable only through a secure, expiring download link (available as a {packet_link} merge tag), and add a Download packet button and column to the entries list. Modern scanner and Office PDFs that use object streams are read with a bundled, GPL-compatible engine, and a file that cannot be read — encrypted, damaged or unsupported — is never silently dropped: it is skipped with a visible notice on the entry, or it fails the packet with a clear message, exactly as you choose. Every page is assembled on your own server: no third-party document service and no outside connection. For Gravity Forms 2.9 and newer.

When a packet is built, the add-on gathers the entry's sources in order: first the generated document (our template renders an entry summary as a PDF, or you map one of the entry's uploaded files), then each uploaded file from the fields you selected. It opens the writer — FPDI on the TCPDF backend — and appends every source into one document: uploaded PDFs are imported page-for-page, and images are drawn one per page and scaled to the page. If you turned them on, it adds a cover page, a table of contents, a bookmark for each source and page numbers across the whole packet, then writes the file with your name pattern into a protected folder under uploads that is closed to direct web access. A modern PDF that uses object streams or cross-reference streams (as scanners and Office apps produce) is read through a bundled, GPL-compatible engine; a file that still cannot be read is never dropped in silence — the add-on records a visible notice on the entry, or fails the packet with a clear message, according to your setting. Delivery is on your terms: the packet can be attached to a notification, downloaded from the entry or the entries list by a user with permission, or reached through a signed, time-limited {packet_link}. All of this happens on your own server — the add-on makes no outside HTTP request beyond the licence and update checks.