> 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/user-interface/concepts/helper-tools.md). # Helper Tools Helper tools, also known as utilities, are small programs designed to enhance your IDA functionality. Most of these utilities are shipped alongside IDA and included with the IDA installation. ## Built-in tools These utilities handle specialized tasks, such as generating signature files or type libraries. Most of them live in the `tools` folder inside the main IDA installation directory; idapyswitch lives directly in the main installation directory itself. Some examples: * **Flair**: allows you to add your own compiler libraries to the FLIRT engine * **IDAClang**: a command-line version of IDAClang plugin * **idsutils**: helps create/maintain IDS files from DLLs * **loadint**: creates your own disassembler comment databases * [**Tilib**](/core/types/how-tos/creating-type-libraries/tilib.md): creates type libraries (til files) for IDA * [**git-ida**](/add-ons/teams/how-tos/git_ida_cli.md): lets Git store, transfer, and reconstruct packed IDA databases efficiently, for use with the Teams add-on * [**idapyswitch**](/getting-started/idapython-environment.md#idapyswitch): selects which Python shared library IDA loads at startup ## Additional tools in the Download Center The **IDA PIN tool** is available for download in the [My Hex-Rays Portal](https://my.hex-rays.com/dashboard/download-center). Additionally, the Download Center provides utilities for older IDA versions (prior to 9.1). ## How to use these tools? For detailed usage instructions and tips, including on tools not listed above, refer to the README file located in each tool's folder, where available. --- # 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/user-interface/concepts/helper-tools.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.