forms.app Pricing: Free, Grow and Scale Compared
forms.app has a Free plan, Grow at US$19 a month and Scale at US$35 a month on monthly billing. All three list unlimited responses and team members. The practical upgrade question is often different: how many forms will you keep, how much file storage will accumulate, and must respondents receive an email? Count those requirements before treating unlimited responses as a complete operating budget.
Compare the current plans and billing terms
These USD figures were checked on November 22, 2026, against the official forms.app pricing page. The page currently presents Free, Grow and Scale. Older search snippets and some help pages still use Basic, Pro and Premium; those names are not the current public plan table used here.
| Plan | Monthly billing | Normal annual monthly equivalent | November annual offer, monthly equivalent | Forms | File storage |
|---|---|---|---|---|---|
| Free | US$0 | US$0 | US$0 | 5 | 10 MB |
| Grow | US$19 | US$15 | US$12.50 | 25 | 100 GB |
| Scale | US$35 | US$24 | US$19 | Unlimited | Unlimited |
The normal annual figures appear in the page's structured offers; the active November Sale appears on its visible annual cards. At those sale equivalents, multiplying by twelve gives US$150 for Grow and US$228 for Scale. The normal annual references are US$180 and US$288. These are different billing contexts, so keep them in separate columns when preparing a budget.
The sale's public display did not provide a confirmed end date during this check. The displayed monthly equivalent is not a promise that the service can be purchased for one month at that rate. Confirm the full charge, eligibility, tax and renewal conditions at checkout before agreeing to an annual purchase. An existing subscriber should compare their own account terms separately.
For a short project, compare the total commitment as well as the headline. Three monthly Grow payments would be US$57 before tax; twelve would be US$228. That gives you a concrete question: do you need three months of access, or will the intake and follow-up remain open throughout the year? A lower annual equivalent does not by itself answer it.
Count forms you will keep, including the next launch
Consider a fictional small agency collecting consultation requests. It plans to maintain four separate intake forms and prepare two more for an upcoming launch. The following is a planning exercise, not observed customer usage.
| Intended form | Why it remains separate |
|---|---|
| New consultation request | Collect the initial project outline |
| Existing-client additional request | Relate new work to an existing engagement |
| Partner inquiry | Route a different type of conversation |
| Post-consultation feedback | Ask only questions relevant after the meeting |
| New service intake | Prepare the next launch |
| Alternate-language intake | Review a distinct set of published wording |
Four plus two is six. In this example, the Free allowance does not cover the planned set; Grow's form allowance does. That result follows from the operating design, even if only a handful of people respond each week. You do not need a larger response forecast to explain this upgrade.
Before paying, check whether each separate form is necessary. Could one genuinely shared question set serve two services with a service-choice field? Would merging them create confusing questions, inappropriate data collection or extra manual sorting? A single shared form can be sensible, but combining unrelated processes merely to reduce a form count can move the cost into staff time.
Also ask how your account counts unpublished drafts, duplicates, archived forms and deleted items. This article does not assume that every form state has the same billing treatment. Check the usage display while creating and removing a harmless test draft. Keep the result beside the inventory so that a colleague can reproduce the decision later.
The useful output is a short list: forms needed today, forms needed during the next launch, and forms that can be retired safely. Use the peak overlap rather than the average number opened in a quiet week. If you must preserve an older public address while launching its replacement, include that overlap in the plan.
Calculate stored files across the retention period
Response count and file storage measure different things. A text-only request can be small, while a single document or image can change the storage requirement. Make the attachment budget explicit before asking clients to upload files.
For the same agency, assume one uploaded file averages 2 MB, forty inquiries arrive each month, and the agency intends to keep three months of files in the form service:
2 MB × 40 inquiries × 3 months = 240 MB of estimated stored files.
The 2 MB average, forty inquiries and three-month retention period are chosen assumptions. Replace them with your own evidence and policy. This calculation is a file-size estimate, not a measurement of the service's internal storage accounting; existing files and other counted assets may add to the displayed usage.
Under these assumptions, the current free storage allowance is already too small, while the Grow allowance has room for the estimate. The reason is cumulative storage, not a monthly response cap. If the business keeps files for twelve months instead of three, the same simplified estimate becomes 960 MB. A quiet intake can keep growing long after the launch ends.
Separate the average file size from the largest accepted file. The former helps estimate storage over time; the latter determines whether an individual client can complete the intake. Try a typical harmless file and an oversized dummy file, then inspect what the respondent sees. A generous total storage figure cannot establish that every intended upload will be accepted.
Before deciding on a retention period, ask who needs access after the consultation and where the authoritative project record will live. Do not choose a shorter retention period merely to fit a free allowance if that conflicts with your operating requirements. Conversely, do not keep unused client files indefinitely because a higher plan has more capacity.
Ask support how deleted items, trash and exports affect the account's current storage reading, and what happens when capacity is reached. Record the answer for the current plan. Some help content retains older plan terminology, so do not silently apply an old plan limit to a new subscription.

