Carousels

A carousel is a tiny story and the sequence is what makes it work. Studio will happily let you style a deck that says nothing; structure first.

Choose a slide count

Slide counts are five or seven. Five is the tighter story and the one to default to. Seven earns its length only if each extra slide carries a distinct point rather than padding one.

Structure before styling

Decide what each slide says, in order, then design:

1. The hook slide has one job: earn the swipe. State the payoff, the tension or the surprising claim, and make it readable at a glance. If somebody reads only this slide, they should understand why the rest is worth their time.
2. The value slides each make exactly one point. A slide making two points is two slides.
3. The last slide says what to do next. One action, stated plainly.

Editing

Every slide's text is editable. So is the imagery: a slide can use a stock photo, an uploaded image, or an AI-generated one. See AI images, which also covers the per-slide generation cap.

Rendering and export

Rendering turns the laid-out slides into final images. Rendering a deck spends generations, because each slide is a real render; previewing does not.

A finished deck exports as a ZIP of images, ready to upload as a carousel. Whether your export carries a watermark depends on your plan. See brand styling in Studio.

Common mistakes

• Text too small. A carousel is read on a phone. If it is not legible in the thumbnail, it is not legible.
• The hook slide describing the topic instead of selling the swipe. "Five things about onboarding" is a table of contents, not a hook.
• A call to action that asks for two things. Pick one.