> For the complete documentation index, see [llms.txt](https://docs.flora.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flora.ai/nodes/text-node/video-to-text.md).

# Video to Text

## Summary

Video to text can be performed by connecting a Video Node with a Text Node. Similar to Image to text, it can be used to extract information from any video inputs.

This combination of nodes can be used to take actions like **describe the video**, or **give a numbered list of frames with detailed description of visual content.**

<figure><img src="https://526296967-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWthH0GpcCHwVdtbvahZS%2Fuploads%2FNHoC1pglZd6Ar0arGMbT%2FScreenRecording2025-02-23at11.38.45AM-ezgif.com-optimize.gif?alt=media&amp;token=858deba5-7397-403b-81bb-e84b9f9c0df2" alt="" width="563"><figcaption></figcaption></figure>

## Prompt

* **"**&#x44;escribe this video in a few sentenc&#x65;**"**
* "Describe the composition and focal points of each frame, on how elements are arranged and how they guide the viewer's attention."
* "Illustrate the atmosphere of each scene, focusing on sensory details such as lighting, visceral color sensation, and spatial depth."
* "Describe how recurring motifs and visual patterns contribute to thematic development in the video."
* "Give me a list of frame in this video and describe each visual composition."


---

# 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.flora.ai/nodes/text-node/video-to-text.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.