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

# Composer

The Composer is your layout engine. It lets you layer multiple elements — images, text overlays, logos, graphics — into a single composed visual, similar to basic design tools.

Common use cases include placing a logo on a generated image, adding text overlays to product shots, or assembling multiple generated elements into a final ad creative.

The Composer supports both image and video output. Configure layer positions, sizes, and ordering directly in the node's visual editor.

This unlocks workflows that were impossible before:

* **Localize 20 ads in 20 languages** without rebuilding layouts manually
* **A/B test 50 headline variations** without touching a design tool
* **Generate seasonal campaign assets on autopilot**

### Quickstart (2 minutes)

{% embed url="<https://youtu.be/WSC_HpueuBg>" %}

Think of it as having a design canvas directly inside your agent where you can arrange, layer, and finalize your creatives:

* Generate all elements through your agent
* Connect them as inputs for the Composer node
* Set up your rules and guardrails (layout, typography)
* Run the node, let the Composer do its job
* Download the finished creatives

### When to use the Composer

Use the Composer node when your agent generates multiple elements that need to be combined into a final asset:

* **Ad creative production** - Combine product shots, headlines, logos, and CTAs into finished ad formats
* **Asset localization** - Create the same creative in multiple languages without rebuilding layouts manually
* **Social media templates** - Assemble branded posts with consistent layouts across platforms
* **A/B test variations** - Generate dozens of ad variants by swapping elements without manual composition
* **Multi-element campaigns** - Bring together background images, product photos, text overlays, and branding

### Use cases examples

<details>

<summary>Static ad creation</summary>

Create polished ad creatives by combining:

1. Background or lifestyle image → Composer
2. Product shot → Composer
3. Generated headline → Composer
4. Brand logo → Composer
5. CTA button or text → Composer

Result: Campaign-ready ad creative without leaving Pletor

</details>

<details>

<summary>Localized campaigns</summary>

Generate one ad template, then create variations for different markets:

1. Set up your composition once in the Composer
2. Connect an AI Text node with localization instructions
3. Run the agent multiple times with different language inputs
4. Each run produces the same layout with localized text

Result: 10 market variations in the time it takes to create one

</details>

<details>

<summary>A/B test variants</summary>

Scale your testing by programmatically swapping elements:

1. Create your base composition in the Composer
2. Use Control nodes to let users choose between headline options
3. Connect multiple image variants to test different visuals
4. Run the agent to generate dozens of testable variations

Result: A complete testing suite generated automatically

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pletor.ai/build-agents/nodes/composer.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.