Forms
Is Jotform free? Current limits and upgrade triggers
Last updated · A-Widget
On this page6
The current pricing page names Starter as free and explains that paid plans increase limits and remove branding. This reference is based on listed sources, not a test of a paid account.
Is Jotform free? Current plan allowances
Jotform's listed support explanation of Starter gives the following limits. Confirm the current usage screen and plan terms for your account before relying on them.
| Dimension | Published Starter allowance | Why it matters |
|---|---|---|
| Active forms | 5 | Count forms still enabled, not just the one embedded today |
| Monthly submissions | 100 across the forms | Each form does not receive a separate full account allowance |
| Available storage space | 100 MB | Uploads can constrain a low-volume form |
| Monthly form views | 1000 | A view is not a completed submission |
| Total stored submissions | 500 | Retained records differ from the monthly intake count |
| Payment submissions | 10 | Payment-related scope is separate from all submissions |
| Branding | Present on free forms and signed documents under the current pricing explanation | A paid offer is needed for the documented removal route |
These are account allowances, rather than a separate allocation for every embedded form. Read the account's current usage and plan terms before relying on them; older subscriptions may have different conditions.
Limits and reset periods
A monthly submission limit measures intake during the vendor's monthly period. Total stored records measure retained data. Reaching the start of a new month does not mean old stored responses and files have been deleted.
Views and submissions are distinct units. A user can open a form and leave without sending it. A busy public page may reach a view limit. That can matter even if few people finish the form.
Check the current usage screen for which limit is close. Do not assume that removing a local download changes the account's retained records. Use the vendor's supported controls and confirm the result in the account.
If a limit affects delivery, the business needs a fallback contact route. A public form should not silently stop being useful while the owner assumes the monthly allowance will cover every visit.
Payments, uploads and branding
Payments need more than a free form
The current pricing explanation says Starter includes standard payment connections within its limits. A supported gateway still has its own account, availability and charges. A free form does not prove free payment processing.
Use the gateway's real status to confirm a charge. An order request or a calculated total can exist without a successful payment. The order-form guide explains that distinction.
Uploads use storage
Decide whether a file is necessary for the request. A few large uploads can matter more than a long list of short text answers. Check supported file limits and who can read the stored material.
Do not collect private records through a general free inquiry form without a suitable process. The presence of an upload control is not evidence that every kind of data belongs there.
Branding is a real plan condition
If vendor branding matters to the page, inspect the current removal plan scope. Do not describe a free form as unbranded because a paid demo lacks the mark. Open the published form from your own account to see the branding visitors will receive.
Is Jotform free enough for your task? Upgrade triggers
Consider a paid plan when a verified need exceeds the ongoing free scope. Identify the exact limit or feature first. A larger package will not shorten the form. It will not staff an inbox that no one checks.
Compare an alternative when the task is better suited to another workflow. A simple spreadsheet-led response form may not need a broad hosted intake package. A WordPress owner may prefer a native route, with responsibility for hosting and delivery.
Use the Jotform alternatives guide to compare those reasons. Use the Jotform review for the broader feature and limit check.
A small account checklist
- Confirm the account's current plan name and ongoing state.
- Count active forms across the account.
- Inspect monthly submissions and form views separately.
- Review retained responses and upload storage.
- Check payment-submission scope if payments are used.
- Open the listed form to verify branding and public access.
- Keep a contact alternative if a limit blocks the form.
Estimate a peak month without assuming unused capacity
Suppose a fictional account receives 60 inquiry responses and expects another 50 event registrations in the same month. That is 110 expected submissions across the account, even if the forms have different owners. Compare the combined workload with the account’s displayed allowance before sharing the event form.
Do not assume that deleting an old response restores a monthly submission allowance. Stored-response capacity, uploads and monthly usage have different meanings. If one campaign has an unpredictable spike, plan a supported upgrade or an alternate contact path before the counter is reached. The account usage screen, rather than the number of published forms, tells you which constraint is close.
Continue with the right task
FAQ
Does each form get its own full response limit?
The cited Starter explanation describes the monthly submission allowance across the account's forms. Do not multiply it by the form count. Check the current account usage screen to see the account-wide usage total and inspect other limits, including views and storage, separately.
Does a free form make payments free?
No. A form plan and a payment processor have separate terms. Inspect the supported gateway, account access and applicable charges. A calculated total or a saved response does not prove payment. Confirm the real charge through the supported payment record.