Title: wp plugin activate
Published: February 5, 2018
Last modified: October 14, 2026

---

# 󠀁[wp plugin activate ](https://developer.wordpress.org/cli/commands/plugin/activate/)󠁿

Activates one or more plugins.

## In this article

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

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

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

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

>  **Note:** The following options are not part of a stable WP-CLI release yet: `--
> force`. To use them 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.

 Options added later: `--exclude` (2.7.0).

### 󠀁[Options](https://developer.wordpress.org/cli/commands/plugin/activate/?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.  [<plugin>…]
One or more plugins to activate. [–all] If set, all plugins will be activated. [–
exclude=<name>] Comma separated list of plugin slugs to be excluded from activation.[–
network] If set, the plugin will be activated for the entire multisite network. [–
force] If set, deactivates and reactivates the plugin to re-run activation hooks,
even if already active.

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

    ```
    # Activate plugin
    $ wp plugin activate hello
    Plugin 'hello' activated.
    Success: Activated 1 of 1 plugins.

    # Activate plugin in entire multisite network
    $ wp plugin activate hello --network
    Plugin 'hello' network activated.
    Success: Network activated 1 of 1 plugins.

    # Activate plugins that were recently active.
    $ wp plugin activate $(wp plugin list --recently-active --field=name)
    Plugin 'bbpress' activated.
    Plugin 'buddypress' activated.
    Success: Activated 2 of 2 plugins.

    # Activate plugins that were recently active on a multisite.
    $ wp plugin activate $(wp plugin list --recently-active --field=name) --network
    Plugin 'bbpress' network activated.
    Plugin 'buddypress' network activated.
    Success: Activated 2 of 2 plugins.

    # Force re-running activation hooks for an already active plugin.
    $ wp plugin activate hello --force
    Plugin 'hello' activated.
    Success: Activated 1 of 1 plugins.
    ```

### 󠀁[Global Parameters](https://developer.wordpress.org/cli/commands/plugin/activate/?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._