Not by collecting the episodes. Sixty hours of podcast is 550,000 to 900,000 words with no argument running through it, and a book is 70,000 to 90,000 with one. The work is finding the through-line and rebuilding around it — the transcription is the easy part, and doing it first is why most podcast books stall.

Turn your podcast into a book

Four routes, and which one works

The first row is what almost every podcaster tries and it is the only one that reliably fails.

ApproachWhat it isVerdict
Episode collectionTranscripts in broadcast order, tidiedFails. No argument, heavy repetition, and the listener's context is missing.
Thematic rebuildMaterial regrouped around 5–8 themes and rewrittenThe standard answer for most shows. Requires cutting 85% of your archive.
The argument bookOne claim the archive supports, best material as evidenceStrongest result, for expertise-led shows with a consistent position.
Curated best-ofThe strongest 15 conversations, framed and introducedWorks for guest-interview shows with recognisable names. Reads as a companion product.
Free. No card. Private.

A themes report on your archive

Send a handful of episodes or transcripts and we'll email back what the material is actually about — themes, best statements, and where you're repeating yourself. Free.

By signing up, you agree to receive useful writing tips and occasional Your Book Pro offers by email. You can unsubscribe at any time. We will never sell your details or share them with third parties for their own marketing.

We'll email it, then a short series on finishing and publishing a book. Unsubscribe in one click, any time.

Or see how it works first

The arithmetic first

Ninety episodes at forty minutes is sixty hours — roughly 550,000 to 900,000 words. A book is 70,000 to 90,000.

So the job is selection at about one word in ten, then rewriting. That ratio is the thing podcasters find hardest to accept about their own archive, and it is not a judgement on the material. The 90% that goes is not the weak 90% — much of it is good and belongs to a different book.

Why the spine has to come first

A podcast is held together by a release schedule. That works, because the listener arrives weekly carrying their own continuity.

A reader arrives at page one with nothing. If chapter three does not follow from chapter two they notice immediately, and by chapter five they have stopped.

Most podcasters cannot see the through-line in their own archive — you remember the episodes rather than the material, and you overvalue the ones you enjoyed recording. That is not a failing; it is what being inside something does.

The repetition problem

Across ninety episodes you have said your central ideas dozens of times, slightly differently each time. On a weekly show that is correct — new listeners arrive constantly and repetition is how a podcast teaches.

In a book it is fatal. The reader gets your framework in chapter two and meets it again in five, nine and fourteen.

You cannot find these clusters by listening back. Seeing them laid out — this idea appears in these nineteen episodes, here is the clearest statement of it — is what turns the archive from an obstacle into a resource.

Guests, permissions and rights

If a guest's words appear substantially in the book, get permission in writing. Check your original release form if you have one — many cover broadcast and nothing else — and ask again for book use.

Most guests are pleased to be asked. A few will want to review their sections, which is reasonable and worth agreeing in advance rather than discovering late.

If your show is co-hosted, settle authorship, credit and money before you start writing. This is where podcast books most often turn into arguments.

What it costs, and what it earns

With freelancers: £1,500–£4,800 for a developmental edit, £800–£1,600 copy-edit, £400–£800 proofread, £250–£800 cover. Transcription on top, at £60–£120 an audio hour for human work.

As a direct revenue line, a podcast book rarely repays that. As a credential, a speaking asset, a thing that reaches people who do not listen to podcasts and outlives the feed — frequently yes, and that is usually the real reason.

Worth being honest with yourself about which one you are doing before you start.

What Your Book Pro does here

Your Book Pro is a British book-writing platform. You bring a book — an idea, a folder of notes, half a draft, or a finished manuscript written somewhere else — and it gives you the editorial process a publisher would run: a plan, structured feedback, a simulated beta read, a line edit, a proofread, a cover, a blurb and a print-ready file. You can type it, upload it or speak it. The tools sit in one place and work on the same manuscript, so the feedback compounds instead of arriving as twelve disconnected opinions.

Themes from Bulk Audio is the tool built for this. It reads across your entire archive at once and reports what the material is actually about: the recurring themes, where each is stated best, which ideas cluster, and which apparent themes are one guest's hobby-horse rather than yours. That report is the thing you cannot produce by listening back, and it is where the project either starts or stalls.

Then Plan Feedback tests the structure you build from it, Transcription handles the episodes you actually use, and Light Edit turns spoken material into prose without erasing how you talk.

Plus lets you upload material you made anywhere, run whichever tool you actually need, and export it again. No subscription to start, 1,000 welcome credits that never expire, and a plain export of your own words is free forever.

What we do not do is decide what your book is about. The report shows you what is there; the claim is yours.

Upload your archive

See what's in it first

Email me the report

Questions people ask

How many episodes do I need?
Thirty good ones is plenty of raw material — you will use a fraction of any archive. More episodes means better selection, not a longer book.
Should I transcribe everything first?
No. Work out the through-line first, then transcribe what serves it. Transcribing sixty hours before you know what the book is produces an unusable document and a large bill.
Do I need permission from guests?
For substantial use of what they said, yes. Check your original release and ask again for book use — most guests are pleased, and it is far better asked than assumed.
Will it read like a podcast?
Only if you let it. Spoken material edits into strong prose, but the passes have to be done deliberately: filler, paragraphs, repetition, then structure.
Is a book worth it for a podcast?
Rarely as direct revenue. Frequently as a credential and as something that reaches non-listeners — and that is usually the honest reason.