Popular online form builder website, jotform.com, forms, surveys, payments, tables, apps, approvals, e-signatures, templates, pricing, and WHOIS domain data

Jotform

Jotform is a popular online form builder website for creating forms, surveys, order forms, payment forms, quizzes, tables, no-code apps, approvals, documents, and e-signature workflows.

Official site

jotform.com is the main public website for Jotform.

Product focus

Jotform focuses on drag-and-drop forms, surveys, payment forms, templates, tables, no-code apps, approvals, documents, reports, and e-signatures.

Plan shape

Jotform's pricing page lists a free Starter plan and paid plans with higher limits for forms, submissions, storage, payment submissions, signed documents, and HIPAA features.

The Jotform wordmark.View image on Wikimedia Commons

What Jotform is

Jotform is an online form builder website at jotform.com for creating forms, surveys, quizzes, order forms, registration forms, payment forms, approvals, reports, documents, tables, and no-code apps. Its official homepage presents Jotform as a free online form builder and form creator for people who need to collect information without building a custom web application.

Form builder core

Jotform's main product is a drag-and-drop form builder. Users can start from a blank form or a template, add fields, create conditional logic, collect file uploads, accept signatures, embed forms on websites, and send submissions to email or connected apps. This makes it useful for intake, registration, feedback, applications, and order workflows.

Payments and commerce

Jotform supports payment forms and order forms through payment integrations. A small organization can collect donations, sell products, accept deposits, process event payments, or gather billing details in the same form that collects customer information. Payment workflows still require careful handling of taxes, refunds, fraud, privacy, and local rules.

Tables, apps, and workflows

Jotform has grown beyond simple forms. Its product pages describe Jotform Tables for organizing submissions, Jotform Apps for no-code apps, Jotform Approvals for review flows, Jotform Sign for e-signatures, Jotform Report Builder for visual reports, and document tools for turning submissions into PDFs and other outputs.

Templates and AI help

Jotform emphasizes a large template library and AI-assisted creation tools. Templates can help users start quickly for common tasks, while AI tools can draft forms, apps, agents, and workflows from prompts. These tools save setup time, but form owners still need to review wording, required fields, privacy notices, and the final data flow.

Who uses Jotform

Jotform is used by small businesses, nonprofits, schools, healthcare teams, event organizers, marketers, agencies, human resources teams, customer support teams, creators, and operations teams. It is especially useful when a team needs a quick public-facing intake form, internal request form, signup page, payment form, or lightweight workflow without developer time.

Pricing and plan shape

Jotform pricing is organized around usage limits. The pricing page lists differences in the number of forms, monthly submissions, available storage, monthly form views, total submission storage, payment submissions, signed documents, HIPAA availability, branding removal, custom domains, and team or enterprise features. The best plan depends on response volume and compliance needs.

Why it matters

Jotform matters because forms are one of the simplest ways organizations turn messy requests into structured data. A form can replace email back-and-forth, standardize intake, trigger approvals, collect payments, generate documents, and feed a spreadsheet or workflow. That can help small teams automate practical work without building software from scratch.

Limits and cautions

Jotform does not remove the need for privacy review, clear consent, secure access controls, careful field design, accessibility checks, spam protection, data retention rules, payment review, and compliance planning. A form is easy to publish, so teams should decide who owns responses, who can export data, and how long sensitive submissions are kept.

WHOIS domain data

Data pulled: May 20, 2026View current WHOIS record

Domain: jotform.com
IP address: 34.102.158.113
Registrar: Tucows Domains Inc.
WHOIS server: whois.tucows.com
Referral URL: http://www.tucows.com
Created: November 9, 2005
Updated: June 10, 2025
Expires: November 9, 2034
Nameservers: jay.ns.cloudflare.com (172.64.33.123); leah.ns.cloudflare.com (172.64.32.129)
Domain status: clientTransferProhibited; clientUpdateProhibited
DNSSEC: signedDelegation
Registrant organization: Contact Privacy Inc. Customer 0130367910
Registrant country: CA
Contact privacy: Registrant contact details are provided through Contact Privacy Inc. Customer 0130367910.

Key concepts

Online form buildera hosted tool for collecting structured information through web forms.
Conditional logicrules that show, hide, or route fields based on earlier answers.
Submissionone completed response or entry sent through a form.
Workflow automationrouting submitted information into approvals, notifications, documents, or connected apps.

Main tools

Form Builder, templates, conditional logic, file uploads, widgets, and embed options.
Payment forms, order forms, donation forms, and integrations with payment processors.
Jotform Tables, Apps, Approvals, Sign, Report Builder, PDF tools, and no-code workflow products.
Team, enterprise, HIPAA-oriented, security, branding, and custom-domain features depending on plan.

Common misconceptions

A form builder is not automatically a secure database; access, retention, and exports still need governance.
Templates can save time, but they may include fields or wording that do not fit a specific use case.
Payment forms still require business rules for refunds, disputes, taxes, receipts, and fraud risk.
No-code workflows can become hard to maintain if ownership, naming, and documentation are ignored.

Open questions

How will AI-generated forms affect question quality and privacy defaults?
How should teams decide when a Jotform workflow is enough versus when they need a purpose-built app?
How can organizations prevent form sprawl as many departments publish their own intake pages?
Which submitted data should be stored in Jotform, and which should move into a system of record?