Overwrite Behavior Setting for Web Interface

By default, when a file is uploaded to the Web Interface and a file of the same name already exists, Files.com renames the new file by appending a digit to the filename. This default protects against accidental data loss when dragging and dropping files. The way the Files.com platform handles case sensitivity also affects overwrite behavior.

Site administrators can configure a setting so that users instead receive a prompt asking whether to overwrite the file or cancel the upload. To enable the setting, type "Overwrite behavior" in the search box at the top of every page and select the matching result.

This is a site-wide setting and cannot be customized by folder. Having different overwrite behavior in different folders is too confusing, so Files.com does not support that.

Where This Setting Is Used

This setting governs upload name collisions, and it applies to authenticated users on the Web Interface and to inbound AS2 transmissions. It does not apply to uploads made via the API, SDKs, FTP, SFTP, Zapier, or other integrations. Copy and Move operations have separate overwrite settings: per action in Automations v1 and per node in Automations v2.

Web uploads with duplicate names to Inboxes trigger automatic renaming, even if the site-wide overwrite behavior is "Allow files to be overwritten, but ask first". Inbox email uploads follow the site-wide setting: they rename duplicates when automatic numbering is selected and overwrite them without a prompt when overwrites are allowed.

Duplicate uploads to Share Links depend on the link's allowed actions. Links that allow only uploads or both downloads and uploads always rename the new upload when its filename is already in use, preserving both files.

These visitors can add files but cannot replace existing ones, regardless of the upload client or the site-wide overwrite setting. Full access links allow visitors to replace existing files and follow the site-wide overwrite behavior.