03
RESULTS
~50% lighter, typical
JPG: 40–70%. PNG: 50–85%. WebP: 25–35% vs JPG.
What it actually does
02
PREVIEW
Before/after on one screen
See the trade before you commit. Sliders adjust the bitrate live; the preview updates with each move.
04
PRIVACY
Local-only encode
Photos stay on your device.
How it works
- Open morph.cool in any modern browser — no account, no install.
- Drag a JPG / PNG / WebP onto the drop zone, or pick a folder.
- Slide between visually-lossless and aggressive. Preview updates live.
- Mozjpeg / oxipng / libwebp encode locally via WebAssembly.
- Download. Originals untouched. No upload, no log.
0%Upload
50%Typical reduction
Why every blog post about image compression eventually drives you here
Image compression is one of the most-Googled web-perf topics on earth, and the answer is always "use mozjpeg or oxipng." Both are open-source, both have been the gold standard for a decade. The problem is the ergonomics: they're command-line tools, they require Node or Rust toolchains, and most photo-people don't live in a terminal. So the market filled with web wrappers that all run the same encoders but charge for the convenience of not setting up a build environment. Some upload to a server you don't control (privacy cost). Some cap at 5 MB. Some have license terms that change yearly. Morph runs the same encoders compiled to WebAssembly directly in your browser tab.
Where the upload sites still win
If you're compressing tens of thousands of images per day as part of a CMS pipeline with retries and CDN integration, server-side tooling (or a CLI encoder in Docker) makes more sense. Morph is for the daily-driver path — one folder, drop, compress, attach.
Frequently asked
How is this different from the compressor sites?
The compressor sites upload every image to their servers and apply a 5MB-per-file cap on the free tier. Morph runs mozjpeg, oxipng, and libwebp directly in your browser via WebAssembly — no upload, no per-file cap beyond your machine's memory, and no daily quota of any kind.
How much smaller will my files be?
Typical results: JPG drops 40-70 percent, PNG drops 50-85 percent on photo-style content with large flat regions, WebP drops 25-35 percent versus JPG at the same visual quality.
Will it ruin my image quality?
Not at the recommended settings. Mozjpeg uses perceptual quantization that preserves what your eye notices and discards what it doesn't. The default quality is calibrated to be visually identical to the original at roughly half the file size.
Can I batch-compress a whole folder?
Yes — drop a folder, drop fifty files, drop two hundred. The free tier has no batch limit. The only constraint is your device's available memory.
Are originals safe?
Originals stay where you dropped them from — Morph never modifies the source file. Compressed copies are downloaded to your machine. Nothing is uploaded, nothing is logged.
Does it support WebP and AVIF?
WebP encoding is available via libwebp. AVIF is supported on browsers that ship the libavif binding (Chrome and Firefox at the time of writing). Output format is independent of input — you can drop a 5MB PNG and get back a 400KB WebP in one step.
Nothing leaves your device · Free for what you make, credits for what we run