> 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.2/archive/graphing_tutorial.md).

# Graphing tutorial

IDA Pro has a tightly integrated disassembly view that is graph-based, giving a control flow view to the disassembly as opposed to the standard text-style disassembly output. Different colored arrows are used to distinguish the various types of flows. You can also zoom in or out of the graph for greater clarity. For complicated graphs, you can use the Graph Overview window which can provide you with overall awareness of the area that you are viewing in the graph.

Graphing also gives you the ability to rearrange, group, and collapse blocks in the graph. As only one function can be viewed in each individual graph, you can create other disassembly graphs for other functions, so that you can view two or more at the same time.

Here’s an overview of the Graph features:

{% file src="/files/C1QjvpZdnLmftaZnF4Ro" %}
Download Graphing tutorial
{% endfile %}


---

# 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.2/archive/graphing_tutorial.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.