Believe it or not, file name limits aren't all that easy to come by. The reason it's difficult is because you have limits imposed by NTFS itself, limits imposed by the Windows operating system, and limits imposed by the application dealing with the files (e.g., Windows Explorer).
Experimentation reveals that for a file created at "C:\", you can create a file name with at most 255 characters. If you were to try to create a file with a longer path (e.g., "C:\Documents"), the length of the file name would have to be reduced accordingly. This implies that in addition to the length of the actual file name, you also have to deal with the name of the path, which, according to Microsoft, is set at 260 characters for local files.
File names can use any character in the current code page, including Unicode characters and characters in the extended character set (128–255), except for the following:
This tip (5835) applies to Windows 7, 8, and 10.
If your hard disk becomes problematic to the point where you can't even boot from it, you'll be glad you have a bootable ...
Discover MoreYou can fine-tune Indexed Searches by adding file types to the search index. This tip tells you how.
Discover MoreFiles are the basis of how information is stored on a disk drive. In order for files to be organized and effectively ...
Discover MoreFREE SERVICE: Get tips like this every week in WindowsTips, a free productivity newsletter. Enter your address and click "Subscribe."
2017-09-11 03:58:36
Richard
You say that the path length limit limit set by Microsoft is 260 characters for local files. What about files on a network?
This feature of the operating system has been in my mind recently, using the Office application Excel. After looking on the internet I found a DOS command to list paths in a folder structure, which I could then analyse for length to discover which paths were near the limit. The longest path I found was 212 characters but occasionally my AV suite notifies a buffer overflow message.
The command is: dir /s /b | sort /r /+261 /o pathlong.txt.
This command produces a text file containing the paths looking downwards in the folder structure from the current folder. It doesn't sort the list though - I have do that myself so I'm unsure what the sort parameter is doing.
Back to my original question - what about files on a network? Should some characters from the server be added (or subtracted from the 260 limit)?
2016-02-29 13:22:16
John Hawklyn
Don't forget reserved words: CON LPT1 etc. (https://en.wikipedia.org/wiki/Filename) can't be used in filenames.
Also there can be problems with some software correctly managing long file names with punctuation.
Usually resolved by "quoting" the file names.
It might be useful to explain why some of those characters are unavailable. Like the * asterisk and question mark - they're reserved as wildcard characters. Legacy of DOS days...
FREE SERVICE: Get tips like this every week in WindowsTips, a free productivity newsletter. Enter your address and click "Subscribe."
Copyright © 2018 Sharon Parq Associates, Inc.
Comments