Large images slow down websites, frustrate users, and hurt SEO. Modern formats like AVIF promise smaller sizes with better quality, but the ecosystem is still young. I decided to explore AVIF and build my own converter to see what works in practice.
Why AVIF
AVIF images can be 50β70% smaller than JPEG or PNG at similar or better visual quality. This means faster loading times, lower bandwidth, and improved PageSpeed scores. Yet, support for AVIF in editing tools and converters is still limited, which makes it hard for developers and content creators.
Why I built my own converter
Existing tools are either slow, require file uploads (privacy concerns), or are paid. I wanted a converter that is fast, privacy-first, and free. That led me to create Convertify.
Tech stack
- Rust for performance-critical processing
- libvips as a high-speed image processing backend
- Next.js SSG for static landing pages and SEO
Challenges
- AVIF encoding is slower than JPEG/PNG
- Browser compatibility is still patchy
- UX: making drag & drop intuitive without blocking the main thread
Results
- Conversion speed improved significantly with Rust + libvips
- PageSpeed scores for test pages increased
- Early users appreciated privacy-first, instant conversion
Conclusion
AVIF adoption will grow as tools improve. Building your own converter is a great way to learn about modern image formats and get early traction. Check out a quick AVIF-to-JPG demo Convertifyapp.
Top comments (2)
Nice one π
I faced the same issue with heavy images slowing things down. AVIF really helps, but most tools either ask for upload or are too slow.
Thatβs why I ended up using simple tools like image converter for quick tasks. Privacy-first + fast feels like the right direction.
Good to see someone actually building in this space, not just talking about it.
Thanks! Exactly the problem I was trying to solve β most tools feel like a trade-off between speed and privacy. Glad the direction resonates. Would love to hear if you try it out!