> 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.5/core/flirt/how-tos/makesig.md).

# Generate FLIRT signatures from analyzed binaries (Makesig)

The built-in Makesig plugin is a tool for generating FLIRT signatures from a current database. This tutorial shows how to create signatures from an analyzed binary.

{% hint style="info" %}
For more background on the Makesig plugin, see the [Makesig plugin overview](https://hex-rays.com/blog/an-overview-of-the-makesig-plugin/) on the Hex-Rays blog.
{% endhint %}

## How to make signatures from a working database

1. Export the patterns from the database into a `.sig` file.

   * In the opened database, navigate to **File → Produce file → Create SIG file...**.
   * Configure the options in the *Create .sig file* dialog and click **OK**.

   ![Create .sig file dialog](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-7fa3042ae395d96d58945ca9567778d13762d618%2Fcreate-sig-file-dialog.png?alt=media)

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>By default, Makesig skips unnamed functions (<code>sub_</code>, <code>loc_</code>, etc.). To include them, uncheck <strong>Valid, user-specified names only</strong> in the <em>Create .sig file</em> dialog.</p></div>
2. Re-import the `.sig` into the target database.
   * Go to **File → Load file → FLIRT signature file...** and select the `.sig` file you exported.

## Example: Migrating function names across binary versions

Here is a real scenario: a long-term reversing project with frequent new versions. With the Makesig plugin, you can migrate the carefully curated list of functions that you already reverse-engineered and exported as a signature file into the current binary (given that compiler flags didn’t change too much between releases). Say you identified an interesting function in the older release (source) binary and want to port that information to the newer binary:

![](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-39e92731fafac1f53344024584125da0f584a0b9%2Fmakesig.png?alt=media)

You can export a signature file for this function via **File → Produce file → Create SIG file...**

![Create .sig file dialog](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-af6ce2ee9eb2c120f3775a651acc17e1f5b5d180%2Fcreate-sig-file.png?alt=media)

Then, in the target database, you can import the signature file in the **Signatures** window. Open it via **View → Open subviews → Signatures**. Right-click to open the context menu and choose **Apply new signature...**. In the **List of available library modules** dialog, click **Load SIG file...** and select the `.sig` file you exported earlier.

![Import signature](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-525e7b63a3da3a182ef0252822fb8316b83befcf%2Fimport-signature.png?alt=media)

IDA applies the signature and reports that it found a match in the new database. And indeed, you can find the function, labeled as a library function, because its function name came from the signature file:

![Applied signature](https://492083732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFP6ibt8r6WPBHTqekG9u%2Fuploads%2Fgit-blob-bac1db65c7024d6d06a681715509e50f199ee4a7%2Fapplied-signature.png?alt=media)


---

# 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/ida-9.5/core/flirt/how-tos/makesig.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.