A "duplicate file name" occurs when two or more files stored in the same folder or directory on a computer system share exactly the same name. This is not permitted because the operating system uses the file name, combined with its location, as a unique identifier to manage, access, and store the file. When an attempt is made to create or move a file with the same name as an existing one into the same folder, the system typically triggers an error or automatically appends a number (like "(1)" or "_copy") to make the new name unique, preventing the duplication.

This situation frequently arises in everyday tasks. For instance, when downloading multiple attachments labeled "Report.pdf" from different emails into your "Downloads" folder, the subsequent files might become "Report (1).pdf" or similar. It's also common in collaborative environments where two team members inadvertently upload documents both called "ProjectPlan.docx" to the same shared cloud storage folder or network drive, requiring manual renaming to avoid confusion.

The main advantage of enforcing unique filenames is maintaining organized and unambiguous file access. However, a significant limitation is the potential for user confusion when automatic renaming happens silently, leading users to potentially work on unintended versions. Using descriptive and unique naming conventions from the outset remains the best practice to prevent these issues and maintain clarity.