HN Showcase
Back to browse
ImgPakt – Client-side image compressor, nothing leaves the browser

ImgPakt – Client-side image compressor, nothing leaves the browser

by isuatfurkan·Feb 24, 2026·1 point·0 comments
Visit ProjectView on HN

AI Analysis

●●SolidSolve My ProblemSlick

Client-side compression when TinyPNG, Compressor.io already exist and work fine.

Strengths
  • •Zero-upload architecture genuinely eliminates privacy concerns vs TinyPNG
  • •Batch processing with Web Workers keeps UI responsive
  • •Multi-format support (JPEG, PNG, WebP, AVIF) with preset profiles
Weaknesses
  • •Image compression itself is a solved, commoditized problem with dominant free alternatives
  • •$3.99/mo tier is incremental (batch size, format conversion) without clear pricing moat
Category
Productivity
Target Audience

Privacy-conscious users, designers, content creators

Similar To

TinyPNG · Compressor.io · Squoosh

Post Description

Hey HN,

I built ImgPakt because every image compressor I found uploads files to a server. TinyPNG, Compressor.io, iLoveIMG — they all require sending your images over the internet.

ImgPakt compresses images entirely in the browser using Canvas API and Web Workers. There's no fetch(), no XMLHttpRequest, no upload endpoint in the code. Files literally cannot leave your device.

Technical details: - FileReader → offscreen Canvas → toBlob() at target quality - Web Workers keep the UI thread free during batch processing - Supports JPEG, PNG, WebP, AVIF - 5 preset quality profiles instead of a manual slider

Free tier: 5 images per batch, all profiles. Pro ($3.99/mo): unlimited batch, format conversion, AVIF.

I'd appreciate any feedback on the compression approach or UX. Happy to answer questions about the architecture.

Similar Projects