Loading the profile
Loading the profile
We use cookies you can say no to for analytics, ad measurement, and embedded videos. Signing in works either way. You can change this any time from Cookie settings at the bottom of every page. What we use
For podcasters and interview hosts: turn an episode transcript into show notes ready to paste. You get a summary, topic bullets, chapter timestamps, word-for-word pull quotes, and links mentioned, from a local script that reads SRT, VTT, or timestamped lines so every time and quote is exact.
For video makers with an SRT or VTT caption file: fix overlapping cues, lines too long for the screen, and captions too fast to read. A local script repairs timing and line breaks and counts each fix, then lists the cues that need words cut or a split, and Claude helps edit them.
For anyone with an auto transcript from Zoom, Otter, or YouTube: remove the ums and stutters, fix speaker names, and join broken lines. A local script makes each fix and counts it, then flags inaudible spots for you to check. It never rewrites what anyone said.
For creators with a tutorial, talk, or YouTube video: turn its transcript into a blog post that reads on its own. A local script strips timestamps and filler, groups the text into sections, and flags every "as you can see" to rewrite, then Claude writes the post with steps, a headline, and every number kept exact.
For YouTubers with a finished video: turn its transcript into title options, a description that works in search, chapter timestamps, and tags. A local script checks every YouTube limit (title length, chapters from 0:00, 10 second minimum) and builds the description ready to paste.
