How to Turn One Facebook Live Into 12 Pieces of Content

A ninety-minute workflow for mining a Facebook Live replay: transcribe it, sort what you said into four categories, and build clips, posts, and email from the result.

A Facebook Live that ran for an hour is the most under-used asset most Pages own. It got its audience once, on the day, and then it sat in the video tab. Nobody goes back and watches it. Including you.

The problem is not that the content was weak. It is that an hour of video is unsearchable. You cannot skim it, you cannot quote it, and you cannot find the good bit without scrubbing through a timeline. So it stays where it is.

This is a workflow for turning one Live replay into somewhere between eight and twelve publishable assets, in about ninety minutes.

Why Lives are worth mining

Live video is unusually rich material for repurposing, for three reasons.

You were unscripted. The phrasing is natural, which is exactly what short-form video wants. Scripted content read off a page sounds scripted. A sentence you said unprompted in minute 34 usually needs no rewriting at all.

You answered real questions. If people asked questions in the comments and you responded, you have a list of your audience's actual objections in their own words. That is expensive to obtain any other way.

You went long. An hour of talking contains ideas you would never have sat down to write. Most people find at least two things in a transcript that surprise them.

Step one: get the transcript

Everything downstream depends on having the text. Copy the URL of the finished replay and paste it into the Facebook transcript generator.

Two practical notes. The broadcast has to have ended: a stream still in progress has no final audio track to work from. And use the full facebook.com URL rather than an fb.watch short link, which cannot be resolved from outside a browser session.

Keep the timestamps switched on. You are going to need them to find the moments in the video later.

Step two: read it once, marking only

Read the transcript start to finish without editing anything. Mark passages in one of four categories:

• A claim. Something you asserted that would stand alone as a statement.
• A story. A specific anecdote with a beginning and an end.
• An answer. A response to a question somebody asked.
• A phrase. A sentence that is well put, regardless of what it is about.

Do not judge quality yet. An hour of talk typically yields fifteen to twenty five marks. You will cut that down later.

Resist the urge to start writing during this pass. The value of reading the whole thing first is that you see which themes recur, and recurring themes are the ones worth building around.

Step three: sort marks into assets

Now assign. Different marks suit different formats.

Claims become short-form video. A claim is a hook. Take the sentence, tighten it, and it becomes the first three seconds of a Reel or a TikTok. The rest of the clip is you justifying it, which you already did in the Live, so the body is written too.

Stories become the emotional posts. A specific anecdote with a real outcome is the hardest content to fake and the easiest to engage with. One story is one post, on whichever platform your audience reads.

Answers become FAQ and email. A question someone actually asked, with your actual answer, is customer support content, sales enablement, and email newsletter material simultaneously. If one person asked it live, a hundred people wondered it silently.

Phrases become the connective tissue. Well-put sentences are captions, subject lines, and pull quotes. Keep a running list.

Step four: build the clips

For each claim you kept, use the timestamp from the transcript to find the moment in the replay. Cut from a few seconds before you started the sentence to wherever the thought lands.

The rewriting question is whether the spoken version works as-is. Often it does. Where it does not, the usual problem is that you buried the point: you spent fifteen seconds getting to the thing that should have opened the clip. Move it to the front.

If you would rather not do that by hand, paste the passage into the Script Rewriter and ask for a HOOK / BODY / CTA structure. It will front-load the claim, which is nearly always the correct edit.

Step five: adapt per platform

The same clip does not land identically everywhere.

TikTok wants the rough version. Jump cuts, no polish, the claim stated flatly. Over-editing hurts you here.

Instagram Reels wants slightly more finish and a text overlay, because a large share of Reels are watched with the sound off. Your transcript is the source for that overlay: use the key phrase, not the full sentence.

LinkedIn wants the claim written out as a post with the video attached, and it wants credibility rather than energy. The story marks work better here than the claim marks.

YouTube Shorts wants a slightly longer runway. You can spend five seconds setting up where a TikTok gets three.

A single Live usually produces four to six clips that are worth cutting, plus two or three written posts, plus a newsletter section. Twelve assets from ninety minutes of work is a reasonable expectation.

Doing this across a back catalogue

If you have a year of Lives sitting unused, one at a time is the wrong approach. Bulk processing takes up to 100 URLs in a single job and returns every transcript in one CSV.

The reason to do it in bulk is not speed. It is that having every transcript in one file lets you search across all of them at once. Searching your own back catalogue for a phrase like "the mistake people make" surfaces every time you have made that point across a year, which tells you what your actual recurring message is. Most people are surprised by the answer.

Where else this applies

The same workflow works on any long video. YouTube uploads, webinar recordings, and LinkedIn video posts all respond to it. Facebook Lives are simply the format most likely to be sitting unused, because they were never treated as content in the first place. They were treated as an event.

They are content. The transcript is what makes that obvious.