Jotform vs Typeform: Notes from Running Both for Client Waitlists (2026)

The short version

Both work. That is the honest headline and it is why this is not a fifteen-tool roundup. We have run Jotform and Typeform for real client campaigns, sometimes on the same project, and neither one let us down on the thing they are for, which is collecting a name and an email address and putting it somewhere a sales team can see it.

The difference is where the money starts. Typeform cut its free plan to 10 responses a month in February 2026, down from 100, and when you hit the cap the form stops accepting submissions. Jotform gives you 100 a month free but also has a lifetime ceiling of 500 stored submissions that almost nobody notices until they hit it. If you are running a campaign rather than testing an idea, budget for a paid tier on either from day one.

Pick Jotform when the form has to do something clever with routing and conditional logic. Pick Typeform when the form is short and the experience of filling it in is the point. And if you can build a form yourself in an afternoon, read the last section before you pay for either.

What we actually used them for

This is client work, not our own stack. We do not collect email addresses on our own products, by policy. But we have set up forms for an email marketing company and for several of its clients, and the jobs were always the same three: a waitlist for a launch, a second opt-in step to confirm people actually wanted to hear from the client, and a booking form for a meeting or a phone call.

The output was almost always a Google Sheet. The sheet was shared with whoever was doing the selling, so a lead arriving in the form appeared in a row the sales team could work from within a minute or two. One client also wanted every submission emailed to them as it arrived, not because they needed the email, but because they wanted to feel the campaign working in real time. Both tools handle both outputs without fuss.

One client had a strong preference for one tool over the other, which is how we ended up running both rather than standardising on one. That turned out to be useful. Having done the same job in both, the comparison below is not a feature-list exercise. It is what it was like.

Why a forms tool at all

Worth being honest about the context. When we started using these, the realistic alternatives for a small client were the form builder inside Squarespace or a WordPress plugin. Neither was good at conditional logic, neither styled well, and neither pushed cleanly into a spreadsheet. A dedicated forms tool gave you an embed you could restyle, a hosted page if you had no site to embed it in, and a one-click connection to Google Sheets. That was the whole value, and it was worth paying for.

Today, a builder can put a form in front of a database in an afternoon, and that changes the calculation for anyone technical. It does not change it for a client who needs a form live by Thursday and does not have a developer on hand. Both of those people are reading this, and the recommendation is different for each. The last section covers the build-it-yourself case.

Jotform: the one with more on the free tier

We started with Jotform because, at the time, the free plan simply did more. That is still true. The Starter plan gives you five forms, 100 submissions a month, 100 fields per form, and 10,000 monthly views, with Jotform branding on the form. For a small business testing whether a campaign works, that is enough runway to find out.

Where Jotform is genuinely better is anything with branching. Conditional logic, showing or hiding questions based on earlier answers, routing a respondent down one path or another, calculated fields: Jotform does all of it, and it does it on plans where Typeform does not. If the form has to work out which sales person to send a lead to, or ask different questions of a business than of a consumer, Jotform is the one to reach for.

The catch that the pricing page does not put in large type: the free plan has a lifetime ceiling of 500 stored submissions. You can stay under 100 a month for a year and still hit it. When you do, the account stops storing new responses until you upgrade or delete old ones. There is also a separate cap of 10 payments and 10 signed documents a month on the free plan, which matters if the form takes deposits. Paid plans start at around $34 a month billed annually and lift the monthly submission limit to 1,000.

Aesthetically it is fine. It is a form. It looks like a form. That is not a complaint, but it is the reason the second tool exists.

Typeform: the one that looks better and costs sooner

Typeform asks one question at a time, animates between them, and makes filling in a form feel less like filling in a form. For a short waitlist or a booking request, that polish is real. Completion rates on short Typeforms were noticeably good, and clients liked how it looked embedded in their pages. If the form is five questions and the brand matters, Typeform is the nicer experience for the person on the other end.

The free plan is where it turns. It was 100 responses a month. In February 2026 Typeform cut that to 10, without much warning, and limited free forms to 10 questions. Ten responses is not a campaign. It is a test. And when you reach the tenth, the form does not warn the eleventh person; it stops collecting, and anyone who arrives after that gets nothing. If the form is a waitlist and it is live on a page you are sending traffic to, that is a silent failure in the exact place you cannot afford one.

