> 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/9.1/user-guide/user-interface/menu-bar/edit/convert-to-string-literal.md).

# Convert to string literal

#### Convert to string literal

```
 Action    name: MakeStrlit
 
```

This command converts the current unexplored bytes to a string.

The set of allowed characters is specified in the [configuration](/9.1/user-guide/configuration/configuration-files.md) file, parameter StrlitChars. Character '\0' is not allowed in any case. If the current [assembler](/9.1/user-guide/user-interface/menu-bar/options.md#specify-target-assembler) does not allow characters above 0x7F, characters with high bit set are not allowed.

If the [anchor](/9.1/user-guide/disassembler/navigation/anchor.md) has been dropped, IDA will take for the string all characters between the current cursor position and the anchor.

Use the [anchor](/9.1/user-guide/disassembler/navigation/anchor.md) if the string starts a disallowed character.

This command also generates a [name](/9.1/user-guide/disassembler/navigation/how-to-enter-an-identifier.md) for the string. In the [configuration](/9.1/user-guide/configuration/configuration-files.md) file, you can specify the characters allowed in names (NameChars).

You can change the literal string length using [Array](/9.1/user-guide/user-interface/menu-bar/edit/convert-to-array.md) command.

The GUI version allows you to assign a special hotkey to create Unicode strings. To do so, change the value of the StringUnicode parameter in the IDAGUI.CFG file.

#### Pascal Strings

To create Pascal style strings (with first byte indicating string length) use [Set String Style](/9.1/user-guide/user-interface/menu-bar/options.md#string-literal-style-dialog) command.

See also [Edit](/9.1/user-guide/user-interface/menu-bar/edit.md) submenu


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hex-rays.com/9.1/user-guide/user-interface/menu-bar/edit/convert-to-string-literal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.