Blog
How to Transcribe a Podcast to Text (Free Preview)
Author: Hushscript Published: Last reviewed:
To transcribe a podcast, upload the episode’s audio file, check the free 5-minute preview, then sign in and run the full transcription. Hushscript labels every host and guest, you rename the labels once, and you export the text as TXT, DOCX, or SRT. A full episode needs an account and enough available minutes; a card is not required to create one.
A podcast transcript earns its keep twice. It makes the episode searchable and accessible to listeners who read rather than listen, and it gives you raw material for quotes, chapters, and captions without replaying the recording. Platform support is concrete: Apple Podcasts documents transcripts and chapter navigation for creators. This guide covers how to transcribe a podcast, label the voices, fix common problems, and use the result. For the product page, see podcast transcription.
The step that saves the most time is speaker separation. A transcript that reads as one block of text is nearly as much work as the audio. Hushscript labels each voice automatically, free on every transcript, so the conversation comes back as a conversation.
What you need before you start
A recording of the episode, in any common audio or video format, or a direct link to the audio file. If you exported a plain audio file from your editor (MP3, WAV, M4A), that works directly. If your only copy is the video recording from Zoom, Riverside, or Ecamm, that works too, and the audio is pulled from it in your browser so the video never uploads.
Clean source audio helps more than anything else. Speaker labels work best when each voice is distinct and people are not constantly talking over each other. If you recorded each participant on a separate track, you already have the cleanest possible input. A single mixed track still works; it just leans harder on the diarization to tell voices apart. If you can, record voices dry and add the music bed afterward in your editor, since a jingle running under continuous speech is the one thing that reliably nudges accuracy down.
You will need an account to transcribe a full episode. The 5-minute preview is the no-account step, so you can check the speaker labels and the text quality on your actual file before signing up for anything.
How to transcribe a podcast to text, step by step
The flow is preview first, then sign up, then transcribe the rest. This is how to transcribe podcast audio to text.
- Drop the file at the podcast transcription page. Hushscript clips the first 5 minutes in your browser and returns a speaker-labeled preview. No account is needed for this step. You see exactly how the host and guest get split and how clean the text reads on your own audio.
- Sign up to transcribe the rest. Once you enter your email and sign in, you upload the full episode. Eligible personal accounts can receive 30 free minutes to try, granted once, after card verification or with their first purchase; pricing has the terms. Full transcription needs an account and enough available minutes.
- Let the transcription run, then export. The transcript comes back with a label and a timestamp on every utterance. Export DOCX for a document you will edit into show notes, TXT for a clean block to paste into your CMS, SRT for captions on a video version, or JSON if your podcast host accepts utterance-level transcript uploads.
The 30 free minutes can cover a short episode or a representative section of a longer one. A 60-minute episode uses 60 minutes from your balance, so it needs a top-up after the trial allowance.
Past the trial allowance, pay-as-you-go transcription means prepaid minute packs with no subscription, so a quiet month between episodes costs nothing.
Label every host and guest
Speaker diarization runs automatically, so you do not turn anything on. For a two-person episode (one host, one guest), the transcript comes back cleanly split, with every line attributed to one of two labels. For a panel, Hushscript separates as many distinct voices as it hears, with no speaker cap.
To replace the generic labels with real names:
- Click any instance of
Speaker Ain the editor. - Type the name, such as “Alex” or “Host”.
- Every instance of that label updates throughout the transcript at once.
You relabel each voice once, not line by line. A two-person episode takes about a minute; a four-person panel takes a few. After relabeling, a stretch of the transcript reads like this:
Alex [00:03:12]: So you were running the company at that point. What were the first signs?
Jamie [00:03:19]: Honestly, it was the numbers. We had a 40% drop in one quarter.
Alex [00:03:27]: And you couldn't explain it at the time?
Jamie [00:03:35]: Not for weeks. That was the part that kept me up.
That is the structure you need for pulling quotes and writing timestamped chapters. Because the labels carry through the whole file, a long episode is labeled exactly once. For the mechanics behind voice separation, see how speaker diarization works.
When the labels need a fix
Diarization is accurate on clean recordings but not infallible, and a couple of patterns are worth knowing so you can correct them quickly.
If two guests have very similar voices, an occasional line can land on the wrong speaker. Scan the transcript with the audio open and reassign the few misattributed lines by hand. This is far faster than typing speaker names from scratch, because you are only fixing exceptions.
If a quiet co-host who barely speaks gets merged into another label, give the main speakers their real names first, then sweep for the handful of lines that should belong to the quiet voice. On a well-separated recording you rarely hit either case, which is why a separate track per person is worth the small extra setup at record time.
Common issues, and what actually causes them
Most transcription problems trace back to the recording, not the tool. A few are worth planning around before you publish a show.
Crosstalk and people talking over each other. This is the hardest thing for any speaker-separation system, because two voices in the same instant cannot be cleanly split. The text usually stays readable, but a moment of heavy overlap may land on one speaker or blur at the seam. Good podcast hygiene already helps here: a host who lets guests finish produces a cleaner transcript as a side effect. Where it does happen, fix those few lines by hand against the audio.
Remote guests recorded on one track. A call recorded as a single mixed file is harder to separate than the same call captured as a track per participant. If your tool supports local per-participant recording, use it; if you only have the mixed file, the transcript still comes through, it just relies more on the diarization. Either way the audio is the same upload, so there is nothing different to do at transcription time. If you did record separate per-guest tracks and need them merged into one file before uploading, the free audio-joiner tool handles that in your browser, nothing uploaded. A guest who joins through a Chrome tab can be recorded with the free Hushscript Chrome extension, which mixes the tab and your microphone into one recording. Tell your guest before you start.
Strong accents and code-switching. Hushscript detects the language automatically and transcribes around 99 languages, with top-tier accuracy in eighteen of them, so a guest with a pronounced accent in a supported language is handled well. A guest who switches between two languages mid-sentence is the genuinely hard case; expect to clean up the switched phrases by hand. For the full list of supported languages, see the languages page.
Intro music and stingers. A music bed between segments is generally skipped rather than transcribed as nonsense. Trouble starts only when music runs under continuous speech for a long stretch. The clean fix is editorial: record voices dry and lay the music in afterward, so the transcription only ever sees speech.
Names, jargon, and brand spellings. A specialist guest will use terms and product names the model may render phonetically. These are quick to fix because they repeat, and a search-and-replace on the exported document handles a recurring misspelling in one pass.
A few accuracy tips
The single biggest lever is recording quality, so the effort spent on microphones and a quiet room pays back at transcription time. Beyond that, a track per speaker gives both the cleanest text and the cleanest speaker labels, since the system never has to untangle two voices from one waveform. Keep a guest’s mic close and consistent rather than drifting, and you will spend your editing time on substance instead of repairs.
When you do proofread, read with the audio open and fix in passes: speaker labels first, then misheard names and jargon, then the occasional overlap. Working by category is faster than reading top to bottom, and it leaves you with a document clean enough to publish.
Use the transcript
Once the text is clean, it works as a base for quotes, chapters and captions. Timestamps come with every utterance, so you can find a topic shift without replaying the episode. To search the text for spoken URLs, look for fragments like “dot com” or “slash”. For a pull quote, decide on purpose whether to keep the filler words; clean verbatim vs verbatim covers both.
Show notes, chapters and the rest of the publishing routine are in the podcast transcription workflow.
Spotify podcast transcripts
Spotify can show a transcript next to an episode. Its creator help says some shows get auto-generated transcripts, and listeners see them in the Now Playing view and on episode pages in the Spotify mobile app. To post your own reviewed text instead, you upload a VTT or SRT file of up to 5 MB. Include timestamps, or the text will not sync during playback.
To make that file, transcribe your original episode audio, not a copy pulled from Spotify. Hushscript does not import episodes from Spotify pages, and your editor’s export is the cleanest source anyway. Fix names and speaker labels in the editor, then export SRT or VTT. Both formats carry the timestamps Spotify asks for.
Two things to check first. Spotify says an uploaded transcript is replaced if you enable auto-generated ones, so decide which you want. And you cannot edit a transcript inside Spotify for Creators: you change the file offline and upload it again. Keep your corrected SRT as the master and re-export after any fix. Spotify also says that, depending on your podcast host, you may not be able to sync your transcripts, and that transcripts are not available to every creator or in the Spotify for Creators mobile app. Its help puts the controls in Spotify for Creators on the web: Settings, then Transcripts for the whole show, or an episode’s Details for one episode.
Add captions or subtitles
If you publish a video version of the episode to a platform such as a video host, Spotify video, or LinkedIn, the SRT export is a timed subtitle file ready to upload. There is no extra step, because the transcript you already generated carries the timing data. If you only have the audio and the platform wants a video file, the free MP3 to MP4 tool turns the episode into an MP4 with a still image or a solid color, in your browser with nothing uploaded. It takes files up to 200 MB and about 3 hours. For the broader workflow of getting captions onto a clip, including burned-in versus sidecar files, see how to add subtitles to a video.
If your starting point is a video recording rather than an audio export, the process is identical; the audio is extracted in your browser first. The video to text page covers that path in full.
Long and multi-part episodes
For a feature-length episode or a live recording, Hushscript takes uploads up to 10 hours long, with no file-size limit. A four-hour panel or a documentary-format episode goes through as one file rather than being split into chunks, which matters for two reasons. The speaker labels stay consistent across the whole file, so you relabel once. And the timestamps are continuous, so a chapter at the three-hour mark reads [03:12:40] rather than restarting from zero in part two.
If you record a multi-part series in one session, transcribe the whole session as a single file and split the show notes by part afterward. Cutting the audio first only multiplies the relabeling work.
Independent sources and standards
Hushscript consulted these independent, non-competing references. They explain research, standards, or platform behavior and do not endorse Hushscript.
Sources reviewed: