Browse VMFS Datastores in VMware vSphere

Learn how to find VMFS datastores, open the vSphere datastore browser, inspect virtual machine files, verify host access, and avoid unsafe file operations.

What a VMFS Datastore Is

VMFS stands for VMware File System. It is a clustered filesystem used by ESXi hosts to store and access virtual machine data. A datastore is the logical storage container that vSphere presents for virtual machine files, templates, ISO images, logs, and other related data.

VMFS supports coordinated access from multiple ESXi hosts. This makes it suitable for shared storage in clusters, where virtual machines may be run or migrated between hosts that can access the same datastore.

Object	Meaning	Example
Virtual machine	The complete virtual computer, including its virtual hardware, operating system, memory, and disks.	A Windows Server VM
Datastore	A logical storage container used by vSphere for VM files and related data.	VMFS-Production
Storage device or LUN	A storage volume presented by a storage system. It may be formatted with VMFS and then mounted as a datastore.	A Fibre Channel LUN or iSCSI volume
ESXi host	The VMware hypervisor that accesses datastores and runs virtual machines.	esxi-01

The storage relationship is usually: a storage system presents a volume or LUN to an ESXi host, the host recognizes the device through a storage adapter, and VMFS is mounted on the volume as a datastore. One VMFS datastore may be visible to one host or to several hosts.

For background on the broader platform, see VMware vSphere components.

Where to Browse Datastores in the vSphere Client

Datastore browsing is normally performed in the vSphere Client. The exact labels and available actions can vary by vSphere version, permissions, and whether the selected object is a vCenter inventory object or an individual ESXi host.

Storage inventory: Use the Storage view to list datastores, review their properties, and open a datastore browser.
Host context: Select an ESXi host and inspect its storage view to see which adapters, devices, volumes, and datastores are mounted on that host.
Virtual machine context: Select a VM to review its configured storage locations and virtual disks. This view identifies where the VM is configured to store files, but it is not the same as opening the complete datastore inventory.

To browse from the Storage inventory, open the vSphere Client, select Storage, choose a datastore, and open its Datastore Browser or file browser. In some versions, the browser is available from the datastore's actions menu or related files view.

Browsing requires permission to view the datastore and its files. File operations may require additional privileges, such as datastore browse, allocate space, write, or delete-file permissions. A user may be able to see a datastore without being allowed to upload, rename, move, or delete files. Use the least privilege needed for the task.

Finding the Correct VMFS Datastore

Open the vSphere Client and select the Storage inventory.
Review the datastore list and identify the datastore associated with the VM or task.
Check its type, capacity, free space, and host accessibility before opening it.
Filter or sort the list if the environment contains VMFS, NFS, vSAN, or other datastore types.
Select the intended datastore and open its file browser.

VMFS Datastore Information to Review
Property	What it indicates	Why it matters when browsing
Name	The vSphere inventory name of the datastore.	Prevents browsing or placing files on the wrong storage container.
Type	The datastore technology, such as VMFS or another supported type.	Confirms that the selected datastore is the expected VMFS datastore.
Capacity	Total logical space available to the datastore.	Provides context for file sizes and placement decisions.
Free space	Space currently available for new or expanded data.	Helps determine whether an upload, clone, migration, or disk expansion can succeed.
Hosts	ESXi hosts that can access or mount the datastore.	Indicates whether a VM can be run or migrated from each host.
Accessibility and status	Whether the datastore is mounted, accessible, read-only, or otherwise impaired.	Explains why browsing or file operations may fail.

When verifying space before placing a file, first review the datastore's capacity and free-space values. Then confirm the datastore name and use the browser to verify the destination folder. Free space alone does not guarantee that an operation is safe or that the user has sufficient write permission.

Opening and Navigating the Datastore Browser

Select the VMFS datastore in the Storage inventory.
Launch the datastore file browser.
Open folders by selecting them or using the browser's navigation controls.
Locate the folder associated with the virtual machine you are investigating.
Review names, sizes, timestamps, and file types without changing anything.
Refresh the browser if a recent upload, migration, snapshot change, or folder creation is not visible.

