> For the complete documentation index, see [llms.txt](https://help.vectary.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.vectary.com/documentation/design-process/design-mode/3d-text.md).
# 3D Text
The 3D Text tool allows for the creation of editable 3D typography directly within the scene. Font, size, depth, and other parameters can be customized to integrate text seamlessly into a design.
Text can also be dynamic by using **expressions** and **variables -** [Variables & Expressions](/documentation/3d-configurator/variables-and-expressions.md)
The 3D text tool provides comprehensive customization options similar to those found in standard text editors.
{% hint style="success" %}
A wide selection of fonts is available, with support for custom font uploads in **`OTF`** format
{% endhint %}
* **Quality** – increasing this value adds more polygons, improving the detail and smoothness of the text.
* **Depth** – adjusts the extrusion depth of the text
* **Contour offset** – expands the outline of the letters
To edit individual letters separately, convert the 3D text into geometry:
{% embed url="" %}
---
# 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://help.vectary.com/documentation/design-process/design-mode/3d-text.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.