Paid plans start at $25 a month billed annually for 100 responses, $50 for 1,000, and $83 for 10,000. Month-to-month billing is meaningfully more. Compared to Jotform, you are paying sooner and getting fewer responses per pound, and the conditional logic is thinner at the lower tiers. What you are buying is the experience, and for the right form that is a fair trade.

One more honest note: our Typeform experience predates some of its redesigns, and the product has changed. The polish was better than Jotform then and, from what we can see, still is. Check the current plan page before you assume the limits above, because they have moved once already this year.

The trap: a form that stops collecting

The only thing that ever went wrong for us with either tool was the paywall, and it is worth spelling out why that is worse than it sounds.

A form is the one part of a campaign you do not look at once it is live. You look at the sheet. You look at the email notifications. You look at the ad spend. The form is a fixed thing on a page, and if it quietly stops accepting submissions, nothing on your side tells you. The sheet just stops growing, and the natural first assumption is that the campaign has stopped working, not that the form has.

On Typeform the free cap is 10 a month, so any real campaign hits it in the first day or two. On Jotform the monthly cap is more forgiving, but when you exceed it every form in the account is disabled until the next reset, not just the one that went over. The 500-lifetime ceiling on stored submissions lands later and with less warning, because it is a total rather than a rate.

The practical habit we ended up with: know the cap before the campaign starts, watch the submission count like a fuel gauge, and if the form is doing a job that matters, pay for the tier that removes the question. The paid plans are not expensive next to the cost of a waitlist that silently closed on day two.

Where the data went, and why it matters more than the form

Both tools connect to Google Sheets in a couple of clicks, and that integration is the reason to use either one for lead capture. The form is the front door. The sheet is where the work happens.

The pattern that worked: one sheet per campaign, shared with the sales team, with the form pushing a new row per submission. Sales worked the rows top to bottom. Nobody logged into Jotform or Typeform after setup, because nobody needed to. The tool disappeared into the plumbing, which is what you want from it.

Email notifications are the other output, and they are for a different audience. The client who wanted every submission in their inbox was not going to act on them there. They wanted to see the campaign breathe. If your client is that person, turn notifications on for them and keep the sheet for the people doing the follow-up.

Both tools also connect to Zapier and the usual automation platforms if the destination is a CRM rather than a sheet. For the small businesses we set these up for, a shared sheet was the CRM, and that was the right call. Our CRM article covers why.

Which one, for which job

If the form has depth, use Jotform. Anything with branching, routing to different people, calculated fields, or more than a handful of questions is easier to build and cheaper to run there. The conditional logic is the feature that separates them, and Jotform has more of it at every price point.

If the form is short and the experience is the point, use Typeform. A five-question waitlist on a brand-conscious landing page is what it was made for, and it does that better. Pay for it from the start, because the free tier cannot run a campaign.

If you are not sure, the tie-breaker is the free tier. Jotform lets you find out whether the campaign works before you pay. Typeform asks you to pay to find out. For a client project where the budget is the client's and the timeline is short, that difference decides it more often than the feature list does.

If the client has a preference, follow the preference. We did, and it was fine both ways.

When to skip both and build it

If you can put a form in front of a database yourself, and the form is for your own product rather than a client, you probably should. A form that posts to your own API and writes to your own table costs nothing per submission, has no cap, and puts the data where the rest of your app already is. The forms tools earn their fee by removing the build; if the build is an afternoon, the fee is harder to justify.

The honest counter-argument is time and polish. A tool gives you validation, spam protection, a mobile layout that works, and a hosted page, and it gives you them today. If the form is for a launch next week and you have other things to build, paying $25 a month to not think about it is a reasonable trade, even for a builder.

Two free options we have not run ourselves and are including for completeness: Tally, which offers unlimited forms and submissions on its free plan and has become the default suggestion for people who want Typeform's feel without the cap, and Formbricks, which is open source and self-hostable if you want the data on your own infrastructure. We cannot vouch for either from experience. We can say that if we were setting up a client waitlist today and the client had no preference, Tally is what we would try first, precisely because the paywall is the only thing that ever bit us.