And many more tools that can double has hex viewers/dumpers.
- hexdump [util-linux]
- hexdump [BusyBox] (simplified implementation of the above). BusyBox itself has more than one implementation.
- od [Coreutils]
- od [BusyBox]
- od [uutils]
- xxd ports (e.g. in gvim)
- xxd [BusyBox]
- hexdump [Yori]
- hexdump [hextools]
- sfk hexdump
- HexDump [Mahoning Valley Software]
- Byte2hex
- hexdump [DI Management] ("simplified version of the Linux utility")
- hexdump (Ron Charlton).
- https://github.com/nicolasbauw/hexdump-lt
- https://github.com/rickkas7/crc32_and_xxd
- https://github.com/hollasch/hex
- https://github.com/jaxhax-travis/0xdump
- https://sourceforge.net/projects/lessbin/
- https://sourceforge.net/projects/hexviewer/
- http://www.mklasson.com/hexit.php
- http://www.zz9pza.net/dump/
- http://www.richpasco.org/utilities/hexdump.html
- http://bytepointer.com/tools/index.htm#bd
- hex
- http://adoxa.altervista.org/xd/index.html
- xd [fourmilab]
- hexdump [dcs]
- http://www.diamondspirit.net/adunk/soft ... xdump.html
- An "xxd implementation". Download link.
- vbindiff (a TUI). Shows dump when a single file is opened.
- Cygutils dump (Doesn't need full cygwin)
- https://kmrconsulting.com/freeutil (od)
- This batch file using certutil!
Such wealth of tools begging to be collected and organized in a usable way!
The point of adding all these tools is to make a repository for all available tools because there is currently none. I don't know which of these tools is better at what (yet). One's preferred/best-known tool can suddenly fail him and you don't know which alternative can work on that situation. Also, this is just laying the best foundation for curation because of all the hidden gems out there.
There are multiple reasons to choose one of the dump tools over the others:
- Some people want the first working tool they can find.
- Some go for the most popular/supported tools
- Some want the fastest tools (I noticed significant differences in speed with hexdump tools in identical conditions)
- Some want tools that can handle large files
- Some want a TUI with search and highlight etc.
- Some want a tool already included in their toolset (e.g. BusyBox or sfk)
- These tools have different styles of hex output (spacing, separators etc) which affects readability or space constraints.
- Some tools have colored output
- Some may not run on an older system or without certain dependencies
My point is: Whether a tool is "worth considering" is something I leave for the user because they know what they want better than me. I simply collect and add these tools because no one else did so far on the internet (for Windows at least). There are already multiple curated lists out there. I don't want to ignore tools because I think, at this moment, that they are not useful or interesting.