How to batch create TikTok slideshows: a one-sitting workflow for a week of posts

How do you batch create TikTok slideshows in one sitting?

Batching means doing each stage once for the whole week instead of repeating the full cycle for every post. There are five stages.

1. Plan. Choose the topics and the formats for the week, and write them on one sheet.
2. Generate. Make several slideshows per topic, more than you need.
3. Review. Read every candidate in one pass and keep the best.
4. Export. Render the kept slideshows into one folder with their captions.
5. Schedule or post. Queue them in a scheduler, or upload them in the TikTok app.

In our tests, generation is the fast stage. The slow stages are the two that need your judgment: planning and review.

How long does a batch session take?

Only one stage has timings we measured ourselves: generation. On 4 November 2026, ten six-slide slideshows from one topic took 88.0 and 101.6 seconds with a local Ollama model, 259.2 and 207.4 seconds with Claude Code, and 434.2 and 443.8 seconds with Codex, on one Apple M5 Pro Mac with other agents running (method and caveats). Everything else in the table below is a planning assumption, not a measurement.

Example: seven posts for one week, built from two topics.

That adds up to roughly three hours. Only the generation step is measured; everything else is our assumption. If your session runs longer, it is almost certainly the review, and that is the part worth protecting. Your own numbers will differ, so time your first batch and replace our assumptions.

Step 1: Which topics and formats go into a week?

Choose the topics you can speak about with confidence (two in the timing example above, five in the example below), then give each post a format so the week does not look like one post repeated. Formats such as a listicle or a would-you-rather change the structure while the topic stays yours. The template overview and slideshow ideas help when you are stuck.

Use one sheet for the whole batch.

Week of {date} · account {name}
Post 1 · {day} · format {format} · topic {topic} · slides {number}
Hook angle: {mistake / surprise / choice / number}
Caption note: {one line to include}
Post 2 · {day} · format {format} · topic {topic} · slides {number}
…
Images: folder {path}, collection {name}
Do not use: {names, handles, claims you cannot support}

Here is a fictional example for a houseplant account.

Notice that this example gives every post its own topic while two formats repeat. The timing example above uses two topics for seven posts. Pick the split that matches how much you can say about each topic.

Step 2: How many slideshows should you generate per topic?

More than you plan to post. The app can make up to ten slideshows from one topic in one job, with six slides per post by default. Generation is cheap in time, as the table shows, and reading is expensive. So ask for ten and keep the best few; the timing example above keeps seven of twenty.

Judge candidates mainly on the first slide. In our view, a slide one that gives no reason to swipe leaves the rest unseen. No source measures how much slide one matters, so treat this as a habit to test. Slideshow hooks and curiosity hooks show patterns to compare against.

Which AI you choose changes how long a batch feels. Ollama is the fastest of the three we measured; it is free and local (Ollama setup and numbers). Claude Code and Codex are slower in our tests and use your own plan. Gemini was not measured. Fyslide itself charges nothing for AI.

Step 3: What do you check in the review pass?

Review all candidates in one sitting. Reading the same format in a row makes repeated phrasing and shaky facts easy to spot.

• Slide 1 states the payoff in one short sentence.
• Each slide holds one idea and stays under your word limit (words per slide).
• Every number and claim was supplied by you or checked. AI text can invent facts.
• No two posts in the batch open with the same phrase.
• Images are ones you may use, and no handles or private details show.
• The slide count fits the tool you will post with (see Step 5).
• The caption exists, and its length is within TikTok's limit.
• The last slide's call to action matches what you want viewers to do.

Text that reads machine-made is the most common fix. Making AI slide text sound human lists what to change.

Step 4: How do you export a batch?

The app exports the slides as PNG or JPG together with the caption and a zip, into a folder you choose. You upload the files yourself. A simple structure helps: one folder per week, one subfolder per account, and the post number in each name. Open two exported slides on your phone before you schedule the rest, because a phone shows crowding and small text that a desktop hides.

Step 5: How do you schedule or post the batch?

Fyslide does not post to TikTok or Instagram. Posting is marked Coming soon, included in your lifetime access as an update. Today you have two routes.

• Post in the TikTok app. As of November 2026, TikTok's Creator Academy (opens in a new tab) says a photo post can hold up to 35 images and describes the Add Post, Photo, Upload flow. You can do this for each exported folder.
• Queue in a scheduler. As of 5 November 2026, the limits differ. Buffer's help center (opens in a new tab) says up to 10 images per TikTok post, and Publer's help article (opens in a new tab) says up to 35. The scheduler comparison lists others and what is not stated.

Whichever you pick, check the slide count against the cap while you plan, not after you export.

How do you learn from a batch afterwards?

A batch is also a small experiment, because the posts share a topic and differ in format or hook. Keep one row per post and fill it in a few days later.

Automatic analytics in Fyslide are Coming soon. Today you link a post and type its numbers in by hand, or you keep this sheet. Seven posts are too few to prove anything, so treat patterns as leads for the next batch, not as rules. For what the evidence does and does not support, read what makes slideshows perform.

Can an agent do part of the batch?

Yes, for the repetitive parts. Fyslide's local MCP server lets Claude Code, Codex or Cursor list designs, create slideshows, edit texts, replace images and export while the app runs. Agents suit "rewrite slide 3 in each of these five" better than they suit judging a hook. Claude Code for TikTok slideshows explains the setup and gives prompts. Read the results either way.

Where do batches go wrong?

In our view these are the usual failures. None of them is a measured result.

• Everything looks the same. Seven posts in one format, one tone, one opening.
• Posting the first draft. Generation is fast enough that there is no reason to.
• Skipping the phone check. Text that fits the editor can crowd a small screen.
• A stale queue. Date-bound topics need a date check before they go out.
• Expecting reach from volume. A batch saves your time. It does not promise views, and no tool controls how TikTok shows a post.