> 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/types/overview.md).

# Overview

## IDA type system fundamentals

The IDA type system is based on familiar C-like constructs such as:

* **Structures**: Aggregate data types that group multiple members.
* **Unions**: Allow overlapping the same memory with different data types.
* **Enums**: Provide named integer constants.

IDA ships with [type libraries](/core/types.md#type-libraries) out-of-the-box, but you can define custom types in the [Local Types window](/core/types.md#type-management-essentials-local-types-view).

## Type definitions sources

* Built-in or custom [type libraries](/core/types.md#type-libraries)(.til files)
* Custom types
* Debug information (e.g., PDB or DWARF)

## Type libraries

IDA ships with type libraries for popular platforms and operating systems. They provide high-level, predefined data types that can be used in your analysis. You can view a list of currently loaded type libraries in the **Type Libraries** window (**View → Open subviews → Type Libraries**, or <kbd>Shift</kbd>+<kbd>F11</kbd>)

{% hint style="info" %}
**Relation between Local Types and Type Libraries**:

In IDA, **Local Types** are custom or imported type definitions specific to your current project, while **Type Libraries** provide pre-defined types for common platforms and architectures. Types in the **Type Libraries**, once referenced, are copied into the IDB and appear under the **Local Types** window.
{% endhint %}

Type library may contain:

* function prototypes
* typedefs
* structure and enum definitions

**See also**

* [TILIB](/core/types/how-tos/creating-type-libraries/tilib.md) and [IDAClang](/core/types/how-tos/creating-type-libraries/idaclang_tutorial.md) tutorials on creating custom type libraries
* Type libraries in[ Igor's tip of the week](https://hex-rays.com/blog/igors-tip-of-the-week-60-type-libraries/) blog post

## Local Types view

The Local Types view provides a centralized hub for managing and customizing type definitions directly within the IDA UI. To access this view, navigate to **View → Open subviews → Local Types** or press <kbd>Shift</kbd>+<kbd>F1</kbd> keys.

![Local Types window](https://1926493584-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FD7fgl4EL0WWJ18ZQcIxE%2Fuploads%2Fgit-blob-25b680f5d49dc780cd6655b0bf0f349f3c057596%2Flocal-types-window.png?alt=media)

The Local Types view allows you to:

* Create custom structures, unions, and enums
* Modify and delete existing types

See also:

* Refer to the [Working with Types](/core/types/how-tos/working-with-types.md) for a practical step-by-step tutorial covering the essentials of type management


---

# 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/types/overview.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.
