Title: wp post block extract
Published: October 6, 2026
Last modified: October 28, 2026

---

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

Extracts data from blocks.

## In this article

 * [Options](https://developer.wordpress.org/cli/commands/post/block/extract/?output_format=md#options)
 * [Examples](https://developer.wordpress.org/cli/commands/post/block/extract/?output_format=md#examples)
 * [Global Parameters](https://developer.wordpress.org/cli/commands/post/block/extract/?output_format=md#global-parameters)

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

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

>  **Note:** This command is not part of a stable WP-CLI release yet. To use it 
> now, [switch to the nightly build](https://make.wordpress.org/cli/handbook/guides/installing/#updating-wp-cli)
> with `wp cli update --nightly`. If you installed the command as a separate package,
> updating that package may be enough.

 Extracts specific attribute values or content from blocks for scripting.

### 󠀁[Options](https://developer.wordpress.org/cli/commands/post/block/extract/?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.  <id> The ID
of the post. [–block=<block-name>] Filter by block type. [–index=<index>] Get from
specific block index. [–attr=<attr>] Extract specific attribute value. [–content]
Extract innerHTML content. [–format=<format>] Output format. — default: json options:–
json – yaml – csv – ids —

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

    ```
    # Extract all image IDs from the post (one per line).
    $ wp post block extract 123 --block=core/image --attr=id --format=ids
    456
    789
    1024

    # Extract all image URLs as JSON array.
    $ wp post block extract 123 --block=core/image --attr=url --format=json
    ["https://example.com/img1.jpg","https://example.com/img2.jpg"]

    # Extract text content from all headings.
    $ wp post block extract 123 --block=core/heading --content --format=ids
    Introduction
    Getting Started
    Conclusion

    # Get the heading level from the first block.
    $ wp post block extract 123 --index=0 --attr=level --format=ids
    2

    # Extract all heading levels as CSV.
    $ wp post block extract 123 --block=core/heading --attr=level --format=csv
    2,3,3,2

    # Extract paragraph content as YAML.
    $ wp post block extract 123 --block=core/paragraph --content --format=yaml
    - "First paragraph text"
    - "Second paragraph text"

    # Get all button URLs for link checking.
    $ wp post block extract 123 --block=core/button --attr=url --format=ids
    https://example.com/signup
    https://example.com/learn-more

    # Extract cover block image IDs for media audit.
    $ wp post block extract 123 --block=core/cover --attr=id --format=json
    ```

### 󠀁[Global Parameters](https://developer.wordpress.org/cli/commands/post/block/extract/?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”). |  
 |  `--ssh-args=<args>` |  Pass additional arguments to SSH (or other tools specified by –ssh scheme). |  
 |  `--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. |  
 |  `--alias=<name>` |  Name of the alias to use. Aliases can reference local WordPress installations or remote SSH connections. Aliases are defined in the wp-cli.yml file. |  
 |  `--assume-https` |  Set $_SERVER[‘HTTPS’] to make WordPress treat the site as HTTPS. Use when WordPress is behind an HTTPS proxy or load balancer. |

 _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._