03
KEEP
Both files stay local.
Local-first by architecture.
What it actually does
01
DECODE
PNG decoded by the browser. Pixel grid extracted.
Lossless input — every pixel exact, alpha channel intact.
02
ENCODE
Color-quantized to a 256-color palette, then written as GIF.
Smart quantization picks dominant colors. Posterization is intentional — it's the GIF look.
04
BATCH
Drop a folder of PNGs.
Each becomes a single-frame GIF.
How it works
- Open morph.cool in any modern browser.
- Drop your .png file onto the drop zone, or click to browse.
- Pick GIF as the output format.
- Download your converted .gif file. Done in seconds.
0Max colors
0%Upload
Why it lives in the tab
Most of the time, going PNG → GIF is the wrong move — you're trading lossless modernism for a 1987 codec with a 256-color palette. But there are still contexts (legacy systems, messaging apps, retro aesthetics) where GIF is the right answer. We do the quantization in the tab so neither file ever leaves your device.
Frequently asked
Why GIF instead of PNG?
Some legacy tools or messaging contexts specifically want GIF. For everything else, PNG is the better target.
Will it look posterized?
If the PNG has many distinct colors, yes — 256 is a hard cap. For sharp graphic content with limited palettes, the GIF looks identical.
Does transparency carry over?
GIF supports a single transparent color, so subtle alpha is lost. Hard-edged transparency survives.
Single frame or animated?
Single frame. PNG is a still image; the GIF output is a single frame.
Does this batch?
Yes — drop a folder, each PNG becomes a GIF.