PAGES
← all tools
◆ Reverse Engineering

x64dbg

2026.05.27 open-source

x64dbg is an open-source binary debugger for Windows, aimed at malware analysis and reverse engineering of executables you do not have the source code for.

Summary

x64dbg is an open-source binary debugger for Windows, free to use, distributed as a desktop application you download and run directly rather than install as a service. It targets malware analysts and reverse engineers working on executables without source code, letting them step through disassembly, set breakpoints, inspect memory and registers, and script automation through a plugin system. Recent work adds struct-view type inspection, intermodular call search in trace recordings, and early Linux debugger support via ptrace, alongside accessibility improvements for screen readers. First committed in 2013 and still active, with 190 contributors and nearly 300 commits in the past year, it shows no sign of stalling.

x64dbg is an open-source binary debugger for Windows, aimed at malware analysis and reverse engineering of executables you do not have the source code for.

How x64dbg helps

What is this unknown executable actually doing when it runs?

steps through the live disassembly instruction by instruction, with breakpoints, register and memory views updated at each stop, so behavior hidden from static reading becomes visible at runtime

Which API calls does this sample make, and where do they come from across loaded modules?

searches trace recordings for intermodular calls with a dedicated module name column, pinpointing exactly where in the code an external routine gets invoked

Did this thread already run through the code I care about, or is it still in library startup?

provides a run-to-user-code step that skips ahead past non-user modules, landing execution at the first instruction that belongs to the analyzed binary

Which instructions actually executed, and in what order, during a suspicious run?

records an execution trace that can be filtered at the module level, so noise from unrelated modules can be excluded when reconstructing what happened

Can I tell whether a saved memory breakpoint or trace file came from a compatible version before trusting it?

stores traces and blocks in an extended root JSON structure with user-defined blocks, so old and new trace files can be distinguished when loaded back in

all 18 features, with the evidence for each →

Languages

Chinese (Simplified) Documentation: Chinese (Simplified)

Features

18 capabilities

Built from x64dbg's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

What x64dbg offers you

  • Command-line interface2
  • Natural-language query1
  • Plugin API support1
  • Scripting language support1
All capabilities 18 capabilities
Register and CPU View Customization shipped Enables direct raw byte editing of registers, module RVA address display modes, and font size adjustments. 3 releases · first seen Aug 2025

release

  • Adds module RVA address display mode in the CPU view. 2026.05.27 · May 2026 · source · release history
  • Supports editing raw bytes of a register directly in the UI. 2026.04.20 · Apr 2026 · source · release history
  • Supports adjusting font size in RegistersView via Ctrl+scroll wheel. 2025.08.19 · Aug 2025 · source · release history
Breakpoint Management Enhancements shipped Adds bulk toggling of software breakpoints, expression validation feedback in dialogs, and copy shortcuts. 3 releases · first seen Apr 2026

release

  • Enables bulk toggling of software breakpoints across all selected instructions in the disassembly view. 2026.04.20 · Apr 2026 · source · release history
  • Adds expression validation with red/green border feedback directly in the breakpoint dialog. 2026.04.20 · Apr 2026 · source · release history
  • Adds copy shortcuts (Ctrl+C, Shift+Insert) in SearchListView and a copy address shortcut in the References tab. 2026.04.20 · Apr 2026 · source · release history
Debugging Workflow Improvements shipped Adds process detachment options, focus actions for windows, and call stack highlighting by module. 3 releases · first seen Jun 2025

release

  • Adds option to detach instead of terminate when attaching to a new process. 2026.04.20 · Apr 2026 · source · release history
  • Adds call stack highlighting by module or symbol. 2026.04.20 · Apr 2026 · source · release history
  • Adds Focus on Window action in the Handles view to bring a target window to the foreground. 2025.06.30 · Jun 2025 · source · release history
Trace Analysis Capabilities shipped Adds intermodular call searching, step filtering by module, and user-defined trace blocks. 3 releases · first seen Aug 2025

release

  • Supports user-defined blocks in trace and extends root JSON structure. 2026.04.20 · Apr 2026 · source · release history
  • Adds TraceSetStepFilter command for module-level trace filtering. 2026.04.20 · Apr 2026 · source · release history
  • Adds ability to search for intermodular calls in trace recordings, with a dedicated module name column — useful for pinpointing where APIs are called during execution. 2025.08.19 · Aug 2025 · source · release history
Headless and Scriptable Automation shipped Supports automated debugging workflows through headless mode, deterministic event loops, and startup command flags. 3 releases · first seen Jun 2025

Also counts toward: Command-line interface, Scripting language support

release

  • Rewrites the scripting engine to execute commands on a deterministic event loop, enabling more reliable complex automation scripts. 2025.08.19 · Aug 2025 · source · release history
  • Introduces -cf flag to specify a script file executed immediately on x64dbg startup, and -c for a one-shot startup command. 2025.08.19 · Aug 2025 · source · release history
  • Adds headless mode proof-of-concept for automated/scriptable debugging workflows. 2025.06.30 · Jun 2025 · source · release history
Dynamic Type Inspection shipped Enables on-the-fly type display, interactive selection with live previews, and configurable pointer depth limits. 3 releases · first seen Jun 2025

