Content Repurposing: Turn a Video or Podcast Into Blog Posts and Newsletters
The single highest-leverage move when you repurpose content is to start from a transcript, not from scratch. Content repurposing means reshaping one thing you already made — a video, a podcast episode — into a blog post, a newsletter, and show notes. If you already recorded the episode, the words are done — you said them. Repurposing is editing, not writing: pull the transcript, find the structure that's already in it, and reshape that into a blog post, a newsletter, and a set of show notes. The reason most "turn one video into ten pieces" advice falls apart is that it skips this step and asks you to re-watch the recording and transcribe by ear, which is slower than just writing something new.
I run Subanana, an AI speech-to-text tool, so I'll be honest about where it fits: it's for the transcript step — turning the recording into accurate, readable, quotable text you can edit down. The repurposing itself (deciding what becomes a newsletter versus a how-to post) is editorial judgement, and no tool does that for you. What a good transcript does is collapse the slowest part of the job so the editorial work is all that's left.
What does "content repurposing" actually mean?
Content repurposing is taking one piece of content you already made and reshaping it for a different format or channel — so a single 40-minute podcast episode becomes a blog post, a newsletter issue, a set of show notes, and a handful of social pull-quotes. The point isn't to copy-paste the same thing everywhere; it's that the ideas and the quotes are already there, and you're changing the packaging for each audience.
The case for doing it is mostly about return on effort:
- The hard part is already done. Recording a podcast or filming a video is the expensive step. Repurposing reuses that investment instead of starting a blank page each time.
- Different people consume differently. Some of your audience will read a blog post who would never finish a 40-minute episode; some live in their inbox. Repurposing meets them where they already are.
- Search engines and AI answer engines read text. A video is hard for a search crawler or an LLM-based answer engine to index well. A blog post built from that video's transcript is text they can read, rank, and quote — so repurposing is also how spoken content earns search traffic.
- It compounds. Show notes link to the blog post, the newsletter links to both, and each format reinforces the others.
Why start from a transcript instead of re-watching?
Because re-watching is the slowest possible way to find the good parts. A transcript lets you read the whole episode in a few minutes, scan for the strongest passages, and copy exact quotes without scrubbing back and forth on a timeline. The structure of a good blog post is almost always already sitting inside the conversation — the transcript just makes it visible.
There's a quality reason too. When you repurpose, you're often quoting yourself or a guest verbatim — in a newsletter, in pull-quotes, in show notes. That means accuracy matters more than it does for rough personal notes: a misheard product name or a wrong number in a published quote is a credibility problem, not a typo. So the transcript you build from should be one you'd be comfortable quoting, which is why this whole workflow lives or dies on getting that first text right.
A few things make a transcript genuinely reusable rather than just "words on a page":
- Punctuation and paragraphs, so it reads like prose instead of a wall of text.
- Speaker labels (diarization) for interviews and multi-host shows, so you know who said which line before you quote it.
- Filler-word cleanup ("um," "you know," false starts), so quotes are clean without you hand-editing every sentence.
- Correct proper nouns — names, brands, and jargon spelled the way you actually spell them.
How do you repurpose a video or podcast, step by step?
Here's the workflow I'd run. The first row is the only one a tool does for you; everything after it is editorial.
| Step | What you do | What you get |
|---|---|---|
| 1. Capture the transcript | Run the recording through transcript mode; turn on punctuation, paragraphs, and speaker labels | A readable, quotable transcript |
| 2. Skim and mark | Read the transcript, highlight the 3-5 strongest passages and any quotable lines | A shortlist of the best material |
| 3. Outline the blog post | Group the marked passages into 3-5 sections with H2 headings — the structure is usually already in the talk | A blog post skeleton |
| 4. Rewrite, don't transcribe | Tighten spoken phrasing into written prose; keep verbatim only the quotes you want to land word-for-word | A publishable blog draft |
| 5. Cut the newsletter | Pull the single sharpest idea + one quote into a short, personal email; link out to the full post | A newsletter issue |
| 6. Assemble show notes | List the key topics with timestamps, the names mentioned, and any links referenced | Show notes for the episode page |
Two notes on the editorial steps. First, rewrite rather than paste: spoken language is loose and repetitive, and a transcript pasted straight into a CMS reads like a transcript. Use it as raw material — the order and the quotes are the gift, not the exact sentences. Second, the newsletter is not a summary of the blog post; it's the one idea you'd tell a friend, written in your own voice, with a link to the full thing. Repurposing works because each format does a different job, not because it's the same text three times.
What's the difference between a transcript, subtitles, and show notes?
People reach for the word "transcript" to mean three different deliverables, and picking the wrong one wastes time. For repurposing into written content you want the first kind:
- A transcript is made to be read — punctuation, paragraphs, speaker labels, the whole thing top to bottom. This is your raw material for a blog post or newsletter.
- Subtitles are made to be watched over a video — short timed lines, conventionally without punctuation, exported as SRT or VTT. Useful for republishing the video itself with captions, not for building a blog post.
- Show notes are a derived summary — topics, timestamps, links, and names — that you write from the transcript; no tool hands them to you finished.
So if you run a podcast through a subtitle workflow expecting reusable prose, you get a stack of short, unpunctuated, timestamped fragments that are harder to repurpose, not easier. Choose transcript mode for repurposing; choose subtitle mode only when you also want to caption the original video for YouTube or social.
How to produce the transcript with Subanana
I run Subanana, so I'll walk through the transcript step with it. Where it earns its place for repurposing is multilingual accuracy, speaker identification, automatic punctuation and paragraphing, and the fact that you can import straight from a public link — so a podcast already on YouTube doesn't need a manual download first.
The critical first choice is the mode. Subanana has a subtitle mode, a transcript mode, and a meeting mode — for repurposing into written content you want transcript mode, because it adds punctuation, breaks the text into paragraphs by meaning, and produces something you can read and quote. The flow is four steps:
- Import the recording. Upload the audio or video file (.mp4 / .mov / .webm / .ogg), or paste a public YouTube, Instagram, or Facebook link to import it directly — handy when the episode is already published as a video. If the source is behind a private or access-restricted link, use file upload instead.
- Choose transcript mode and set the source language. Pick the language of the recording — Subanana covers 80+ languages — set speakers to auto-detect (or type the count), and turn on automatic punctuation and paragraphing. For the names, brands, and jargon you don't want misspelled, set up a Glossary first and the system will prefer your spellings while transcribing.
- Proofread and label speakers. When transcription finishes you land in the editor. It splits voices into Speaker 1, Speaker 2, and so on, strips filler words, and tidies the text. From here you can rename "Speaker 1" to "Host" and "Speaker 2" to "Guest" (the whole transcript updates in sync), click any word to fix it, and chat with the transcript directly — "pull out the three main arguments" or "where does the guest talk about pricing?" — which is the fastest way to find your blog post's structure inside a long episode.
- Export the raw material. Pick the format that fits where you'll edit. For repurposing, DOCX (drop into Word or Google Docs) or TXT (into Obsidian or Notion) are the usual choices; XLSX lays out timecode, speaker, and text as a table, which is convenient for building show-note timestamps. SRT, VTT, and Markdown are available too.
One accuracy point worth being clear about: AI transcription does the overwhelming majority of the work, but it doesn't replace a final proofread on anything you'll publish as a verbatim quote. Check names, proper nouns, and numbers in the passages you're actually going to quote — high accuracy isn't zero errors, and a published quote carries more weight than a private note. Subanana helps here in two ways: it continuously benchmarks the available speech-recognition models and routes each job to the best performer for that source language rather than locking to one vendor, and if a transcription comes out poorly it automatically re-runs the affected segments on a different model — a re-run that doesn't cost you extra minutes.
For the underlying tools, the AI video-to-text and AI audio-to-text pages cover the file-by-file specifics, and AI meeting transcription is the mode you'd use for a recorded interview or panel. If you also want to caption the original video before you republish it, that's the AI subtitling side. And if the workflow you care about is a live event rather than a finished recording — captions and translation shown to an audience in real time — that's a different feature, AI real-time transcription, not transcript mode.
What if the recording is multilingual or accented?
This is exactly where general-purpose speech tools tend to struggle — accented speech and languages outside the usual English-and-a-handful set. Two things are worth checking when you pick a tool for repurposing:
- Accuracy across languages. Subanana benchmarks the available speech-recognition models per language and routes to the best performer, instead of running everything through one model. Combined with the automatic re-run on a weak result, that's what keeps an accented or non-English episode reusable rather than a cleanup chore.
- Translating the transcript. You might record in one language and want to repurpose into another. Transcript mode supports a single translation target, so you can transcribe in the source language and translate into one other language in the same pass — enough to repurpose an episode for a second-language audience.
One boundary to flag: mid-sentence code-switching — a speaker flipping between two languages inside one sentence, detected in real time — is a strength of Subanana's live caption feature, not transcript mode. For repurposing a finished recording you're leaning on multilingual accuracy and speaker labels, not real-time in-sentence switching.
Content repurposing FAQ
How many pieces can I get from one video or podcast? Realistically, one solid blog post, one newsletter issue, and one set of show notes from a single episode — plus a few pull-quotes for social. The "one video, twenty assets" promise usually means twenty thin assets. Start from the transcript, build the blog post properly, and let the newsletter and show notes derive from it.
Should I just publish the transcript as the blog post? No. A raw transcript reads like a transcript — loose, repetitive, full of spoken tics. Use it as the skeleton and the quote source, then rewrite into proper prose. The exception is a lightly-edited "full episode transcript" page you publish alongside the post for search and accessibility, which is fine as a complement, not a replacement.
Can the free tier produce a transcript I can repurpose? You can run a recording and preview the result, but exporting is a paid step. The free tier doesn't support transcript file downloads, and you can't select-and-copy the editor text either — the only output is a watermarked video, first 5 minutes only, at 720p, with a 3 GB per-file limit. To export usable transcript files (DOCX / TXT / XLSX), you need a paid plan, which also raises the limit to 15 GB / 3 hours per file. See pricing for details.
Does a long episode (one or two hours) work? Yes. Paid plans take up to 15 GB / 3 hours per file, which covers most podcast episodes and recorded talks. For a long one, I'd use the editor's AI chat to locate the strongest passages first, then proofread closely only the parts you intend to quote.
Can I quote an AI transcript verbatim? Do one human proofreading pass first on the passages you'll quote. AI transcription handles the bulk of the text and the paragraphing, but names, proper nouns, and key numbers in a published quote are worth checking line by line. The companion guide how to transcribe an interview goes deeper on producing speaker-labelled, quotable transcripts.
Once the transcript is accurate and exported, the repurposing is the easy part — outline, rewrite, and ship the same idea in the formats your audience actually reads. Start a transcript from your latest episode and see how little of the work is left once the words are already on the page.