How to Repurpose a Video into 9 Posts with Blotato
Blotato is most useful when it is the last step of a pipeline rather than the whole thing. Repurposing one long video into nine posts is the case that pays for it: the same source, cut differently, scheduled across networks from one queue.
That is a production process, not a button. Below is one that runs in about two hours per video.
What does nine posts from one video look like?
A 20-minute video yields roughly:
| Output | Count | Source |
|---|---|---|
| Vertical clips (9:16, 30–60s) | 4 | Best four moments |
| Carousel (4:5, 6–8 slides) | 1 | Key points as text slides |
| Short text post with one image | 2 | Best quotes |
| Thread or long caption | 1 | Structured outline of the video |
| Quote graphic | 1 | Single strongest line |
Four clips do the volume work on TikTok, Reels and Shorts. The carousel is the highest-effort item and the one most often skipped — it also tends to get saved and shared most.
How do you pick which moments to cut?
Do not pick by memory. Pull the transcript, mark every place where a number, a contrast or a mistake is mentioned, then choose four.
Selection rules that consistently work:
- A clip must be understandable with no prior context.
- The first two seconds must contain the claim, not the setup.
- One idea per clip — two ideas in 45 seconds means both get cut.
- Prefer clips where you say something slightly against the consensus.
If you have captions burned in, check them on a phone at arm’s length before scheduling. Auto-captions drift on technical words.
How do you schedule without posting three clips in a day?
Spread them across ten days: clips every other day, carousel on a weekday morning, text posts in between. Same account, same network, never two posts within four hours.
Set the queue once, per platform, with the per-network overrides on length and hashtags. Then leave it. Editing the queue daily defeats the point of the pipeline.
If you post across four networks, that is 36 items from one video. Build it once with the API and templates and the tenth video takes thirty minutes instead of two hours.
What does the API actually save you?
The repetition. Whatever creates your clips — a clip tool, an editor, a script — the upload-and-schedule step is what the API replaces. You generate a JSON payload per item, post it, and check the returned status.
Two practical notes from people running this: handle rate limits by queuing rather than retrying instantly, and store the returned post ID per item so you can pull metrics later without guessing which scheduled item became which link.
Where the pipeline breaks
Verticals cropped from widescreen. Cropping a 16:9 frame to 9:16 loses whatever was at the edges, and talking-head framing usually survives while on-screen text does not. Re-render verticals from the source, not from the export.
Networks with different caption rules. Instagram allows more hashtags than perform well; X punishes more than two.
Scheduling too far ahead. A news-sensitive quote scheduled three weeks out can land badly. Keep a 10-day horizon and drop items if something changes.
Who should build this
Creators with an existing long-form library, agencies repurposing client webinars, and B2B teams turning one customer call into a month of posts.
It does not suit anyone producing fewer than two long videos a month — the setup cost never amortises — and it does not replace a human deciding whether a clip is worth posting.
Quick Summary
- A 20-minute video yields about nine outputs: four vertical clips, one carousel, two text posts, a thread and a quote graphic.
- Select clips from the transcript by numbers, contrasts and mistakes; the claim belongs in the first two seconds.
- Spread 36 items across four networks over ten days, never two posts within four hours on one account.
- Use the API for the upload-and-schedule step, queue on rate limits, and store returned post IDs.
- Re-render verticals from the source rather than cropping a 16:9 export.
