TGS contains Lottie animation data compressed with gzip and prepared for Telegram’s requirements. It is closely related to Lottie JSON, but an arbitrary Lottie animation does not become compatible just by being compressed. Separate the animation data, its supported features and the file packaging when choosing a workflow.
Separate data, compatibility and packaging
Think of three checks. First, is the animation data valid and understandable? Second, does it use features and composition settings supported by the intended renderer? Third, is it packaged in the file format that renderer expects? Passing one check does not imply the other two pass.
A JSON file can parse correctly while describing unsupported layers. A gzip file can decompress correctly while containing unrelated text. A technically well-formed animation can still exceed a platform’s duration or size requirement. This is why renaming files is not a substitute for export validation.
Understand the Telegram relationship
Telegram documents TGS as gzipped Bodymovin JSON containing Lottie animation data. That explains why a developer can decompress a TGS and inspect JSON. It does not mean the decompressed document is the original SVG or the original motion-design project.
For a logo assembled from an SVG and a preset, the source artwork and generated animation are different artifacts. Keep the SVG if you want to edit the shape later. Keep the animation project when using another authoring tool. The compressed delivery file should not be your only editable record.
Check features before compression
Telegram’s animation requirements restrict the kinds of content and effects used in TGS. If an animation depends on images, text layers or effects outside that supported set, compression cannot recreate them as compatible shape geometry. The source animation needs preparation.
For example, a Lottie animation might contain a photograph fading behind a vector logo. Compressing its JSON does not turn the photograph into vector paths. Decide whether to redraw that part, simplify the design or use a video-based delivery workflow appropriate for the content.
Choose the correct input for this converter
SVG to TGS accepts SVG artwork, then generates its supported static or preset animation output. It does not import Lottie JSON, existing TGS, GIF or video. The explanatory Lottie page describes the relationship between formats; it is not a hidden JSON upload mode.
If you have only an existing TGS, ask the creator for the original source when changes are needed. If you have a static SVG, this converter can provide the next animation step after Telegram login.
| What you have | Practical next step |
|---|---|
| Vector SVG | Prepare shapes and use SVG conversion |
| Editable animation project | Export through a compatible animation workflow |
| Lottie JSON | Check renderer support with a suitable Lottie tool |
| Existing TGS | Inspect delivery data; retain or request the original source |
Use a known example to understand the structure
The site provides an SVG square, readable Lottie JSON and its TGS counterpart as a small format example. Compare those artifacts to understand which one represents the source drawing and which ones represent animation data. Do not assume every export will share the example’s size or structure.
For troubleshooting, start with basic fields such as canvas dimensions and frame rate, then move to layer types and unsupported content. A plausible header is only a preliminary check. The final file still needs validation and a visual review in Telegram before it is ready for a pack.