- Forum
- Windows Programming
- Create txt files without extra data/info
Create txt files without extra data/info
Is it possible to create textfiles without the extra data that comes with it? ( like creation date, filetype and everything else that is added behind the scenes? )
Just the size of its name
Just the size of its name
You're referring to metafiles and metadata. Those stats you list aren't actually part of the text file itself.
https://stackoverflow.com/questions/4954991/are-0-bytes-files-really-0-bytes
This goes beyond Windows itself and gets into the inner workings of the NTFS (NT File System).
Suggested reading: https://blogs.technet.microsoft.com/askcore/2013/03/01/where-did-my-space-go/
When you format a hard drive, you don't get access to all of its space. A percentage of that space is used by the file system itself to store metadata so that the file system can keep track of its own files for accessing/modifying/deleting/etc. This also handles NTFS security descriptors for access control.
To view/edit this "metadata", you need to use a "section editor". Do a search of "section editor ntfs" for some results. I have not used these and will not endorse any, maybe someone else on this forum has...
e.g. http://www.disk-editor.org/
Specifically, information like filenames, filesizes, modification dates, are stored in the Master File Table ($MFT). (Also note, "filetypes" aren't actually a thing. That's just information that Windows gives you based on it reading the arbitrary extension of the filename, if any. Those strings are stored somewhere in the registry, but not per file.)
Now... for the meat of your question. How do you actually correctly edit this thing? I don't know the inner-workings of the NTFS format. Again, maybe another person on this forum does. But it comes down to you editing NTFS system files. I would start by reading through NTFS guides, such as http://ntfs.com/ntfs-system-files.htm
Can Windows even handle a file if it can't find certain metadata about it? Will Windows just fill in default metadata for files it finds that don't have metadata? Is messing with this stuff really worth it to save a few bytes? I have no idea. But if you wish to explore more, hopefully the suggestions I linked might be of value.
Mess something up while trying to edit the $MFT, and you'll brick your drive (practice with Virtual Machines).
Good luck!
https://stackoverflow.com/questions/4954991/are-0-bytes-files-really-0-bytes
This goes beyond Windows itself and gets into the inner workings of the NTFS (NT File System).
Suggested reading: https://blogs.technet.microsoft.com/askcore/2013/03/01/where-did-my-space-go/
When you format a hard drive, you don't get access to all of its space. A percentage of that space is used by the file system itself to store metadata so that the file system can keep track of its own files for accessing/modifying/deleting/etc. This also handles NTFS security descriptors for access control.
To view/edit this "metadata", you need to use a "section editor". Do a search of "section editor ntfs" for some results. I have not used these and will not endorse any, maybe someone else on this forum has...
e.g. http://www.disk-editor.org/
Specifically, information like filenames, filesizes, modification dates, are stored in the Master File Table ($MFT). (Also note, "filetypes" aren't actually a thing. That's just information that Windows gives you based on it reading the arbitrary extension of the filename, if any. Those strings are stored somewhere in the registry, but not per file.)
Now... for the meat of your question. How do you actually correctly edit this thing? I don't know the inner-workings of the NTFS format. Again, maybe another person on this forum does. But it comes down to you editing NTFS system files. I would start by reading through NTFS guides, such as http://ntfs.com/ntfs-system-files.htm
Can Windows even handle a file if it can't find certain metadata about it? Will Windows just fill in default metadata for files it finds that don't have metadata? Is messing with this stuff really worth it to save a few bytes? I have no idea. But if you wish to explore more, hopefully the suggestions I linked might be of value.
Mess something up while trying to edit the $MFT, and you'll brick your drive (practice with Virtual Machines).
Good luck!
Last edited on
Hello Ganado!
This is from the article.
I assume that even if space is already being set aside for metafiles/metadata, the space for it will be expanded at some point, right?
My question is, will I gain more in the long run if I keep as much content as possible in the same file, unlike if I would separate all content into multiple files and folders? (because this would extend the space for metafiles? If that's true, that is to say)
This is from the article.
| $MFT: The more files you have and the more fragmentation you have, the more entries will be created in the Master File Table. This will cause the $MFT metafile to grow. |
I assume that even if space is already being set aside for metafiles/metadata, the space for it will be expanded at some point, right?
My question is, will I gain more in the long run if I keep as much content as possible in the same file, unlike if I would separate all content into multiple files and folders? (because this would extend the space for metafiles? If that's true, that is to say)
Last edited on
First part: Sounds like that's correct, the space will be expanded.
Second part: Yes, a bunch of small files will contain more overhead percentage-wise than a few large files. But unless you're making millions of files that are only a few bytes big, any reasonable file will easily outweigh the overhead of storing a few bytes for the file size/modification/security NTFS stuff.
If we're just talking about some configuration files here and there, it's really nothing to worry about. If you're talking about millions of files you need to keep track of, perhaps some sort of SQL database is better.
Second part: Yes, a bunch of small files will contain more overhead percentage-wise than a few large files. But unless you're making millions of files that are only a few bytes big, any reasonable file will easily outweigh the overhead of storing a few bytes for the file size/modification/security NTFS stuff.
If we're just talking about some configuration files here and there, it's really nothing to worry about. If you're talking about millions of files you need to keep track of, perhaps some sort of SQL database is better.
Last edited on
Topic archived. No new replies allowed.