How-to carousels for apps: teach one thing and earn the save

A how-to carousel for an app teaches one useful thing, one step per slide, so the viewer can follow along now or save it for later. The cover promises a specific result, the middle slides give numbered steps, a recap slide makes it worth saving, and the app appears where it genuinely helps: as one of the steps, or on the last slide with its real icon and a real screenshot.

What is a how-to carousel for an app?

A how-to carousel (also called a tutorial carousel) is a multi-image post that walks the viewer through a task step by step. For an app, the task is usually something your audience already does, with or without you: budgeting a month, restarting a habit, learning new words, cleaning up a camera roll.

The difference from a regular app carousel is the deal you offer. A promo carousel argues that the viewer has a problem and your app solves it. A how-to carousel gives them something useful right away, whether they install or not. That's what makes it worth saving.

Why do tutorial carousels work for apps?

• They're useful on their own. The viewer gets value before you ask for anything, which earns attention for the moment you do ask.
• They show you understand the task. An app that teaches a task well is an app people trust to handle it.
• They're evergreen. "How to plan a week of dinners" is as useful in March as it is in October.
• They suit the format. Steps fit naturally on slides, and the viewer moves at their own pace.

How do you choose the one thing to teach?

One carousel, one task, one result. If your outline needs the word "and" in its title, it's two carousels.

Good tutorial topics have four traits:

• A task your audience already does. Not a task your app invented.
• A result in plain words. "A budget for next month", "a clean camera roll", "five words you'll remember".
• Steps people forget. If they'd remember every step after reading it once, there's nothing to save.
• A natural place for your app. Somewhere in the task, your app makes a step easier. If it doesn't, the post is still useful, but it won't do much for your app.

How should a tutorial carousel be structured?

A tutorial needs a few more slides than a promo carousel, because each step gets its own. Seven to nine slides is a common range for how-tos.

The cover: promise the result, not the topic

"Budgeting tips" is a topic. "Find the subscriptions you forgot, in 4 steps" is a result. A cover that names a result tells the viewer exactly what they'll have by the last slide, and the step count tells them how long it will take. The curiosity-gap and true-promise patterns in our hook formulas adapt well to tutorial covers.

How to write step slides

• One step per slide. If a step has two actions, split it.
• Number every step. "Step 3 of 5" tells the viewer how far they've come and how much is left.
• Start with a verb. "List every payment that repeats" is clearer than "Repeating payments".
• Show the action. An image of the thing being done (a list, a calendar, a screen) beats a decorative picture.
• Keep headlines short. Under ten words, with an optional line of detail beneath.

Where should your app appear in a how-to carousel?

There are three honest places for it:

For reaching new people, the first two work best. The tutorial should still make sense to someone who never installs your app. If every step needs the app, it's a product tour, and viewers can tell.

Whichever placement you choose, keep the app name and logo off the cover. The last slide shows the real icon, a real screenshot and one call to action, as the carousel playbook recommends for every app carousel.

Why are saves the signal to watch?

A like takes a second and means "nice". A save means "I'll need this again". For a tutorial, that's the clearest sign you taught something useful.

Platforms don't publish exactly how they weigh each interaction, so treat saves as feedback on your content rather than a ranking trick. A sensible way to read them:

• Saves relative to reach. Compare tutorials with each other, not with your promo posts.
• Comments with follow-up questions. "What if I miss step 2 twice?" means people are trying it.
• Shares to direct messages. People send tutorials to the friend who needs them.

To design for saves:

• Add a recap slide that holds every step on one screen.
• Make the steps reusable. A checklist or a simple template is something they'll come back to.
• Ask once, in the caption. "Save this for next payday" is fine. Asking on every slide isn't.

To decide which numbers to track across all your posts, see the guide to social media metrics for apps.

How to make a how-to carousel, step by step

1. Pick the task and the result. Finish this sentence: "By the last slide, the viewer can [result]."
2. List the steps, then cut any step a viewer could skip and still get the result.
3. Write the cover as a result with a realistic count: "in 4 steps", not "in seconds".
4. Write one slide per step, numbered and starting with a verb.
5. Add a common-mistake slide and a recap slide.
6. Decide where the app appears, and check that every claim about it is on your App Store listing.
7. Build the last slide from your real icon and a real screenshot.
8. Write a caption that repeats the result and asks for one action. The captions and hashtags guide covers search-friendly first lines.

