NumoForms vs Jotform
Jotform is a general-purpose online form builder with a very large public
integrations directory, a large template library, payment-gateway
connections and a separate e-signature product (checked July 2026, from
Jotform’s own site). NumoForms is narrower on purpose: 16 question
types, conditional logic, per-choice scoring with percentage bands,
save-and-continue resume links, per-survey partner logos, and survey
content and responses stored in London (eu-west-2). We do
send each response onward by signed webhook, but that is one endpoint, not
a directory. If the form needs to drop into a long list of named apps, buy
Jotform. If the survey is long, branching and has to stay in the UK, we are
the closer fit.
What Jotform is genuinely good at
Jotform’s strength is breadth. Its public integrations directory lists connections across categories including payments, cloud storage, CRM, email marketing, project management and automation platforms — that is a genuinely large surface area, and no small vendor matches it. Jotform also markets a large template library, a drag-and-drop builder, conditional logic, an e-signature product and mobile apps. Checked July 2026. Jotform ships changes often and feature availability varies by plan — read jotform.com and their current pricing page rather than our summary of it.
For a registration form that must create a record in a CRM, take a deposit, and file a copy in cloud storage, a general form builder with a long integration list is the right tool and we would say so to your face. We have not built any of that. Our signed webhook will hand the response to an endpoint you write, and that is the whole of it — no CRM connector, no payment gateway, no cloud-storage integration, and no Zapier app to stand in for the ones we lack.
Side by side
| Capability | NumoForms | Jotform |
|---|---|---|
| Integrations, webhooks, Zapier | Webhooks only: each response posted to your https URL, HMAC-SHA256 signed with a per-webhook secret, delivery log in the builder. No Zapier app, no public API. Otherwise CSV export, or one response printed to PDF | Large public integrations directory across many categories |
| Payment collection | Not built | Payment-gateway integrations advertised on their site |
| E-signatures | Simple electronic signatures: typed or drawn, stored with the agreement text, a SHA-256 hash of it, timestamp and user agent. Not qualified signatures (QES) | Separate e-signature product advertised on their site |
| Question types | 16 kinds, including matrix, drag-to-rank, recommend score, address with postcode checking | Large field library — check Jotform’s current form-elements documentation |
| Conditional logic | Show/hide on earlier answers; rules match any or all |
Conditional logic documented on their site — check the rule types you need |
| Scoring and bands | Per-choice score, per-question weight, percentage bands on the thank-you screen, hidden questions excluded | Form calculation and scoring widgets documented — check their help centre |
| Save and continue | Resume link on a 24-character token; partials in a table with no RLS policies, reachable only via SECURITY DEFINER functions |
Jotform documents saving and continuing later — check current behaviour and plan |
| Close date and response cap | Enforced by a database trigger, not the interface | Form-limit settings documented — check how they are enforced |
| Partner co-branding | Collaborator logos set per survey, separate from the org brand kit | Branding and white-label options documented at account/plan level |
| Data residency | London (eu-west-2) on every account, TLS in transit, AES-256 at rest |
Jotform documents data-residency options; check which apply to your plan |
| Mobile apps | None. Web only, for building and responding | Mobile apps advertised on their site |
Jotform column: taken from jotform.com/integrations and jotform.com, checked July 2026. Rows that say “check” are ones we have not verified to the standard we would want quoted back at us — read Jotform’s own documentation rather than a competitor’s précis of it.
Where the difference actually is
A form and a survey are not the same object
A form collects a transaction: one person, one submission, usually short, usually followed by something happening in another system. A survey collects a dataset: hundreds of people, questions that only apply to some of them, and a results view that has to hold up to scrutiny afterwards. Jotform is built around the first job and does the second as well; we only do the second. That shows up in small places — matrix questions exporting one CSV column per row, an “Other (please specify)” answer stored separately from the option label so it lands in its own column, and randomisation that is seeded per page load so pressing Back does not reshuffle the options underneath the respondent.
Scoring that survives branching
Scoring gives every choice a score and every question a weight, then places the total in a percentage band shown on the thank-you screen. The part that matters is what it ignores: only questions the respondent actually saw are scored, so conditional logic never penalises someone for a branch that did not apply to them. A readiness checklist that skips ten irrelevant questions should not score lower than one that answers them all badly.
Long surveys, and people who close the tab
Save and continue issues a
resume link keyed on a 24-character token. Partial answers live in their
own table with no row-level security policies whatsoever, reachable only
through SECURITY DEFINER functions, so an unfinished
response is not sitting in the results set waiting to be exported into a
report by mistake. On an eighty-question consultation this is the
difference between a response and an abandonment.
Closing a survey properly
Responses insert straight from the browser. That means a close date or a response cap policed only by the interface is decoration, not a control. Ours is a database trigger: past the date or over the cap the insert is refused, and the respondent gets your custom closed message instead of a silent failure.
Branding a partnership, not a company
Jotform’s branding controls sit at account and plan level, which is right for an organisation putting its own face on its own forms. Ours are per survey, because a research team or a consultancy badges a different council, funder or partner on each piece of work and should not need a separate account for each one.
Where the data lives
Survey content and responses sit in Supabase’s London region on every account, encrypted in transit with TLS and at rest with AES-256. File uploads go to a private bucket that is readable only by the owning organisation, through signed URLs that expire after 300 seconds. The security page sets out the controls and the sub-processor list names everyone in the chain. We are not ISO 27001 certified and have not completed a SOC 2 audit, and we would rather say so than imply otherwise.
Reasons to choose Jotform instead
- The form has to trigger something in another system and you want a ready-made connector. We have a signed webhook and nothing else — no Zapier app, no public API — so anything past an https URL you control is code someone has to write.
- You need to take payment, or you need a qualified electronic signature (QES). Ours are simple electronic signatures with an audit trail, which is a different legal instrument.
- You need an approval chain with several steps, delegation or escalation. We do single-step sign-off: approve or reject, with an optional comment, recorded by the database.
- You need SSO/SAML or offline collection — neither of which we have built. Multi-language surveys we do have, per survey and by link. Spam protection we have too, but as a honeypot, a dwell-time floor and a rate limit rather than a CAPTCHA, so if a CAPTCHA is what your policy names, we are not it.
- You want native mobile apps for field data collection.
- You want a very large ready-made template library today. Ours is a set of template guides that lead into the builder, not a one-click in-app library.
Common questions
Is NumoForms a good Jotform alternative?
NumoForms is a reasonable Jotform alternative when the job is a
long, branching, scored survey whose responses must stay in the UK. It
has 16 question types, conditional logic, per-choice scoring with
percentage bands, save-and-continue resume links, per-survey partner
logos and storage in London (eu-west-2). Jotform is the
better choice when the form has to drop into a long list of named apps,
take payments, or produce a qualified electronic signature. NumoForms
posts signed webhooks and sends notification emails, but has no Zapier
app, no Google Sheets connector, no public API and no payment
collection, and its signatures are simple electronic signatures rather
than qualified ones.
Does NumoForms integrate with Zapier or webhooks like Jotform?
Webhooks yes, Zapier no. Each response is posted to an https URL you choose, signed with HMAC-SHA256 using a per-webhook secret, with a delivery log and the last HTTP status in the builder. There is no Zapier app and no public API, so anything past an endpoint you control is code you write yourself. Data also leaves as a CSV export, or as a PDF of a single response printed from the browser. Jotform publishes a large integrations directory covering payment, storage, CRM and automation tools, which is a far bigger surface than one webhook.
Other comparisons
If respondent polish is the deciding factor, read NumoForms vs Typeform. If you need respondents as well as an instrument, read vs SurveyMonkey. If the real incumbent is the free thing already installed, read vs Google Forms. All four sit under compare, and the product overview covers the builder end to end.
Build the branching version.
Put your real questions in, turn on conditional logic and scoring, and look at what a respondent is actually asked. The total counts only the questions they saw, so a branch that did not apply never costs anyone marks.
- Show or hide individual questions on earlier answers
- Per-choice scores, weights and percentage bands
- Each response posted onward by signed webhook
