Contact EasyLottie

Email

Email Cheng525570145@gmail.com. This inbox is read by the maintainer, not a ticketing system. Include the tool URL, your browser and operating system, the file type, the step that failed, and the visible error message. Do not email confidential source files unless you have permission to share them; a trimmed or anonymized sample is usually enough.

Response times

EasyLottie is maintained by one person, so replies are not instant. Expect an answer within three business days for bug reports and correction requests, and within a week for general questions. Privacy and data-deletion requests are prioritized; what can be deleted and how is described in the privacy policy. If you have not heard back after a week, send a short follow-up; mail does occasionally land in spam.

Community

Join the EasyLottie Telegram group for short questions and workflow discussions. Other users and the maintainer answer there. Avoid posting private client assets or personal information in the group; use email for anything confidential.

Reporting a bug

Most problems are specific to a file, a browser, or a codec. The fastest way to get a fix is to let us reproduce it. What helps:

• The exact page where the problem happened, including the language prefix if any.
• Your operating system and browser name and version.
• The input format, the approximate file size, and for video the codec if you know it.
• The steps needed to reproduce the behavior, and whether it happens with the sample file on the tool page.
• A screenshot or screen recording with private information removed.
• A sample file that shows the problem, if you are allowed to share one. Samples are used only to reproduce the issue and are deleted afterwards.

Requesting a correction to a guide

If a guide states something that is wrong, out of date, or no longer matches how a tool behaves, tell us. Include the guide URL, the sentence or step in question, and, where possible, a source or a file that demonstrates the discrepancy. Corrections replace the inaccurate statement and bump the guide's reviewed date; the editorial policy describes the process.

Feature requests

Requests are welcome, with one honest caveat: the roadmap is driven by problems that many users hit, and the project is intentionally small. Tell us what you were trying to do and where the current tool stopped you. That is more useful than a feature name, because the fix is often a limit we can raise or an explanation we can add.

Privacy, legal, and advertising questions

Review the privacy policy and terms of service first; they cover what runs locally, what is uploaded for accounts, sharing, and AI generation, and how cookies and analytics are used. If the answer is not covered, use the email address above and put “Privacy” or “Legal” in the subject line. Advertising and partnership inquiries go to the same address; note that sponsored content, if ever accepted, will be labeled and will not change a guide's recommendations.

What we cannot help with

• Recovering a file you processed earlier. Core tools run in your browser and do not keep copies of your inputs or outputs unless you saved them to your workspace.
• Editing an animation on your behalf, or producing custom animations.
• Supporting After Effects, Figma, or other third-party software beyond what our guides already cover.