Everyone tells you to repurpose. "You already made the video — just turn it into a Short, a Reel, a TikTok, a blog post, a Facebook post!" What they don't mention is that "just" is doing a lot of work in that sentence. Done naively, repurposing one video is an afternoon: re-exporting, re-cropping, re-writing, re-uploading, five times over, each platform with its own rules and its own login screen.
If you're publishing weekly and doing everything yourself, an afternoon per video isn't repurposing — it's a second job. So here's a workflow with a hard constraint baked in: one hour, timer running, everything downstream of the main video. If a step doesn't fit, the step gets simpler, not the hour longer.
The hour, in one line: ten minutes cutting the vertical, fifteen writing one source document, ten on YouTube, fifteen posting that one vertical to Shorts, TikTok and Reels, ten on Facebook and a blog seed. It only fits because two decisions are made before the timer starts — you flag your clips during the edit, and each platform has a default treatment you don't re-litigate every week.
The one rule that makes the hour possible
Repurposing decisions happen during the edit, not after it. The expensive version of repurposing is finishing your video, exporting, and then asking "okay, what can I cut out of this?" — which means re-watching your own video like a stranger. The cheap version is flagging moments while you're already in the timeline: you know exactly where the best 45 seconds is, because you just spent hours with it. Two markers in your editing software while you work cost you nothing and save you the entire "hunting" phase later.
Second rule, nearly as important: each platform gets a default treatment, decided once. Not "what should Instagram get this week?" but "Instagram gets a Reel and one feed post, always, unless the video is unusual." Deliberation is the silent time sink.
The hour, minute by minute
This assumes your main YouTube video is edited and its 16:9 master is exported. The hour covers everything downstream.
:00–:10 — Cut the vertical. Go to the moment you flagged during the edit. Punch in to 9:16, reframe so nothing important lives at the edges (every short-form platform stacks UI over the bottom and right of the frame), and add burned-in captions — most short-form viewing happens with sound off. Export one clean master, no watermarks. This single file serves Shorts, TikTok, and Reels; the differences between those platforms are captions and timing, not the video file (the details are in Cross-Posting Shorts to TikTok and Reels: What Changes, What Doesn't).
:10–:25 — Write the source document. One note, five ingredients: the YouTube title, the description, a one-line hook rewritten for short-form captions, three to five topic keywords in plain language, and your call to action. Every platform's text comes from this note by adaptation, never from a blank box. This is the highest-leverage fifteen minutes in the whole hour — writing from scratch per platform is where afternoons go to die.
:25–:35 — YouTube. Upload (or finalize the scheduled upload), paste in title and description from the source doc, set the thumbnail, schedule for your channel's best hour. YouTube gets the most care because it has the longest shelf life — search and recommendations can feed a video for months, so its packaging compounds in a way a feed post's doesn't.
:35–:50 — The vertical, three times. Upload the clean 9:16 master natively to Shorts, TikTok, and Reels. Adapt the hook line per platform from your source doc: searchable title for Shorts, conversational keyword-rich caption for TikTok, hook-first caption for Reels (no links — they're dead text there). Schedule each for that platform's active hours rather than dumping all three at once.
:50–:60 — Facebook + the blog seed. Facebook gets a native video upload with a short caption — native video is widely observed to travel better on Meta platforms than a pasted YouTube link, so don't take the link shortcut. Then spend the last five minutes pasting your source doc into a blog draft with three section headings. Not writing the post — seeding it. A structured draft turns "write a blog post someday" into a 30-minute task on another day, and if the video answers a question people search for, the blog post is the only repurposed asset that can keep earning search traffic for years.
Timer done. Five platforms served.
What deserves more than the default (and what deserves less)
The hour is the default, not a law. A quick decision framework:
- Give a video extra repurposing only if it's evergreen (answers a searchable question), clearly outperforming your baseline in its first days, or central to something you're promoting. Then a second clip or a full blog post writeup is justified.
- Give a video less if it's timely and will be stale in a week (skip the blog seed), or if no moment jumped out during the edit — a video with no obvious clip is telling you something, and forcing a mediocre vertical out of it costs time and does nothing.
- Never let the repurposed assets delay the main video. The video is the product; everything else is distribution. If the hour isn't available this week, YouTube plus one vertical is a perfectly good week.
The hour still has a tab problem
Run this workflow and you'll notice where the remaining friction lives: not in the creative work, but in the five upload screens, the five schedule pickers, and the five guesses about timing. That's the layer ChannelzIQ was built to remove. Alex — Travel and Food Guy on YouTube — ran a version of this exact hour every week and went looking for where it leaked (the method he uses to price it is here).
In ChannelzIQ, minutes :25 through :60 collapse into one composer: attach the 16:9 master and the vertical once, adapt each platform's text in a single view, and schedule every platform for its own best window — suggested from your audience's actual activity per platform, not a generic chart. When posts go live, they appear in your unified dashboard immediately, and comments from all five surfaces flow into one inbox instead of five apps. Cue, the in-product agent, is there when you want a first draft of a caption or title to react to instead of writing cold.
It's pre-launch — there's a waitlist while it's being built.
Stop guessing
One hour per video is achievable by hand today with the workflow above — and the leftover friction is exactly what ChannelzIQ is being built to erase. Join the waitlist, and answer the one question on the form ("what are you trying to improve right now?") — those answers directly shape what gets built first. Join the waitlist →
Frequently asked questions
Can you really repurpose one video across five platforms in an hour?
Yes, but only if the repurposing decisions are already made. The hour covers execution: cut, write once, upload five times. It does not cover hunting through your own video for a clip or deciding weekly what each platform "deserves" — those are the two things that turn the hour into an afternoon.
Which platform should get the most care?
YouTube, if it's your main platform, because it has the longest shelf life — search and recommendations can feed a video for months, so its packaging keeps earning. A feed post's packaging stops mattering in about two days.
Is the blog post worth ten minutes?
The ten minutes buys you a seeded draft, not a finished post — the source document pasted in with three headings. If the video answers a question people search for, the blog post is the only repurposed asset that can still be earning traffic in two years. If the video is timely, skip it.
Do I need a different video file for TikTok, Reels and Shorts?
No. One clean 9:16 master with burned-in captions and no watermark serves all three. What differs is the caption and the timing, not the file — the details are in Cross-Posting Shorts to TikTok and Reels.
What if I can't find the hour this week?
Publish the main video and one vertical, and let the rest go. The video is the product; everything else is distribution. A missed Facebook post costs you far less than a delayed video, and nothing in this workflow is worth pushing the main upload for.