Free or Paid Shopify Apps: What You Give Up

Free apps are the default starting point for most merchants, and the reasoning is sound — try it, see if it helps, pay if it does.

The complication is that the subscription is rarely the largest cost, and the costs that matter do not appear on an invoice. A free app that adds half a second to every product page is expensive; it simply bills you in conversion rather than in currency.

Which meter applies decides everything

Every free tier is limited by something, and the choice of meter matters far more than the headline number.

Metered by orders. You hit the ceiling as the business grows. This is the most predictable meter, and it has the advantage of arriving at the point when you can most easily afford to pay.

Metered by views or impressions. You hit it when the feature works. A popup app limited by impressions becomes expensive precisely because it is being seen, which is an awkward incentive.

Metered by products or items. You hit it when your catalogue grows, which may be soon and unrelated to revenue.

Metered by feature. The most common and the most consequential. The free tier does something adjacent to what you need, and the thing you actually want is on the paid plan.

That last row is worth noting. Some free tiers include no meaningful support, which is fine until you need it — and the moment you need support is the moment you have least patience for discovering you do not have any.

The costs that are not the subscription

Page weight. The main one. An app loading JavaScript on every page charges you on every visit whether or not anyone uses its feature. Free apps are not systematically heavier than paid ones, but a merchant who installs freely because the trial costs nothing accumulates weight faster.

Dependency. Every app is something that can break, change, be discontinued, or start charging. A free app doing something important is a business dependency with no contract behind it.

Uninstall residue. Apps that write into theme files frequently leave code behind. Trialling several free apps over a year can leave a theme carrying the debris of all of them.

Your attention. Every app is one more thing to configure, one more thing to understand, and one more candidate to eliminate when something on the store goes wrong.

A free app that becomes essential is a paid app with a delay

The pattern worth anticipating.

You install a free app, build a workflow around it, and it becomes part of how the store runs. Then you hit the meter, or the feature you need turns out to be paid, or the vendor changes the free tier.

At that point you have no leverage. The alternatives are paying whatever is asked or unpicking a workflow the business now depends on, usually at a moment you did not choose.

The prevention is straightforward and rarely done: before building anything on a free tier, find out where the ceiling is and what happens at it. If the answer is that you would have to pay, decide now whether that price is acceptable, because you will not be deciding freely later.

When paying is straightforwardly better

Four situations where the free option is a false economy.

The function is central to how you sell. A dependency this important should have a support relationship behind it.

You will hit the ceiling imminently. Building on a tier you are about to outgrow is work you will redo.

The paid app is lighter. This happens more than expected. A well-built paid app using theme app extensions and loading only where needed can cost you less in conversion than a free one loading globally.

You need support that answers. For anything touching checkout, payments or inventory, a support relationship is not a luxury — those are the areas where a problem costs you orders while you wait, and free tiers are precisely where support is thinnest.

A worked example of the actual comparison

Take a review app metered by number of monthly orders on its free tier, with a paid tier above that ceiling. The obvious comparison is the monthly fee against zero, and on that comparison free always wins.

The fuller comparison looks at what each tier actually loads and what it actually does. Say the free tier displays a basic star rating and loads a script on every product page regardless of whether a review exists yet. The paid tier adds photo reviews, a request-for-review email flow, and loads only on pages that have reviews to show. Now the paid tier is doing two things at once: adding a feature you might want, and reducing page weight on products that have nothing to display.

Work through the order-volume side first. If the store processes close to the free tier's ceiling already, the free plan is not really free, it is a paid plan starting next month, and building a workflow around it now means migrating that workflow later regardless of the feature comparison.

Then work through the weight side. If DevTools shows the review script loading on every product page including the ones with zero reviews, that is measurable page weight bought for a feature that, on those pages, displays nothing. A merchant with a thousand-product catalogue and a few hundred reviewed products is paying that cost on the majority of pages for no visible benefit.

Put the two findings side by side rather than in sequence. A free tier that is about to hit its order ceiling and is also loading unnecessary weight on unreviewed pages is not a marginal case. It is already costing more than the paid tier's monthly fee, just not in a place that shows up on an invoice. A free tier with headroom on its ceiling and a script that only loads where reviews exist is a genuinely different situation, and staying on it is the reasonable choice.

The general method transfers to any app category: price the meter against your real trajectory, price the weight against what DevTools actually shows loading, and only then compare that combined figure to the paid tier's fee. Comparing the fee alone answers the wrong question.

Genuinely free apps exist

Worth saying, because the section above is sceptical by design.

Some apps are free because the vendor monetises elsewhere — a paid tier aimed at larger merchants, an adjacent product, or the app functioning as an introduction to a service. Others are free because they are small, cheap to run, and built by someone who wanted them to exist.

These are legitimate, and some are excellent. The thing worth knowing is which arrangement applies, because it tells you how likely the free tier is to persist. An app that is free as a funnel into a paid product will stay free. An app that is free because nobody has worked out the business model may not.

Reading a pricing page properly

Pricing pages in the App Store are designed to be scanned, and the things that matter are usually not the things emphasised.

Find the meter first, not the price. The headline figures tell you what each tier costs. What you need is what moves you between them, and that is usually stated less prominently.

Check what happens at the limit. There are three possibilities and they differ enormously: the feature stops working, the app keeps working but stops counting, or you are automatically upgraded and billed. The third is the one to identify before it happens.

Look for per-unit charges on top of the tier. Some apps charge a subscription plus a cost per message, per verification, or per order processed. At volume the variable component can exceed the subscription substantially.

Check whether pricing scales with your Shopify plan. Some apps price by your store's plan rather than by usage, which means an unrelated upgrade increases your app costs.

Look at the gap between tiers. A jump from a small monthly fee to a much larger one, with nothing in between, means outgrowing the lower tier is a significant cost event rather than a gradual one.

Check the annual commitment terms. Discounted annual billing is common and reasonable, and it is also a year of commitment to an app you have used for a fortnight.

None of this takes long. Five minutes on a pricing page, done properly, prevents the most common app regret — which is not choosing a bad app but choosing a good one on terms that stopped working as the store grew.

A reasonable default

Start free where the app is genuinely peripheral and the ceiling is far away. Pay from the outset where the function is central, where support matters, or where the free tier's limitation would force an upgrade within months.

And review annually. Free apps accumulate more quietly than paid ones, precisely because nothing bills you for them — which means nothing prompts anyone to ask whether they are still needed.

That asymmetry is worth naming plainly, because it inverts the usual instinct. A paid app gets scrutinised every time someone looks at the invoice; a free one is invisible in every financial review a store ever does. The result is that the apps most likely to be sitting unused on a storefront, loading scripts and doing nothing, are almost always the free ones.

The practical response is to audit by what loads rather than by what costs. Open a product page in DevTools, look at what third parties appear, and check each against what you can actually point at on the storefront. That list includes the free apps your billing page never mentions, and it is where most of the recoverable page weight on a typical Shopify store turns out to be hiding.

For the wider app selection question, see Shopify apps. Page weight and its consequences are covered in storefront and design.