Theme blocks support the `{% schema %}` Liquid tag. This tag is used to define the following block attributes and settings: - [`name`](#name) - [`settings`](#settings) - [`blocks`](#blocks) - [`presets`](#presets) - [`tag`](#tag) - [`class`](#class) These attributes and settings enable different customization options and preconfigurations of the block inside the theme editor. The following is an example of a block schema that opts-in to supporting nested blocks with its `block` attribute, defines some background-related `settings`, and assembles different variations of those settings with its `presets` attribute:

Each block can have only a single `{% schema %}` tag, which must contain only valid JSON and can only use the attributes listed below. The schema tag can be placed anywhere within the block file, but it can’t be nested inside another Liquid tag. It doesn’t output its contents, or render any Liquid included inside it. > Caution > Having more than one `{% schema %}` tag, or placing it inside another Liquid tag, will result in an error. ## name The `name` attribute determines the block title that's shown in the theme editor. For example, the following schema returns the following output: ```json {% schema %} { "name": "Slide" } {% endschema %} ```

### Showing dynamic block titles in the theme editor In specific cases, the theme editor can display an input setting value as the title of a block in the theme editor sidebar. This can help merchants to identify and rearrange blocks in a section. The theme editor checks [the `id` values](/docs/storefronts/themes/architecture/settings/input-settings#standard-attributes) of the settings in a block to determine the best one to use for the block title. The theme editor uses settings with the following `id` values, in the following order of precedence: 1. `heading` 2. `title` 3. `text` If a setting with a matching `id` value doesn't exist, then the block name is used as the title. For example, the following block with a setting `id` of `text` displays in the sidebar with the title `Welcome to our store`.

## settings You can create block-specific [settings](/docs/storefronts/themes/architecture/settings/input-settings) to enable merchants to customize the block with the `settings` object:

> Caution: > All block setting IDs must be unique within each block. Having duplicate IDs within a block throws an error. ### Accessing block settings Block settings can be accessed through the [`block` object](/docs/api/liquid/objects/block#block-settings). Refer to [Access settings](/docs/storefronts/themes/architecture/settings#access-settings) to learn more. ## blocks Theme blocks can accept other app and theme blocks as children using the `blocks` attribute of their schema: ```json {% schema %} { "name": "Slide", "blocks": [{"type": "@app"}, {"type": "@theme"}] } {% endschema %} ``` The `"@app"` type denotes that this block accepts app blocks. [App blocks](/docs/storefronts/themes/architecture/blocks/app-blocks) enable app developers to create blocks for merchants to add app content to their theme without having to directly edit theme code. The `"@theme"` type denotes that this block is compatible with other theme-defined blocks that live in the `/blocks` folder of the theme. Theme blocks can also be made individually accessible by explicitly referencing them.

> Note > Unlike sections, which can define blocks locally using the blocks attribute of their schema, Theme blocks can't define local blocks in the `blocks` attribute of their schema. ### Rendering nested blocks You can render a block's child blocks by using the `{% content_for 'blocks' %}` Liquid tag: ```liquid
{% content_for 'blocks' %}
``` In the example above, each block's content is outputted by the `{% content_for 'blocks' %}` tag in the order stored in the [JSON template](/docs/storefronts/themes/architecture/templates/json-templates). > Tip > Theme blocks can be nested up to 8 levels deep, excluding the section level. ## presets Presets are default configurations of blocks that enable merchants to easily add a block to a JSON template through the theme editor. A block can have multiple different presets that combine its settings in a variety of different configurations. Additionally, presets of a block may reference other child blocks and assemble them in any number of configurations. Presets have the following attributes:
presets attributes
Attribute Description Required
name The preset name, which displays in the theme editor's Add section picker. Yes
settings A list of default values for any settings that you might want to populate. Each entry should include the setting name and the value. No
blocks A list of child blocks that you might want to include. Each entry should be an object with attributes of type and settings. The type attribute value should reflect the type of the block that you want to include, and the settings object should be in the same format as the settings attribute above. No
The following is an example of including presets in a block, assuming that the theme also contains a text block located in the `/blocks/text.liquid` Liquid file:

## tag By default, when Shopify renders a block, it’s wrapped in a `
` element with a unique `id` attribute: ```html
// Output of the block content
``` If you don’t want to use a `
`, then you can specify which kind of HTML element to use with the `tag` attribute. For example, the following schema returns the following output:

> Tip > The `tag` attribute accepts any string up to a limit of 50 characters. It can also be used to render custom HTML elements. ### Rendering blocks without a wrapper In some advanced use cases, you might want more control over the tag and the attributes that are passed to it. For example, dynamically setting a tag or class name based on the settings of the block. In these scenarios, you can render blocks without a wrapper by setting the `tag` attribute to `null`. When the `tag` attribute is set to `null`, Shopify doesn't wrap the contents of the block in a wrapper element, and instead directly outputs the contents of the block. > Warning > Blocks that make use of `“tag”: null` should contain a single top level HTML tag within the same Liquid file. Only a single HTML element can be tagged with `{{ block.shopify_attributes }}`. This element should be the topmost HTML element in the file. This is important to allow the theme editor to move the entirety of the block's markup to a new index when merchants re-order blocks without leaving orphaned HTML elements.

For blocks to be compatible with the theme editor, the top level HTML element must be tagged with the `{{ block.shopify_attributes }}` Liquid tag. This adds the necessary data attributes for the block to be identified by the theme editor. Shopify's theme editor uses that attribute to identify blocks in its [JavaScript API](/docs/storefronts/themes/architecture/sections/integrate-sections-with-the-theme-editor#javascript-events). > Note > Shopify automatically adds this attribute for you when it renders the wrapper around blocks, but when the `tag` attribute is set to `null`, you must ensure that the top level HTML element of your block has this attribute for it to be compatible with the theme editor. ## class When Shopify renders a block, it’s wrapped in an HTML element with the `shopify-block` class. You can append other classes by using the class attribute: