Vidi brought a launch special.
First 100 eligible new subscribers: 30 days of Starter free + 100 processing minutes.
Payment method required via Stripe. Then US$9/month unless cancelled before renewal.
https://t.co/Oo0wVSy0fJ
Pick a VideoWorker recipe and open it in the Playground. The FFmpeg command is already there. Add your files, tweak it, and run.
26 recipes, including fade-outs and short reverse clips. REST and MCP examples included.
https://t.co/49xIhozwVU
We love FFmpeg. We just think your CPU deserves a break sometimes.
Small job? Run it locally. Bigger workflow? Send it to VideoWorker via API or MCP.
https://t.co/O4JSFESVcH
Subtitles in. Job updates out.
Bring your SRT/VTT: burn captions in or add a switchable MP4 track.
Get signed webhooks when jobs finish.
Web, REST API & MCP. Same processing allowance.
More features on the way.
https://t.co/O4JSFESnn9
Four new presets. And we're just getting started. MP4 video, MP3 audio, JPEG thumbnails & GIF previews โ now live in VideoWorker. Web, REST API or MCP. Custom FFmpeg commands still work. More features on the way. Stay tuned.
https://t.co/O4JSFESnn9
@FunDipVapeRip Yup! GPU encoding is great for local workloads. VideoWorker is more about offloading processing and integrating it into automated workflows. If local FFmpeg works for you, thatโs perfectly valid too :)!
Meet Vidi! Small mascot. Big video jobs.
We're launching VideoWorker: run your FFmpeg jobs via API or AI agent. Vidi's coming along for the ride.
https://t.co/O4JSFESVcH
@ThomasBurkhartB Fair point! ๐ For smaller tasks, running FFmpeg locally makes perfect sense. But for heavier workloads, why not let your agent call an API and offload the processing? Less setup, less CPU load.
Weโre live ๐
FFmpeg for your apps. And your agents.
Convert, compress, trim and combine media via REST API, MCP or web.
Launch offer: 30 days of Starter free for the first 100 eligible new subscribers. Then $9/mo; cancel before renewal.
https://t.co/O4JSFESVcH