I replaced a $200/month audio processing server with 40 lines of browser JavaScr

<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>Every day, developers and power users need quick micro-tasks done:</p> <ul> <li>Formatting or minifying a raw JSON response</li> <li>Inspecting a JWT header &amp; checking

<div class="highlight js-code-highlight"> <pre class="highlight markdown"><code>privacy webdevEvery time I uploaded a file to an online PDF tool, I wondered: what happens to it

<p>I run <a href="https://videocompress.dev/" rel="noopener noreferrer">a video compressor that works entirely in the browser</a>.<br /> No upload, no server, nothing leaves the

<p>Server-side video rendering is expensive. FFmpeg on a Railway worker, Vercel Sandbox spin-up times, memory limits — it all adds up fast. But modern browsers now ship <a

<h2> You Probably Don't Need a Server for That </h2> <p>A few months ago I needed to convert about forty HEIC photos from my phone into PNGs. The first three results on Google

<p><strong>TL;DR:</strong> When a tool says your files never leave your device, that is an architectural claim, not a marketing one. Here is the stack that makes it true, and what