---
title: stack es snapshot delete cli command
description: Delete snapshots. Behaviour flags: --dry-run — validate all inputs and exit without performing any action 
url: https://www.elastic.co/elastic/docs-builder/docs/4089/reference/elastic-cli/cli/stack/es/snapshot/delete
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview
---

# stack es snapshot delete cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack es snapshot delete \
  --repository <repository> \
  --snapshot <snapshot> \
  [options]
```

Delete snapshots.
**Behaviour flags:**
`--dry-run` — validate all inputs and exit without performing any action

## Options

<definitions>
  <definition term="--repository string required">
    The name of the repository to delete a snapshot from.
  </definition>
  <definition term="--snapshot string required">
    A comma-separated list of snapshot names to delete.
    It also accepts wildcards (`*`).
    **Repeatable:** pass `--snapshot` multiple times to supply more than one value
  </definition>
  <definition term="--master-timeout string">
    The period to wait for the master node.
    If the master node is not available before the timeout expires, the request fails and returns an error.
    To indicate that the request should never timeout, set it to `-1`.
  </definition>
  <definition term="--wait-for-completion">
    If `false`, the request returns a response as soon as the deletes are scheduled.
    If `true`, the request returns a response when the matching snapshots are all deleted, and the post-deletion cleanup work associated with the request has completed.
    If you make several requests to the delete-snapshots API targetting overlapping collections of snapshots then some of those requests may perform different parts of the associated post-deletion cleanup work, returning their responses at different times.
    For example, if you make two requests to delete the same snapshot then sometimes all of the post-deletion cleanup work will be associated with the first request, delaying its response, while the second request has no associated post-deletion cleanup work and receives its response as soon as the snapshot has been deleted.
  </definition>
  <definition term="--error-trace">
    When set to `true` Elasticsearch will include the full stack trace of errors
    when they occur.
  </definition>
  <definition term="--filter-path string">
    Comma-separated list of filters in dot notation which reduce the response
    returned by Elasticsearch.
    **Repeatable:** pass `--filter-path` multiple times to supply more than one value
  </definition>
  <definition term="--human">
    When set to `true` will return statistics in a format suitable for humans.
    For example `"exists_time": "1h"` for humans and
    `"exists_time_in_millis": 3600000` for computers. When disabled the human
    readable values will be omitted. This makes sense for responses being consumed
    only by machines.
  </definition>
  <definition term="--pretty">
    If set to `true` the returned JSON will be "pretty-formatted". Only use
    this option for debugging only.
  </definition>
  <definition term="--input-file string">
    path to a JSON file to use as command input
  </definition>
  <definition term="--dry-run">
    validate all inputs and exit without performing any action (preview changes without applying them)
  </definition>
  <definition term="--yes">
    confirm destructive action without prompting
  </definition>
</definitions>


## Global Options

<definitions>
  <definition term="--json">
    output as JSON
  </definition>
</definitions>