Visit Website →
← Back to blog

WP-CLI Basics: 6 Copy-Paste Commands to Start Safely

October 4, 2026
WP-CLI Basics: 6 Copy-Paste Commands to Start Safely

WP-CLI is the command-line tool that lets you manage WordPress faster by running admin actions from a terminal instead of clicking through the dashboard. It covers nearly every admin action WordPress offers, from updating plugins to editing users, and it saves real time once you learn the pattern. Start with read-only commands and verify your setup with wp --info before you touch anything that writes to the database.

TL;DR:

  • WP-CLI allows for fast, scriptable management of WordPress sites, especially useful for bulk updates, migrations, and server provisioning.
  • Installation can be easily verified with wp --info, and it supports common platforms via a Phar build or package managers like Homebrew and Composer.
  • Commands follow a predictable structure with global parameters and output formats, and --help provides comprehensive argument information for each subcommand.
  • Recommended initial practice involves running read-only commands such as wp plugin list and testing search-and-replace with --dry-run before applying changes to live sites.
  • Using environment variables, config files, and remote SSH options helps streamline workflows and avoid repetitive typing or permission issues.
inSave Hosting
Run WordPress With Less Hassle
inSave Hosting provides WordPress hosting with easy installation, staging tools, free migration, and managed security features.
Explore WordPress hosting

Table of Contents

What is WP-CLI and when should you use it?

A command-line interface replaces mouse clicks with typed instructions, and WP-CLI applies that idea to WordPress specifically. Instead of opening the Plugins page and clicking "Update" ten times, you type one line and update ten plugins at once. The WP-CLI handbook describes the tool as aiming to provide a command equivalent for nearly every admin action available in the dashboard, which means almost anything you can do by hand, you can script.

That matters most in a few recurring situations: mass plugin or theme updates across many sites, scripted installs for new projects, search-and-replace during a domain migration, and regenerating thumbnails after a theme change. You do not need to be a developer to benefit.

  • Solo site owners save time on routine maintenance like updates and backups.
  • Agencies managing dozens of client sites use it to script repetitive setup work.
  • Developers and SREs lean on it for deployments, automated testing, and server provisioning.

How to install and verify WP-CLI on common platforms

The official recommendation is the Phar build, which works the same way across Linux, macOS, and most Unix-like environments.

  1. Download the Phar file: curl -O https://raw.githubusercontent.com/wp-cli/builds/gh-pages/phar/wp-cli.phar
  2. Confirm it runs: php wp-cli.phar --info
  3. Make it executable: chmod +x wp-cli.phar
  4. Move it into your PATH: sudo mv wp-cli.phar /usr/local/bin/wp
  5. Verify the install: wp --info

On macOS, brew install wp-cli handles the same steps automatically. Developers who prefer dependency management can add it to a project with Composer, and Windows users typically run it through a wrapper script or WSL rather than a native binary. Before any of this, check your PHP version with php --version since WP-CLI needs a supported release to run properly.

If the binary ends up owned by root, you may need sudo later to update it, so installing WP-CLI per user from the start avoids that friction, a point the installation guide calls out directly.

Pro Tip: Run wp --info right after installing, before anything else. If it prints your PHP version, WordPress path, and WP-CLI version cleanly, you're ready to move on.

Understanding WP-CLI command structure and syntax

WP-CLI command syntax structure illustration

Every WP-CLI command follows the same shape: wp plus a command, a subcommand, and then arguments. wp plugin list is the command plugin with the subcommand list. Run wp plugin update --help and you will see a synopsis showing which arguments are required and which are optional, usually marked with brackets for optional ones and no brackets for required ones.

A few patterns are worth memorizing early:

  • Global parameters like --path, --url, --user, and --ssh tell WP-CLI which WordPress install, site URL, or remote host to target, and they override anything set in a config file.
  • Output formats change how results print: add --format=table, --format=csv, --format=json, or --format=yaml to any list command depending on what you need to read or parse.
  • The --help flag works on any command or subcommand and shows every available argument, so when in doubt, add --help before you guess at syntax.

This structure is consistent across the entire tool, which is why learning it once pays off across hundreds of commands.

Common copy-paste commands every beginner should know

Start with commands that only read data, then move to writes once you trust the output. The WP-CLI handbook's quick-start guide recommends exactly this sequence for beginners building confidence.

  1. Check your site: wp plugin list and wp post list show current data with no risk of changing anything.
  2. Install WordPress core: wp core download followed by wp core install --url=example.com --title="My Site" --admin_user=admin --admin_password=strongpass --admin_email=you@example.com sets up a fresh site in two lines, a workflow documented in common tasks.
  3. Update everything at once: wp plugin update --all and wp theme update --all clear routine maintenance in seconds.
  4. Manage users: wp user create newadmin admin@example.com --role=administrator adds an account without touching the dashboard.
  5. Search and replace safely: wp search-replace 'oldsite.com' 'newsite.com' --dry-run previews every change during a migration before you commit with the same command minus --dry-run.
  6. Regenerate media: wp media regenerate --yes rebuilds thumbnails after a theme switch.

