> 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/ida-9.3/ida-actions/setupdata.md).

# SetupData

## Description

Setup data types. This command allows you to select the data types used in the round-robin carousel in the Data (action `MakeData`) command.

Valid data types are:

| Data Type   | Size           |
| ----------- | -------------- |
| byte        |                |
| word        | 2 bytes        |
| double word | 4 bytes        |
| float       | 4 bytes        |
| quadro word | 8 bytes        |
| double      | 8 bytes        |
| long double | 10 or 12 bytes |
| packed real | 10 or 12 bytes |
| octa word   | 16 bytes       |

Naturally, not all data types are usable for all processors. For example, Intel 8051 processor doesn't have the 'double word' type. Furthermore, this command allows you to select a data type for the current undefined item and convert it to data. Please note that if the current processor does not support a data type, you cannot assign it even if you have selected it. If you unselect all data types, IDA will use the 'byte' type.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hex-rays.com/ida-9.3/ida-actions/setupdata.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.