Three things that broke when I moved video compression into the browser

<p>Every few weeks I hit the same wall: I have a 300 MB screen recording, and something on the other end wants it <em>under 8 MB</em>. Discord, an email attachment, a bug tracker,

<p>Last year I was paying $200/month for an EC2 instance that did one thing: accept audio file uploads, run FFmpeg, and return the converted file. FLAC to MP3. WAV to OGG. Bitrate

<p>I spent a weekend building a video-to-GIF converter that runs entirely in the browser. No server, no uploads, no ffmpeg binary — just raw JavaScript turning video frames into

<h2> TL;DR </h2> <p>Modern WebAssembly codecs (MozJPEG, libavif, OxiPNG/imagequant, libwebp, gifsicle, SVGO) now run fast enough in the browser that you can ship a real

<p>CogniPrep's interview practice records five video answers in the browser and sends them to object storage, where a worker picks them up. I wrote about <a

<p>When we first started building ClipCrafter's browser-based video engine, our biggest enemy wasn’t the complexity of FFmpeg—it was something much more silent and deadly:

<p>Every developer working with cloud infrastructure, CI/CD pipelines, or containerization deals with YAML and JSON daily. </p> <p>Whether configuring a Kubernetes manifest,

<p><em>A free game center at <a href="https://wqnlll.github.io" rel="noopener noreferrer">wqnlll.github.io</a> — no framework, no build step, no npm install. Just HTML files on