> For the complete documentation index, see [llms.txt](https://docs.hex-rays.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hex-rays.com/core/decompiler/overview.md). # Overview ## What are IDA decompilers? IDA decompilers transform low-level machine code into clear, C-like pseudocode, enabling faster and more intuitive binary analysis directly on top of disassembly. By reconstructing program structure, types, and logic, they significantly reduce the effort required to understand complex binaries. The decompiler output is generated in seconds and is fully interactive: you can rename variables, adjust types, and refine the pseudocode as your understanding evolves. With a rich type system, recognition of compiler idioms, and a highly extensible SDK, IDA decompilers adapt to a wide range of analysis tasks. ## Local vs. cloud decompilers IDA decompilers are available as **cloud-based** or **local**, depending on your IDA plan. Local decompilers run entirely on your machine, so you can decompile offline, with no network dependency. Cloud decompilers require an internet connection, since part of the decompilation is performed remotely. IDA automatically loads the appropriate decompiler based on the input file. If no suitable decompiler is found, none will be loaded. ## Decompiler types/flavors IDA Decompilers come in 12 different flavors: * x86 decompiler (32-bit code) * x64 decompiler (64-bit code) * ARM decompiler (32-bit code) * ARM64 decompiler (64-bit code) * PowerPC decompiler (32-bit code) * PowerPC64 decompiler (64-bit code) * MIPS decompiler (O32 and N32 ABI) * MIPS64 decompiler (N64 ABI) * RISC-V decompiler (32-bit code) * RISC-V 64 decompiler (64-bit code) * ARC decompiler (32-bit code) * V850 decompiler (32-bit code) ## Where to find it ### Pseudocode View The Pseudocode View is the primary interface for analyzing decompiled code. It presents the binary program as high-level, C-like pseudocode that is easy to read and understand. ### Microcode View The Microcode View provides access to the intermediate representation (IR) used internally by the decompiler. This low-level view exposes the step-by-step transformations and operations that bridge the gap between assembly and pseudocode. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hex-rays.com/core/decompiler/overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.