We propose a modular architecture based on a standardized API layer. To bridge the gap between HxD's native Delphi codebase and modern security tooling, we suggest a wrapper-based approach.
Use a compiler supporting Delphi, C++, or C to compile the DLL.
To install a plugin manually (using the Z80 plugin as an example): hxd plugins
If the built-in features aren't enough, the best way to "plugin" to HxD is to write a script that interacts with the file.
Reduce the need to constantly switch between HxD and external Python scripts or command-line tools. Understanding HxD’s Native Extensibility We propose a modular architecture based on a
It decodes or encodes text selections in common formats like Base64, URL encoding, and HTML entities.
Currently, users must rely on external tools or manually write Pascal scripts for repetitive tasks. This paper proposes a transition from simple scripting to a robust , allowing third-party developers to extend the HxD GUI and processing capabilities while maintaining the application's lightweight footprint. To install a plugin manually (using the Z80
It integrates with the Data Inspector, interpreting the hex data as instructions for the Z80 CPU.
HXD remains in maintenance mode, but its plugin system is stable and complete. While newer tools like ImHex (with built-in scripting and pattern language) have emerged, HXD's simplicity, speed, and low resource footprint keep it relevant. Plugins extend its life by allowing the community to add modern features without waiting for core updates.
Here is a technical white paper outlining a proposed framework for standardizing and securing HxD extensions.