> 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/disassembler.md). # Disassembler Everything you need to understand and get the most out of IDA disassembler. ### Basic Resources

	Cover image
Overview	overview.jpg	Overview
Supported Processors	Supported processors.jpg	Supported processors
Supported File Formats	supported file formats.jpg	Supported file formats
Disassembly Gallery with Examples	Disassembly gallery.jpg	Examples

### Going deeper


Learn how IDA handles segment address space	Segment Address Space
Understand bitfields and how to work with them	Bitfields
Load Windows dump files with the Windmp loader	Windmp file loader
Analyse Apple Dyld Shared Caches	Dyld Shared Cache
Learn how IDA uses environment variables	Environment Variables

View all [Concepts](/core/disassembler/concepts.md) ### Try it yourself


Work with bitfields	Bitfields tutorial
Work with structures	Structures tutorial
Define data types, operands and constructs	Data types, operands and constructs
Unpack hostile PE executables	Unpack hostile PE executable

View all [How-tos](/core/disassembler/how-tos.md) --- # 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/disassembler.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.