Skip to main content
wp-config.org

WordPress

WordPress WP-CLI command builder

Create a WordPress site or prepare plugin, theme, user and maintenance commands. Review the explained steps and run them yourself as the site owner.

  • 23 task types
  • Passwords asked in the terminal
  • Backup reminders

Free, no sign-up. It runs in your browser, so nothing you type is sent to this site.

Nothing you enter leaves your browser.

This tool runs in your browser and needs JavaScript. Turn JavaScript on and reload the page.

WP-CLI commands

What you can do

  • Fresh WordPress download, configuration and install

  • Plugin and theme installs, activation and management

  • User, database, media, content and multisite tasks

  • Maintenance, cron, cache, options and permalink commands

  • Address change dry runs and password prompts in the terminal

  • Quoted command previews with scope and backup notes

How to use it

  1. Choose the task

    Pick the task and action. Enter the full path to the WordPress folder and, for an existing site, the site address the commands are for.

  2. Fill in the details

    Complete the fields for that task. A new site needs a database user and the site details; passwords are asked for in the terminal. Check which files or database tables the task changes.

  3. Run one step at a time

    Copy the commands and run them one at a time as the site owner, stopping if one fails. Keep backups, test on staging and read a migration dry run before you turn on its write command.

Commands you run yourself

This free WP-CLI command builder prepares the commands for a new WordPress site and for everyday plugin, theme, user and maintenance work. Each step is explained, and the commands are written so they are safe to paste: values are quoted and passwords are asked for in your terminal.

Know the limits

Commands are built in this browser and are never run or saved by this website. Setting up WordPress does not create a database user, DNS records, web server routing, HTTPS or file ownership. On multisite, plugin and theme files and some database work affect every site, even with --url. Backups need both the files and the database, and checking core checksums is not a malware scan.

Read the WP-CLI command reference for every option.

Frequently asked questions

Does “Create a WordPress site” provision a server?

It prepares the application steps: download core, create the configuration, optionally create a database, install WordPress and optionally install packages. Your host must provide the database user, document root, file ownership, DNS and HTTPS routing.

Where do I enter passwords?

In your own SSH terminal when WP-CLI asks for them. Database and account passwords are never entered into this form or written into its commands.

How do I add plugins and a theme?

Choose Manage plugins or Manage themes, select Install and enter repository slugs or trusted ZIP paths. Choose activation deliberately. A fresh-site plan can include selected packages after core installation. Commercial licenses and parent-theme requirements remain your responsibility.

How do I use this on multisite?

Use the target site URL for site-context commands. Network activation and theme enabling have an explicit network scope. Package files are shared, and prefix-wide search and replace can affect several sites; a target URL does not isolate those operations.

Can I paste the whole output into a terminal?

Review and run one command at a time. Stop and fix any error before moving on. Keep file and database backups; the migration write command stays commented out until you deliberately uncomment it.

Related tools