Title: wp block template list
Published: January 7, 2026
Last modified: May 31, 2026

---

# 󠀁[wp block template list ](https://developer.wordpress.org/cli/commands/block/template/list/)󠁿

Lists block templates or template parts.

## In this article

 * [Options](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#options)
 * [Available Fields](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#available-fields)
 * [Examples](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#examples)
 * [Global Parameters](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#global-parameters)

[ Back to top](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#wp--skip-link--target)

 [ ⌊GitHub⌉ ](https://github.com/wp-cli/block-command)

 [ View Open Issues (0) ](https://github.com/login?return_to=%2Fissues%3Fq%3Dlabel%3Acommand%3Ablock-template-list+sort%3Aupdated-desc+org%3Awp-cli+is%3Aopen)
[ View Closed Issues (0) ](https://github.com/login?return_to=%2Fissues%3Fq%3Dlabel%3Acommand%3Ablock-template-list+sort%3Aupdated-desc+org%3Awp-cli+is%3Aclosed)
[Create New Issue](https://github.com/wp-cli/block-command/issues/new)

### 󠀁[Options](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#options)󠁿

 See the [argument syntax](https://make.wordpress.org/cli/handbook/references/argument-syntax/)
reference for a detailed explanation of the syntax conventions used.  [--type=<type
>] Template type. 
—default: wp_template options: – wp_template – wp_template_part—[--
slug=<slug>] Filter by template slug(s). Accepts a single slug or comma-separated
list. [--area=<area>] For template parts, filter by area (header, footer, sidebar,
uncategorized). [--post-type=<post-type>] Filter templates by post type they apply
to. [--source=<source>] Filter by source (theme, plugin, custom). [--field=<field
>] Prints the value of a single field for each template. [--fields=<fields>] Limit
the output to specific template fields. [--format=<format>] Render output in a particular
format. —default: table options: – table – csv – json – count – yaml – ids—

### 󠀁[Available Fields](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#available-fields)󠁿

 These fields will be displayed by default for each template:

 * id
 * slug
 * title
 * source
 * type

 These fields are optionally available:

 * theme
 * description
 * status
 * origin
 * is_custom
 * has_theme_file
 * author
 * area (template parts only)
 * content

### 󠀁[Examples](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#examples)󠁿

    ```
    # List all templates
    $ wp block template list

    # List template parts for the header area
    $ wp block template list --type=wp_template_part --area=header

    # List templates from the theme
    $ wp block template list --source=theme

    # List specific templates by slug
    $ wp block template list --slug=single,archive

    # List templates for a specific post type
    $ wp block template list --post-type=page

    # Export templates as JSON
    $ wp block template list --format=json
    ```

### 󠀁[Global Parameters](https://developer.wordpress.org/cli/commands/block/template/list/?output_format=md#global-parameters)󠁿

 These [global parameters](https://make.wordpress.org/cli/handbook/config/) have
the same behavior across all commands and affect how WP-CLI interacts with WordPress.

  |  **Argument** |  **Description** |  
   |  `--path=<path>` |  Path to the WordPress files. |  
 |  `--url=<url>` |  Pretend request came from given URL. In multisite, this argument is how the target site is specified. |  
 |  `--ssh=[<scheme>:][<user>@]<host\|container>[:<port>][<path>]` |  Perform operation against a remote server over SSH (or a container using scheme of “docker”, “docker-compose”, “docker-compose-run”, “vagrant”). |  
 |  `--http=<http>` |  Perform operation against a remote WordPress installation over HTTP. |  
 |  `--user=<id\|login\|email>` |  Set the WordPress user. |  
 |  `--skip-plugins[=<plugins>]` |  Skip loading all plugins, or a comma-separated list of plugins. Note: mu-plugins are still loaded. |  
 |  `--skip-themes[=<themes>]` |  Skip loading all themes, or a comma-separated list of themes. |  
 |  `--skip-packages` |  Skip loading all installed packages. |  
 |  `--require=<path>` |  Load PHP file before running the command (may be used more than once). |  
 |  `--exec=<php-code>` |  Execute PHP code before running the command (may be used more than once). |  
 |  `--context=<context>` |  Load WordPress in a given context. |  
 |  `--[no-]color` |  Whether to colorize the output. |  
 |  `--debug[=<group>]` |  Show all PHP errors and add verbosity to WP-CLI output. Built-in groups include: bootstrap, commandfactory, and help. |  
 |  `--prompt[=<assoc>]` |  Prompt the user to enter values for all command arguments, or a subset specified as comma-separated values. |  
 |  `--quiet` |  Suppress informational messages. |

 _Command documentation is regenerated at every release. To add or update an example,
please submit a pull request against the corresponding part of the codebase._