Choose the file format before choosing a frame rate. Telegram’s vector TGS animations use 60 frames per second, while its video sticker requirements allow up to 30 FPS. A setting that is valid for a WebM video is not automatically valid for a TGS file.
Start with the delivery format
TGS describes vector animation data, while WebM is a video container. They have different preparation and validation requirements. If you are using SVG to TGS, you are following the vector workflow; changing video export settings elsewhere does not configure the TGS exporter.
Use the nature of the artwork to guide the choice. A clean animated icon is a sensible vector candidate. A filmed gesture or detailed photographic sequence may belong in a video workflow. This converter accepts SVG, not video or GIF, so the latter needs an appropriate video editor and exporter.
Understand the relationship between frames and seconds
Frame rate describes how many frames correspond to one second of animation time. Duration describes the length of the animation. In an illustrative 60 FPS composition, two seconds correspond to 120 frames; three seconds correspond to 180. Those numbers describe timing, not the amount of vector detail in the picture.
Changing a frame-rate field without adjusting the associated timing can change playback duration or invalidate assumptions in an animation. Treat the exporter’s timeline consistently. Do not edit a TGS header from 30 to 60 and assume that an incompatible animation has become a properly prepared Telegram file.
Separate frame rate from motion quality
A higher frame rate does not repair a poorly chosen motion curve, an abrupt position change or a loop that resets visibly. Those are animation-design problems. A simple movement with appropriate pacing can look smoother than a complicated motion that jumps between incompatible poses.
For a bouncing dot, compare where it slows and how it returns to its starting point. If the bounce feels mechanical, inspect the available preset and timing options rather than looking for a higher FPS setting. The vector sticker export already has a defined target rate.
Do not use the wrong frame rate to solve file size
When a TGS is too large, inspect path complexity and independently animated elements. Lowering its frame rate below the required value is not a useful way to produce a compliant file. The result may be smaller and still fail the actual delivery requirement.
A logo with many tiny decorative paths often benefits more from simplified geometry than from arbitrary changes to timing metadata. Keep the same motion while simplifying the source so you can compare the effect on the final export.
| Question | Relevant control or decision |
|---|---|
| Is it the correct rate? | Use the requirement for TGS or WebM |
| Is it too long? | Adjust animation duration |
| Does it jump? | Inspect poses and the loop seam |
| Is the file too large? | Simplify geometry and motion data |
Check the exported file rather than a preview label
A browser preview may use its own rendering loop and device resources. The important settings for delivery are those inside the exported animation. For TGS, inspect the exporter’s validation result and the duration it reports, then review playback in Telegram.
If you receive an existing animation from someone else, ask for its format and intended export settings before trying to repair it. The converter does not import an existing TGS or Lottie JSON file. Keep any source project so the author can change timing consistently and export a new version.