Compress Lottie JSON Files Online

It depends on what is inside. An already-minified vector-only JSON may barely change, while formatted JSON or animations with large embedded images can shrink substantially. The tool analyzes the file first and reports the measured result.

Safe minifies JSON and removes only assets proven unused or byte-identical. Balanced also re-encodes embedded PNG, JPEG, or WebP images at 82% quality and keeps the new image only when it is smaller.

Every result is checked for required composition fields and asset references, then rendered again with the Lottie player before download. Your original is never overwritten and remains available.

No. Analysis, image re-encoding, preview, validation, and export all run in your current browser.

Almost always one of three causes. Embedded bitmaps: a PNG grows by roughly a third when base64-encoded, and a few of them can account for over ninety per cent of the file. Formatting: pretty-printed JSON and excessive numeric precision. Or complexity: effects, masks and expressions multiplying keyframes. Upload the file and read the analysis before deciding — it shows where the bytes actually went, which tells you whether to compress or go back to the source file.

There is no universal number and it depends on the job. UI icons and loaders usually land under a few tens of kilobytes; illustrated animations with embedded images can reasonably run into the hundreds. The real test is how long it takes to load on your target network and whether it blocks first paint, not an absolute figure.

This tool works on the Lottie JSON. For a .lottie or ZIP, extract the JSON and compress that. Note that an image-sequence Lottie produced by video conversion carries its weight in the image frames, so the way to shrink it is a smaller output size and frame rate at conversion time, not JSON compression afterwards.

After. Lock the content down with the Color Changer or Image Replace first, then compress, otherwise each edit can write optimized assets back at full weight. Treat compression as the last step before you ship.

Then the file had little to reclaim. A vector-only, already-minified JSON may drop only a few per cent, and that is a correct result rather than a broken tool. At that point the size has to come out of the source: simplify paths, cut layers and keyframes, drop masks and expressions, or re-export at fewer frames.