FFmpeg is a powerful tool for media processing, but using it traditionally can be cumbersome, especially when combined with server-side scripting. The article explains how the authors transitioned to a browser-based solution using WebAssembly (Wasm). Instead of relying on complex bash scripts that often break with unusual filenames and require dedicated server resources, they integrated FFmpeg directly into a Chrome extension. This approach simplifies media workflows, allowing for tasks like adding subtitles, trimming, and uploading videos to YouTube without the overhead of external APIs. The integration leverages a Virtual File System (VFS) to handle files locally within the browser, reducing the need to transfer large video files over the network. Commands are sent as JSON payloads, which simplifies the command structure and eliminates issues with shell quote escaping. While the performance can lag for longer clips, this method makes it easier to generate and process short videos. Users can create workflows that treat FFmpeg as a simple tool, streamlining media tasks into a serverless, event-driven chain. The article also includes practical examples and prompts for users to experiment with this setup. By drawing simple images and converting them into videos, users can see firsthand how the integration works. The authors emphasize the importance of making FFmpeg a workflow primitive rather than a standalone service, allowing for smoother automation and task execution.