ReelMyApp makes carousels of 3 to 10 slides in 3:4, 1:1 or 9:16, so a seven-slide tutorial fits. You can rewrite any slide's headline, supporting line or visual direction and redraw it, which helps when you want each step worded exactly. The last slide always shows your real icon and a real screenshot with a download call to action. A seven-slide Draft version in one language costs 12 credits (5, plus 1 per slide), so you can check the flow before remaking it in Standard or HD.

Examples of how-to carousels for fictional apps

These examples are for apps that don't exist, and each assumes its listing supports what the app slide says.

Budgeting app: "Find the subscriptions you forgot, in 4 steps"

• Cover: "Find the subscriptions you forgot, in 4 steps."
• Step 1: "Open last month's statement."
• Step 2: "Mark every payment that repeats."
• Step 3: "Check each one against what you actually used."
• Step 4: "Cancel one today. Not all of them."
• Mistake: "Don't skip the yearly ones. They hide."
• Recap: all four steps on one slide.
• App: icon, screenshot and a one-line promise taken from the listing.

Habit tracker: "How to restart a habit after a missed week"

Steps: shrink the goal to two minutes, do it at the same time as before, track the days you show up instead of the streak, and decide now what you'll do on the next missed day. The app appears in step 3, where the tracking happens. The mistake slide: "Don't restart at your old goal. Start smaller."

Language app: "Practice listening in 10 minutes a day"

Steps: pick audio slightly above your level, listen once without text, listen again with text, then repeat one sentence out loud. The app appears only on the last slide, as a source of short daily audio. The tutorial works with any audio the viewer already has.

Photo organizer: "Clean up your camera roll in one sitting"

Steps: delete screenshots first, then duplicates, then blurry shots, then mark the keepers as favorites. The mistake slide: "Don't start with old photos. You'll get nostalgic and stop."

Common mistakes with tutorial carousels

• Teaching three things at once. Split them into a series instead.
• Steps without verbs. "Repeating payments" isn't a step. "List your repeating payments" is.
• A product tour dressed as a tutorial. If the tutorial is useless without the app, call it a feature walkthrough and aim it at existing users.
• No recap slide. It's the slide people screenshot, and often the reason they save.
• Unrealistic covers. "In 30 seconds" sets up disappointment when the task takes ten minutes.
• Facts the listing doesn't support. The app slide follows the same rule as every other post: no invented features, numbers or reviews.

Tutorials also make a natural recurring series. If you plan your posts around a few themes, a weekly how-to fits well as one of your content pillars.

Key takeaways

• A how-to carousel teaches one task with one clear result, one step per slide.
• Put the result on the cover, number the steps, and add a common-mistake slide and a recap.
• Place the app where it genuinely helps, and keep the tutorial useful without it.
• Saves are the signal that a tutorial worked; a recap slide gives people a reason to save.
• Keep the app name off the cover and end with the real icon and a real screenshot.

Frequently asked questions

What is a how-to carousel?

A multi-image post that teaches one task step by step, with one step per slide. For an app, the task is usually something your audience already does, and the app appears where it genuinely helps.

How many slides should a tutorial carousel have?

Seven to nine is a common range: a cover, one slide per step, a common-mistake slide, a recap and the app slide. Cut any step the viewer could skip and still get the result.

Should a tutorial carousel be about my app?

For reaching new people, make it about the task and let the app handle one step or appear at the end. A tutorial that only works inside your app is a feature walkthrough, which suits existing users better.

Why do saves matter for tutorial carousels?

A save means someone plans to come back to the post, which is the clearest sign a tutorial was useful. Platforms don't publish exactly how they weigh saves, so treat them as feedback on your content, not a ranking trick.

What makes people save a carousel?

Steps they won't remember after one read, a recap slide that holds everything on one screen, and a checklist or template they can reuse.