ShrinkRay
Compress files in your browser. No uploads, no sign-up.
Start new thread

ShrinkRay - Compress files in your browser. No uploads, no sign-up.

by•
ShrinkRay compresses images, video, audio, PDFs, 3D models, and more — entirely in your browser. No uploads, no sign-up, no watermarks. Your files never leave your device. Built with Next.js, ffmpeg.wasm, Canvas API, Web Audio, pdf-lib, and Three.js. 100% client-side, open source. Supports: PNG, JPEG, WebP, AVIF, HEIC, MP4, WebM, MOV, MP3, WAV, FLAC, PDF, GLB, GLTF, STL, OBJ, FBX, SVG, and any other file via gzip.

Add a comment

Replies

Best
Maker
📌
Hey Product Hunt! 👋 I built ShrinkRay because every online compressor I found uploads your files to their servers. For tax PDFs, personal photos, and sensitive documents, that didn't feel right. ShrinkRay runs entirely in your browser using WebAssembly — there is no backend. Your files literally never leave your device. It handles almost any file type: images, video, audio, PDFs, 3D models, SVGs, text/code, and anything else via gzip. Would love your feedback! Happy to answer any questions about how the ffmpeg.wasm setup works or the architecture.

Hi, I was trying ConvertIt but the website seems down, so I ended up here instead. ShrinkRay appears to be a 500MB limitation. Has that something to do with limits imposed by the browser?

Maker

 Hey Jonathan — sorry about that, ConvertIt had a brief deploy blip but it's back up at now. Give it another shot!

On the 500MB limit: yep, that's a browser constraint, not a choice by these tools. It comes from how in-browser converters load files into memory (WASM/ArrayBuffers) — there's a per-tab memory ceiling (~2–4GB depending on browser/device), and since conversion often needs a working copy alongside the original, the practical limit lands around 100–500MB before the tab crashes. The mobile limit is even tighter (~100MB) since phones have less RAM.

ConvertIt caps mobile video at 100MB for exactly this reason and handles larger files on desktop. Anything past ~1GB really does need a server — which defeats the whole privacy pitch. Hope to see you back!

 Ah yes you are right. I was looking into it just now. It seems that there is a workaround, but challenging to implement: . Would be awesome if you manage to pull it off. Usually, "user videos" are at least 600MB in size.

Maker

 Also ConvertItshould be up and running now. sorry for that!