Long File Names: Limits and What Counts

This page explains what counts as a long file name, the practical limits imposed by different operating systems and file systems, and which limit applies to you. In short, a long file name is any name that exceeds the traditional 8.3 format (eight characters, a dot, and a three-letter extension) used by older DOS and Windows systems; the most common modern limit is 255 characters for the name itself, but the full path length can be limited to 260 characters on Windows unless long path support is enabled.

Formula

The calculator above computes pace and speed from a given finish time and distance. The formulas are:

• Pace (min/km) = Finish time (minutes) ÷ Distance (km)
• Speed (km/h) = Distance (km) ÷ (Finish time (minutes) ÷ 60)

Where Finish time is entered in minutes, Distance in kilometers, Pace is the time per kilometer, and Speed is the average speed in kilometers per hour. For example, if you run 10 km in 50 minutes, your pace is 5.00 min/km and your speed is 12.00 km/h.

Worked Example

Using the default values from the calculator: Finish time = 50 minutes, Distance = 10 km.

1. Pace = 50 ÷ 10 = 5.00 min/km
2. Speed = 10 ÷ (50 ÷ 60) = 10 ÷ 0.8333 = 12.00 km/h

The calculator shows 5.00 min/km and 12.00 km/h, matching the example.

Background: The 8.3 Convention

The concept of a “long file name� dates back to the 1980s when MS-DOS and early Windows used the File Allocation Table (FAT) file system. That system imposed a strict 8.3 format: up to 8 characters for the base name, a dot, and up to 3 characters for the extension. This limit was a practical constraint of the era’s memory and disk structures. When Windows 95 introduced long file names (LFN) with the VFAT file system, users could finally use spaces, multiple dots, and names up to 255 characters. This change was a major usability leap, but it also introduced compatibility issues with older software that only understood 8.3 names.

How Long File Names Work

Modern file systems store file names as Unicode strings, allowing a wide range of characters. The most common limit is 255 characters for the file name component, which includes the extension and any dots. This limit applies to NTFS (Windows), ext4 (Linux), APFS (macOS), and most other contemporary file systems. However, the full path—the complete address from the root directory to the file—can be much longer. On Windows, the traditional maximum path length is 260 characters (MAX_PATH), which includes the drive letter, colon, backslashes, and the file name. This limit has been a common source of errors when copying or moving files with deeply nested folders. Windows 10 and later offer a registry or Group Policy setting to enable long paths (up to 32,767 characters) for applications that support it. On Linux and macOS, the path length limit is typically much higher (around 4096 characters), so it is rarely a practical issue.

Which Limit Applies to You?

The limit that applies depends on the file system and operating system you are using:

• Windows (NTFS): File name component: 255 characters; full path: 260 characters by default, extendable to 32,767 with long path support enabled.
• macOS (APFS): File name component: 255 UTF-16 code units (roughly 255 characters); full path: 1024 bytes (not characters) for the POSIX layer, but practical limits are higher.
• Linux (ext4): File name component: 255 bytes (not characters, so multi-byte UTF-8 characters reduce the count); full path: 4096 bytes.
• Cloud storage (e.g., Google Drive, Dropbox): These services often have their own limits, typically 255 characters for the name, but they may also impose limits on the total path length when syncing to a local folder.

To check your system’s limits, you can create a file with a very long name and see when it fails. On Windows, you can also use the \\?\ prefix to bypass the 260-character limit in some applications, but this is not universally supported.

Common Problems with Long File Names

Long file names can cause several practical issues:

