Only the application that reads those file types is going to be able to make sense of the file, interpret the content, and render it correctly on screen. If you're talking about how the application reads and renders the content of the file on screen, what you're talking about is impossible. When it's "converted back" a utility is decompressing the file back to its original content so the application assigned to reading that file type is then able to read it again.ĭisplaying a file "as the computer sees it" is just a stream of bytes, some of it may represent text, but most will be non-human readable, seemingly random garbage. It sounds as though that script you have may be a compression utility that compresses files into smaller archives.
bin files by default on your machine, has any clue how to convert that file back. That file only has meaning to the script that created it and only that same script, or whatever is setup to open. I have no idea what your talking about when you say "pick a file and convert it to. You can pick any file you want and simply change the file extension and it's the exact same file. bin file doesn't have any meaning or format. The application knows how to take that data and render it on screen as readable information.Ī. THAT is when the data in the file becomes meaningful and "readable". Text can be multiple bytes per character.Īpplications that are reading data typically are reading the file as "binary" but deserializing that data into data structures in the application. How a file is read is either going to be in "binary" mode, read as a stream of bytes, or as a text stream, where the stream of bytes is interpreted as text depending on an encoding used. They stay "binary", which is just a stream of bytes. There is no such thing as "converted back when opened". Yeah, you didn't clear up any of the naivety.