> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/wu-dai-ma-ti-yan/avatar-studio-experiences/customizing-your-avatar.md).

# 自定义你的头像

了解如何使用 Avatar Studio 配置器从视觉和行为上个性化你的 Convai 头像。

## **概述**

一旦创建好角色，您就可以开始使用 **头像工作室**.

{% embed url="<https://youtu.be/-08pVVY5yQo>" %}

## 您可以自定义的内容

在头像工作室中，您可以执行以下操作：

* **选择一个示例头像，**

  从一系列现成可用的高保真头像库中挑选。
* **自定义外观**\
  修改面部特征、服装、发型和其他视觉元素，以体现您角色的身份。
* **上传您自己的头像**\
  想要独特设计？上传您自己的 3D 头像模型，完全掌控其外观。
* **设置智能动画**\
  配置挥手、点头、回应和思考等动作——这些都会在对话中根据上下文自动触发。
* **选择虚拟环境**\
  将您的头像放置在沉浸式数字场景中，使其与您的体验语气和使用场景相匹配。
* **调整交互行为**\
  微调头像的沟通方式，例如说话风格、语气和用户互动偏好。
* **设备与品牌适配**\
  自定义头像界面在不同设备上的表现，并使其与您的品牌视觉形象保持一致。

在完成自定义后，只需 **保存并发布** 您的头像，即可将其带入角色对话中。


---

# 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.convai.com/api-docs/zh/wu-dai-ma-ti-yan/avatar-studio-experiences/customizing-your-avatar.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.