I had 200+ short videos sitting in Discord that I needed to turn into GIFs.
I tried the usual online converters. They technically worked, but using them felt oddly exhausting: cluttered interfaces, settings everywhere, and a constant need to guess which parameters actually mattered.
What bothered me wasn’t that they were powerful — it was that every tool seemed to expect me to care about compression details when all I wanted was a specific moment turned into a usable GIF.
Just figuring out what each option did was already more work than the task itself.
After a while, I got tired of fighting the tools and spent one night vibe coding my own.
Video to GIF Converter
The goal wasn’t to build something “better”, just something calmer: a simple, straightforward workflow instead of a page full of knobs.
You upload a video, trim the exact segment you want on a timeline, optionally crop it, pick a quality preset, and convert — all in one flow. No need to think about color palettes, bitrates, or dozens of technical settings that don’t map to real decisions.
You can try it yourself here: Video to GIF Converter
The presets themselves are intentionally opinionated: smallest possible file size for strict platform limits, balanced options for social media, and a max-quality mode that still handles color optimization properly.
The next night, I focused on mobile.
That meant rethinking touch interactions, making trimming usable on smaller screens, and ensuring the same workflow actually holds up on a phone instead of becoming a stripped-down afterthought.
This is where the trade-off became obvious.
On my Mac, conversion feels instant.
On the web, especially with larger files, it can take 20 seconds — sometimes close to a minute.
The flow itself feels right, but performance is clearly constrained by compute. Faster servers would directly translate into a noticeably better experience.
But running enough compute to keep the tool fast and free at scale could eventually cost ~$1K+/month.
I want the site to stay free and usable without friction, but it also needs to sustain its own infrastructure costs if it’s going to remain reliable at scale. Light, non-intrusive ads feel like the most reasonable way to support that balance — keeping the tool accessible while funding the compute it depends on.
I’m still figuring out how that equilibrium looks in practice, especially for a free, compute-heavy product that people expect to “just work”.
Curious to hear how others have navigated similar trade-offs.
If you want to see it in action, check out Video to GIF Converter