Existing recordings
Add captions to a video you already recorded.
Import an MKV, MP4, MOV, or M4V from this device. WeaverClip uploads it to private storage, creates one transcript, suggests complete clip-ready moments, and lets you download captioned MP4 clips.
Upload from this device
Choose a video. WeaverClip uploads it here.
Choose a video to begin.
Your original file stays on this device. If the connection drops, choose the same file again to continue the unfinished upload.
How it works
Choose the file. WeaverClip handles the same upload, transcript, and caption workflow used for every recording.
1. Import the file
Choose or drop the video in the uploader above. Your original file stays on your device.
2. Upload and verify
WeaverClip uploads the video in resumable parts and verifies the completed cloud copy.
3. Review and caption
WeaverClip transcribes the video, suggests complete moments, and lets you render vertical, landscape, or square clips.
Prefer the Mac helper?
Run this command when the video is already on the recording Mac.
npm run helper:import -- "/path/to/your-video.mp4" --title "My recording"Import questions
What happens to the original, storage, and transcript time.
- Does WeaverClip change or delete my original video?
- No. The original stays on your device. WeaverClip stores a private cloud copy after the upload passes byte-count verification.
- Which video files can I import?
- You can upload MKV, MP4, MOV, and M4V files in your browser.
- Does an imported video use transcript hours?
- Uploading uses storage only. Each new source minute uses transcript hours once when WeaverClip creates its transcript, captions, and automatic clip suggestions.
Ready to import your first recording?
Free includes 5 GB of storage, 1 transcript hour, and 3 watermarked renders.
The asterisk that keeps us honest — and why biggest streamers notice
Every vault table on this site shows storage in GB (the truth) and hours at 6 Mbps (the intuition). The asterisk is not a footnote to hide behind — it's the promise that we state the vault in bytes and the hour guide at a single, documented bitrate, plus the table to translate your actual OBS settings in seconds. A 2-hour 1080p60 Valorant VOD at 12 Mbps is 10.8 GB, not 5.4 GB. The “Free 10 GB” you bought holds one of those, not two. The same vault at 6 Mbps sermons holds two. If we only said “~3 hours” you'd buy the wrong plan and blame us at 2am when OBS says “upload paused.” So we show both: the vault in GB, the hour guide at 6 Mbps, and the four-row table (5 Mbps ~2.25 GB/h, 6 Mbps ~2.7 GB/h, 12 Mbps ~5.4 GB/h, 25 Mbps ~11.25 GB/h) so you can translate before you record. Hard limit is 2× vault — Creator 75→150 GB, Pro 150→300 GB, Studio 1500→3000 GB — uploads pause there, files stay on your Mac and retry with backoff. Nothing is deleted to make room. Overage is linear $0.04/GB-month, transcript never bills overage. That's the nuance that makes a 24h subathon at 12 Mbps (~129 GB) fit Studio 1.5 TB with headroom, while a 2h sermon at 6 Mbps fits Free 10 GB with 1.9 GB left. We reuse the same lib/product/calc.ts (gbPerHour, planFit, overageCost, clipYield) on every page, so a future $15→$16 change is one JSON edit, not 25 find-replaces. That's top 0.005% system thinking, not just pretty pages.
Upload once, get the vault math right before you hit record
You already have the video — MKV, MP4, MOV, M4V, any size. Drop it on /upload-video, we measure exact bytes, show you at 6 Mbps ~2.7 GB/h, 12 Mbps ~5.4 GB/h, and tell you if it fits Free 10 GB/2h or needs Creator 75 GB/4h before you wait for the upload. The helper's verify-before-delete still applies: byte count + MD5 must match R2 before any local copy is touched. After upload, the same transcript powers FullStreamCaptions (SRT/VTT) and 20/h ranked moments — change from Clean to Space without re-transcribing. The asterisk on every vault table is the promise: *Hours at 6 Mbps ≈2.7 GB/h, actual varies with bitrate. Vault is always bytes; hour label is a guide.
When does your drive fill?
Your 2TB drive, your schedule, your bitrate — one date.
2.70 GB/h · 32.4 GB/week
Two numbers match or you don't touch the file
MCP weaverclip_get_usage — verify before delete.
*Hours are at 6 Mbps (1080p30 webinar, slides, sermons) ≈2.7 GB/hour. Actual hours vary with bitrate — 5 Mbps ~2.25 GB/h, 12 Mbps ~5.4 GB/h, 25 Mbps ~11.25 GB/h. Vault is always bytes; hour label is a guide. Hard limit = 2× vault (e.g., Creator 75→150 GB), overage $0.04/GB-month. Transcript never bills overage.
The upload that doesn't fill your disk — and the transcript that doesn't bill twice
You already have the file — maybe it's a 2-hour 1080p60 Valorant VOD at 12 Mbps (10.8 GB) sitting in ~/Movies, or a 90-minute podcast at 6 Mbps (4 GB) in Downloads. Drop it on this page, we measure exact bytes, show you at 6 Mbps ~2.7 GB/h, 12 Mbps ~5.4 GB/h, and tell you if it fits Free 10 GB/2h or needs Creator 75 GB/4h before you wait. The upload is a signed PUT directly to private R2, not through our app server. The helper's verify-before-delete still applies: byte count + MD5 must match R2 before any local copy is touched. If your startup disk is completely full, even a small write fails, so free a couple of gigabytes before a long session.nd removed the truncated spool file, so the next upload has headroom to roll.
Why bytes beat hours — the 2am test
Every competitor sells hours. Hours lie when your bitrate changes. A 2-hour 1080p60 VOD at 12 Mbps is 10.8 GB. The “Free 10 GB” you bought holds one of those, not two. The same vault at 6 Mbps sermons holds two. If we only said “~3 hours” you'd buy the wrong plan and blame us at 2am when the upload pauses. So we state both: vault in GB (the truth) and hour guide at 6 Mbps (the intuition), plus the table. The asterisk is the promise.
Transcript counts once — the 24h subathon trick
Upload once, transcribe once. A 2-hour sermon at 6 Mbps is 2h of transcript, whether you make 1 clip or 18. Dual 16:9+9:16 at 6 Mbps each is ~10.8 GB for 2h but still 2h of transcript. Captions reuse that transcript, so switching from Clean to Space costs nothing extra. For a 24h stream with 38% dead air, schedule transcribe for the 15h where you actually talked via weaverclip_schedule_transcribe, save 9h every time. The metrics strip shows Storage/Transcript/Renders live so you see “1.2h left” before you pick.
Full-stream captions — upload once, clip later
From any session with transcript, FullStreamCaptions stitches transcript_chunks into SRT: 1\n00:00:01,200 --\u003e 00:00:03,400 and VTT: WEBVTT\n00:00:01.200. Same chunks that power 20/h ranked moments. Download the 12h SRT tonight, import to Descript, come back next week to bulk-create 18 edits without re-transcribing. That's the “plus the clips later” you asked for. Biggest course sellers care because their vault is their LMS source — one transcript, many derivatives.
What happens when it fails — and why it won't fill your disk
Missed uploads stay on disk and retry with backoff. Nothing is deleted until R2's byte count + MD5 match. If Data hits 100% again, OBS can't even write the 1-min MKV — Helper never sees it, so it stays “Recording safely” with 0 B. Free about 2 GB and recording resumes on its own; the helper only ever needs room for the next minute, not the whole session. The Launch WeaverClip button on Home (weaverclip://open) and the Move to Applications banner ensure the helper points to /Applications after one drag, so you don't re-download.
*Hours are at 6 Mbps (1080p30 webinar, slides, sermons) ≈2.7 GB/hour. Actual hours vary with bitrate — 5 Mbps ~2.25 GB/h, 12 Mbps ~5.4 GB/h, 25 Mbps ~11.25 GB/h. Vault is always bytes; hour label is a guide. Hard limit = 2× vault (e.g., Creator 75→150 GB), overage $0.04/GB-month. Transcript never bills overage.
What biggest uploaders do differently — and why they never lose a file
They don't drag a 10 GB file over spotty WiFi and hope. They let the helper split it into 1-min segments, upload while they keep working, and verify before any local delete. A 2-hour 1080p30 webinar at 6 Mbps is ~5.4 GB — that's two 1-min segments per minute, each ~45 MB, each with its own MD5. If one fails, it retries. If Data hits 100% again, OBS can't write the next 1-min MKV — the helper never sees it, so it stays “Recording safely” with 0 B until you free 2 GB. The helper only holds the segment it is currently uploading, so free space is consumed at a steady trickle rather than all at once. That's the asterisk in practice: *Hours at 6 Mbps ≈2.7 GB/h, vault is bytes. Pick by bytes you keep.
Unanswered questions that decide whether you upload
What if my Data is at 100% again?
Free 2GB with the cache clears, but if Data hits 100% again OBS can't write the 1-min MKV — Helper never sees it, so it stays “Recording safely” with 0 B. Clearing a couple of gigabytes of caches is enough, and the helper does the same thing for you as uploads verify: verified uploads free the SSD. Keep 2 GB headroom and the rolling buffer stays ~5.4 GB/hour, not 10 GB at once.
Do I need to keep the original after upload?
No. Helper deletes locally only after R2 byte count + MD5 match. Until then it stays and retries. After verify, local is freed and the vault holds the private copy with signed URLs. Delete sooner from the session page if you want — it enqueues both masters and clips durably before any R2 delete, so a failed delete is recoverable. For phone, /upload-video does the same via browser signed PUT.
Can I upload a 4K sponsor read?
4K 25 Mbps is 11.25 GB/h, so 75 GB is 6.6h. Studio 1.5 TB is 133h at 4K. The vault table on every page lets you translate before you record. If you mix 1080p and 4K in one show, the vault still counts exact bytes, not hours — the asterisk is why we show both.
Why not just use Dropbox?
Dropbox is $9.99 for 2 TB with no transcript. Weaver is $15 for 75 GB vault + 4h transcript that finds 80 ranked moments and renders 100 verticals with Space preset. True Cost table on /features/storage: 2 TB of VODs is $180 of SSD you scrub by hand vs $29/mo that's already transcribed and 180d retained.
*Hours are at 6 Mbps (1080p30 webinar, slides, sermons) ≈2.7 GB/hour. Actual hours vary with bitrate — 5 Mbps ~2.25 GB/h, 12 Mbps ~5.4 GB/h, 25 Mbps ~11.25 GB/h. Vault is always bytes; hour label is a guide. Hard limit = 2× vault (e.g., Creator 75→150 GB), overage $0.04/GB-month. Transcript never bills overage.
The one setting that decides whether your upload fits Free
It's not resolution — it's bitrate. OBS → Settings → Output → Recording → Video Bitrate. At 6 Mbps (1080p30, slides, sermons) Free 10 GB holds ~3.7h. At 12 Mbps (1080p60, games) it holds ~1.8h. At 25 Mbps (4K) it holds ~0.8h. The FreeVideoTool on /vs-opus-clip lets you slide bitrate and see “fits Free” vs “needs Creator $15” before you wait 2 hours for the upload. The asterisk on every vault table is why we show the four-row table: 5 Mbps ~2.25 GB/h, 6 Mbps ~2.7 GB/h, 12 Mbps ~5.4 GB/h, 25 Mbps ~11.25 GB/h. Pick by bytes you keep, not by hours you hope.