PlaybooksFor brands

The carousel

The swipeable post is its own format. Slide one as the hook, one idea per slide, designing for the swipe, and the last-slide call to action.

Adam Murray4 September 20268 min read
On this page

You have a good point to make, so you make an image with the point on it, post it, and it does nothing. The point was fine. The format was wrong. A single image gives the viewer everything at once and asks for nothing back. So they take it in, or don't, and scroll on either way.

A carousel (the swipeable set of slides on Instagram and LinkedIn) works differently. It doles the idea out one slide at a time, and each swipe is a small commitment the viewer makes to keep going. That sequence is the whole point of the format, and it is why a carousel can hold someone through an argument that a single graphic could never make land. It is also why a carousel built as "a few images posted together" almost always underperforms: the format is a sequence, and if you do not design the sequence you are not really using it.

Reach for a carousel when the idea has steps, or a before-and-after, or a list where each item earns its own moment. It is the format for "here is a thing explained", "here are five ways to", "here is how this changed", "here is the argument in order".

Reach for something else when the idea is a single image that needs no unpacking (a strong photo, a one-line statement, a product shot), because wrapping a single idea in a swipeable wrapper just adds friction. And reach for video when the thing is genuinely temporal: motion, a demonstration, a voice. A carousel is silent, still and self-paced, which is a strength for an argument and a weakness for anything that needs to move. If you are weighing a carousel against a clip, the retention logic of the moving-image alternative is in short-form video that holds; pick the format the idea actually is, not the one you can make fastest.

There is a distribution reason too. Because a carousel invites repeated interaction, a viewer who swipes through several slides has spent real time on the post, and both surfaces treat that dwell time as a signal worth acting on. The exact weighting is undocumented and shifts, so do not build a strategy on it. But a format that manufactures dwell time honestly is a useful thing to have in the mix.

Slide one is the whole click

Only the first slide is guaranteed to be seen. It appears in the feed exactly like a single image, and it has to do a single image's job (stop the scroll) plus one more: make the swipe feel worth it.

That means slide one is a hook, and the same logic that governs a video opening governs it. Open a question the viewer wants closed, promise a specific payoff, or state something that demands the explanation on slide two. What it must not do is give the whole idea away, because a first slide that resolves itself has removed the only reason to swipe.

Two design consequences, both covered properly in design principles for content and worth stating here in carousel terms. First, slide one has to read at feed size (small, moving, surrounded by competitors), so it lives or dies on contrast, one clear focal point, and type large enough to be legible on a phone at a glance. Second, the words on it have to carry, which is a specific craft: the discipline of copy that works on a graphic rather than in a paragraph is in writing copy that works on a graphic, and slide one is where it matters most.

A small, reliable trick: put a visible cue that there is more: a peeking edge of the next slide, an arrow, a "1/7", a sentence that clearly continues. The platforms show a dot indicator, but a designed cue does better, because it tells the viewer the swipe pays off before they have to gamble a thumb on it.

One idea per slide

The most common carousel failure is cramming. A slide with three points and a paragraph is a slide the viewer skims and swipes past, having absorbed none of it.

One idea per slide is the rule that makes the format work. Each slide should hold a single point, expressed in as few words as it takes, with enough space around it that the eye lands on the one thing that matters. The viewer is reading at swipe speed (a second or two per slide, often less), so a slide is not a page of a document. It is closer to a line of a speech: one beat, delivered, before the next.

This is liberating once you accept it. You do not have to fit the argument onto one slide, because you have as many as the idea needs. Spend them. A seven-slide carousel that makes one clean move per slide beats a three-slide carousel that makes the viewer work.

Designing for the swipe

A carousel is read in motion, so design the transitions, not just the slides.

Each slide should end slightly unresolved (a point that implies the next, a "but", a step that obviously has a step after it), so the swipe feels like following a thread rather than starting over. This is the same open-loop mechanism that holds a video, translated to a format the viewer controls. Because they control the pace, the loops have to be gentle and constant: every slide earns the next one.

Consistency does the quiet work. A shared layout, type and colour across the set means the viewer's eye does not have to re-orient on each swipe: it knows where the point will be and can spend its attention on the point itself. A carousel where every slide is laid out differently reads as effortful and slows the swipe to a stop. Keep the frame the same and let the content change inside it; the underlying grammar of that is, again, design principles for content.

One practical constraint worth naming: not everyone swipes to the end, and the drop-off compounds slide by slide. So the value cannot all live on slide six. Front-load enough that a viewer who stops at slide three still got something, and treat the later slides as depth for the people you have earned, not as the place you finally deliver.

The last slide: the call to action

The final slide is the one moment you have the attention of someone who read the whole thing. That is the most qualified viewer the post will ever have, and most carousels waste the slide on a logo or a "thanks for reading".

Ask for one thing. Save this for later, follow for more of these, tell me your version in the comments, read the linked piece. One clear action, matched to what the carousel just did: a how-to earns a "save this", an argument earns a "what's your take", a resource earns a "share with someone who needs it". Two asks split the response and usually get neither.

The caption is the other half of this. A carousel and its caption are one unit: the slides carry the idea and the caption carries the context, the nuance the slides were too tight to hold, and often the real call to action. Writing that caption is its own craft (the first line that survives the feed's truncation, the value, the ask), and it is worth treating as deliberately as the slides themselves rather than as an afterthought pasted in at upload.

The two platforms it lives on

Carousels behave slightly differently on Instagram and LinkedIn, and both change their specifics often enough that a remembered number is a liability.

On Instagram it is a native multi-image or multi-video post, and the maximum number of slides has moved over time. So plan the sequence around the idea, keep each slide's key content clear of the interface, and check the current limit and aspect-ratio guidance in Instagram's own help for posting multiple photos and videos before you build the template, rather than trusting a spec from a year-old post.

On LinkedIn the swipeable format is typically a document post (a PDF the platform renders as pages you swipe), which is a different production path from Instagram's image slides and has its own size and format rules. Confirm the current requirements in LinkedIn's own help centre before exporting, because a PDF that renders wrong turns a designed sequence into an unreadable one.

In both cases the craft above is the same. The platform mechanics are the part to re-check each time; the sequence logic is the part that lasts.

Where Acumin fits

Two shipped surfaces. Studio is where the carousel actually gets built: a consistent slide template, type and colour applied across the set, exported to the current spec for the platform you are posting to, which is most of the "designing for the swipe" problem solved in one place. And Content Analysis reads which formats earn engagement for accounts like yours, so the choice between a carousel, a single image and a clip is grounded in your category rather than in a habit.

Neither decides the format for you, and neither should. The format is a property of the idea; the tools just make the version you chose faster to ship well.

Do this today

Take your next single-image post idea and ask one question: does it have steps, or an order, or a list where each item deserves its own moment? If it does, it is a carousel, and you were about to under-serve it.

Then draft it as slides before you design anything: one idea per slide, in a plain document, slide one as the hook and the last slide as a single clear ask. If the sequence works in plain text, the design will make it better. If it does not, no design will save it, and you have found that out before spending an afternoon in the template.

Written by
Adam Murray
Founder, Acumin

Adam builds Acumin. He spends his days on the same two problems this library is about: working out what a piece of content is actually worth, and getting a brief through production without it turning into something else.

Want this done on your own channel?

Acumin reads your public content and your category and hands back what to make next. Every call comes with its confidence and the evidence it rests on. The first Snapshot is free.