> 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/editions-and-licenses/license-types/ida-pro-headless/reference/package-contents.md).

# Package contents

IDA Pro Headless ships as one ready-to-use zip per platform, on the [My Hex-Rays portal](https://my.hex-rays.com/), under **Download center → Installers → Release → IDA Pro Headless**, in a folder per version.

## Supported platforms

| Platform             | On the portal                            | File                                | Docker image            |
| -------------------- | ---------------------------------------- | ----------------------------------- | ----------------------- |
| Linux x64            | **IDA Pro Headless linux:x86\_64 9.5**   | `ida-pro-headless-9.5-x64linux.zip` | Yes                     |
| Linux arm64          | **IDA Pro Headless linux:arm64 9.5**     | `ida-pro-headless-9.5-armlinux.zip` | Yes                     |
| macOS, Apple silicon | **IDA Pro Headless mac:arm64 9.5**       | `ida-pro-headless-9.5-armmac.zip`   | No                      |
| Windows x64          | **IDA Pro Headless windows:x86\_64 9.5** | `ida-pro-headless-9.5-x64win.zip`   | Yes (Windows container) |

On macOS, Docker runs Linux containers: use the image of the Linux package. See [Run IDA Pro Headless in Docker](https://docs.hex-rays.com/editions-and-licenses/license-types/ida-pro-headless/how-tos/run-in-docker.md).

## What is in a package

Every package has the same layout. Its texts are written for its platform (for example `setup.ps1` instead of `setup.sh` on Windows).

```
ida-pro-headless-9.5-x64linux/
  README.md               start here: setup, scripts, idat, Docker, update, remove, support
  AGENTS.md               for coding agents: environment, API, rules
  BUILD.txt               which build this is; include it when contacting support
  setup.sh                accepts the license agreement for the user (setup.ps1 on Windows)
  examples/
    check_license.py      takes a seat without opening a database, prints the license
    list_functions.py     analyzes a binary and lists its functions
    wait_for_seat.py      waits for a free seat, then analyzes a binary
    licensing.py          what the three share: the seat IDA_LICENSE names, online or offline
  license-client/         the license server's client, to borrow a seat for an offline machine
  docker/                 Linux and Windows x64 only
  ida-pro-headless-9.5/   IDA Pro Headless, installed, as the installer leaves it
```

The `ida-pro-headless-9.5/` folder is a regular IDA installation: this is the folder `IDADIR` points to. It holds `idat`, idalib and the `idapro` Python module (in `idalib/python/`).


---

# 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/editions-and-licenses/license-types/ida-pro-headless/reference/package-contents.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.
