Clyp
A long video goes in. Short, captioned, correctly-shaped clips come out — already sized for wherever you are about to post them.
Use itUploading from a phone on real mobile data now survives a dropped connection — it picks up where it left off rather than starting the whole file again. That was the last thing standing between this and being genuinely usable away from a desk.
Next on the bench: the preview pager, so you can see a clip laid out exactly as each platform will crop it before you commit.
Clipping is ten minutes of judgement and two hours of admin.
Finding the good forty seconds in a ninety-minute recording is the part a human is actually good at. Everything after it — trimming to the frame, burning in captions, re-cropping for a square, a vertical and a wide, exporting three times, checking nothing got cut off at the edges — is clerical work, and it is where the habit dies. Most people stop clipping not because they run out of good moments but because they run out of patience for the export dance.
Five stages, and you only supervise two of them.
Take it in
Large files upload in pieces, so a lost signal costs you the piece and not the file. A two-hour recording from a phone is an ordinary case, not an edge case.
Understand it
The whole recording is transcribed and time-aligned, so the system knows what was said and precisely when. Every later decision hangs off this.
Find the moments
Candidate clips are proposed and ranked, then cut on sentence boundaries rather than arbitrary timestamps — so a clip opens and closes on a complete thought.
Dress it
Captions, framing and safe margins applied per destination. Seven platform layouts with their real geometry, so nothing important sits under a UI overlay.
Hand it over
You review a page of finished clips shown as each platform will actually crop them, and take the ones you want.
It also runs without a screen.
The whole pipeline is exposed as a set of tools an AI assistant can drive directly, published as an installable package. You can say “pull three clips out of yesterday's recording and shape them for vertical” in a chat window and the work happens — no interface, no clicking. The web app and the assistant are the same engine wearing different faces, which is why a feature never exists in one and not the other.
The problems that took the longest.
- Uploads that survive real life A phone on patchy data drops mid-transfer constantly. Making a failed chunk cost seconds instead of the whole upload took several rewrites and a lot of unglamorous testing on actual hardware, outdoors.
- Cutting on meaning, not on time A clip that starts half a word in reads as broken no matter how good the moment was. Aligning cuts to speech required the transcript to be trustworthy to the fraction of a second.
- Honest previews Every platform crops differently and hides parts of the frame behind its own controls. Reproducing that geometry faithfully — without lifting anyone's branding — is fiddly, and it is the difference between a preview you trust and one you ignore.
The last few weeks.
Mobile uploads verified on real hardware over cellular. Assistant package published and confirmed installable from a clean machine.
Error reporting fixed — a server fault no longer reaches the browser disguised as a network problem, which had been sending people to check their wifi for the wrong reason.
Preview layouts settled: seven destinations, faithful geometry, decoupled from whether you have connected that account yet.
Clip ranking reworked so long recordings surface as many candidates as short ones.