Jotform — the form builder, its free tier and where the limits bite

• Jotform

  This page

  PricingRival leads

  • Free Starter plan with the standard feature set and low submission and storage ceilings
  • Paid tiers named Bronze, Silver and Gold that raise those ceilings rather than unlocking the builder
  • Enterprise is a quote, with dedicated support and custom limits
  • Nonprofit and education discounts, plus a money-back window on paid plans

• Google Forms

  PricingRival leads

  • Free with a personal account, included in the same workspace as the rest of the suite
  • No paid form tier at all for individuals
  • Business and enterprise pricing applies to the wider workspace, not to the forms feature
  • No separate form subscription to evaluate, which is the entire argument for it

• Typeform

  PricingRival leads

  • Free plan with a monthly response cap and branding on the form
  • Paid tiers named Basic, Plus and Business that raise the cap and remove branding
  • Higher tiers add logic, integrations, team seats and custom domains
  • Priced per month on annual billing, with a seat-based business tier

• Tally

  PricingRival leads

  • Free plan with unlimited forms and submissions, which is unusual in this group
  • Pro and Business tiers raise the per-form submission and upload limits
  • Paid tiers add custom domains, file uploads, team workspaces and integrations
  • No charge for the builder itself or for the number of forms you create

1. Jotform — official site
2. Jotform — pricing
3. Jotform — form templates
4. Jotform — integrations
5. Jotform — terms of use
6. Google Forms — official site
7. Typeform — official site
8. Tally — official site

Free tier

Yes

Pricing summary

The thing to understand before comparing prices is that Jotform's free plan is not a demo of a reduced product. The Starter plan carries the standard feature set — templates, conditional logic, payment fields, widgets, integrations — and the paid tiers differ mainly in how many submissions you can receive and how much you can store. That is a gating model rather than a feature ladder, and it has an important consequence for anyone budgeting: the question that decides your plan is not "does it do X" but "how many responses does this form take in a month". Submissions, storage, upload space and monthly form-view allowances all scale up the ladder and are the numbers to compare against your own traffic before you choose — they are also the numbers most likely to be revised, which is why this page describes the shape of the tiers rather than quoting the ceilings. Above the self-serve tiers sits Enterprise, sold as a quote with the controls a security review tends to ask for, and there are standing nonprofit and education discounts worth checking before you pay list price, along with a money-back window on paid plans. Two further costs belong in the arithmetic. The first is that anything regulated — payments, signatures, sensitive intake — may push you up a tier or into Enterprise sooner than submission volume alone would suggest. The second is the opposite risk: a lot of teams buy a mid-tier plan to get headroom they never use, when a plain free builder would have carried the same forms for nothing. Current tier names, ceilings and discount terms belong on the official pricing page.

Reviewed on 19 September 2026 · Jotform — pricing

• A drag-and-drop builder with a very large template library

  Building a form is the least interesting part of the product and it works the way you expect: drag fields, configure them, publish a link or an embed. The library is the differentiator — thousands of ready-made forms for registrations, orders, bookings and internal requests mean most people start from something that already has the fields right rather than from an empty page.

• Payments collected inside the form

  Payments are native rather than bolted on through an integration: you connect a processor and the form becomes a checkout, with the totals, tax fields and confirmation handled in the same flow. That single capability is what moves a lot of users off a free builder, because the alternative is a form that collects intent and a separate invoice process to actually get paid.

• Conditional logic, calculations and multi-page flows

  Fields can appear or disappear based on earlier answers, values can be calculated, and long forms can be split into steps with progress shown. This is table stakes for a paid builder and it is the point where a simple free tool stops being enough: the moment a form needs to behave differently for different people, you are in this tier of product.

• Signatures and document workflows

  Jotform Sign and the PDF tooling let a submission become a document that gets signed, tracked and filed — including Smart PDF Forms, which turns an existing PDF into a fillable form rather than asking you to rebuild it as a web form. If your intake ends in a signature, this is the feature that removes a whole separate e-signature subscription.

• Data that lives somewhere after it arrives

  Submissions can land in a spreadsheet view, a table, a structured inbox or a board, and reports can be built on top. This is the difference between a form tool and an intake system: the data stays workable inside the product instead of existing only as rows someone has to process by hand.

• Compliance-oriented forms and controls

  The product has carried HIPAA-friendly forms, encryption options, access controls and GDPR tooling for years, plus data-residency options on higher tiers. For anyone collecting health, financial or otherwise regulated information, this is the reason a general-purpose free builder is not an option, regardless of price.

• Assignments, approvals and workflow routing

  Submissions can be assigned to people, moved through approval steps and tracked, which turns a form into a lightweight process engine. It is deliberately less powerful than a dedicated workflow product, and for the common case — a request that needs one approver and a record — that is exactly the right size.

• A very large integration surface

  Hundreds of connectors cover CRM, storage, payments, email marketing and automation platforms, so the intake can push into the systems that already run the business. The practical advice is to wire up as few as necessary: every connection is another place the submission can silently fail, and the product's own inbox and tables are often enough on their own.

