# Render and carousel

> Mix native channel UI with React snapshots in one message using Render and Carousel.

You want native text plus React cards in one message. A header, a sale note, and a Buy button sit next to a product card that your app already draws in React.

Wrap each snapshot in `<Render alt>`. Group the slides in `<Carousel>`. The SDK draws each snapshot to a PNG and keeps the rest as native channel UI.

```tsx
import {
  Button,
  Carousel,
  CarouselCard,
  Header,
  Message,
  Render,
  Section,
} from "@copilotkit/channels/ui";

<Message>
  <Header>This week</Header>
  <Carousel>
    <CarouselCard>
      <Header>Shoes</Header>
      <Render alt="Red shoes" width={400}>
        <ProductCard product={shoes} />
      </Render>
      <Section>On sale</Section>
      <Button
        value="buy-shoes"
        onClick={async ({ thread }) => {
          await thread.post("Added the red shoes to your cart.");
        }}
      >
        Buy
      </Button>
    </CarouselCard>
    <Render alt="Hat">
      <ProductCard product={hat} />
    </Render>
  </Carousel>
</Message>
```

`alt` is required and must not be blank on `<Render>`. Its canvas inherits `render.width` and `render.height`, defaulting to 720 by 480 pixels. Set `width` and `height` on an individual `<Render>` to override them.

`<Image url>` shows a public URL image. It does not take children. Inside a carousel, supply both a URL and nonblank `alt` text. Carousel limits:

- A carousel holds 1 to 10 slides.
- A `<CarouselCard>` holds at most one header, one section, one image or snapshot, and three native buttons.

Use `thread.post()` or `thread.update()` for messages containing `<Render>`. These native messages keep normal message references and button callbacks. Ephemeral snapshots are unsupported: `thread.postEphemeral()` rejects `<Render>` before posting.

<Callout type="warn" title="No Channels Button inside Render">
  A Channels `<Button>` inside `<Render>` throws. A host HTML button is fine. The snapshot is a PNG, so that HTML button does not receive clicks.
</Callout>

Set the renderer, fonts, and styles once on `createChannel({ render })`. `<Render>` needs `render.renderer`, the same as an image post. See [Posting JSX as images](/teams/posting-jsx-as-images).

The Slack example posts this mix when you ask the agent to show a carousel. The agent calls the `render_carousel` tool in `examples/slack`.

This feature targets managed Slack and Teams:

- **Slack:** the SDK stores each PNG and puts its file handle in `slack_file.id`. Intelligence stages the image in Slack before posting the native message or carousel. Native buttons keep their action callbacks.
- **Teams:** the SDK embeds snapshots as data URIs in an Adaptive Card. The complete delivery packet, including all images, text, and actions, must fit the existing **64 KiB** limit. Oversized cards fail with an error explaining the limit. Reduce the snapshot dimensions, use public `<Image url>` images, or post a larger snapshot separately with `thread.post(jsx)`, which uses the managed upload path.

Run `pnpm channel` in `examples/slack` for the managed example. Direct adapters, including Discord and WhatsApp, reject `<Render>` with an error.

| Managed platform | Carousel output |
| --- | --- |
| Slack | Native carousel with interactive buttons |
| Teams | Adaptive Card carousel with interactive actions |
