> For the complete documentation index, see [llms.txt](https://university.mindstudio.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.mindstudio.ai/building-ai-agents/blocks-reference/lip-sync-video-block.md).

# Lip Sync Video Block

Use AI to generate lip-synced and/or translated video in your AI agents. Sources may include image, audio, and/or video.

This block generates a video that lip syncs or translates from source asset(s). Sources may include the following:

* audio+video
* image+audio
* video

## Configuration

### Output

#### Output Variable

Save the generated video URL to a variable that can be used in other parts of your workflow.

#### History Access

Include the output variable in the workflow's history or hide it. Set to **Include** by default.

#### Branding

Include a small MindStudio watermark on the video. **None** by default.

### Model Settings&#x20;

#### Select Model

* ByteDance LatentSync (audio+video)
* ByteDance Omni Human 1.5 (image+audio)
* HeyGen Video Translate (video)
* Kling AI Avatar Standard (image+video)
* MeiGen Infinitetalk (image+audio)

{% hint style="info" %}
Please note that different models will have different configuration settings.
{% endhint %}


---

# 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://university.mindstudio.ai/building-ai-agents/blocks-reference/lip-sync-video-block.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.
