> For the complete documentation index, see [llms.txt](https://docs.exavault.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exavault.com/files-and-folders.md).

# Files and Folders

ExaVault stores files and folders in a case-sensitive file system. The behavior below is consistent across the current appliance implementation. Client applications can add their own naming restrictions or conflict behavior, so test important automated workflows with the same protocol and client they will use in production.

## Names Are Case-Sensitive

ExaVault preserves the case of file and folder names and compares names case-sensitively. `Report.csv` and `report.csv` can therefore exist in the same folder as different files.

This behavior is different from Files.com, whose cloud file system compares names case-insensitively. A migration or transfer from ExaVault to a case-insensitive destination can create a conflict when two ExaVault items differ only by letter case.

## Paths and Special Names

The forward slash (`/`) separates folders and cannot be part of a single file or folder name. ExaVault normalizes path components: `.` refers to the current folder, `..` refers to the parent, repeated slashes are collapsed, and trailing slashes are removed.

The current appliance can store names that some client operating systems reject, including a backslash or a trailing space. For interoperability with Windows and third-party transfer tools, avoid backslashes, control characters, and names ending in a space or period even when ExaVault accepts them.

## Overwrites, Moves, and Renames

Uploading or writing to an existing file can replace its contents. ExaVault records the first write as a create event and a subsequent replacement as a write or overwrite event. Configure [Notifications](/notifications.md) for both event types when you need to observe new and replaced files.

An ordinary move or rename does not replace an item that already exists at the destination; ExaVault reports a destination conflict. A workflow that intentionally overwrites must explicitly use an operation or client behavior that supports it.

Moving or renaming an item keeps ExaVault records attached to that item in sync. For example, a Share Link continues to target the moved item. Deleting the item removes a Share Link that targets it.

## Checksums

The web interface can calculate a checksum for a selected file. Current ExaVault releases support MD5, SHA-1, SHA-256, SHA-512, and CRC32. Use the same algorithm at both ends of a transfer when comparing values.

A matching checksum confirms that two byte sequences match for the selected algorithm. It does not prove who supplied the file or replace a digital signature when origin authenticity is required.