• Path too long errors: On Windows, when copying or moving files, you may see “The file name(s) would be too long for the destination folder.â€� This happens when the full path exceeds 260 characters.
• Backup and sync failures: Some backup tools and cloud sync clients do not handle long paths well, leading to skipped files or errors.
• Compatibility with older software: Programs that were not updated for long file names may truncate names or fail to open files.
• Character restrictions: Each file system has a set of forbidden characters (e.g., <>:"/\|?* on Windows) and reserved names (e.g., CON, PRN, AUX). Using these can cause errors even if the length is fine.

To avoid these problems, keep file names descriptive but concise—typically under 100 characters—and avoid deep folder nesting. If you encounter path length errors on Windows, you can enable long path support via the Group Policy Editor or registry, or use a tool that supports long paths, such as 7-Zip or robocopy with the appropriate flags.

How to Choose a File Name

When naming files, consider the following:

• Use meaningful names that describe the content, e.g., 2025-03-15_Project_Report_Final.docx instead of report.docx.
• Include dates in a sortable format (YYYY-MM-DD) to make sorting easier.
• Avoid special characters that are problematic across systems, such as :, *, ?, and leading/trailing spaces.
• Be mindful of case sensitivity: Windows and macOS are case-insensitive by default, but Linux is case-sensitive. Using consistent capitalization helps avoid confusion.

For shared files, consider the target audience’s platform. If you are sharing files with Windows users, avoid creating names that exceed 260 characters in total path length, even if your own system allows it.

Comparisons: File Systems and Their Limits

Here is a quick comparison of common file systems and their file name limits:

• FAT32: 255 characters for the name, but no built-in long path support; the total path is limited by the cluster size and can be problematic.
• NTFS: 255 characters for the name, 32,767 characters for the path with long path support enabled.
• ext4: 255 bytes for the name, 4096 bytes for the path.
• APFS: 255 UTF-16 code units for the name, path limit is 1024 bytes for the POSIX layer.
• exFAT: 255 UTF-16 code units for the name, no practical path limit.

These limits are important when moving files between systems, especially if you are using external drives formatted with FAT32 or exFAT.

Safety and Best Practices

While long file names are generally safe, there are a few safety considerations:

• When using a file name that is close to the limit, always test that the file can be opened and copied to another location.
• Be cautious with names that are extremely long; they can cause issues with backups, version control systems, and email attachments.
• If you are working with a team, agree on a naming convention that avoids path length issues, especially if the project uses a shared network drive.

If you encounter errors due to long paths, the safest solution is to shorten the folder structure or file names, rather than relying on system tweaks that may not be portable.

Frequently Asked Questions

What is the maximum file name length in Windows 10/11?

In Windows 10 and 11, the file name component is limited to 255 characters, and the full path is limited to 260 characters by default. However, you can enable long path support (up to 32,767 characters) by changing a Group Policy setting or a registry key. Many modern applications, including File Explorer, support long paths after this setting is enabled.

Does a file name include the extension?

Yes, the file name limit includes the extension and any dots. For example, myfile.txt has 10 characters, and myfile is 6 characters. The 255-character limit applies to the entire name, including the dot and extension.

Why do I get a “path too long� error when copying files?

This error occurs on Windows when the full path (including the drive letter, folders, and file name) exceeds 260 characters. It often happens when copying a deeply nested folder structure. To fix it, enable long path support or shorten the folder names. Some third-party tools can also handle long paths.

Are there differences between file name limits on Linux and Windows?

Yes. Linux (ext4) limits the file name to 255 bytes, which means that if you use multi-byte UTF-8 characters (like emojis), the number of characters will be less than 255. The full path limit is 4096 bytes. Windows (NTFS) allows 255 characters (UTF-16 code units) and has a 260-character path limit by default, which can be extended.

Can I use spaces and special characters in file names?

Yes, spaces are allowed on all modern systems, but some special characters are forbidden on Windows: < > : " / \ | ? *. On Linux and macOS, the slash (/) is the only character that is always forbidden, but other characters may cause issues in certain contexts. It is best to avoid characters that are problematic across platforms.

What is the best way to avoid long file name issues?

The best way is to keep file names concise (under 100 characters) and avoid deep folder nesting. Use a clear naming convention with dates and keywords. If you are sharing files, test that they can be copied to a Windows machine with default settings. This prevents most path length errors.

Related

• AI Spending & Green Card Process: What to Know
• How to Build an MCP Server for Live Kenya eSIM Comparisons
• Printer Offline Despite Wi-Fi: Check Status, Queue & Setup

in t | Finish time | min | 50 | 0
in d | Distance | km | 10 | 0
out pace | Average pace | min/km | t / d | 2
out speed | Average speed | km/h | d / (t / 60) | 2