> 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/face-filter.md).
# 面部滤镜
使用面部滤镜功能，让你的头像根据照片呈现出特定人物的外观。
{% hint style="danger" %}
Face Filter 功能仅适用于 Scale 方案及以上。
{% endhint %}
## **什么是 Face Filter？**
Face Filter 可让你使用参考照片，将虚拟形象的外观个性化为看起来像特定的人。
## **如何使用？**
### **1. 启用 Face Filter**
打开 **Face Filter** 选项，在虚拟形象自定义面板中。
### **2. 上传图片**
点击 **“上传你自己的图片”** 以添加照片参考。
### 3. 应用图片
点击已上传的图片以选中它。你的虚拟形象的脸会自动变形，变得与照片中的人相似。
### **4. 管理图片**
* 要删除图片，点击它并选择 **“删除图片”**.
* 你可以上传 **多张图片** 以尝试不同的外观。
借助 Face Filter，你可以打造更加逼真、个性化的角色——非常适合讲故事、培训模拟，或在虚拟环境中代表真实人物。
---
# 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/face-filter.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.
