Private R2 vault, verified before local delete. Your disk stays clean.
One-minute MKV segments, byte count + MD5, signed PUT, verify before the helper deletes locally. Free 10 GB (~3h), Creator 75 GB (~25h), Pro 150 GB (~50h), Studio 1.5 TB (~535h). Hard limit = 2× vault, overage $0.04/GB-month, transcript never bills overage. 30d Free, 180d paid, date shown.
Local ffmpeg piles 30 GB in./outputs while you try to keep operating. Weaver's helper watches OBS's output folder, uploads each 1-minute MKV while you record, and only deletes the local file after R2's byte count + MD5 match. Missed uploads stay and retry with backoff. Playback is short-lived signed URLs, never public. That's why agents can run overnight: upload → verified → tmp deleted, host keeps operating.
One-minute MKVs while you record — helper uploads as you go,
Verify before delete: byte count + MD5 must match R2 before
Private R2, signed URLs expire in minutes, never public, nev
Hard limit 2× vault (Creator 150 GB), overage $0.04/GB-month
SRT ⇄ VTT ⇄ TXT, overlap fixer, 2-line linter
All in browser — your file never leaves the page.
See the 3 moments we'd pull before you sign up
MCP weaverclip_search_transcript — free taste.
How much silence are you transcribing?
Is your old VOD already gone?
Twitch deletes fast. WeaverClip keeps it.
Does your lane keep up live?
Record bitrate vs upstream — will you finish uploading after you stop?
Two numbers match or you don't touch the file
MCP weaverclip_get_usage — verify before delete.
One canvas or two?
1.4 TB freed — zero files lost
Will your webcam get cropped?
Do people actually read this?
*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.
Sharp nuances you didn't know you needed
How uploads stay safe while you record — the 3-lane model
Lane 1 Helper → R2: OBS writes 1-min MKVs to ~/Library/Application Support/WeaverClip/spool (landscape) and verticalSpoolDir for Aitum. Helper measures bytes + MD5, gets a signed PUT, uploads, then HEADs R2 for bytes + ETag (MD5) and compares. Only on match does it unlink the local file. Lane 2 MCP = text only (transcript, markers, timecodes). Lane 3 Render → R2: you or agent create clip decision, helper renders captioned MP4, verifies, uploads. Nothing crosses lanes by accident — video bytes never travel through MCP JSON.
Vault math — bytes beat hours, and hard limit beats surprise bills
Vault is bytes; hour label is at 6 Mbps. 75 GB is ~27h at 6 Mbps, ~13.8h at 12 Mbps, ~6.6h at 4K. Studio 1.5 TB is ~535h at 6 Mbps, ~277h at 12 Mbps. Hard limit is 2× vault — Creator 150 GB, Pro 300 GB, Studio 3000 GB. Over vault you pay $0.04/GB-month and still have 2× headroom to decide: delete a 2h VOD (~5.4 GB) or upgrade. Free never bills; it pauses at 10 GB and files stay on Mac. The nuance: finished clips (~35 MB each) count in the same vault, but 100 of them is 3.5 GB — an hour of source.
Retention — 30d vs 180d and the daily enforcer
Every recording shows its own deletion date (e.g., Deletes May 14). Free 30d, paid 180d, enforced daily at UTC. Delete sooner anytime — that enqueues both masters and all clips durably before any R2 delete (pending_r2_deletions, pending_r2_multipart_aborts), so a failed delete is recoverable. Transcripts and markers can remain while account is current even after source deletes; finished clips are separate MP4s and keep until you delete them. The 24h stream-a-thon nuance: a 24h at 12 Mbps is ~129 GB and needs Studio to hold at once, but most creators split 12h → clip → delete source → repeat, so 75 GB is enough with discipline.
Disk-Full Clock — the tool streamers share
Drive size + free space + weekly schedule (days × hours × bitrate) → the calendar date OBS dies. At 75 GB vault + 10h/week at 12 Mbps (~54 GB/week), your 500 GB SSD fills in 9 weeks without Weaver. With Weaver, verified uploads free the SSD nightly. The Disk-Full Clock on /features/storage is a Discord flex — screenshot 'My drive fills March 14. Weaver deletes that date.' That's why biggest streamers pay attention: it's not storage, it's 'I can keep operating without scrubbing a drive at 2am.'
Safe-to-Delete Check — the trust story made interactive
Local byte count + MD5 vs vault manifest → green light or the exact segment that doesn't match. The helper journal saves filename stem as recording key, variant IDs, checksums, retry backoff, so after a crash it resumes the same PUT and verifies. No 'vibes delete.' Two numbers match or you don't touch the file. Agents call this before advising delete — that's why host keeps operating without piling ffmpeg outputs.
Questions that decide the purchase — answered before you ask
What if my internet drops at 11pm during a 6-hour stream?
OBS keeps recording to disk. One-minute MKVs wait locally, helper retries with increasing delay (exponential backoff), and nothing is deleted until R2's byte count + MD5 match. You lose upload time, not footage. The Safety Rail shows the 38-second gap and the clean ranges you can still clip. After reconnect, the helper drains the backlog; if it's >5 minutes it pushes a notification you enabled.
Do I need a NAS or Dropbox for long VODs?
No for active clipping. Weaver's vault is cheaper than Dropbox ($9.99 for 2 TB with no transcript) and searchable: transcript once, search 'pricing' in 300ms, bulk-create 12 edits. For archival beyond 180d, download the finished clips (separate MP4s, ~35 MB each) and keep the SRT. True Cost of Keeping It 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.
Can I record both 16:9 and 9:16 at once?
Yes via Aitum vertical canvas + Display 1, same filename stem %CCYY-%MM-%DD_%hh-%mm-%ss, TRUSTED: helper pairs only on exact stem match, extensions may differ, extensions don't pair by time. Both masters count as storage (2× bytes) but share one transcript (counts once). Each finished export counts as one render. For a 2h show at 6 Mbps ×2, that's ~10.8 GB storage, 2h transcript.
How does the agent keep my disk clean?
Agent writes to /tmp, uploads to its isolated vault (scoped API key + R2 prefix), helper verifies, deletes /tmp. The agent's vault is not your camera roll — your human vault never sees agent footage. Free 10 GB/2h is enough for 3 tests a week; npx -y weaverclip-mcp is the one-liner.
Try it with the video you already have.
Free holds a full 2–3h webinar at 6 Mbps for 30 days. Upload the whole thing, download the SRT, make clips later — no re-transcribe.