> 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/specification/supported-file-formats.md).

# Supported file formats

IDA Pro can disassemble all popular file formats. The list contains some, but not all, of the file types handled by IDA Pro.

* MS DOS
* EXE File
* MS DOS COM File
* MS DOS Driver
* New Executable (NE)
* Linear Executable (LX)
* Linear Executable (LE)
* Portable Executable (PE) (x86, x64, ARM, etc)
* Windows CE PE (ARM, SH-3, SH-4, MIPS)
* Mach-O for OS X and iOS (x86, x64, ARM and PPC)
* Apple Dyld Shared Cache (DSC) — see [DSC Workflow](/core/disassembler/concepts/dsc-workflow.md)
* Dalvik Executable (DEX)
* EPOC (Symbian OS executable)
* Windows Crash Dump (DMP)
* XBOX Executable (XBE)
* Intel Hex Object File
* MOS Technology Hex Object File
* Netware Loadable Module (NLM)
* Common Object File Format (COFF)
* Binary File
* Object Module Format (OMF)
* OMF library
* S-record format
* ZIP archive
* JAR archive
* Executable and Linkable Format (ELF)
* Watcom DOS32 Extender (W32RUN)
* Linux a.out (AOUT)
* PalmPilot program file
* AIX ar library (AIAFF)
* PEF (Mac OS or Be OS executable)
* QNX 16 and 32-bits
* Nintendo (N64)
* SNES ROM file (SMC)
* Motorola DSP56000 .LOD
* Sony Playstation PSX executable files,
* object (psyq) files
* library (psyq) files

Check out the list of [supported processors](/core/disassembler/specification/supported-processors.md) and screenshots of many processor disassemblies in the [gallery](/core/disassembler/disassembly-gallery.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/specification/supported-file-formats.md?ask=<question>&goal=<user_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.