Swipeable posts that stop the scroll.
Give it a topic. It structures the whole carousel, hook, body, CTA, in your voice, your palette, your typography.
Sign up →One topic in. A dealt deck out.
A carousel is an argument with a running order: a hook that earns the swipe, a body that pays it off, and a close that asks for something.
- 01
The hook
Slide one has one job, and it is not to summarise. It is to be worth a swipe.
- 02
The body
The middle slides carry the argument, one idea each, in your voice.
- 03
The turn
Where the argument becomes advice a reader can use today.
- 04
The close
A specific ask, not a request to follow for more.
Topic in. Carousel out.
You give it a topic. That's it.
“5 mistakes new creators make.” Add an opening hook and slide count if you want, 3 to 10 slides.
It structures the whole arc
Hook, one idea per slide, CTA, written in your voice, colored from your palette, set in your pairing.
It lands in your history
Carousel + caption + hashtags, versioned with honest statuses. Re-open, revise or delete any run.
The anatomy of a carousel.
The hook slide
Slide one earns the swipe, a claim, a question, or a number that stings.
The body slides
One idea per slide, colored from your kit, never crowded.
The CTA slide
The arc ends with the ask, follow, save, share, still in your voice.
Caption + hashtags
Publish-ready and attached to every run, in your tag style.
What this engine reads from your brand:
Real screenshots only: the carousels board is still rolling out, and its screenshot lands here from a real run, never from a mockup.
For the detail-minded.
Input schema
Statuses & history
Every run is saved to your Studio history and versioned, re-open, revise or delete any run. Statuses are honest:
Limits & notes
Slide text regenerates per slide, no need to rebuild the whole deck for one weak line. Heavy load shows as queued, never as fake progress.
3 min read · 6 sections
Why a carousel is a structure problem, not a design problem
A carousel that works has an argument in it. Slide one earns the swipe, each middle slide advances exactly one idea, and the last slide asks for something. Templates cannot do that, because a template is a container and an argument is content. This is why so many generated carousels look fine and say nothing.
Repic writes the structure first. You give it a topic, optionally an opening hook and a slide count between three and ten, and it plans the arc before it fills a single frame. Then it renders that arc through your kit: your palette on the slide backgrounds, your type pairing on every heading, your voice rules on every line, your tag style on the hashtags.
The output is a finished unit, not a starting point: the slides, a publish-ready caption, and hashtags, saved to your history and versioned. Individual slide text regenerates on its own, so one weak line never costs you the whole deck.
Step by step, with nothing skipped
One topic line in
For example "5 mistakes new creators make". An opening hook and a slide count are optional; platform is pressed from your brand and overridable.
The arc is planned before anything is rendered
Hook, one idea per body slide, CTA. The plan is what makes the deck argue rather than list.
Your kit renders it
Palette, typography and voice come from the Brand Kit, so nothing asks you to pick a colour and nothing drifts between decks.
It lands in history, versioned
Carousel, caption and hashtags together, with honest statuses: ready, queued or failed. Never fake progress. Re-open, revise or delete any run.
Structure, made visible
Before
Topic in: "5 mistakes new creators make"
After
Slide 1 (hook): the mistake that costs the most, stated as a claim. Slides 2-6: one mistake each, in your voice, in your palette, with the fix attached. Slide 7 (CTA): the ask, phrased the way you would phrase it. Plus caption and hashtags in your tag style.
Nothing here required you to open a design tool or choose a layout. The slide count you asked for determined how many ideas the arc could carry, which is the only decision that actually mattered.
What this does not do
It is not a slide editor
You are not dragging text boxes. Regenerate a slide, edit its copy, or change the topic; the layout is a consequence of your kit, not a canvas.
It does not publish for you
The deck, caption and hashtags arrive finished. Posting is yours, which also means you read it before the internet does.
It will not fake a source
If your topic implies statistics or citations, supply them. The engine writes in your voice; it does not invent evidence to fill a slide.
Straight answers
How many slides should I ask for?
Ask for the number of ideas you actually have, between three and ten. The slide count is a constraint on the arc, not a padding target: a five-idea topic stretched to ten slides produces two slides of filler and a weaker deck.
Can I regenerate one bad slide without rebuilding the deck?
Yes. Slide text regenerates per slide, which is deliberate. Rebuilding a whole deck to fix one weak line is how people end up shipping the weak line.
Will my carousels look the same as everyone else using Repic?
The structure of a good carousel is genuinely similar across brands, because hook-body-CTA is what works. What differs is everything you can see and read: your palette, your type pairing, your voice rules, your audience. There are no shared templates to collide over.
Which platforms are the slides sized for?
The platform is pressed from your brand profile and is overridable per run, so a deck built for LinkedIn is not silently the wrong aspect ratio for Instagram.
Static Posts
Single-image posts, on brand.
Explore →Stories
Vertical frames sized per platform.
Explore →Free, no signup
Not ready to sign up? Run the brand kit generator instead.
Generate a complete brand kit free: palette with tints and shades, a font pairing, logo direction, and the brand voice other kit tools leave out.