Short description of issue
Shopify limits to 8 nested blocks in depth
Reproduction steps
Push blocks with 8> nested blocks
Additional info
Should increase this limite to 20
What type of topic is this
Feature request
Hey @Drop_Magic -
Just confirming that the current documented limit is 8 nested theme block levels, excluding the section level, so what you’re seeing lines up with the current platform limit.
Just out of curiosity, could you share a bit more about the structure you’re trying to build that needs up to 20 levels? A small example of the block tree, the merchant-facing use case would be helpful so I can pass this along a bit more exactly.
Also, can you confirm whether these are theme blocks in the /blocks folder, app blocks nested inside theme blocks, or section blocks? That distinction matters a little bit since the limits differ a bit depending on the block type.
Once we have that context, we can better understand whether this is a depth-limit gap or if there’s another recommended modeling approach. Hope to hear from you soon!
These are theme blocks (files in the theme’s /blocks folder), nested inside a single custom section via {% content_for ‘blocks’ %} with “blocks”: [{ “type”: “@theme” }]. Each block also accepts @theme children, so they nest recursively — which is where we hit the depth-8 cap. They are not app blocks and not legacy section blocks.
Use case: we’re a visual product-page builder that compiles a merchant’s authored layout tree into theme blocks 1:1. A rich product hero (variant pickers, selling-plan/subscription widgets, bundles) plus the page skeleton’s layout wrappers exceeds 8 levels.
We’re handling it on our side by flattening layout-only wrappers into plain s and falling back to inline HTML past depth 8…
Would love to discuss more about this hello@dropmagic.ai
Hey @Drop_Magic -
Thanks, that extra context helps a lot. Since these are recursive theme blocks in /blocks, nested through @theme inside a custom section, this does look like you’re running into the current theme block nesting limit rather than an app block or legacy section block difference.
Your current approach of flattening layout-only wrappers and falling back to inline HTML past the limit is the most practical workaround I can point to right now as well. I’m going to pass this along as feature feedback for the theme block depth limit, with the product-page-builder use case you shared.
If you have a small sanitized example of the block tree, especially the point where it crosses 8 levels, that would make the request easier to pass on on on our end ( I can set up a DM with you if you’d rather share it that way as well). Let me know if I can clarify anything here.
Hey Alan !
Thank you for your reply !
Let’s continue by DM
Loïc
Sounds good @Drop_Magic - I’ll DM you!