release

  • Adds Display type action directly from the register and stack views for on-the-fly data inspection. 2025.06.30 · Jun 2025 · source · release history
  • Introduces interactive type selection in the struct widget — live preview of data as you choose a type. 2025.06.30 · Jun 2025 · source · release history
  • Configurable default maximum pointer depth in the DisplayType command. 2025.06.30 · Jun 2025 · source · release history
Command Line Interface Extensions shipped Supports passing absolute paths for script files and renames common commands like 'Run to user code' for brevity. 2 releases · first seen Apr 2026

Also counts toward: Command-line interface

release

  • Supports passing an absolute path to the -cf command-line flag. 2026.05.27 · May 2026 · source · release history
  • Renames Run to user code to the rtu command. 2026.04.20 · Apr 2026 · source · release history
Data Export Features shipped Allows exporting tables to tab-separated values and saving function graphs as PDFs. 2 releases · first seen Aug 2025

release

Build System Modernization shipped Migrates the build infrastructure to CMake and Visual Studio 2022, enabling Linux builds via Wine. 2 releases · first seen Jun 2025

release

  • Enables building x64dbg under Linux via Wine with a custom CMake toolchain. 2025.08.19 · Aug 2025 · source · release history
  • Migrated build system to Visual Studio 2022 and CMake, reducing compilation to a single step. 2025.06.30 · Jun 2025 · source · release history
Context Menu Utilities shipped Provides quick actions for copying function call arguments and graph images directly to the clipboard. 2 releases · first seen Jun 2025

release

  • New context menu option to copy calling convention arguments for documenting or reconstructing function calls. 2025.06.30 · Jun 2025 · source · release history
  • New Copy Graph Image option copies the function graph directly to the clipboard. 2025.06.30 · Jun 2025 · source · release history
Hex Dump View Enhancements shipped Improves data representation by auto-rendering character arrays as strings and adding support for half-precision floats. 2 releases · first seen Jun 2025

release

  • Character arrays are now automatically rendered as strings in the struct/dump view. 2025.06.30 · Jun 2025 · source · release history
  • Adds half-precision (16-bit) float display support in the dump view, useful for graphics and ML model reversing. 2025.06.30 · Jun 2025 · source · release history
Cross-Platform Debugger Support shipped Introduces initial Linux debugger support via ElfBug ptrace engine with an AppImage build. 1 release · first seen Apr 2026

release

  • Adds initial Linux debugger support via the ElfBug ptrace engine with an AppImage build for cross/debugger, including pre-alpha architecture detection. 2026.04.20 · Apr 2026 · source · release history
Testing and Regression Framework shipped Introduces a new test framework with expanded memory breakpoint regression coverage. 1 release · first seen Apr 2026

release

  • Introduces a new test framework and significantly expanded memory breakpoint regression coverage. 2026.04.20 · Apr 2026 · source · release history
UI Accessibility Improvements shipped Adds screen reader support and UI automation capabilities across major views like Registers and Disassembly. 1 release · first seen Apr 2026

release

  • Adds initial accessibility support across Registers, Disassembly, Hex Dump, Trace Browser, and most table-based views, enabling screen readers and UI automation tools. 2026.04.20 · Apr 2026 · source · release history
Documentation Access System shipped Integrates documentation into the main repository to enable LLM-based querying via DeepWiki. 1 release · first seen Aug 2025

Also counts toward: Natural-language query

release

  • Moves documentation into the main repository, enabling LLM-based querying via DeepWiki. 2025.08.19 · Aug 2025 · source · release history
Calendar Versioning and Release Management shipped Uses calendar-based versioning with structured GitHub releases and tags to facilitate package manager integration. 1 release · first seen Jun 2025

release

  • Switches to CalVer (Calendar Versioning) with proper GitHub releases and tags for easier package manager integration. 2025.06.30 · Jun 2025 · source · release history
Plugin Host API shipped Provides signals and event callbacks for plugin authors to interact with UI changes and trace lifecycle events. 1 release · first seen Jun 2025

Also counts toward: Plugin API support

release

  • Adds selectionChanged signal to SearchListView for plugin/extension authors. 2025.06.30 · Jun 2025 · source · release history
Type System Extensibility shipped Supports bitfields, enums, and anonymous types to represent complex Windows SDK structures for inspection. 1 release · first seen Jun 2025

release

  • Adds bitfield, enum, and anonymous type support to the type system, enabling all Windows SDK types to be represented and displayed in the struct widget. 2025.06.30 · Jun 2025 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for x64dbg, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail x64dbg puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

4 entries

  1. May 20261
  2. April 20261
  3. August 20251
  4. June 20251
    Show

    4 entries

    Project health

    Issue, contributor and maintainer activity in x64dbg/x64dbg, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 29 +10 vs prior 12 months
    2. Maintainers 3 +2 joined · −2 left, last 12 months
    3. Bus factor 2 committers behind half the commits
    4. Community-filed 93% of issues opened, last 12 months
    5. Median time to close 68 days first maintainer reply 6.7 hours
    6. Open backlog 571 of 2,725 issues ever filed
    1. Issues opened / month 1 · 1 communitymaintainers
    2. Open backlog 571
    3. Contributors / month 5
    4. Commits / month 46
    5. Stars 49,567
    Issue themes, last 12 months
    • bugs 49%
    • features 27%
    • other 24%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Libraries its release ships

    What its latest release locks, checked against known advisories.

    None of its release's images build from a lockfile we can read.

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →