Save, Download, and Profile

How to use this docs page

This page is meant to answer one operational stage of the DullyPDF workflow well enough that you can run a controlled test without guessing. Read the sections below, validate the behavior against one representative document, and only then move to the next linked page.

That order matters because most setup failures come from mixing detection, mapping, fill validation, and sharing into one unstructured pass. A narrower review loop keeps troubleshooting faster and makes the template easier to trust once you save it for reuse.

Download vs save

• Download when you need a one-off generated output immediately. The workspace download menu now offers both a flat PDF and an editable PDF with fields preserved.
• Save to profile when the template will be reused or shared within your account context.
• Saved forms persist template metadata including checkbox rules, radio groups, and text transform rules.
• Fill By Link starts from a saved form or an open group because the public respondent link is tied to the owner account and saved template set.

Saved form workflow

Saved forms preserve PDF bytes and field metadata so you can re-open, re-map, and refill without re-detecting from scratch.

Saved forms are also the publication point for Fill By Link. You can publish one link for the active template or, when a group is open, publish one merged link that asks for every distinct field across that group. Respondent records stay attached to the owner account and the published template/group snapshot.

What must be saved before publishing or API use

• Fill By Link requires a saved template or open saved group because the public form belongs to that saved snapshot.
• If Rename or Map is still running after the editor opens, wait for it to finish before saving that snapshot for Fill By Link or API Fill.
• API Fill publishes one saved-template snapshot, not the unsaved working state in the editor.
• Signature workflows are safest after the template and current record state are both intentionally frozen.

Fill By Link owner flow

1. Open a saved template to publish a template link, or open a group to publish one merged group link.
2. Open your own generated public link to preview the respondent form before you send it out.
3. Share the public DullyPDF-hosted HTML form with respondents.
4. DullyPDF always requires each respondent to provide a name or ID before a submission is accepted.
5. Review stored respondent submissions in the workspace.
6. Select one respondent and run the existing Search & Fill materialization flow against the active template or group targets.
7. Download the final PDF only when it is needed.

Limits and credits

OpenAI credit usage varies by operation:

• Rename/Map formula: total credits = baseCost x ceil(pageCount / bucketSize). Default bucket size is 5 pages. Base costs: Rename=1, Remap=1, Rename+Map=2.
• Fill from Images and Documents formula: each uploaded image = 1 credit. Each uploaded PDF document = 1 credit per 5 pages (bucketed per document). The dialog footer shows estimated cost before sending.
• Base users top back up to 10 credits each month when their balance is below that floor. Premium users get a 500 monthly pool plus refill credits.
• Refill credits do not expire and are consumed after monthly credits.
• Signing uses a monthly sent-request quota. Saving a draft does not consume quota; the first successful send does.

Current default free-tier limits are 5 saved forms, 5 detect pages per PDF, 50 fillable pages per reusable upload, no active Fill By Link cap, 25 accepted Fill By Link responses per month, 1 active API endpoint, 250 successful API fills per month, 50 API pages per request, 25 sent signing requests per month, and a base OpenAI pool that tops back up to 10 each month when needed.

Current default premium-tier limits are 100 saved forms, 100 detect pages per PDF, 1,000 fillable pages per reusable upload, no active Fill By Link cap, 10,000 accepted Fill By Link responses per month, 20 active API endpoints, 10,000 successful API fills per month, 500 API pages per request, 10,000 sent signing requests per month, and a recurring 500-credit monthly pool before refill packs.

API Fill is a hosted backend runtime, not a browser-local tool. Published API endpoints are scoped to one saved template snapshot, use template-specific keys, and are governed by server-side page limits, monthly request caps, rate limits, and endpoint audit logs. Search & Fill stays local in the browser; API Fill sends the submitted record data to DullyPDF backend services.

For the marketing-facing summary of those tiers, use the public Free Features and Premium Features pages.

Stripe billing plans

Profile billing actions are backed by Stripe Checkout:

• Pro Monthly (`pro_monthly`) and Pro Yearly (`pro_yearly`) are recurring Stripe subscriptions.
• Refill 500 (`refill_500`) is a Pro-only one-time credit pack and uses backend-provided Stripe plan metadata.
• Payments are handled through Stripe Checkout for secure transaction processing.
• Canceling Pro schedules cancellation at period end; Pro access remains active until that date.
• If an account downgrades to base while holding more saved forms than the base tier allows, DullyPDF keeps the earliest-created saved forms up to the base cap accessible and marks the rest locked in place instead of deleting them. The retention dialog explains which templates remain accessible, which are locked, and how downgrade-managed Fill By Link records reopen automatically after re-upgrade.

If a user downgrades, stored refill credits stay on the account and become usable again after re-upgrading to Pro.

Replace vs new save

• Use overwrite when you intentionally replace an existing template baseline.
• Create a new saved form when testing alternate mappings or field sets.
• Run one Search & Fill verification before overwriting production templates.
• If a template already has active Fill By Link traffic, publish replacement versions intentionally so response ownership remains clear.