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 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.

Uploading duplicate names to Inboxes will trigger automatic renaming behavior rather than prompting the user for overwrites, even if the site-wide overwrite behavior is "Allow files to be overwritten, but ask first".

Duplicate uploads to Share Links will behave differently depending upon the allowed actions for the link. Uploading duplicate names to Share Links that allow only uploads will always automatically rename the duplicates. Uploading duplicate names to Share Links that allow both uploads and downloads or that provide full access will follow the site-wide overwrite behavior.