Shopify Forms vs Paid Form Apps: Is Free Enough?

There is a line in your app budget that says Klaviyo, or Privy, or a form builder you installed two years ago and stopped thinking about. Meanwhile Shopify gives away a first-party forms app, and every guide to growing an email list still opens by telling you to install something paid. Those two facts have never been reconciled anywhere you can read them, which is why the line survives review after review.

This page reconciles them. Not by ranking form apps — we deliberately do not — but by naming exactly what the free app finishes, the five boundaries where it stops — three of them stated outright in Shopify's documentation, two absent from every page we read — and where each of those five sits on the paid listings' plan cards and feature lists. Everything here comes from Shopify's own documentation and from the App Store listings themselves, read between August 23 and 25, 2026. Our guide to a new store's app stack covers the wider question of what deserves a monthly fee at all.

The Quick Verdict

Find your situation in the first column. Everything after it is the evidence underneath.

What the free Shopify Forms app actually gives you

Start with the thing most comparisons skip: the free app is not a trial edition of the paid ones. It is a finished product with a small number of hard walls, and the honest question is never whether you can afford forms but whether the free one does the specific thing your form needs. It also is not switched on for you — the app has to be installed from the App Store like any other, which is why plenty of merchants paying for a form builder have never seen it.

Two published ceilings bound what the free app can hold. A store can have up to 25 forms in total, and a single form takes up to 31 fields. Neither number changes with your plan, because the app has no plans.

Popup, inline, or both at the same time

A popup floats above the page and needs the Forms theme app embed installed in your theme; an inline form sits inside a section of a page and needs both that embed and a compatible theme. You are not choosing one shape for the store — Shopify's documentation is explicit that you can display multiple popup forms, inline forms, or both types at the same time, which is what makes the 25-form count, rather than the form type, the thing that limits how many you can have.

What fields can a Shopify Form collect?

This list is worth reading slowly, because it is where most people discover the free app does more than they assumed. Multiple choice takes more than one answer where the dropdown list and radio buttons take one; the number field can be bounded to a range you set; and the file upload field is the one that surprises people who assumed collecting a brief or an artwork proof meant paying for it.

Field types and their descriptions from Settings for both popup and inline forms, read on August 24, 2026.

The file field has an edge worth knowing before you plan around it: one attachment of 20 MB or less, and only from a fixed list of formats. A design brief as a PDF is fine. A 40 MB video walkthrough, or a Word document, is not — and that specific mismatch, rather than the absence of the field, is what sends a made-to-order store to a paid builder.

Can one form collect SMS and WhatsApp consent?

This is the part of the native app that moved most recently, and it moved in the direction that matters to anyone weighing a paid list-growth tool. Collecting a marketing opt-in for a third channel is exactly the kind of thing merchants assume they are paying a platform for.

WhatsApp marketing consent arrived on August 6, 2026, joining the email and SMS opt-ins the app already collected. You can also attach a new or existing discount to a form to incentivise signing up for any of the three, which is the mechanism behind every “get 10% off” popup you have ever closed. How deep to make that discount is a separate question, and one our discounts guide takes on properly.

Where does a form submission actually go?

This is the question that decides whether a free form is a real replacement or a toy. A capture tool that dead-ends in a list you have to export by hand is worth less than its price. Shopify's overview page answers it in one sentence, and that sentence is the whole handoff.

One boundary belongs here rather than in a footnote, because it quietly breaks re-permissioning campaigns. When an existing customer submits a form, their email and phone number on file are not modified even if the form carries different ones, and Shopify notes that other fields such as marketing consent might not be updated either. Changing those means editing the customer profile in your admin.

Custom fields become metafields — and that is what you segment on

The practical version: if you ask which category someone shops, that answer is a submission record until you store it as a metafield, at which point it becomes a filter you can segment on. The wider mechanics of custom data — how metafields are defined, where they can be displayed, what an app adds — are their own subject, and our metafields guide covers them in full.

Shopify names a second use for the same mechanism that most merchants never associate with a marketing app: a form can serve as a company account request, with the answers landing under Companies for you to assess before approving a trade buyer. What the form never does is send marketing to the customer — the one email it can send by itself is a per-submission notification to the store owner.

That is the line to hold on to for the rest of this page: capture and sending are two different purchases, even when one invoice covers both.

What the free app will not do

The two kinds of limit are worth telling apart. A documented “not supported” is a fact you can plan against. An absence in the documentation is a weaker claim: it means we looked in the places the feature would be described and did not find it, which is what the box further down records, page by page. Both are real; only the first is certain.

Conditional logic: absent, not weak

This matters because of how the limit is usually described elsewhere, including in older writing of our own: as something for “complex” branching, which implies simple branching exists. It does not. There is no simple case, no two-option case, and no workaround in the settings — the feature is absent from the product, and Shopify says so in one line.

Multi-step forms are not a thing here

The staged form is the single most common conversion-rate technique in list building, which is why this boundary sends more merchants to a paid tool than any other on this page — the first ask is one field, and everything else waits until the visitor has already said yes once.