Pro Tip: Always run search-replace with --dry-run first. It shows you exactly what would change, which catches mistakes before they touch your live database.

Running WP-CLI on remote servers and local dev environments

Most real work happens on a server you reach over SSH, not your own laptop. You can SSH in directly and run wp as if it were installed locally, or use the --ssh=user@host flag to run commands from your machine against a remote site in one line. Setting up SSH on shared hosting takes a bit of initial configuration worth doing early.

  • Direct SSH gives you a full remote shell, useful for longer sessions or scripting on the server itself.
  • The --ssh= alias lets you stay on your local terminal while commands execute remotely, faster for one-off tasks.
  • Docker and Vagrant setups are supported too, though the remote shell sometimes skips profile files that set PATH, so wp may not be found unless you adjust it.
  • Aliases stored in a config file let you type wp @production plugin list instead of a full SSH string every time.

Config files, environment variables, and sensible defaults

Typing --path and --url on every command gets old fast. A project-level wp-cli.yml file or a global ~/.wp-cli/config.yml file lets you set those once and skip the flags afterward. WP-CLI reads these files in a defined order, checking the project folder before falling back to your home directory.

  • Config entries commonly set path, url, and server aliases for remote sites you manage often.
  • Environment variables like WP_CLI_CONFIG_PATH, WP_CLI_CACHE_DIR, and WP_CLI_PHP change where WP-CLI looks for config, where it caches data, and which PHP binary it runs.
  • Project defaults in wp-cli.yml keep deployment scripts short and consistent across a whole team.

Troubleshooting and a safety checklist before you run anything

Most WP-CLI errors trace back to the environment, not the tool itself. Checking PHP version, file permissions, and recent wp-config.php edits resolves the majority of issues before you need to dig further. Enabling WP_DEBUG in wp-config.php surfaces warnings that a silent failure would otherwise hide.

  • Check php --version first since an outdated PHP build breaks commands in confusing ways.
  • Use --dry-run on any destructive command, and back up your database before running the real version.
  • Test on staging before touching a production site, especially for search-replace or bulk updates.
  • Keep WP-CLI current with wp cli update, using sudo only if the binary is owned by root.

Pro Tip: If a command fails with no clear error, rerun it with --debug appended. It shows exactly where WP-CLI stopped.

I tell anyone starting out to run wp --info first, then spend a week on read-only commands like wp plugin list before writing anything. Once that feels routine, practice search-replace with --dry-run on a staging copy, keep a backup ready, and script the tasks you repeat most. A host that gives you SSH access and a staging environment out of the box makes this whole sequence noticeably smoother.

— Ihor

inSave Hosting: hosting plans that simplify using WP-CLI

WP-CLI works best when your hosting does not fight you on access. That means SSH enabled by default, a staging environment you can break safely, control over your PHP version, and backups that run before you need them, not after. InSave Hosting's WordPress hosting plans, including WP Start, WP Growth, WP Pro, and WP Agency, are built around exactly that combination, so running the commands in this guide does not require fighting your host's restrictions first.

inSave Hosting

If you are evaluating hosting as part of learning WP-CLI, check plan details and current pricing on the Managed WordPress Hosting for Small Business page before you commit a site to it.

FAQ

How do I use WP-CLI in WordPress?

Install WP-CLI, confirm it works with wp --info, then run a read-only command like wp plugin list to see your current plugins. From there, use wp core, wp plugin, wp theme, and wp user commands for the action you need, checking --help on any command you are unsure about.

What is WP-CLI and what is it used for?

WP-CLI is the command-line interface for WordPress, letting you manage a site by typing commands instead of clicking through the dashboard. It is used for updates, installs, user management, migrations, and any repetitive task worth scripting.

Is anyone still using WordPress?

WordPress remains one of the most widely used content management systems, and WP-CLI is actively maintained alongside it as part of the official project. Agencies and developers managing WordPress sites at scale rely on WP-CLI specifically because manual dashboard work does not hold up across many sites.

How do I run a CLI command?

Open a terminal, navigate to your WordPress site's root folder, and type a command starting with wp, such as wp plugin list. If you are working on a remote server, either SSH in first or prefix the command with --ssh=user@host to run it from your local machine.