Check what the person receives after submitting
A saved response and a delivered acknowledgment are separate acceptance conditions. A consultation intake may collect the right information while leaving the prospective client uncertain about what happens next. Write the intended acknowledgment before choosing the subscription.
For example, the agency wants to send a short receipt naming the selected service, explaining the review process and stating how to correct an error. Those details define the test. “Has notifications” is too broad to show whether the intended communication is available and configured.
The current pricing comparison places respondent notifications on Grow and Scale. The official respondent-notification help also says this is a paid-plan feature and requires an email field. That can make email a purchase requirement even when the form count and stored files are modest.
Test the complete message with fictional information and an address you control. Inspect the recipient, subject, merged answers and next-step wording. Make sure optional answers do not produce broken-looking sentences. The result you need is a readable acknowledgment received by the intended address, not simply a setting that appears enabled.
List staff alerts separately from respondent acknowledgments. The agency's team may need a summary of new requests, while the client needs a receipt and a reply route. A third requirement, such as a later reminder, is another behavior to verify rather than infer from the receipt feature. Name who reviews failed or missing communication and how they discover it.
Try one private intake in FORMLOVA
If you already use ChatGPT or Claude for work, FORMLOVA offers a way to draft and revise the intake from your existing AI chat. This is useful when you want to check the questions before committing to the full attachment and communication arrangement.
Start in this order: register for FORMLOVA, verify your email, then connect a supported AI client. Review the current AI connection requirements, including your AI account's plan and permissions. A FORMLOVA registration does not automatically add the connection or create a form. For ChatGPT, full custom MCP writing requires an eligible Business, Enterprise or Edu web setup and the necessary permissions; do not assume every ChatGPT subscription can create forms through this connection.
Use fictional business details and ask:
Create a private consultation-request draft for a small design agency. Ask for name, email, requested service, project outline and preferred contact time. Require name, email and requested service. Do not add a file-upload field yet. Explain the saved questions and what I should check before publishing. Do not publish, send messages, invite colleagues or collect payments.
Inspect the saved draft against your own acceptance conditions. Check the service choices, required fields and wording shown to a client. Then ask for one change, such as replacing a vague project-outline question with a more specific prompt. Reopen the saved draft and verify that the intended change is present.
FORMLOVA Free includes form creation and publishing, response collection without form or response count caps, and CSV or Excel export. Keep this trial attachment-free. File uploads and custom participant communication require Standard or above; paid forms and team management require Premium. Compare the current FORMLOVA plans before extending the trial into those operations. AI-client eligibility and any client-side costs are separate.
Check your consultation questions on a private draft
Use fictional details to inspect required fields and service choices before arranging uploads and client communication.
Register free and draft a consultation intake
Register, verify your email and connect a supported ChatGPT or Claude setup. Then use the request above and inspect the saved draft.
Choose the service around the operating decision
forms.app Free can suit a small text-only intake whose form inventory fits the allowance and whose team does not require the paid respondent-notification feature. Grow becomes a candidate when the example's additional forms, stored files or acknowledgments are necessary. Scale is relevant when the operation requires capabilities such as a custom domain, partial responses or saving progress; confirm those requirements in the current comparison before purchasing.
FORMLOVA is worth testing if the main preference is to create and manage the intake through an AI chat you already use. If the intended operators want to work entirely inside a visual form editor, test that working style directly in the services you are considering. Do not assume the lowest subscription or the longest feature list determines which team will use it reliably.
For the fictional agency, write the decision in one sentence: “We need six forms, an estimated 240 MB of retained uploads and a respondent acknowledgment.” Then add the intended billing term and the tests still outstanding. This is a reviewable requirement that a colleague can challenge or update; “we need more features” is not.
For broader choices, start with the form services comparison hub. The cross-provider comparison helps compare operating approaches, while the free AI form guide focuses on an initial creation trial. Return to your inventory and storage estimate before choosing a live plan.
Questions before subscribing
Does unlimited responses mean all intake operations are free?
No. Check the form inventory, accumulated attachments and required communication separately. An unlimited response allowance does not establish that every other requirement is included.
Is the annual monthly equivalent a monthly contract?
No. It expresses an annual billing amount as a monthly equivalent. Review the full payment and renewal terms, and keep a temporary offer separate from the normal reference price.
Should I choose Scale just because I expect more inquiries?
Start by identifying the requirement Grow cannot meet. A custom domain or another required capability may justify it, but a larger response forecast alone is not the reason in a table listing unlimited responses across the plans.
Can I try the questions before setting up attachments?
Yes. Use a private, attachment-free draft with fictional details, inspect the saved fields and refine the wording. Test file collection and participant communication separately on a plan that supports them.
Disclosure and Verification
I develop FORMLOVA. forms.app's current public plan cards, comparison table and structured offers were checked on November 22, 2026. The linked official notification guidance supports the paid-plan and email-field requirements. The temporary annual offer is labeled separately from the normal reference; checkout, renewal pricing and taxes were not verified. FORMLOVA's trial scope was checked against its plan definition and connection requirements. The agency, six-form inventory and storage arithmetic are illustrative, not measured customer results. No subscription, live intake, payment or email delivery was executed for this article.