The native statement is unambiguous and sits beside the conditional-logic line, quoted in the section above: multi-step forms aren't supported. Those two lines are the closest thing the app has to a specification, and the same short considerations list carries the 25-form ceiling — the three of our five boundaries that Shopify states outright rather than leaving to our reading.

No A/B test, no CSS — and here is exactly what we read

These two absences behave differently in practice. Styling is the softer one: brand colours, the field treatment and the font get a form closer to a theme than most people expect, and a merchant who has never tried the native styling usually overestimates what they need. Testing is the harder one, because there is no partial version of a split test.

Is there a cap on forms or submissions?

That reversal is the most underrated fact on this page. The free plans of the paid builders are capped where it hurts a growing store: POWR's free plan stops at 25 form submissions a month and six fields per form against the native 31, and Hulk's free plan at one form and 50 submissions. Those are volume caps, and volume is the thing that grows.

The native ceiling is the opposite shape. Twenty-five is a lot of forms — more than most stores keep switched on — and it does not tighten as the store succeeds. The store most likely to hit it is one running a separate form per landing page or campaign and never retiring the old ones, which is a housekeeping problem before it is a purchasing one.

What does a paid form app actually buy you?

Shopify's own App Store makes the split visible before any of us do: POWR, Hulk and AAA are listed under the Forms category, while Klaviyo and Privy are listed under Email marketing. That is not a detail — it explains why a Klaviyo listing has no conditional-logic feature line to compare against. These tools are not competing for the same job, and a “best form apps” ranking that puts them in one list is comparing a sending platform with a field editor.

Categories, feature lists and prices read on each listing's own App Store page on August 24, 2026. A cell describes what a listing names, not our own test of the product; app pricing moves, so confirm on the listing before subscribing.

Which class you are in decides what “cancelling the form app” even means. Cancel a form builder and you lose conditional logic. Cancel an email platform and you lose the flows that earn the revenue, while the form was never the point. Cancel a popup suite and you lose the targeting and the testing — and keep, at no cost, the popup itself.

What each listing costs to start — and what the feature actually costs

This is the single most useful thing to check before you subscribe, and it is the thing comparison articles get wrong most often by quoting the headline number. Read the plan card that names your feature, not the badge at the top of the listing — on two of these five, that is the difference between the price you compared and the price you will actually be charged.

Plans, prices and free-tier ceilings read on each listing on August 24, 2026: POWR, Hulk, AAA, Klaviyo and Privy. Prices are the listings' own published tiers and change without notice.

Two rows deserve a second look. AAA is the only one of the three builders that does not gate the logic at all — conditional logic appears on every card, including the $9.99 entry — but it has no free plan and its ladder charges for the number of live forms, which is the one dimension where the native app is generous. And Klaviyo's free card already lists forms and A/B testing for up to 250 contacts, which means the testing boundary above can sometimes be crossed without a new invoice at all.

If you already pay Klaviyo, what is that fee buying?

This is where merchants reviewing an app budget make the wrong cut in both directions. Cancelling a sending platform to save the form fee throws away the automation that produced the revenue; keeping a popup-only subscription because “we need forms” keeps a line the native app now covers. The distinction is which meter you are paying: contacts and credits mean sending, pageviews mean display.

There is one genuine advantage to building the form where the sending happens, and it is worth stating plainly rather than pretending the native app wins everything: a form built inside your email platform can be tested, targeted and iterated with the same tooling that sends the campaign. What that buys, and the three rules that decide whether a signup form converts at all, are set out in our Klaviyo signup forms and list growth section — this page deliberately does not repeat them.

So the answer for a platform payer is narrower than “cancel it” and more useful: keep the platform, and stop counting the form as part of what it costs you. On the pricing cards we read the form is bundled into the tier rather than billed as its own line, so there is nothing to save by moving the capture — the line worth re-reading is any second, popup-only subscription sitting beside it.

Which line in your app budget is actually replaceable?

The verdict at the top answers by profile — you find your row and leave. This answers by combination, which is where the money actually hides: what the form has to do, how many forms you run, how far the styling has to go, whether you test, and who sends the email afterwards. It is the crossing of the last two that decides whether your subscription is paying for the capture or for the campaign. The result names a class, not a product, and links back to the table above.

Prove it on your own store before you cancel anything

Steps one to four apply to everyone and take an evening. If the quiz routed you to a paid class, step six is the one that matters most — it is the difference between a capability you genuinely use and a habit of paying. Work down in order; each step's checks are things you verify in your own admin rather than take on trust from this page.

If you would rather watch the build before doing it, the walkthrough below covers setting the app up end to end. It was recorded in 2024, so it predates the WhatsApp consent field added on August 6, 2026 and any interface changes since — treat it as the shape of the workflow rather than a current screenshot tour.

The Bottom Line

The most valuable half hour here is not another comparison table — it is opening the free app and rebuilding the form you already pay for. You will finish that half hour either with a working free form or with your boundary named in one sentence, and that sentence is what tells you which row of the price table you would actually be buying.

Frequently Asked Questions