> 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/8.5/user-guide/user-interface/menu-bar/edit/operand-types/convert-operand-to-stack-variable.md).

# Convert operand to stack variable

```
 Action    name: OpStackVariable
 
```

This command converts immediate operand(s) type of the current instruction to an offset to stack variables, i.e. a local variable or function argument in the stack.

You need to [define](/8.5/user-guide/user-interface/menu-bar/edit/functions.md#stack-variables-window) stack variables before using this command.

If the current operand is based on the value of the stack pointer (\[ESP+xxx]) and the SP value is traced incorrectly, then you need to correct SP value using [change stack pointer](https://github.com/HexRaysSA/docs/blob/8.5/user-guide/user-interface/menu-bar/edit/operand-types/operand-types/functions.md#change-stack-pointer) command.

If a range is selected using the [anchor](/8.5/user-guide/disassembler/navigation/anchor.md), IDA will perform 'en masse' conversion. It will convert immediate operands of all instructions in the selected range to stack variables. However, IDA will ask you first the lower and upper limits of immediate operand value. If the operand value is >= lower limit and <= upper limit then the operand will be converted to stack variable, otherwise it will be left unmodified.

When you use this command, IDA deletes the [manually](/8.5/user-guide/user-interface/menu-bar/edit/operand-types/user-defined-operand.md) entered operand.

If the cursor is on the first operand (the cursor is before ',') then the first operand will be affected; otherwise all other operands will be affected.

See also: [Edit|Operand types](/8.5/user-guide/user-interface/menu-bar/edit/operand-types.md) submenu. [Enter #th operand manually](/8.5/user-guide/user-interface/menu-bar/edit/operand-types/user-defined-operand.md) commands. [Define stack variables...](/8.5/user-guide/user-interface/menu-bar/edit/functions.md#stack-variables-window)


---

# 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/8.5/user-guide/user-interface/menu-bar/edit/operand-types/convert-operand-to-stack-variable.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.