Theme menu block limits (16-50 items): when your catalog outgrows the theme

You’ve just finished organizing your summer catalog. Forty-three new collections are ready to go, each linked to a curated product set. You open the Shopify theme editor, navigate to your header mega menu section, and start adding blocks for each collection. You add the first 16 without issues. Then, when you click “Add block” for the 17th, nothing happens. The button is grayed out. Your theme has hit its block limit, and seven of your new categories have no way to appear in the menu.

This scenario plays out every day in stores running popular themes like Dawn, Prestige, Impact, and Impulse. Each theme sets its own maximum number of blocks per section, and those limits are often lower than what growing catalogs demand. Understanding where these limits come from — and when they become a real problem — saves hours of frustration and prevents the invisible revenue loss of hidden categories.

What block limits actually are

Shopify Online Store 2.0 introduced a section-and-block architecture that governs how themes render content. Every section (header, footer, hero banner, product grid) can contain a fixed number of blocks. Each block represents one configurable element — a menu link, an image, a heading, a promotional banner within a mega menu panel.

The platform itself caps blocks at 50 per section — this is a Shopify-level limit documented in their theme architecture changelog. But themes rarely allow the full 50. Theme developers set a max_blocks value in their section schema that determines how many blocks are available. The reasons for restricting this vary:

Performance stability. Each block adds DOM elements and configuration data. At higher counts, the theme editor slows down, preview rendering takes longer, and less experienced merchants face confusing admin interfaces.

Visual design assumptions. Theme designers build mega menu layouts assuming a certain number of items. A mega menu designed for 16 items might use a 4-column layout where each column holds 4 items. Adding a 17th item would break the grid, push content below the fold, or create an unbalanced visual layout.

Quality assurance scope. Testing a theme across all possible block configurations is expensive. By capping blocks at 16 or 20, theme developers can thoroughly test every possible layout combination and guarantee it looks good. At 50 blocks, the number of layout permutations makes comprehensive testing impractical.

Block limits in popular Shopify themes

Here’s how block limits play out in themes that Shopify stores commonly use:

These numbers are deceptive because not every block is a menu link. In most themes, a single mega menu panel might use blocks for:

• Menu item links (one block per link)
• Section headings (one block per heading)
• Featured images or promotional banners (one block per image)
• Collection cards or product spotlights (one block each)

A mega menu panel with two headings, two promotional images, and 12 collection links uses 16 blocks — the maximum in Prestige — even though only 12 actual menu links are visible. Add one more collection link, and you’re over the limit.

How to tell if block limits are hurting your store

Block limits create a specific kind of problem: invisible categories. Unlike a broken layout or a slow page, the damage from missing menu items is silent. Shoppers simply never discover categories that don’t appear in the menu, and you never hear about the products they didn’t know existed.

Here are the signs:

Your menu doesn’t reflect your full catalog structure. Open your Shopify admin and list all your active collections. Then open your store’s navigation menu. If there’s a gap — collections that exist but don’t appear in any menu — you’ve likely hit a block limit or made a conscious choice to hide categories. Either way, those hidden categories are invisible to shoppers who browse by menu (roughly 69% of online shoppers, according to Baymard Institute research).

You’re making category compromises to fit the limit. Are you grouping unrelated collections under a vague heading like “More” or “Other” to save menu slots? Are you combining “Running Shoes” and “Walking Shoes” into a single “Athletic Shoes” category because you can’t afford two blocks? These compromises trade discoverability for convenience.

Your mega menu looks different on different pages. Some store owners create multiple menu configurations — showing different category subsets on different pages — to work around block limits. This inconsistency confuses shoppers who expect the menu to look the same everywhere.

You’ve stopped adding new collections to the menu. This is the clearest signal. If you create new collections but don’t add them to the navigation because “there’s no room,” block limits are actively constraining your store’s growth.

Your site search shows high usage for category-related terms. If shoppers search for collection names like “outdoor jackets” or “kitchen appliances” that should be browsable categories, it means they can’t find those categories in the menu. Review your site search analytics — if category-level terms appear frequently in search queries, your menu isn’t surfacing those categories effectively.

The math: when block limits cost you revenue

Quantifying the impact of missing menu items requires some assumptions, but the framework is straightforward.

Suppose your store has 35 active collections but your theme’s mega menu only displays 20 due to block limits. That means 15 collections — roughly 43% of your catalog — are not directly accessible from the main menu. Shoppers can still reach these collections through search, direct links on collection pages, or browsing through broader parent categories, but each alternative path adds friction.

Research from the Baymard Institute shows that categories not visible in the main navigation see significantly lower engagement, often 30–50% less traffic compared to menu-visible categories. If those 15 hidden collections average $2,000/month in revenue each (when properly exposed), and hiding them reduces traffic by 35%, you’re losing roughly $10,500/month — $126,000/year — in potential revenue from navigation friction alone.