A typical datastore contains folders for virtual machines, templates, ISO images, backup staging, or administrative files. A VM folder often contains configuration, disk, log, firmware, snapshot, and swap files. Folder names commonly resemble VM display names, but they are not guaranteed to match exactly. Names may have changed, or the VM may have been migrated, cloned, renamed, or removed from inventory.

Example: Inspect a VM Folder

Open the Storage inventory and select the VMFS datastore reported by the VM's configuration.
Open the datastore browser and locate the suspected VM folder.
Identify the VMX configuration file, VMDK files, NVRAM file, and VMware log files.
Look for snapshot-related files, but do not delete, rename, or move them during inspection.
Refresh the view if the expected files are missing after a recent operation.

Datastore browsing is useful for inspection and troubleshooting. Treat the browser as a storage-management interface, not as a general-purpose file manager.

Common Virtual Machine Files

File names and extensions can vary with the VM configuration, virtual hardware version, snapshots, power state, and vSphere release. The following table describes common entries.

Common Files Found in a Virtual Machine Datastore Folder
File extension or pattern	Typical purpose	Safe handling guidance
`.vmx`	Virtual machine configuration, including virtual hardware and device settings.	Inspect when troubleshooting. Do not edit or remove it casually; use VM settings and supported registration workflows.
`.vmdk`	Virtual machine disk format. A disk may include a small descriptor file and separate data files, especially for some disk layouts.	Keep descriptor and data components together. Use migration, clone, disk extension, or other supported operations.
`.nvram`	Saved BIOS or UEFI firmware settings for the VM.	Usually inspect only. Preserve it when maintaining the VM's firmware state.
`.log`	VMware runtime log generated by the virtual machine.	Useful for troubleshooting. Avoid deleting active logs; follow an approved retention or support procedure.
Snapshot delta files, often containing snapshot or delta naming patterns	Records changes made after a snapshot. These files depend on the original virtual disk and may form a disk chain.	Never manually delete or rename them. Manage snapshots and consolidation through vSphere.
Snapshot metadata files	Describes snapshot relationships and virtual machine state.	Do not remove independently from the vSphere snapshot workflow.
`.vswp`	Virtual machine swap file, normally created while a VM is powered on.	Do not remove it from a running VM's folder. Its presence and size can change with VM power state and memory settings.
Other metadata and auxiliary files	Support locking, inventory, compatibility, or VM operation functions.	Assume an unknown file may be important until its ownership and purpose are confirmed.

A VMDK is a virtual disk file format, but it is not always one physically self-contained file. A descriptor can reference the data portion of the disk. Snapshot delta disks depend on a parent disk, so manipulating one component can make the entire disk chain unusable.

Datastore Browser Actions and Their Risks

Datastore Browser Actions and Risks
Action	Appropriate use	Potential impact	Preferred alternative when applicable
Upload	Place an approved ISO, template component, diagnostic file, or other known item on a verified datastore.	Consumes capacity and may fail or cause service impact if space is exhausted.	Use content libraries, image management, or an approved deployment workflow when available.
Download	Retrieve a permitted file for inspection, support, or recovery.	Large downloads consume time and bandwidth; sensitive VM data may be exposed.	Use backup or export procedures for complete VM recovery.
Create folder	Organize non-VM files or prepare a verified destination.	Can create confusion if names resemble production VM folders.	Use an agreed naming and storage organization standard.
Rename	Correct an administrative folder or file name when ownership and dependencies are known.	Can break VM registration, references, backups, or disk chains.	Rename or relocate VMs through supported vSphere workflows.
Move	Relocate an independent, non-active file when the destination and dependencies are verified.	Can disconnect a VM from its disks or interrupt backup and snapshot relationships.	Use Storage vMotion, migration, or another supported relocation operation.
Copy	Duplicate an approved file for a documented purpose.	Consumes capacity and does not necessarily create a usable VM backup or consistent disk copy.	Use clone or backup workflows for virtual machines.
Delete	Remove an explicitly identified, obsolete, non-dependent file after approval.	May cause data loss, break a VM, invalidate snapshots, or interfere with backups.	Use vSphere Delete from Disk, snapshot deletion, cleanup, or backup retention controls as appropriate.

