Ask only the relevant questions
Show insurance questions only when a patient has coverage, or skip shipping for a digital order. The respondent sees a shorter path while the document still gets every value its branch requires.
Build interactive forms and their PDF outputs in one place. Submissions automatically generate customized, branded documents without manual exports or duplicate mapping.
Free account, no credit card
Edit any field below to watch the document preview update in real time. Submit the form to generate a finished PDF directly, without manual data re-entry.
Edit a value and see where it appears.
One template, populated and rendered as a PDF.
Generated from the submitted values without a second data-entry step.
Build the form and its output in the same visual designer. Each field has a defined place in the template, which can also render to PNG, JPEG, or WebP.
Publish a link, embed the form on your site, or connect it to an existing workflow. Prefill values you already know instead of asking for them again.
Each valid submission fills the template and renders the document. Deliver the result to storage, another tool, a webhook, or an inbox.
Collect patient intake, client onboarding, or consent and keep a PDF of exactly what was submitted and signed.
Turn an event or class registration into the ticket, confirmation, or certificate the person needs next.
Collect job, rental, and membership applications as structured data while retaining the submitted document.
Use the order details and payment result to generate the matching invoice, receipt, or confirmation.
Ask for new-hire details once, then use the answers across the documents required for onboarding.
Route an expense report or purchase request for a decision and retain the completed document with it.
A basic questionnaire still leaves payment, approval, missing answers, and delivery for someone else to resolve. Keep those decisions with the submission so the output is usable.
Show insurance questions only when a patient has coverage, or skip shipping for a digital order. The respondent sees a shorter path while the document still gets every value its branch requires.
Let someone sign in the browser with a finger or mouse and place the mark where the template defines it. A submission can also trigger one of six e-signature providers. How signing works.
Collect a deposit, booking fee, or full amount through any of 35 payment gateways. The same answers that determine the charge also fill the receipt. What you can charge for.
Route the submission to the person responsible for approving it. An approval, rejection, or returned note stays with the finished document instead of in a separate thread.
Prefill values you already know and let someone save a longer form to finish later. They spend their time on new answers rather than repeating data or restarting the form.
Search and filter the submitted values beside the document they produced. Export the records when needed, or share one submission with a colleague by link.
A simple text box cannot handle every type of input. With over 380 field types and widgets, you can collect dates, signatures, ratings, and files that map directly to their proper format in the generated PDF without manual reconfiguration.
Use short or long text, numbers, dropdowns, checkboxes, and radio choices, with input masks for fixed formats. Email verification and country-aware phone fields catch more than a generic text input can.
Ask for one date, a range, a reservation slot, or a birth date with an appropriate year picker. Calculate the gap between dates or add working days so the document receives the result, not a manual arithmetic task.
Calculate totals, scores, currency conversions, and unit conversions from earlier answers while the form is being completed. The value shown to the respondent is the one passed into the resulting document.
Collect signatures, freehand drawings, image annotations, files, images, barcode or QR scans, and generated QR codes. Give each item a defined place in the output rather than leaving it as an attachment to reconcile later.
Use star ratings, numeric scales, Likert questions, range sliders, image choices, and input tables. The feedback returns as structured values that can fill a report or feed later analysis.
Use address autocomplete, map location fields, and international telephone entry for contact data. Payment fields send the transaction through any of 35 gateways without storing the card number in the submission.
Choosing the field is only half the setup. Give its answer a place in the template and the submission can fill the document directly, without an export between the two. See how a template binds to an answer.
When payment and document generation live in separate tools, totals and customer details have to be matched again. Use the same submitted values for the charge and its invoice, receipt, or order confirmation.
Process the transaction through the gateway account you already hold. Settlement, fees, and chargebacks remain in the system your finance team uses to reconcile them.
Accept one-time sales, deposits, subscriptions, donations, ACH transfers, and buy-now, pay-later options. Authorize during submission and capture after approval when the workflow requires it.
Apply coupons, timed promotions, answer-dependent shipping, and regional tax rules. Pass the calculated amount into the document so its total matches the payment.
Use sandbox mode to run the form, transaction, and resulting document end to end. Card details are tokenized rather than stored, with PCI DSS handling on the collection path.
Collect intake and consent before the appointment, add the browser signature, and file the resulting PDF with its submission. The record stays connected to the answers instead of becoming another inbox attachment.
Gather new-hire details once and use them in the offer letter, tax form, and equipment sheet. A start date or address does not need to be typed separately into every document.
Route expense claims and purchase requests to an approver, then retain the decision with the filed document. The approval history remains part of the record being reviewed.
Turn course registration and completion data into a certificate with the learner's name, date, and completed hours. The template can render when the completion event arrives.
A separate form tool and document generator need an export or automation layer between them. Each field change then has to be repeated in the mapping before the output can use it.
Here the form and document use the same template model and designer. Change the field and its destination together, then render the PDF through the same browser-based output path as the rest of the platform.
Build the form and document side by side, visually or in HTML when code gives finer control.
Keep forms, templates, and outputs in workspaces with roles and administration.
Use webhooks, storage, schedules, connectors, and the API without copying the design elsewhere.
Build the form and its output document in the same editor, then publish the form. Each submission fills the document template and produces a PDF without an export or a second mapping step. Plans start at $9 a month for 1,000 documents.
No. Forms use the same visual designer as documents. When code is useful, developers can work with the underlying HTML, the REST API, and the eight official SDKs.
Forms that need to leave behind a document are the clearest fit: intake and consent, registrations, applications, orders, and approvals. The submitted values fill the PDF template directly.
No. Anonymous respondents are nonbillable: someone completing your form is never a seat. Seats are for people who build forms or administer the account, so an intake form with 2,000 submissions uses the same number of seats as one with 20. You pay for the plan and the documents produced.
No. Payment volume does not count as a user or move the form to another tier on that basis. The transaction runs through your own gateway account, with 35 supported gateways available.
Yes. Workspaces keep forms, templates, and generated documents with the team rather than in one person’s account. Roles and administration control who can build, change, and manage them.
The document it produces. One finished PDF counts as one render, so 40 submissions a week is roughly 170 renders a month. Producing one copy for the submitter and another for your records doubles that number. The free account includes 50 renders with no card; the entry plan is $9 a month for 1,000.
Yes. Forms can output fillable PDFs where select fields remain interactive instead of being flattened. This is ideal when you collect initial answers and need a client or partner to complete the rest.
Yes. Upload the PDF you already use, review the detected fields, and correct any that need attention. The familiar layout remains the output, which matters for regulator-issued and client-issued forms. It can then be filled online, routed, signed, and returned like another form workflow.
Send it by email, store it in cloud buckets like S3, or route it through 732 connectors with 727 automated actions to update your CRM, cloud drive, and inbox in one step.
Set a fallback for each optional field in the designer. When someone skips an answer, the document uses that fallback instead of leaving an unexplained gap. Required-field validation catches an incomplete submission before the document is produced.
Much more than text values. You can use conditional logic in the template so user answers dynamically show or hide sections, adjust page breaks, apply specific styling, or set custom document names.
Try the first question below. A business sees the seat question while an individual skips it; the total changes and the matching clause appears in the document preview on the right.
Clause 7 is omitted for an individual license, which is not transferable.
Skip logic, conditional sections, jumps, and calculations control both what the respondent sees and what the document contains. The chosen branch reaches the template directly rather than being interpreted again by a separate document system.
This matters when a branch changes price, terms, or required questions: a quote for 3 seats versus 25, a consent clause that varies by jurisdiction, or contractor questions an employee never sees. Each completed document counts as one render regardless of its branch.
A form should fit the way respondents encounter the workflow. Once it is built, share it by link, embed it, prefill it, or open it only for the period and capacity you allow.
Embed the form inline or open it in a lightbox over your content. Advanced embedding controls sizing and scrolling when the standard inline layout does not fit the page.
Customize the form URL, or turn the same destination into a QR code for a poster, table card, or printed pack. Both routes open the same published form.
Pass known values into the form so the respondent can confirm or correct them instead of typing them again. The submitted values still flow into the same fields in the document.
Connect one of 35 payment gateways to collect a deposit or balance during submission. The amount can follow the same conditions and calculations as the rest of the form.
Trigger one of 6 e-signature providers when a counterparty needs that process, or collect a browser signature directly in the form when the workflow does not require a provider.
Enable or disable the form, cap its submissions, and choose where visitors go after it closes. A registration can stop accepting entries when it reaches capacity.
Collection is not complete when the submit button is pressed. Validate the answers, render the document, and deliver the result to every destination the workflow needs.
A submission remains a record after its document is sent. Make it searchable, retain it for the period the form requires, and measure its source. Anonymous respondents never count as seats, so submission volume does not increase the number of internal users.
Filter by field, date, or status. The sent record shows what was delivered and to whom, so the answer does not depend on searching an inbox or another delivery tool.
Delete submissions automatically after a period such as 30 days or 7 years. A signed consent record and a competition entry can use different retention rules because the period is set per form.
Use UTM tracking and form analytics to connect a submission with the campaign that produced it, rather than losing acquisition context at the end of the form.
You get hosted forms and submission-to-document on Starter, from $9 a month for 1,000 renders. This is the cheapest paid plan, so letting somebody else fill the document in is not what you upgrade for. The free account needs no card. See what each plan includes.
Create a free account, connect the answers to a template, and render the resulting PDF.
No credit card required.
Trusted by teams at