Why you cannot delete a template a Web Form still uses

A workspace template is a PDF plus the field marks you placed on it. Web Forms start from that template. Delete is blocked while a Web Form still uses that template. There is no separate template-count cap in this pass. That is template-delete honesty: a live /form/SLUG still needs the layout it was published from, Settings will not “force delete,” and checkout will not sell a delete that this pass does not ship.

Saving the layout is not a send — why saving a template is not an envelope. Disable versus delete on the form itself is Web Form disable versus delete. A blank layout cannot publish — why a template with zero fields cannot publish. Desk help is Docs. This guide is why the Templates row still refuses Delete after you already hid the share link.

The FAQ and reusable templates on Features keep the layout inside the workspace. Ask Inkpacket for why you cannot delete a template a Web Form still uses to open this article. Ask how templates work to open help. Those phrases stay on the product screens. This article is the public version of why Trash on /desk/templates/:id stays off until every Web Form that points at that id is gone.

What still holds the layout

• A published Web Form. The public slug copies marks from this template on every fill.
• A disabled Web Form. Disable stops new fills. The form row still references the template.
• Delete the form first, or keep the template. There is no “detach and keep the slug.”
• Members of another organization cannot see this template. The block is inside this workspace, not a cross-org lock.

Disable is the quiet close. The slug can show Form closed. That is not a template delete. Delete on the Web Form removes the form row so the template is free. Then Delete on the template can succeed. Use template still copies PDF and marks into a new draft while the form exists — that draft is not a delete. Sending that draft still counts. Free allows 5 packets a month. A blocked delete does not return HTTP 402 ENVELOPE_LIMIT. Those are different nos.

What this is not

• Not a send. Delete, or the refusal to delete, does not increment the monthly envelope cap.
• Not the published-form 402. That 402 is a second live slug on Free. This block is “a form still points here.”
• Not zero-field-publish. A template with fields can still refuse delete if a form uses it.
• Not checkout. Billing is not open. Paying a listed price does not force-delete a template a form still holds.

Place the marks once. Signature, date, text, initials, checkbox, and select — up to 80, assigned to recipient slots 1–20. A Web Form fill still creates a sent envelope from those marks. Reminders go out by email today. Text-message (SMS) is coming soon. Email still soft-fails after a fill. Text-message (SMS) is coming soon. Drive archive waits for completed. Stripe off: Payments not live. None of those flags let you delete the layout out from under a live or disabled slug. Ask Inkpacket for why you cannot delete a template a Web Form still uses to open this article.

The click-path

1. Open Web Forms. If a form lists this template, disable or delete that form first.
2. Open Templates. Delete is available when no form row still uses that id.
3. If you only needed to stop fills, disable is enough. Keep the template.
4. If delete still refuses, look for a second form on the same layout. One leftover slug is enough to block.
5. On a phone, Templates and Web Forms are drawer rows. Help is not a drawer row — it stays in the header.

API create-from-template still needs the template id. Deleting the layout after a worker stores that id is a break, not a cleanup. Fill is not send. API fill then send is that order. A blocked delete is not an Idempotency-Key conflict and not Bearer token required. It is a product rule on the Templates row. There is no separate template-count cap in this pass — you can save as many layouts as you want. You cannot trash the one a form still uses.

Ask and the block

Ask Inkpacket for why you cannot delete a template a Web Form still uses to open this article. Ask how templates work to open help. Ask how Web Forms work to open the form section. Marketing Ask stays site Q&A and deep links. It will not delete a template or a Web Form from this article. Remove the form row first.

Caps and what is not open yet

Deleting a template is not a send. A fill is. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not force-delete a template or hide the block. The FAQ and More on templates use Delete is blocked while a Web Form still uses that template in the same words.

Close the form. Then delete the layout. Open a workspace on Free — see published pricing — and try to trash a template a throwaway Web Form still uses so template-delete honesty is a blocked control you already clicked, not a Settings hunt for a force-delete that does not exist.