documentation/Reference/Configuration/Flyway Namespace/Flyway Snapshot Namespace/Flyway Snapshot Filename Setting.md
{% include enterprise.html %}
Location used to store the snapshot as a result of the Snapshot command being invoked. The location type is determined by its prefix, and will be a file path if no prefix is specified.
Locations starting with <code>filesystem:</code> (or with no prefix) point to a file path on the filesystem. Relative paths will be resolved against your working directory.
Locations starting with <code>snapshotHistory:</code> point to the snapshot history table. They are in the format <code>snapshotHistory:<name></code>. The name is an optional field stored in the table which can be used to help look up snapshots if there are multiple entries ( see snapshot history limit). If the name is set to <code>current</code> or <code>previous</code>, it will be left blank, as these are treated as keywords when looking up snapshots.
<i>none - this is a required parameter for the snapshot command</i>
Note that when a snapshot is created as part of a deployment, using
deploy.saveSnapshot,
migrate.saveSnapshot,
or undo.saveSnapshot, the
default will be to store it in the snapshot history table with an automatically generated name, but this behavior can be
overridden using this setting.
This can't be added to a configuration file via Flyway Desktop.
./flyway snapshot -filename=flyway_snapshot.snp
[flyway.snapshot]
filename = "flyway_snapshot.snp"
flyway.snapshot.filename=flyway_snapshot.snp
FLYWAY_SNAPSHOT_FILENAME=flyway_snapshot.snp
The file extension .snp is not required, it is a convenience to help identify the file