The Jotform free plan is called Starter, and it is unusually complete as free tiers go. Every standard feature is in it: the templates, the conditional logic, the payment integrations, the widgets. What is restricted is not what the forms can do. It is how much they can do it, and the restriction is expressed through several separate counters that reset on different schedules and behave differently when they fill up.
That structure is what makes the free plan hard to reason about. A single cap is easy to plan around. Five caps, two of which measure things that sound identical, are not. What follows is each counter, what it counts, and which one a given team is most likely to meet first, using the figures published on the Jotform pricing page as of September 2026.
The numbers on the Starter plan
| Counter | Starter (free) | Resets |
|---|---|---|
| Forms | 5 | Not a counter, a live cap |
| Submissions | 100 per month | Monthly |
| Total submission storage | 500 | Never, until purged |
| Upload space | 100MB | Never, until purged |
| Monthly form views | 10,000 | Monthly |
| Fields per form | 100 | Per form |
| Payment submissions | 10 per month | Monthly |
| Signed documents | 10 per month | Monthly |
| Jotform branding on forms | Present | Removed on paid plans |
Two things are worth noticing immediately. The first is that there is no time limit. Starter is not a trial and does not expire, which is a meaningful difference from tools that give thirty days and then stop. The second is that the two most important numbers, 100 and 500, measure different things and are easy to confuse.
Forms: five, and the cap is on active forms
The form limit counts forms that are live on the account rather than forms created over time. Five is enough for a small team with a stable set of intake points: one contact form, one application form, one event sign up, and two spare. It runs out quickly for anyone who creates a form per event, per campaign or per client, which is a common pattern and the reason some teams hit this cap before any of the volume caps.
Monthly submissions and total storage are two different limits
This is the distinction that catches people out, so it is worth stating plainly.
Submissions is a flow measurement. It counts responses received in a calendar month and resets to zero at the start of the next one. On Starter that number is 100.
Total submission storage is a stock measurement. It counts responses currently held on the account, across all forms and all time. On Starter that number is 500. It does not reset. It only goes down when submissions are deleted and then purged.
A team receiving 80 responses a month never touches the monthly cap. It reaches the storage cap in the seventh month anyway, because 80 a month accumulates. The monthly number is what most people check and the total is what actually arrives first for any steady, low volume use.
What happens when the storage limit fills
This part deserves attention because the behaviour is not a block. According to the pricing page, when the total submission storage limit is exceeded, the system deletes the oldest form response to make room for new submissions.
The practical consequence is that the failure is silent and destructive rather than loud and safe. A monthly submission cap stops new responses from arriving, which is disruptive but visible. A storage cap that discards the oldest record removes data that nobody is looking at, which means it can run for months before anyone notices that last spring's applications are gone. The page notes that warnings are sent by email and shown on the dashboard when a usage limit is reached, so the signal exists. It has to be read.
For any form whose responses have a retention requirement, applications, complaints, consent records, a plan that deletes oldest first is a plan that needs an export routine attached to it.
Which limit a given team hits first
The order is fairly predictable once the shape of the use is known.
A single busy form. An event registration or a campaign landing page taking 400 sign ups in a fortnight hits the 100 per month submission cap in the first few days. The monthly reset does not help, because the event does not wait for the first of the month.
Steady low volume. A contact form receiving 30 to 60 enquiries a month never troubles the monthly cap and hits the 500 total storage cap somewhere between month nine and month seventeen, quietly.
Many small forms. A team that spins up a form per project or per client hits the five form cap long before either volume number, and the workaround, deleting old forms, takes their responses with them.
Anything with file uploads. 100MB is the entire upload allowance for the account, not per form. A recruitment form collecting CVs as PDFs, at roughly 200KB each, has room for around 500 files in theory and far fewer in practice once anyone attaches a portfolio or a scanned document. Photographs exhaust it almost immediately.
Payment or signature work. 10 payment submissions and 10 signed documents a month are demonstration quantities rather than operating quantities.
The counters that rarely bind
Two of the numbers on the list almost never cause trouble, and knowing that saves time when diagnosing which limit has actually been reached.
Monthly form views is set at 10,000 on Starter. A form view is counted each time the form is loaded account wide, so it includes people who opened the page and left. Ten thousand views against a hundred allowed submissions means the view limit only binds if the form is being seen by roughly a hundred times more people than complete it, which happens on public landing pages and essentially nowhere else. For an intake form sent by link to a known audience, this counter is not the one to worry about.
Fields per form is set at 100 on Starter. A hundred elements on a single form is a very long form by any standard, and a form that long has a completion problem well before it has a plan problem. This limit tends to matter only for tools being used as data entry front ends for internal staff, where nobody abandons partway through because filling it in is the job.
Staying inside the free plan deliberately
For teams that genuinely fit the shape, Starter can be run indefinitely rather than treated as a staging post. Doing that well takes two habits.
The first is a regular export. Downloading responses and then purging them is what keeps the 500 total storage counter from becoming the binding constraint, and it converts a plan that silently deletes oldest first into a plan that behaves predictably. The pricing page describes deleting and purging entries as the way to free both submission storage and upload space, so the same routine addresses the 100MB allowance.
The second is keeping file uploads off the form where possible. Uploads consume the scarcest allowance on the plan by a wide margin, and asking respondents to send documents by another route, or collecting them at a later stage from a smaller group, keeps the account well clear of the one limit that fills fastest.
Neither habit is free. Both cost somebody an hour a month, which is the real comparison against a paid tier rather than the price difference alone.
The limit that is not a number
Starter forms carry Jotform branding, which the pricing page confirms is removed once an account is on a paid plan. Whether that matters depends entirely on the audience. For an internal process it is irrelevant. For a form embedded on a client facing site it is often the reason a team upgrades before hitting any counter at all.
What the first paid step costs
The visible paid plans, with prices as listed on the pricing page in USD, are these.
| Starter | Bronze | Silver | Gold | |
|---|---|---|---|---|
| Monthly price | 0 | 39 | 49 | 129 |
| Yearly price | 0 | 408 | 468 | 1,188 |
| Forms | 5 | 25 | 50 | 100 |
| Submissions per month | 100 | 1,000 | 2,500 | 10,000 |
| Total stored submissions | 500 | 10,000 | 25,000 | 100,000 |
| Upload space | 100MB | 1GB | 10GB | 100GB |
| Fields per form | 100 | 250 | 500 | 1,000 |
| HIPAA features | No | No | No | Yes |
The step from free to Bronze multiplies the monthly submission allowance by ten and the storage allowance by twenty, which is a large jump for the first paid tier. The step from Bronze to Silver is much smaller in proportion for a 10 USD per month difference, and the step to Gold is where the price moves sharply, largely because it is the tier that carries the HIPAA compliance features.
One structural point matters more than the individual numbers. On the pricing page's own FAQ, Jotform states that the Enterprise plan is the only multiuser Jotform plan. Team size is therefore not the axis these prices move along. Volume is.
Where per seat pricing changes the arithmetic
Form tools are priced on one of two axes, and which axis a tool uses decides which kind of growth is expensive.
Priced on volume. The bill tracks how many responses arrive. Quiet months are cheap. A campaign, an open application window or an event pushes the account into a higher tier, and the tier has to be held for the whole billing period even though the spike lasted two weeks. Adding colleagues to the work is a separate problem, solved outside the pricing model or not at all.
Priced on people. The bill tracks how many colleagues need access. Responses are unmetered, so a spike costs nothing and no exports are needed to stay under a line. Growth in team size is what moves the price, and a solo user gets the cheapest possible outcome.
Neither is universally better. The question is which of the two numbers is volatile for a given team. An intake process that runs at a predictable trickle and is handled by four people is expensive on the second axis and cheap on the first. An events team of two that takes a thousand registrations in March and forty in July is the reverse.
It is worth checking what a tool meters before comparing headline prices, because two plans at the same monthly figure can mean completely different things. A tool with unlimited forms and unlimited responses on every tier, charging only for the number of people using it, removes the volume question entirely and replaces it with a headcount question.
What to change first
Find out which counter is actually closest to full, rather than assuming it is the monthly one. If total storage is the binding limit and the data has to be kept, set up an export before anything else, because that limit deletes oldest first rather than stopping. If the volume is spiky rather than steady, compare the annual cost of a tier sized for the peak against tools priced on team size, such as Halict, before committing to a year at the higher tier.
Q1. How many forms can be created on the Jotform free plan?
Five active forms. The cap applies to forms live on the account rather than the number ever created, so deleting an old form frees a slot, though deleting it also removes its responses.
Q2. Does the Jotform free plan expire?
No. Starter is free with no time limit and includes the standard feature set, excluding HIPAA compliance features. The restrictions are on volume and on branding rather than on duration.
Q3. What is the difference between 100 submissions and 500 submissions on the free plan?
The 100 is a monthly flow limit that resets each month. The 500 is the total number of responses that can be stored on the account at once, across all forms and all time, and it does not reset. Steady low volume use meets the 500 first.
Q4. What happens when the Jotform storage limit is reached?
The pricing page states that when total submission storage is exceeded, the system deletes the oldest form response to make room for new ones. New submissions keep arriving, and the oldest ones are removed, so an export routine matters for any data that has to be retained.
Q5. How much does the cheapest paid Jotform plan cost?
Bronze is listed at 39 USD per month, or 408 USD paid yearly. It raises the account to 25 forms, 1,000 submissions per month, 10,000 stored submissions and 1GB of upload space, and removes the Jotform branding from forms.
Q6. Can several colleagues share a Jotform account on a paid plan?
The pricing page FAQ states that Enterprise is the only multiuser Jotform plan. Teams needing shared access across named users should confirm the current arrangement directly, since the standard tiers are priced on volume rather than on seats.
