---
title: List, remove, and update installed plugins
description: List, remove, and update installed Elasticsearch plugins on self-managed nodes with the CLI.
url: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/7959/deploy-manage/plugins-and-bundles/self-managed/list-remove-update
products:
  - Elasticsearch
applies_to:
  - Self-managed Elastic deployments: Generally available
---

# List, remove, and update installed plugins
## List plugins

Retrieve the currently loaded plugins with the `list` option:
```sh
sudo bin/elasticsearch-plugin list
```

Alternatively, use the [nodes info API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-info) to find out which plugins are installed on each node in the cluster.

## Remove plugins

Plugins can be removed manually by deleting the appropriate directory under `plugins/`, or with the plugin script:
```sh
sudo bin/elasticsearch-plugin remove [pluginname]
```

After a Java plugin has been removed, restart the node to complete the removal.
By default, plugin configuration files (if any) are preserved on disk so configuration is not lost while upgrading a plugin. To purge configuration files while removing a plugin, use `-p` or `--purge`. You can also use this option after a plugin is removed to clean up lingering configuration files.

## Remove multiple plugins

Remove multiple plugins in one invocation:
```sh
sudo bin/elasticsearch-plugin remove [pluginname] [pluginname] ... [pluginname]
```


## Update plugins

Except for text analysis plugins created using the [stable plugin API](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/extend/creating-stable-plugins), plugins are built for a specific version of Elasticsearch and must be reinstalled each time Elasticsearch is updated.
```sh
sudo bin/elasticsearch-plugin remove [pluginname]
sudo bin/elasticsearch-plugin install [pluginname]
```