1---
2layout: "docs"
3page_title: "operator unseal - Command"
4sidebar_title: "<code>unseal</code>"
5sidebar_current: "docs-commands-operator-unseal"
6description: |-
7  The "operator unseal" allows the user to provide a portion of the master key
8  to unseal a Vault server.
9---
10
11# operator unseal
12
13The `operator unseal` allows the user to provide a portion of the master key to
14unseal a Vault server. Vault starts in a sealed state. It cannot perform
15operations until it is unsealed. This command accepts a portion of the master
16key (an "unseal key").
17
18The unseal key can be supplied as an argument to the command, but this is
19not recommended as the unseal key will be available in your history:
20
21```text
22$ vault operator unseal IXyR0OJnSFobekZMMCKCoVEpT7wI6l+USMzE3IcyDyo=
23```
24
25Instead, run the command with no arguments and it will prompt for the key:
26
27```text
28$ vault operator unseal
29Key (will be hidden): IXyR0OJnSFobekZMMCKCoVEpT7wI6l+USMzE3IcyDyo=
30```
31
32For more information on sealing and unsealing, please the [seal concepts
33page](/docs/concepts/seal.html).
34
35
36## Examples
37
38Provide an unseal key:
39
40```text
41$ vault operator unseal
42Key (will be hidden):
43Sealed: false
44Key Shares: 1
45Key Threshold: 1
46Unseal Progress: 0
47```
48
49## Usage
50
51The following flags are available in addition to the [standard set of
52flags](/docs/commands/index.html) included on all commands.
53
54### Output Options
55
56- `-format` `(string: "table")` - Print the output in the given format. Valid
57  formats are "table", "json", or "yaml". This can also be specified via the
58  `VAULT_FORMAT` environment variable.
59
60### Command Options
61
62- `-migrate` `(bool: false)` - Indicate that this share is provided with the intent that it is part of a seal migration process.
63
64- `-reset` `(bool: false)` - Discard any previously entered keys to the unseal
65  process.
66