# How many Shopify apps is too many?

Source: https://merchantstackdaily.com/blog/2026-09-29-shopify-apps-too-many.html

Published September 29, 2026


September 29, 2026

There is no magic number, but there are clear warning signs. If two apps do the same job, if apps you forgot you installed are still billing, or if your storefront loads noticeably slower than it should, you have too many. Most lean stores run fine on eight to fifteen apps. Past twenty, almost every store is carrying dead weight.

## Why the count creeps up

Apps accumulate the way subscriptions do: one problem, one install, and nobody uninstalls the fix after the problem changes. A popup app from a 2023 campaign. A review app you replaced but never deleted. A loyalty app from a program you paused. Each one seemed small at install time. Together they are a second rent payment and a performance tax you pay on every page load.

The creep is invisible because installs are easy and audits are boring. Shopify makes adding an app a two-click job and gives you no nudge to revisit the decision. So the count only moves in one direction until something forces a reckoning, usually a slow site or a shocking app bill.

## The warning signs

Duplicate features are the biggest tell. Two upsell apps, two email capture tools, a theme that already does what the app does: redundancy means at least one of them is pure cost. Open your app list and group by job. Any job with two apps assigned is an immediate candidate for a cut.

Dead weight is the second. Sort your apps by last meaningful use, not install date. Anything you have not opened or configured in three months is either fully automated, in which case confirm it still works, or forgotten, in which case delete it. The apps billing you quietly are the most expensive ones per unit of value.

Performance is the third. Run your storefront through a speed test with apps active, then think about which apps inject storefront code: script tags, theme app extensions, pixels. Every one of them adds load time. A store that got noticeably slower over a year of installs is telling you the app count is the problem.

## The audit method

Once a quarter, export your app list and score each app on three questions. What job does it do, stated in one sentence. What would break if you removed it today. What it costs per month, including the performance cost. Anything without a clear one-sentence job goes. Anything whose removal breaks nothing goes. Anything expensive whose job a cheaper app or theme feature covers gets replaced.

Do the audit on a duplicate theme first when removing storefront apps, the same way you would test any theme change. Delete, check the storefront, confirm nothing visual broke, then keep the change. Removals are reversible for a short window, but testing first is still cheaper than discovering a broken checkout later.

## What a healthy stack looks like

Most lean stores converge on the same shape: email and SMS, reviews, one upsell or bundling tool, search and merchandising if the catalog is large, loyalty if repeat purchase matters, plus two or three utilities for shipping, taxes, or accounting. Everything else should have to argue for its place every quarter.

The number is a symptom, not the disease. Ten well-chosen apps beat five random ones. Judge the stack by coverage and cost, not by count, and keep the audit on the calendar. The stores with the cleanest stacks are not the ones that installed carefully. They are the ones that delete regularly.

They are the ones that delete regularly. Put the audit on the calendar now, while you are thinking about it, because the stores that skip it are the ones that wake up with thirty apps and no idea what half of them do.

## Frequently asked questions

### How many Shopify apps is too many for a store?

There is no universal number, but the warning signs are consistent: apps whose function nobody on the team can name, overlapping apps doing the same job, and site wide scripts from apps used on one page. Many healthy stores run somewhere in the teens to twenties of apps with each one owned and earning its place. The count matters less than the audit: every app should be able to answer what it does and what it returns.

### Do more apps always slow a store down?

Not automatically. Apps built on modern extension points and confined to the pages they serve can cost almost nothing in speed, while one old app injecting heavy scripts site wide can cost more than ten tidy ones. The damage comes from unexamined accumulation: leftover code from uninstalled apps, duplicate trackers, and widgets loading everywhere by default. Test the pages that make money, product and collection pages, and judge apps by their script weight there.

### What is the right way to prune an app stack?

Quarterly, with data. List every app, its cost, its owner, and the last time its output was checked. Disable, do not delete, the doubtful ones first and watch the metrics they supposedly support for a full cycle. Remove what nothing misses, clean out leftover theme code, and record why each surviving app stays. Pruning done this way rarely hurts revenue and regularly returns speed, which is the closest thing to a free conversion improvement most stores have.