Before any operation, verify the datastore name, target folder, file ownership, VM power state, snapshot state, and available backup or recovery path. Manual manipulation outside normal vSphere workflows can affect VM registration, snapshots, backups, and virtual disk chains.

Supported vSphere Workflows

Use the datastore browser primarily for inspection and carefully controlled file transfers. Prefer supported vSphere operations for VM lifecycle changes:

Use migration or Storage vMotion to move a VM and its storage.
Use clone to create a consistent VM copy rather than copying individual disk components.
Use the VM's supported Delete from Disk operation when permanently removing a VM and its files.
Use vSphere snapshot controls to delete snapshots or consolidate snapshot disks.
Use backup software and recovery procedures for backup and restore tasks.

For more context, review virtual machine files in ESXi, VM migration, reverting snapshots, and checking disk space.

Storage Visibility and Multi-Host Access

A shared datastore is accessible by more than one ESXi host. Shared access is important for clusters, high availability, and migrations. However, a datastore being visible in vCenter does not necessarily mean that every ESXi host can access it.

From an ESXi host's storage view, check the mounted datastores and confirm that the required hosts see the same VMFS datastore. The storage path includes several related layers:

A storage system provides a volume or LUN.
A storage adapter, such as an iSCSI or Fibre Channel adapter, exposes the storage to ESXi.
The ESXi host detects the device and mounts the VMFS volume.
vSphere presents the mounted volume as a datastore.
VM folders and files are stored inside the datastore.

If a host cannot see the datastore, it may be unable to power on a VM located there, register that VM, or participate in a migration that requires the datastore. Verify visibility on every host that is expected to run or access the VM.

Optional ESXi Shell Inspection

When GUI access is unavailable and authorized shell access is enabled, the ESXi shell can provide read-only-oriented inspection. These commands do not replace vSphere storage management.

esxcli storage filesystem list

The command lists filesystems and mounted volumes. After confirming the datastore name, a directory listing can inspect its top-level contents:

ls -la /vmfs/volumes/<datastore-name>

Use the shell for inspection only unless a documented, supported procedure specifically requires another action. Do not present shell-based file deletion as a standard way to manage VM files.

Troubleshooting Datastore Browsing

The VMFS Datastore Is Not Listed

Verify that the storage device or LUN is presented to the selected ESXi host.
Confirm that the storage adapter can see the device.
Perform a supported storage rescan when appropriate.
Check whether the datastore is mounted and accessible to the host.
Verify datastore browsing permissions for the administrator.

The VM Folder Cannot Be Found

Check the VM's configured datastore and disk locations.
Search other accessible datastores.
Confirm that the VM was not migrated, cloned, renamed, or removed from inventory.
Do not assume the folder name exactly matches the VM display name.
Refresh the browser after recent storage changes.

Browser Operations Fail or Are Unavailable

Verify datastore free capacity and accessibility.
Check whether the datastore is read-only or inaccessible.
Confirm permissions for browsing, allocating space, and deleting files.
Check whether a lock, active VM process, snapshot, or backup job makes the action unsafe.

Unexpected Snapshot or Disk Files Appear

Check whether vSphere reports snapshots for the VM.
Determine whether backup software is using temporary snapshots.
Do not manually remove delta disks, descriptors, or snapshot metadata.
Use supported snapshot deletion or consolidation procedures, and follow the backup product's guidance.

Operational Checklist

Identify the VM, its configured datastore, and the ESXi hosts that need access.
Confirm the datastore type is VMFS and review capacity, free space, and accessibility.
Open the datastore browser from the Storage inventory.
Navigate to the intended folder without changing files during inspection.
Refresh the browser when recent changes are not visible.
Confirm file ownership, VM power state, snapshot state, and backup coverage before any operation.
Use migration, clone, snapshot, backup, or Delete from Disk workflows instead of manual file manipulation whenever they apply.

For exam and support work, remember the distinction: a LUN or volume is storage presented by the storage system; VMFS formats that storage for ESXi; the datastore is the vSphere storage container; and the VM's files reside inside that datastore. Host visibility determines which ESXi hosts can use those files.