Getting Things Done With a Hex Editor
Most people don't realize how much of their software life depends on occasionally opening a file in a hex editor. Hexanauts handles that task well enough for day-to-day work. It's a free Windows hex editor that handles large files without choking, supports multiple tabs, and lets you search, replace, and modify raw binary data with a reasonable degree of comfort. I first started using it around 2019 when I needed to tweak some old save file formats for a project. It wasn't the most polished tool, but it was fast and didn't ask for a subscription. I've stuck with it since.
What Are Hexanauts Actually Used For?
The name refers to the program itself. Hexanauts is a hex editor application for Windows, developed by Hexanaut Software. It opens files in both hex and ASCII representation side by side, which is standard for this type of tool. You can navigate with arrow keys, jump to a specific offset with Ctrl+G, and search for byte sequences or strings. The main use cases are file modification at the byte level. This includes things like editing ROM headers, patching game saves, analyzing binary file formats, or recovering deleted data from certain storage media. It's not a forensic tool. It's not a disassembler. It's a hex editor and nothing more, which is actually its strength. You can download it directly from the developer's site at hexanaut.com. The current version is Hexanauts 3.x, and it runs on Windows 7 and later. No installation is required. It's portable, which matters because I've seen too many hex editors bloat the registry for no reason.
How to Use It Without Wasting Two Hours
Open the program and drag your file into the window, or use File > Open. The interface splits into three panes: the hex dump on top, the ASCII representation below it, and the offset column on the left. It looks dated but functional. Start by learning the keyboard shortcuts immediately. Ctrl+F opens the find dialog. Ctrl+G goes to offset. Ctrl+R does a replace. If you try to click through the menus for any of these, you're going to lose time you don't have. The menu structure is buried under unnecessary submenus in places. When editing bytes, just click on the hex value you want to change and type the new value. It accepts both hex and decimal input. When you press Enter, the change applies. The ASCII pane updates automatically. This basic workflow covers probably eighty percent of what anyone needs from the tool.
For searching, the byte sequence search is the most useful feature. You can search for something like A3 F0 2B 00 and it will find every occurrence in the file. This is how I found the health value in an old JRPG save file once. The string search is less reliable on binary files because of encoding differences. The byte sequence search doesn't care about encoding, so it works on everything. One thing beginners always miss: Hexanauts has a bookmarks feature. Press F2 to set a bookmark at the current cursor position. It sounds trivial but it saves you from scrolling back and forth when you're working on a file that's several megabytes in size. I keep maybe six or eight bookmarks open at once across my usual projects.
A Problem I Ran Into and How I Fixed It
Last year I was working on modifying a custom game asset file that used a self-contained compression scheme. The file was roughly forty megabytes. Hexanauts opened it fine, but whenever I tried to do a replace-all operation across the entire file, the program would hang for about two minutes and then complete. The issue seemed to be related to how the find-and-replace function re-indexed offsets as it modified the file in place. The workaround was straightforward: instead of replace-all, I did a sequential find and replace. Ctrl+F to find the first occurrence, make the change, then use Find Next (Ctrl+Shift+F) to step through each instance one by one. It takes longer but the program stays responsive. I lost about twenty minutes to this before I realized the pattern, and now I avoid replace-all on files over ten megabytes entirely. There's also a known issue with files larger than about two hundred megabytes. The interface starts lagging noticeably past that point. It's not a crash, just a performance problem. For very large files I switch to HxD or a command-line hex tool instead. Hexanauts isn't built for that scale.
Things Beginners Get Wrong
The biggest mistake is assuming that editing a hex value and saving the file produces the same result every time. It doesn't. Some file formats store checksums or hash values alongside the data you're modifying. Change the data without updating the checksum, and the file becomes corrupt or gets rejected by the application that reads it. I wasted an afternoon on this with a game mod once because I didn't check for a header checksum field first. Another common error is changing the size of data in place. If you replace a two-byte value with a four-byte value without adjusting everything around it, you'll shift all subsequent offsets and likely break the file structure. Hex editors don't warn you about this. They just let you do it. I always keep a backup copy before making any structural changes, even when I think I know what I'm doing. The undo feature only goes back a limited number of steps. I believe it's around fifty to a hundred, but I never trusted it enough to rely on it. Always save frequently and keep backups. The undo system is convenient for small edits but unreliable for anything that matters.
When Hexanauts Is the Wrong Tool
If you need to reverse engineer a compiled program, use a disassembler instead. IDA Free or Ghidra are better choices and they'll save you from frustration. Hexanauts shows you bytes. It doesn't interpret them for you in any meaningful way beyond the basic hex and ASCII display. If you're working with compressed or encrypted files, Hexanauts won't decompress them for you. You need to handle that outside the editor first. I've seen people try to find patterns in encrypted data and give up because they expected the tool to help with something it's not designed to do. For automated batch processing or scripting, the command-line tools like xxd or Python's binascii module are far more efficient. Hexanauts is a manual tool. It's fine for interactive work but terrible if you need to process hundreds of files through a pipeline.
The developer doesn't publish release notes regularly and support is limited to a forum that hasn't had much activity since 2023. The software works as advertised, but if something breaks in a future Windows update, there's no guarantee anyone will fix it. That's acceptable for a free portable tool, but it's something to keep in mind if you're considering it for production work.
