Reka Vig

Reka Vig

Building smart tools. Design + Dev + AI

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Forums

Quick question — what image format do you usually export/save to for the web?

Curious about everyone's workflow here.

When you're optimizing images for websites, landing pages, or e-commerce what's your go-to output format?

  • WebP smaller files, great browser support now

  • JPG the reliable classic

  • PNG when you need transparency

  • AVIF the new kid on the block

  • Something else?

I've been building Tinify (launching tomorrow!) and made the deliberate choice to output WebP and JPG skipping PNG entirely because WebP handles transparency AND compresses way better.

Why I built Tinify — and why your images deserve better

Hey everyone

I'm Reka, a web designer and developer running The WOW Studio. I work mostly with Shopify and Webflow stores, so I deal with product images all day, every day.

Here's what kept frustrating me:

Every image optimizer out there follows the same playbook let you compress a few images for free, cap the file size at 5MB, then push you toward a subscription. I get it, businesses need revenue. But it always felt wrong that something as basic as image compression was locked behind monthly fees.

Client-side vs server-side image compression — why I chose the browser

When I started building Tinify, the first big architectural decision was: should image compression happen on a server or in the user's browser?

Most tools (TinyPNG, Compressor.io, etc.) upload your images to a server, compress them there, and send them back. It works, and server-side processing can use more advanced algorithms.

I went the other way 100% client-side processing using the Canvas API and browser-native encoding.

Here's why:

View more