themes

The themes commands show the WordPress themes of one environment and update them through Kinsta. They work exactly like the plugins commands. To look across all sites of the company, see kinstactl company themes.

kinstactl themes list my-site --env live
kinstactl themes list my-site --env live --updates
kinstactl themes update my-site --all --env live

themes list

List the themes of an environment.

kinstactl themes list my-site --env live --updates

kinstactl themes list [site] [options]

List the themes of an environment

Arguments

Argument	Description
site	site name or ID

Options

Option	Description
--env <env>	environment name or ID
--updates	only themes with an update available

Global options --profile, --json and --no-input apply too. See scripting and CI.

Kinsta API: GET /sites/environments/{env_id}/wp-themes

The table shows each theme with its status, version, the version it can be updated to and whether the installed version is known to be vulnerable. --updates keeps only the themes with an update available.

themes update

Update one theme, or all themes with an update.

kinstactl themes update my-site twentytwentyfour --env live

kinstactl themes update <site> [name] [options]

Update one theme, or all themes with an update

Arguments

Argument	Description
site	site name or ID
name	theme name

Options

Option	Description
--env <env>	environment name or ID
--all	update every theme that has an update
--dry-run	print the resolved target and request; change nothing
--no-wait	return the operation ID instead of waiting
--timeout <minutes>	give up waiting after this many minutes (default 30)

Global options --profile, --json and --no-input apply too. See scripting and CI.

Kinsta API: GET /sites/environments/{env_id}/wp-themes, PUT /sites/environments/{env_id}/themes, PUT /sites/environments/{env_id}/themes/bulk-update

Pass either a theme name as shown by themes list, or --all, not both and not neither; both mistakes are USAGE errors. A theme that is not installed or already up to date also fails with a USAGE error, while --all with nothing to update just reports that all themes are up to date. Updates are not destructive and need no confirmation, but they do change a running site. Check what would be sent first with --dry-run:

kinstactl themes update my-site --all --env live --dry-run

Updating waits for Kinsta to finish by default, and accepts --no-wait and --timeout <minutes>; see operations.