iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
A long file name is any file name that is longer than the old MS-DOS “8.3” naming style. Microsoft uses this relative definition, so there is no single universal character count that makes a name “long.” People also use the phrase loosely for a different problem: a full path, meaning the chain of folders leading to a file, that is too long for Windows or an application to handle. The name limit and the path limit are separate, and the fix depends on which one you are hitting.
What the definition means
Microsoft’s naming documentation defines the term this way: “A long file name is considered to be any file name that exceeds the short MS-DOS (also called 8.3) style naming convention.” The 8.3 convention limited names to eight characters, followed by a dot and an extension of up to three characters. A name such as Quarterly Report 2026.docx is therefore “long” simply because it does not fit that pattern. Long names are ordinary on modern Windows, so the length of a name on its own is rarely what causes an error. The errors people see come from limits applied to a single component or to the whole path.
Filename, component, and path
A filename is one component: the last piece after the final backslash. A path is every component from the drive or root down to the file, for example C:ProjectsClient Archive2026InvoicesMarchinvoice-0312.pdf. Each component is checked against the filesystem’s own limit, and the complete path is checked against a separate limit set by the operating system interface or the application that opens the file.
This is why a file can have a short, ordinary name and still fail. A file named invoice-0312.pdf can sit deep enough inside nested folders that the full path exceeds what a particular program accepts. Shortening the file name would not help in that case.
#1 Best Overall
- Easily store and access 2TB to content on the go with the Seagate Portable Drive, a USB external hard drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
The figures, and which layer each one measures
Several numbers circulate for Windows, and they describe different layers. Read them together rather than as one limit.
| Layer | Figure | What it applies to | Source and date |
|---|---|---|---|
Traditional Win32 path (MAX_PATH) |
260 characters | Traditional Windows API behavior for full paths. It is not an unconditional filesystem maximum. | Microsoft Learn, Win32 path documentation, last updated 2024 |
| Extended-length Windows API paths | Approximately 32,767 characters | Paths written in the extended-length form and handled by APIs that support it. It does not remove component limits. | Microsoft Learn, Windows path documentation, last updated 2024 |
| Filename component on NTFS, exFAT, and FAT32 | 255 Unicode characters | A single filename or folder name within a path | Microsoft, File System Functionality Comparison, table accessed 2026 |
| Maximum path name on NTFS, exFAT, and FAT32 | 32,760 Unicode characters | The filesystem’s tabled path maximum; each component still stays within 255 characters | Microsoft, File System Functionality Comparison, table accessed 2026 |
| OneDrive and SharePoint web paths | 400 characters | Cloud web paths only. URL-encoded special characters count toward the total. | Microsoft Support, accessed 2026 |
| Component and pathname limits in an archived Apple manual | 255 characters per component; 1,023 characters per pathname | Historical values in the documented environment of that manual. Not a current macOS-wide limit. | Apple Developer Documentation, archived pathconf(2) manual dated June 4, 1993 |
The 260-character figure and the roughly 32,767-character figure are both Windows API numbers, but they belong to different eras and code paths. The 32,760-character filesystem table value is slightly lower than the extended API maximum for a reason tied to how the documentation frames each limit, so it should not be used as a substitute for the API figure. For troubleshooting, the figure that matters is the one that applies to the program that is failing.
Rank #2
- Easily store and access 5TB of content on the go with the Seagate portable drive, a USB external hard Drive
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
Why Windows still reports a path as too long
Long-path support is opt-in at two levels
Starting with Windows 10 version 1607, many common Win32 functions can accept longer paths, but only when two conditions are both met. The first is a system-wide setting, the Group Policy option Enable Win32 long paths (found under Computer Configuration, Administrative Templates, System, Filesystem), or the equivalent LongPathsEnabled value under HKLMSYSTEMCurrentControlSetControlFileSystem. Changing either requires administrator rights. The second is application opt-in: the program must declare itself longPathAware in its manifest. Enabling the setting does not make every app support long paths.
Some common tools do not opt in
Microsoft’s OneDrive support documentation states that File Explorer and Office desktop apps do not opt in to long paths. A user working in those tools may therefore still meet the traditional limit even on a system where the setting is enabled. Treat the registry or policy change as a possible fix only for software you know supports it, not as a universal repair.
Rank #3
- Easily store and access 1TB to content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop. Reformatting may be required for Mac
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
The shell can reject a path the filesystem would accept
A path can be valid for the filesystem and still be refused by Explorer, a dialog box, or a script that builds its own path strings. When the error appears only in one program, the filesystem is usually not the problem.
Limits on Linux and macOS
Linux documentation describes pathnames in bytes rather than characters, so a name containing accented or non-Latin letters uses more of the limit than its visible length suggests. The maximum length of a single component depends on the filesystem. Rather than assuming one value, a program can query the limit with pathconf or fpathconf.
Rank #4
- Easily store and access 4TB of content on the go with the Seagate Portable Drive, a USB external hard drive.Specific uses: Personal
- Designed to work with Windows or Mac computers, this external hard drive makes backup a snap just drag and drop
- To get set up, connect the portable hard drive to a computer for automatic recognition no software required
- This USB drive provides plug and play simplicity with the included 18 inch USB 3.0 cable
- The available storage capacity may vary.
On macOS, the only figures in the table above come from an archived manual dated June 4, 1993. Those numbers describe that historical environment and should not be presented as the current limit on Apple systems. Current Apple documentation indicates that a volume can report its own maximum filename component length, so the value that counts is the one the volume reports, not an old constant.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why a file that syncs can suddenly break
A path that is acceptable in OneDrive on the web can become too long after it syncs to a Windows computer. The reason is that the local OneDrive folder prefix, such as the path to your user profile’s OneDrive directory, adds characters to every path. The web limit in the table counts URL-encoded special characters too, so a single space encoded as %20 takes up three characters in that count. Microsoft recommends shorter file names and shallower folder structures. If a file exceeds the local desktop limit, Microsoft’s guidance is to rename it on the web so the change syncs back down.
Best Value
- [Upgraded Version] - This external hard drive features a mirrored logo stripe combined with a striped anti-slip design, and the rounded corners of the casing make it easier to grip. The stripes also have a heat dissipation function, ensuring stable and fast data transfer.
- 【Ultra-thin and quiet】 - The motherboard adopts JMicron 578 noise-free solution, giving you a quiet working environment. Lightweight and portable size designed to fit in your pocket for easy portability.
- 【Ultra-Fast Data Transfers】 - Pairing this external hard drive with JMicron 578 solution USB 3.0 and USB 2.0 interfaces enables blazing-fast data transfer. It boasts theoretical read speeds of up to 125MB/s and write speeds of up to 103MB/s.
- 【Plug and Play】 - With no software to install, just plug it in and the drive is ready to use.The hard disk chip is wrapped with an aluminum anti-interference layer to increase heat dissipation and protect data.
- 【What You Get】 - 1 x Portable Hard Drive, 1 x USB 3.0 Cable, 1 x User Manual, Gift-type shell packaging ,Three-year manufacturer's warranty and free technical support services.
How to troubleshoot a long name or path error
- Read the error text. If Windows says the file name or extension is too long, the problem is usually a single component. If it says the path or folder is too long, the problem is the combined path.
- Measure the full path. Right-click the file, choose Properties, and read the Location field. Add the file name and the separators to estimate the total length.
- Identify the program. Note whether the error comes from File Explorer, an Office application, a sync client, a build tool, or a command-line utility. Each may apply a different limit.
- Shorten or flatten the structure. Rename long folder names, and move the project closer to the drive root, for example from
C:UsersnameDocumentsClients...toC:Work.... This fixes the problem in every program at once. - For OneDrive, rename on the web if needed. If the local client refuses a file that exists online, rename it in the web interface, then let the sync complete.
- Enable long paths only where it is supported. Use the system setting and confirm the application opts in. If the program does not declare
longPathAware, changing the setting will not help, and the structure must be shortened instead.
Work through the steps in order. Most errors are resolved at step four, and the later steps are needed only when the path cannot be shortened or the application’s behavior is the cause.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
