Editorial Policy

What we publish

EasyLottie publishes practical material about Lottie preview, editing, conversion, optimization, browser behavior, asset packaging, and delivery. We prioritize questions that users encounter in actual design and development workflows: a file that will not play, a color that has to change before a review, a video that needs a transparent background for a web page. We do not publish news round-ups, listicles written for search volume, or articles about topics we have not worked with ourselves.

How a guide is produced

1. Start from a real problem. Topics come from support emails, the Telegram group, failed conversions seen in aggregate analytics, and questions the maintainer hit while building the tools.
2. Reproduce the workflow. The task is performed with the relevant EasyLottie tool and representative files, usually both a simple file and a difficult one. The result is checked in at least one target runtime, such as lottie-web, a mobile player, or a browser video element.
3. Record evidence. Screenshots are taken from the actual tool, not mocked up. Measured results, such as file sizes, frame counts, or export times, are recorded with the sample they came from. Where licensing allows, the sample file is made available for download so readers can repeat the test.
4. Write the limits first. Every guide states what the workflow cannot do before explaining what it can. If a result depends on a browser, codec, Lottie renderer, or file structure, the dependency is named.
5. Review and date. The maintainer reviews the draft against the live tool. The guide shows its publication date and its last reviewed date.

Testing and sources

Workflow claims are reproduced with the relevant tool before publication. Technical explanations link to original specifications, official documentation, or primary project documentation when those sources are available, such as the Lottie format documentation, browser codec support tables, and the dotLottie specification.

We distinguish a verified product behavior from a recommendation or an inference. Limits that depend on a browser, codec, Lottie renderer, or file structure are stated clearly rather than generalized.

Screenshots, examples, and sample files

Images in guides are captured from the tools on this site with real files. Sample animations offered for download are either created by us, released under a license that allows redistribution, or used with permission. When a guide compares formats, the comparison uses the same source file exported through each path, and the figures quoted come from those exports.

AI-assisted work

AI tools may help organize research, draft an outline, propose a translation, or identify language that needs clarification. A guide is not published solely from generated text. Product behavior, measured results, examples, links, and final wording require human review against the live tool. Pages whose translation has not received that review are kept out of search engines until it has.

Updates and corrections

Articles show a publication date and a last reviewed date. We update material when product behavior, browser support, file handling, or authoritative documentation changes. Substantive corrections replace the inaccurate statement rather than preserve it for search traffic, and the reviewed date is updated when that happens.

To report an error, use the contact page and include the guide URL, the sentence or step in question, and a source or reproducible example when possible. Correction requests are normally answered within three business days.

Advertising independence

Advertising must not determine a guide's conclusion or recommended workflow. Ads are kept outside tool workspaces and away from upload, playback, export, and download controls. Sponsored material, if introduced in the future, will be labeled, and a sponsor will never be allowed to review or alter a guide before publication.

What we will not publish

• Claims that a tool does something it does not, including that video can be converted into editable vector Lottie.
• Comparisons with other products that are not based on dated, verifiable testing.
• Pages that exist only to rank for a search phrase and do not help a reader complete a task.
• Guides written about workflows we have not reproduced ourselves.

Who is responsible

The maintainer described on the about page is responsible for every guide on this site and is the person who reviews corrections. Questions about this policy can be sent through the contact page.