The numbers scale with your catalog. A store with 60 collections hitting a 16-block limit is hiding 44 collections. Even conservative estimates suggest significant lost revenue from categories that shoppers simply never discover.

Working around block limits within your theme

Before switching to an app, there are legitimate ways to stretch your theme’s limits:

Consolidate menu headings and images. If your mega menu uses blocks for section headings and promotional images, removing some of these frees up slots for actual category links. A heading that says “Shop by Category” is taking a block that could be a direct link to a collection. Shoppers don’t need to be told they’re looking at categories — the context is obvious.

Use fewer promotional blocks. Featured product images and seasonal banners in the mega menu look attractive, but each one consumes a block. During periods when you need maximum category visibility (seasonal launches, sales events), temporarily replace promotional blocks with category links.

Restructure your category hierarchy. Sometimes the real problem isn’t the block limit — it’s an over-granular category structure. If you have separate collections for “Blue T-Shirts,” “Red T-Shirts,” and “Green T-Shirts,” consolidating them into “T-Shirts” and using product filters for color reduces your block usage without losing functionality.

Edit the theme code to increase the limit. If you have access to a developer, the max_blocks value in the theme’s section schema can be increased. Open the relevant .liquid section file, find the max_blocks parameter, and increase it. This is a low-risk code change, but be aware that:

• Increasing blocks beyond what the theme was designed for may cause layout issues
• Theme updates may overwrite your change
• Performance in the theme editor may degrade at higher block counts

Here’s what the code change looks like:

// In the theme's header section schema
{
  "name": "Mega menu",
  "max_blocks": 16  // Change this to 30 or 50
}

This works, but it’s a patch, not a solution. The layout was designed for 16 items, so adding 30 will likely create overflow issues that need additional CSS fixes.

When to move to a menu app

The decision point is clear when you’ve exhausted the workarounds:

You’ve consolidated categories and still don’t have enough blocks. If your category structure is already as lean as it can be and you’re still hitting limits, the theme simply can’t support your catalog.

You need blocks for both navigation and merchandising. If your mega menu strategy includes promotional images, featured products, and full category links, you’ll burn through blocks fast. Apps separate these concerns — the navigation structure lives in the app, and your mega menu can include rich merchandising content without sacrificing category coverage.

Your catalog grows seasonally. If you add 10–20 collections during holiday seasons and remove them after, constantly adjusting your menu to stay within block limits is a recurring maintenance burden. An app that renders categories dynamically from your collection list handles seasonal changes automatically.

Multiple staff members need to manage the menu. Apps typically offer visual editors that are easier to use than the theme editor’s block system. When non-technical team members need to add or reorganize menu items, an app’s drag-and-drop interface reduces errors and training time.

Apps like Navi+ render navigation independently of the theme’s block architecture, which means the 16-block or 50-block limit simply doesn’t apply. You define your menu structure in the app, and it renders directly on your storefront. The theme’s built-in header section still exists (for logo, search, and cart), but the navigation layer is entirely managed by the app.

Before you switchExport your current menu structure (screenshot or document every link and its nesting level) before installing an app. This gives you a baseline to replicate in the app and ensures no categories are lost during the transition.

Migrating from theme blocks to an app: what to expect

The migration from a theme mega menu to an app-managed menu typically takes 1–3 hours for a store with 20–50 collections. Here’s what the process involves:

1. Install and configure the app. Most menu apps provide an onboarding wizard that reads your existing Shopify menu structure and imports it.
2. Map collections to menu items. For collections that weren’t in the theme menu (because of block limits), add them to the app’s menu structure. This is the step where you recover the hidden categories.
3. Configure the layout. Choose the mega menu style, column count, and any promotional elements. Apps typically offer multiple layout options that adapt to item count.
4. Test on mobile and desktop. Verify the menu renders correctly across devices. Pay attention to mega menu panel sizing, scroll behavior, and tap targets on mobile.
5. Disable the theme’s built-in menu. Most apps provide instructions for hiding the theme’s native navigation to avoid duplicate menus.

The most common issue during migration is duplicate menus — the theme’s built-in navigation showing alongside the app’s menu. This happens when the theme’s header section isn’t properly configured to hide its navigation. Most apps include theme-specific documentation for handling this, and support teams can help with the toggle.

After migration, monitor your analytics for 2–4 weeks. Look for changes in:

• Collection page traffic (should increase for previously hidden categories)
• Mobile navigation engagement (more taps, lower bounce rate)
• Site search volume for category terms (should decrease as categories become menu-visible)

If the numbers improve — and the research suggests they will for stores that were hitting block limits — the app has paid for itself.

This article is part of the larger guide on Shopify theme menu limitations: when to use a menu app instead.