1. 1

   Map the submission’s destination before you build the form

   The single most useful decision happens before a single field is dragged: where does the answer go when it arrives? If it ends in a spreadsheet, you may not need this product at all. If it ends in a payment, a signature, an approval or a filing obligation, that destination determines which features you configure — and choosing the plan first and the destination second is how teams end up paying for a tier to solve a problem they created in the builder.

2. 2

   Start from a template that already has the field set right

   The library is the fastest path to a competent form. Pick the closest template and delete what you do not need rather than building the field list from scratch; the templates encode conventions — the right fields for a booking, a job application, a supplier request — that are easy to get subtly wrong when you design from a blank page.

3. 3

   Test the flow as a stranger, on a phone, twice

   Send yourself the live link and complete it as a first-time visitor would, including a payment if the form takes one, then check the whole path to the destination — the table row, the notification email, the PDF, the signature request. Most failures in form projects are not in the form: they are in the connection between the form and whatever was supposed to happen next, and they are only visible when you follow the whole chain.

4. 4

   Use conditional logic to shorten the form rather than to show off

   The right use of branching is to remove questions a respondent should never see — the section about shipping that only appears for physical orders. It is tempting to build elaborate multi-path forms; the forms that convert are the short ones, and every branch you add is another path to test after every edit.

5. 5

   Watch the submission count from week one, not at the ceiling

   Because the paid tiers are drawn by submissions and storage, the cost of a successful form arrives quietly. Track the rate rather than the total: a form that takes a few hundred entries a month is comfortably free, and the same form on a launch week is not. Knowing that in advance turns an upgrade into a planned decision instead of an interruption to a live campaign.

6. 6

   Restrict the account before you collect anything sensitive

   If the form touches health, financial or identity data, the compliance features are only useful if they are configured — encryption, access controls and who can see what. Doing that after intake begins is a much harder problem than doing it before, and it is also the point at which it becomes worth checking whether the tier you are on actually includes the controls you assumed you had.

• Operations teams running an intake process

  The natural buyer is the person who owns a process nobody calls software: supplier onboarding, facilities requests, expense submissions, event registrations with payment. They need a form, but what they really need is for the submission to become a tracked item with an owner and an outcome, and they do not want to commission a developer to get it.

• Small businesses whose forms have to take money

  Bookings, deposits, orders, class sign-ups — the moment payment is part of the form, a free builder stops being an option and a checkout becomes necessary. Being able to collect payment, confirm it and issue a document from one submission is a materially shorter process than stitching a form, a processor and an invoice together.

• Organisations with a compliance obligation on intake

  Clinics, schools, legal teams, HR departments and anyone handling regulated data need a vendor who can describe their controls. Jotform has built the paperwork for that over years, so it is often the answer that passes a review that a cheaper competitor would not survive — which matters more than the subscription difference between them.

• Teams replacing several disconnected small tools

  A form tool, an e-signature subscription, a PDF filler and a spreadsheet that acts as a case tracker is a common stack in a growing company. Consolidating into one product is not always the right call, but when the same vendor covers all four and the data stays joined up, the comparison is usually decided by the subscription maths rather than by features.

• Nonprofits and schools with a discount and a small budget

  The standing nonprofit and education discounts change the arithmetic considerably for exactly the organisations that need the most capable free tier. Registration forms, volunteer sign-ups, permission slips and applications are all standard intakes here, and the templates mean a small team can ship them without design help.

A hosted platform across many sub-products

Forms, apps, tables, inbox, boards, report builder, workflows, PDF tooling, signing and AI agents all live under one account, and the branding for several of them is separate from the core product. Know which one you are paying for: a plan decision made for forms can look different once the adjacent products are in the picture.

Metered by submissions and storage rather than by features

The paid tiers are drawn by monthly submissions, storage, upload space and form views, not by access to the builder. Those limits are the numbers that decide your bill, they are the numbers most likely to change, and they are deliberately not quoted here — check the official pricing page against your own expected volume before buying a tier.

Compliance features that vary by tier and configuration

HIPAA-friendly forms, encryption options, GDPR tooling, access controls, SSO, audit logs and data residency exist across the product, but availability and the surrounding paperwork differ between plans and between regions. The contracts matter more than the feature names: verify the current posture in the terms and any signed agreement before sending regulated data anywhere.

Where your data lives and who can reach it

Every submission is stored on Jotform's infrastructure, and the answers are only as private as the sharing settings on the form, the table and the account. It is worth reviewing who on the team can see the responses and export them — the common leak in a form project is not an attacker but a share link that was left open.

What it does not do

It is not an application backend: there is no general API-driven data model to build your own product on, and the forms are hosted rather than part of your codebase. It is not a full marketing automation platform, not a CRM, and not an enterprise workflow engine — it covers the intake end of each of those jobs and integrates outwards for the rest.

An established vendor with a large product surface

Jotform is a long-running, privately held company with tens of millions of users, which is the opposite of an early-stage risk profile: the product will not disappear, and it will also not change direction quickly. The practical consequence for a buyer is that the stable facts are the ones being purchased — a very large feature surface and a long track record — while tier limits and add-on pricing are the moving parts.