Free · 30 minutes a day · no signup

Drop one recording ship a week of content.

Blog post, show notes, 3-5 vertical clips, a LinkedIn post, and a tweet thread — generated from the same transcript and matched to your voice. One drop, every derivative.

30 min / day free · no signup · $1/hr PAYG after · Never used to train AI · Or upload a file →

✓Blog + show notes + clips + posts · ✓All from one transcript · ✓Voice and tone matching · ✓Never used to train AI

What you get

What one recording should produce.

1500-2000 word blog post

A long-form post that follows the structure of your recording — intro, three to five sections with subheads, conclusion. Every claim links back to a timestamp in the transcript so you can verify before publishing.

250-400 word show notes

Tight episode notes for the podcast feed, newsletter, or YouTube description. Hook line, 3-5 bullet takeaways, key quote, links mentioned in the recording. Drops straight into Apple Podcasts Connect or a Substack draft.

3-5 story-arc clips

Clips with setup, turn, and payoff — picked by the same engine as our standalone clipping tool. Each clip ships in 9:16, 1:1, and 4:5 with burned-in word-level captions and AI-suggested per-platform titles.

LinkedIn post + tweet thread

One LinkedIn post (200-300 words, hook + insight + question) and one X tweet thread (5-7 tweets) — both written from the actual content, not generic templates. Edit and post directly; no separate copywriting pass.

Why one transcript should drive every derivative

Manual repurposing vs one-drop pipeline.

✗ Manual repurposing workflow

Transcribe in tool A, summarize in tool B, clip in tool C, write the LinkedIn post yourself in tool D. Three to five hours per recording, three to five subscriptions, voice drifts across tools.

3-5 separate tools, separate subscriptions
3-5 hours of context-switching
Voice drifts between tools
Re-uploads of the same audio
Manual SRT-to-burned-in render

✓ Whipscribe one-drop pipeline

One file, one engine. Blog, show notes, clips, LinkedIn post, tweet thread — all generated from the same transcript with the same voice profile. Render time: 5-10 minutes for a one-hour recording.

One drop, every derivative
Same voice across blog and posts
5-10 min render for an hour of audio
Story-arc clips, not random hot moments
All exports ready, no re-runs

Sample output

Speaker-labelled. Source for everything.

All seven derivatives — blog, show notes, three clips, LinkedIn post, tweet thread — are generated from this one transcript.

transcript · whipscribe.com/view/repurpose-video

HOST 00:08:21 Let's go to the part of your operating system that I think is the most counterintuitive — the weekly review.

GUEST 00:08:28 Right. So most people who try a weekly review do it on Sunday evening, it lasts forty-five minutes, and they quit after three weeks. I do mine in twelve minutes on Friday afternoon.

HOST 00:08:39 Twelve minutes. What did you cut?

GUEST 00:08:41 Everything that wasn't 'what's blocking next week.' I stopped journaling the past, stopped scoring myself on goals, stopped reviewing the calendar in detail. The whole point became: what one thing, if I unblock it tonight, makes Monday better?

Export

One transcript. Five clean formats.

Every paid tier exports all five. The free tier exports TXT and SRT.

.txt

Plain text

De-ummed paragraphs. Ready to paste.

.srt

SRT captions

Word-level. Every video editor reads this.

.vtt

WebVTT

HTML5 player + YouTube uploads.

.docx

Show notes

Formatted with chapters and pull-quotes.

.json

Machine-readable

Per-word timing + speaker IDs.

Pricing

Honest pricing, no surprises.

Credits never expire. Upgrade or downgrade any month. Free tier resets daily — no signup, no card.

Free

$0/forever

Try every feature for 30 minutes a day. No card.

30 min / day
Speaker labels included
TXT + SRT export
No history retention

Try free

Pay-as-you-go

$1/hour

Best for one-off projects. Credits never expire.

$10 minimum top-up
Every export format
365-day history
API access

Top up

Pro

$8/month

Indie creators. 100 hours / month, all features.

100 hours / month
Clips + every aspect ratio
Branded captions
Priority queue

See Pro

Team

$29/month

Teams. 500 hours / month, shared workspace.

500 hours / month
Shared library
API + MCP for Claude
Workspace billing

See Team

FAQ

Repurposing questions, answered.

How many derivatives do I get from one hour of audio?

Realistic output per hour of recording: 1 long-form blog post (1500-2000 words), 1 show notes block (250-400 words), 3-5 story-arc clips in 3 aspect ratios each, 1 LinkedIn post, 1 X tweet thread (5-7 tweets). Roughly 7 ready-to-publish artifacts from one drop.

Can I customize the blog or post style?

Yes on Pro and Team. Set a voice profile — formal vs casual, short-sentence vs long-paragraph, heavy-hyphen vs sparse-punctuation, jargon-friendly vs explanatory. Future runs match the profile. Free tier uses a sensible default — clear, neutral, business-casual.

Will it match my voice?

On Pro and Team — yes. Drop in 5-10 of your previous blog posts or LinkedIn posts and we extract a style profile (cadence, sentence length, vocabulary preferences). New derivatives match the profile. Free tier produces a clean default voice; you'd edit before publishing.

Do the clips include burned-in captions?

Yes. Every clip renders with word-level burned-in captions in your brand colors (Pro/Team) or the default Whipscribe style (free). Captions are styled to read at a glance on a muted phone — that's the bar for short-form video.

Can I re-run with different settings?

Yes. Once a recording is transcribed, you can re-render any derivative — different blog length, different LinkedIn tone, different clip count — without re-uploading. Free tier counts each re-render against your daily quota; paid tiers have higher limits.

What about scheduling posts to platforms?

Honest answer: not yet. We generate the artifacts (blog, posts, clips); you publish them through your existing scheduler (Buffer, Hypefury, Later, native platform). Scheduled-publish-to-platform is a deliberate feature we haven't built — too many platforms with unstable APIs to support reliably right now.