Your system automatically appends suffixes like "(1)" or "copy" to a new file's name when it detects a file with the exact same name already exists in the target folder. This is a fundamental file system conflict prevention feature, not a malfunction. Operating systems enforce unique names within a single folder to avoid overwriting existing files unintentionally. If you save or copy a new file with a name identical to one already present, the system modifies the new file's name to preserve both.

For instance, if a folder already contains "budget.xlsx" and you attempt to save another file there named "budget.xlsx," your system (like Windows File Explorer or macOS Finder) will automatically save it as "budget (1).xlsx" or "budget copy.xlsx" instead. Similarly, downloading a file with the same name as an existing download from a web browser triggers this behavior. This occurs universally across applications (word processors, image editors) and file management interfaces when saving or copying files locally or to network drives.

This naming convention prevents data loss by safeguarding the original file. However, it can create clutter if many near-identical files accumulate. The main limitation is the lack of user control over the specific suffix format applied automatically. Future improvements might offer smarter options, like timestamps, but the core benefit of preventing accidental overwrites remains crucial for data integrity, outweighing the minor inconvenience of the modified filename.