BlogTag
Templates
Save a PDF and its field marks once, then start the next envelope from that layout without placing fields again.
Related product pages
Guides
Bulk send for HR and sales envelopes
Send one Inkpacket template to a list of names and emails: CSV or paste, column mapping, one envelope per unique address, shared reminders, expiry, and optional access code.
Templates that reuse field layouts
Save an Inkpacket PDF and its signature, date, text, initials, checkbox, and select marks once. Start the next envelope from that workspace template — or bulk send it — without placing fields again.
Publish a Web Form from a template
Turn an Inkpacket workspace template into a public /form/SLUG. The filler does not sign in. Each submission creates an envelope and counts as one monthly envelope — Free includes 1 published Web Form at 5 packets a month.
How to place signature fields on a PDF
Place signature, date, text, initials, checkbox, and select marks on an Inkpacket PDF. Coordinates are page percentages. Suggest starting layout is a page-count heuristic, not a model that reads the file.
Bulk send vs Web Forms: which tool starts the envelope
Choose between an Inkpacket bulk job and a published Web Form: you already have the emails, or strangers start themselves. Both count toward the monthly envelope cap — Free allows 5 packets a month.
Web Form intake when you don’t have the emails
Use an Inkpacket Web Form when strangers should start the envelope: publish /form/SLUG from a template, collect name and email, and count each fill toward the monthly envelope cap — Free allows 5 packets a month.
Create an envelope from a template via the API
Mint an org-scoped Bearer token, POST /api/v1/packets with a templateId, fill known values, and send with an Idempotency-Key — one envelope toward the monthly cap. Free allows 5 packets a month.
Assign fields to each signer on one envelope
Assign signature, date, text, initials, checkbox, and select marks to recipient slots on an Inkpacket envelope so a multi-signer PDF files with the right mark in the right box.
Templates versus one-off envelopes
Choose an Inkpacket workspace template when you will send the same PDF again, or upload once when the file is unique. Bulk send and Web Forms need a saved layout; a one-off envelope does not create one.
Template field types overview
An Inkpacket template holds signature, date, text, initials, checkbox, and select marks — up to 80 — assigned to recipient slots 1–20. Select needs two options. That is field-types-overview honesty, not a model that reads the PDF.
Why saving a template is not an envelope
Saving an Inkpacket template does not count toward the monthly envelope cap. Sending the draft does. That is template-save honesty — not a hidden send, not a Free-plan tease.
Why you cannot delete a template a Web Form still uses
Inkpacket blocks template delete while a Web Form still uses that layout. Disable or delete the form first. That is template-delete honesty — not a hidden send, not a Free-plan tease.
Why a template stops at 80 fields
An Inkpacket template accepts 80 fields. An 81st mark is not a second envelope and not a plan unlock. That is field-cap honesty — not HTTP 402, not checkout.
Why a select field needs two options
An Inkpacket select field needs at least two comma-separated options. One choice is not a menu. That is select-options honesty — not a missing model, not checkout.
Why there is no template-count cap
Inkpacket has no separate template-count cap. Saving another layout is not a plan unlock. That is template-count honesty — not HTTP 402, not checkout.
Why a checkbox stamps an X
An Inkpacket checkbox stamps an X when checked. It is not a one-option select and not a plan unlock. That is checkbox-stamp honesty — not a missing model, not checkout.