Edit a six hour VoD with zero bytes on your drive.

A four hour Twitch VoD at 6 mbps is about 11 GB. A week of streams is 70 GB. After a month your drive is full and you are juggling external SSDs just to keep editing.

Voding keeps the source on our infrastructure. You stream the segments you actually look at inside the editor. Storage is metered by plan, never by your hardware.

Because the whole workspace is server-rendered, opening Voding on a second machine gives you the same clips, categories, and overlays. No sync setup. No project file shuffling across Dropbox.

Twitch deletes VoDs after 14 to 60 days. Voding keeps a copy as long as your storage allows. Build a permanent archive of moments worth saving without writing a single byte to your own disk.

A four-hour Twitch VoD at 6 Mbps source bitrate is 11 GB. A typical streamer's week is six VoDs — about 66 GB. A month is 280 GB. A year is 3.4 TB. That is one 4 TB external drive per channel per year, and you bought the editing rig assuming it would last three.

Voding stores the source on infrastructure-grade NVMe in eu-central-1 and streams the segments you actually scrub through to your browser. The numbers above never touch your machine. If you delete a VoD from Voding it is gone — no shadow copy on your drive, no project file referencing a path that no longer exists, no scavenger hunt for the right external when you want to re-edit something six months later.

Editing bandwidth — the bytes that move from Voding's storage to your editor — is generous on every plan and is not the bill's variable. What you pay for is concurrent storage. Render bandwidth (downloading your finished MP4s and chat MOVs) is also included up to a soft cap proportional to your storage tier, which is set high enough that the realistic ceiling for a working editor is "have you downloaded everything from the past year three times".

If you exceed the soft cap we email before throttling, never silently. Heavy archival use cases (re-downloading every clip to local cold storage) are the only scenarios that have hit the cap so far in testing.