> 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/video-node/text-to-video.md). # Text to Video ## Summary Text-to-Video models generate videos by taking a text prompt as input, using the prompt to guide scene composition, motion, and style, resulting in dynamic video content that matches the described narrative or visual concept.
### Parameters These are parameters that are applicable to all our base models.
ParameterTypeEffect on Output
PromptTextThe text prompt is processed through the selected model.
Aspect Ratio

Landscape - 16:9 (576x1024),

Portrait - 9:16 (1024x576), Square - 1:1.

This changes the output size of the node with a couple of options.
SeedSeedThe seed is a deterministic number that indexes generations from the model. It's typically randomized, but you can set a seed if there's a particular output you're looking for! Keep in mind that all parameters must be the same in order for a given seed's output to persist.
### How to use Prompting is everything for Text to Video. Refer to the [Text to Text](/nodes/text-node/text-to-text.md) card to explore more workflow combinations, or browse example workflows on the [Community page](https://app.flora.ai/community). --- # 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/video-node/text-to-video.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.