Why your computer relies on a simple dot to identify your digital files
In short: Filename extensions are more than just a suffix; they are a legacy of 1960s time-sharing systems. While modern operating systems often treat them as mere text, these tiny markers remain a primary way for users and software to guess what a file contains, despite their inherent unreliability and security risks.
The concept of the filename extension originated in 1961 with MIT's Compatible Time-Sharing System (CTSS). To simplify file management on the IBM 7090, the system allowed users to append a dot and a class name to a file, which the system then stored in a separate field. This design choice was later adopted by DEC for systems like the PDP-6 and PDP-10, eventually influencing the naming conventions of CP/M and DOS.
As computing evolved, the implementation of these extensions diverged. While early systems like DOS strictly enforced an 8.3 character limit, newer file systems like NTFS and Unix-like systems treat the extension as part of the filename string itself. In these environments, the dot is just another character, and the extension serves primarily as a human-readable hint rather than a system-enforced metadata flag. This shift reflects a broader move toward internal file metadata, where the file's content—often identified by a 'magic number' in the header—is a more reliable indicator of its true nature than its name.
This reliance on extensions creates significant security vulnerabilities. Because extensions can be easily renamed, they are frequently exploited by malware authors to disguise malicious executables as harmless documents. By hiding extensions by default, some operating systems inadvertently assist this deception, allowing files like 'document.txt.vbs' to appear as simple text files. Furthermore, the global nature of extension associations in Windows can lead to conflicts, where different applications claim the same suffix, or where web servers fail to correctly identify file types, leading to interpretation errors across the internet.
Today, modern desktop environments and operating systems like macOS are moving toward more robust identification methods, such as Uniform Type Identifiers or media types (MIME types). While the filename extension persists for compatibility and user convenience, it is increasingly viewed as a legacy convention. In professional computing, relying on extensions for security or system logic is considered poor practice, as it exposes implementation details and leaves systems vulnerable to simple spoofing attacks.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: Filename extension
To cite this card, link to https://intellectplus.co.uk/app/technology-filename-extension.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?
Related
More in Computing and information technology · More in Technology · Latest · A–Z · All topics