Additional Information
A freeware resource compiler & decompiler for Windows PC applications
| Version | Resource Hacker 5.2.5 Build 409 |
| Requirements |
Windows XP/Vista/Windows 7/Windows 8/Windows 10 |
| Updated | November 15, 2023 |
| Author | Angus Johnson |
| Category | Developer Tools |
| License | Freeware |
| Language | English |
| Download | 166 |
Overview
Resource Hacker is a resource editor for 32bit and 64bit Windows PC applications. It's both a resource compiler (for *.rc files), and a decompiler - enabling viewing and editing of resources in executables (*.exe; *.dll; *.scr; etc) and compiled resource libraries (*.res, *.mui). While Resource Hacker™ is primarily a GUI application, it also provides many options for compiling and decompiling resources from the command-line.
Compiling can be initiated either by opening an existing resource script file or by creating one from scratch using Resource Hacker's editor.
Once a resource file has been opened, its resources will generally be displayed as either an image (or group of images) or as decompiled text. Binary resources, usually images, can't be edited directly with the app, but they can still be very easily exported and imported once they've been modified by an external image editor. (I see no benefit in duplicating what third-party image editors do so well.)
Just about all the functionality of Resource Hacker™ can be accessed from the command line without having to open the Resource Hacker™ GUI. Command-line instructions and Resource Hacker™ scripts can remove the drudgery entailed with repeating Resource Hacker™ tasks.
Some executable files are "packed" or "compressed" using compression algorithms. Not only does this reduces file size, but it also makes viewing and modifying resources marginally more difficult. I suspect that this resource 'hiding' is (or was) a common objective in this process. Anyhow, in deference to these authors, I've chosen not to unpack files with the program.
As a side note, it seems that "packed" executables have become quite uncommon over the last 5-10 years, and software authors are exposing more rather than less information in executable resources. I suspect that earlier concerns about the loss of intellectual property with reverse engineering have been allayed.
Features and Highlights
Compiling can be initiated either by opening an existing resource script file or by creating one from scratch using Resource Hacker's editor.
Once a resource file has been opened, its resources will generally be displayed as either an image (or group of images) or as decompiled text. Binary resources, usually images, can't be edited directly with the app, but they can still be very easily exported and imported once they've been modified by an external image editor. (I see no benefit in duplicating what third-party image editors do so well.)
Just about all the functionality of Resource Hacker™ can be accessed from the command line without having to open the Resource Hacker™ GUI. Command-line instructions and Resource Hacker™ scripts can remove the drudgery entailed with repeating Resource Hacker™ tasks.
Some executable files are "packed" or "compressed" using compression algorithms. Not only does this reduces file size, but it also makes viewing and modifying resources marginally more difficult. I suspect that this resource 'hiding' is (or was) a common objective in this process. Anyhow, in deference to these authors, I've chosen not to unpack files with the program.
As a side note, it seems that "packed" executables have become quite uncommon over the last 5-10 years, and software authors are exposing more rather than less information in executable resources. I suspect that earlier concerns about the loss of intellectual property with reverse engineering have been allayed.
Features and Highlights
- View resources in Win32 executable files (*.exe, *.dll, *.cpl, *.ocx) and in Win32 resource files (*.res) in both their compiled and decompiled formats.
- Extract (save) resources to file in: *.res format; as a binary; or as decompiled resource scripts or images. Icons, bitmaps, cursors, menus, dialogs, string tables, massage tables, accelerators, Borland forms, and version info resources can
- be fully decompiled into their respective formats, whether as image files or *.rc text files.
- Modify (rename or replace) resources in executables. Image resources (icons, cursors, and bitmaps) can be replaced with an image from a corresponding image file (*.ico, *.cur, *.bmp),
- a *.res file, or even another *.exe file. Dialogs, menus, string tables, accelerators, and message table resource scripts (and also Borland forms) can be edited and recompiled using the internal resource script editor.
- Resources can also be replaced with resources from a *.res file as long as the replacement resource is of the same type and has the same name.
- Add new resources to executables. Enable a program to support multiple languages, or add a custom icon or bitmap (company logo, etc) to a program's dialog.
- Delete resources. Most compilers add resources into applications that are never used by the application. Removing these unused resources can reduce an application's size.
