Skip to content

Radare2

Unix-like reverse engineering framework and command-line toolset for binary analysis.

Self-hostedNot yet verified
Report issueDemo online
MIT★ 21000

Open the official app on rada.re

This tool is hosted by its maintainers. Click below to open rada.re in a new tab — it's their official demo.

Browse security tools →

What's next with Radare2?

Choose how you want to get started.

Use it free

Open the official tool or demo — no account needed.

Free

Self-host it

Run the open-source version on your own infrastructure.

Open

What is Radare2?

Radare2 is an open-source reverse engineering framework designed for Unix-based systems, offering a comprehensive set of tools for analyzing binary files, debugging, and disassembling software. It serves as a command-line interface (CLI) toolkit that enables users to inspect and modify machine code, making it essential for security researchers, malware analysts, and developers working with low-level software. The tool addresses challenges in understanding compiled binaries by providing granular control over memory, registers, and execution flow. Its modular architecture allows for extensibility through plugins, catering to both advanced users and those new to reverse engineering. Radare2's lightweight design and cross-platform compatibility make it a popular choice for tasks requiring deep system inspection without relying on proprietary tools.

How it works

Radare2 is a UNIX-like reverse engineering framework that provides a suite of command-line tools for analyzing, debugging, and modifying binary files. It is designed to offer low-level insights into executable code, enabling users to dissect software without access to source code. The primary purpose of Radare2 is to developers and security professionals to understand, analyze, and manipulate binary programs. It bridges the gap between high-level programming and machine code, making it indispensable for tasks like malware analysis, firmware debugging, and security research. Radare2 supports disassembly of multiple architectures (e.g., x86, ARM, MIPS), memory editing, and dynamic debugging. It integrates with tools like GDB for advanced debugging and offers scripting capabilities via its Rizin plugin system. Features like pattern matching, code signing analysis, and memory forensics are also available, making it versatile for reverse engineering tasks.

How to use it

  1. 1Install Radare2 via package managers (e.g., `apt install radare2` on Debian) or build from source. 2. Open a binary file using `r2 <file>` to enter the interactive shell. 3. Use commands like `p` to disassemble code, `d` to debug, or `a` to analyze sections. 4. Leverage plugins (e.g., `aaa` for auto-analysis) to automate tasks. Practical tips include using `help` for command lists and `config` to customize settings.

What it can do

  • reverse engineering framework

Use cases

Assumptions and limitations

Assumptions

  • source: https://github.com/radareorg/radare2
  • license: LGPL-3.0 — free to use
  • privacy: Self-hosted — you control your data

Limitations

  • For authorized use only — use on systems you own or have explicit permission to test.
  • Limited graphical interface (GUI) support compared to commercial tools
  • Steep learning curve for beginners due to CLI-based workflow
  • Incomplete support for some modern architectures or instruction sets
  • Dependence on Unix-like systems (less native Windows support)

Understanding the result

Unix-like reverse engineering framework and command-line toolset for binary analysis.

Tool details

  • Clearly flagged when a network request is needed.
  • No account, no sign-up, and no tracking of your content.
  • Powered by (MIT).
Built with
(radareorg/radare2)
License
MIT
Runs locally
No — requires a network request
Verification
Not yet verified
Input
Query
Output
Text
Open-source source & license

Built with radareorg/radare2. OpenToolVault provides the discovery and browser interface while crediting the original project maintainers.

Built with
License
MIT
View source on GitHub

Open-source project

OpenToolVault is an independent directory. We are not affiliated with or endorsed by this project.

References

Frequently asked

What is Radare2 used for?

Radare2 is used for reverse engineering, debugging, and analyzing binary files. It enables users to disassemble code, inspect memory, modify executables, and debug programs at the machine code level. It is widely used in malware analysis, firmware research, and security audits.

How does Radare2 work?

Radare2 operates as a command-line framework that interacts directly with binary files. It uses a modular architecture with plugins for tasks like disassembly, debugging, and analysis. Users issue commands to navigate memory, execute code, and inspect registers, with support for scripting in Rizin and Python for automation.

How do I analyze a binary with Radare2?

To analyze a binary, first install Radare2 and open the file using `r2 <file>`. Use `aaa` to auto-analyze the binary and identify functions. Then, use `p` to disassemble code, `d` to debug, and `pdf` to view function details. For advanced analysis, load plugins like `bin` for binary parsing or `asm` for assembly editing.

How does Radare2 compare to Ghidra or IDA Pro?

Radare2 is open-source and CLI-focused, making it lightweight and customizable for Unix systems. Ghidra and IDA Pro are commercial tools with GUI interfaces, offering more advanced features like decompilation and cross-referencing. Radare2 lacks some high-level abstractions but provides deeper control over low-level operations, appealing to developers and researchers who prefer scripting and customization.

How do I troubleshoot common errors in Radare2?

Common errors include missing libraries (e.g., `libbfd` for binutils) or incompatible architectures. To fix this, install dependencies via package managers or rebuild Radare2. If commands fail, check for typos or use `help` to verify syntax. For plugin issues, ensure plugins are enabled with `config` or reinstall them via `r2 -p <plugin>`.

Spotted something wrong with Radare2, or want to maintain it? See how to help.