Free Lottie Animations for Commercial Use: License and Format Guide 2026

Free Lottie Animations for Commercial Use: License and Format Guide 2026

A Lottie animation is not a video and not a GIF. It is a set of instructions: a JSON file that describes shapes, colours, and keyframes, which a player on the visitor's device draws in real time. That one fact changes the licensing question. A stock photo ships flattened into your layout and stays there. A Lottie file ships as working data inside your app or page, close to its original form, and anyone technical can pull it back out. The license has to cover that, and the main free library's license is written with it in mind.

This guide covers free Lottie animations for commercial work. It reads the main library license in full, explains the two file formats you will download, separates the format (which is an open standard) from the files (which are licensed one by one), and ends with a checklist you can run before an animation ships in client work.

This is practical guidance for working designers, not legal advice. For a paid campaign, a product sold at scale, or an animation that becomes part of a brand identity, take the actual license text to a qualified reviewer.

Lottie Licensing Before You Ship

For client work, the main source is LottieFiles, and its free animations are covered by one document: the Lottie Simple License, first published by Design Barn Inc. in 2021. Read firsthand for this guide, it grants any person who obtains a copy of the public animation files permission, free of charge, to:

• Download and reproduce the files, including for commercial purposes.
• Modify the files. Modifications count as derivative works and must be distributed under the same license terms.
• Publish, distribute, publicly display, and publicly perform the files, as long as any display, publication, performance, or distribution carries the same terms and conditions. You may not add extra terms of your own, or apply technical measures that restrict the rights the license grants.

And it withholds one thing in plain words: the license does not include the right to collect or compile files from LottieFiles to replicate or develop a similar or competing service.

Attribution is not required. The license permits use without attributing the creator, says attribution is strongly encouraged, and asks that any attribution you do include be visible to the end user.

LottieFiles' own licensing help page adds two practical limits on top of the legal text: do not redistribute animations as standalone animation files, and do not resell the original animation files. Read together, the two documents draw a clear line. You may ship an animation inside a product, a site, or a client project. You may not hand the raw file onward as a product of its own. That distinction, finished product versus bare file, is the same one the stock videos guide and the 3D models guide draw for their asset types.

Two warnings before you download anything. First, the help page also says to check the specific license on each animation page, because some animations carry additional restrictions from their creator. The library license is the default, not a guarantee for every file. Second, the format being open does not make any given file free. The next two sections separate those two things, because confusing them is the most common error in this field.

For the audit across every asset type, pair this guide with the design asset licensing checklist, which runs the same questions over fonts, icons, photos, and motion in one pre-shipment pass.

What a Lottie File Actually Is

Lottie started as a workaround. In 2015, Hernan Torrisi released Bodymovin, a plugin for Adobe After Effects that exports an animation as JSON instead of as rendered frames. In 2017, engineers at Airbnb (Brandon Withrow on iOS, Gabriel Peal on Android, Leland Richardson on React Native, with lead animator Salih Abdul-Karim) built player libraries that render that JSON natively in apps, and named the format Lottie after Charlotte "Lotte" Reiniger, the German pioneer of silhouette animation. The history is recorded in the format's reference material and in LottieFiles' own account of the open standard.

The format is now an open standard, not one company's product. The Lottie Animation Community, formed under the Linux Foundation's Joint Development Foundation and announced on 30 January 2024, stewards the specification, and published Lottie spec v1.0 on 17 September 2024. LottieFiles is a member of that community, not the standards body. This matters for licensing in one specific way: the standard governs how files are written and played. It says nothing about who owns an animation or what you may do with it. Rights live in the file's license, not in the format.

Three practical properties follow from the format, and each one shows up in licensing or production later:

1. The file is vector data, so it is small and resolution independent. An icon animation that would be a heavy GIF is usually a JSON file measured in kilobytes, sharp at any size, and recolourable in code. That is why Lottie took over loading spinners, success ticks, onboarding illustrations, and empty-state animations from GIF and video.

2. The file is readable and editable. JSON can be opened in a text editor. Colours, text, and timing can be changed without the original After Effects project. That is why the license's modification clause matters: editing a downloaded animation is normal production work, and the Lottie Simple License expressly covers it, on condition that the derivative stays under the same license.

3. The player renders only a subset of After Effects. Bodymovin exports the features the players understand. Some effects, blending modes, and expression behaviours do not survive export or render differently per platform. LottieFiles runs a feature support checker in its help centre for exactly this reason. Test any downloaded animation in the player your product actually ships, not only in the library's web preview.

JSON and dotLottie: The Two Downloads

You will meet two file tokens, and they are not synonyms. LottieFiles documents both on its format page, and the comparison below follows that documentation.

Choose by delivery, not by fashion. Plain JSON is the portable default: every player reads it, your team can inspect and diff it, and there is nothing to unpack. Choose dotLottie when one file must carry several animations, when the animation embeds raster images you do not want inlined as data URIs, or when the design uses dotLottie's theming or state machine features. The licence question is identical either way, since both containers can hold the same animation. The container is packaging. It is not a licence, and a .lottie extension does not change the terms attached to the animation inside it.

The Licence, Clause by Clause

Most licence summaries in this field repeat the marketing bullets. The Lottie Simple License is short enough to read whole, and four of its clauses decide real production questions.

The grant is wide, and it names commercial use. "Including for commercial purposes" is in the first sentence of the permission. Client sites, paid apps, ads, and monetised content are inside the grant, not in a grey area. LottieFiles' terms of service list the same ground from the other side, defining commercial use to include advertising, products that are sold, monetised content, corporate communications, broadcast, and client projects.

Distribution carries the licence with it. Any display, publication, performance, or distribution of the files must contain, and be subject to, the same terms and conditions. In practice: if your deliverable passes animations onward in a form someone else will reuse (a component library, a white-label product, a client handover with source assets), the licence has to travel with the files, and you cannot wrap them in your own stricter terms or in technical restrictions that cancel the granted rights. Ship the licence text in the project, the same way you would ship a font licence from the fonts for logos guide.

Derivatives stay under the same licence. Edit a free animation, recolour it, retime it, combine it, and the result is a derivative work that must be distributed under the same terms. You cannot take a free animation, adjust it, and then claim it as a proprietary asset under your own licence. Inside a finished product this rarely bites. It bites when the edited animation itself is the thing being handed over, sold, or published as a reusable asset.

No competing collection. The licence excludes collecting or compiling files from LottieFiles to replicate or develop a similar or competing service. Downloading animations to build a rival library, a competing stock collection, or a scrape-and-republish site is outside the grant even though each individual download was free.

On top of the legal text, keep the help centre's two practical lines in the project record: no redistribution as standalone files, no resale of the originals. If your delivery model needs either (a template you sell with the animations inside as editable files, for example), that is the point to stop and either buy a licence that allows it or commission original work.

Free, Premium, and Marketplace Are Three Different Deals

LottieFiles is one site with three licensing situations, and the animation page, not the site, tells you which one you are in.

Free animations sit under the Lottie Simple License described above. That is the deal this guide is mainly about.

Premium animations come with the paid plans. The licensing help page says premium animations under a Pro or Enterprise subscription carry all the rights of free animations, plus extended commercial use rights and priority support for licensing questions. Treat the exact extension as a subscription term to check at purchase time, and note the platform's team account terms as well: the terms of service state that work created through the platform for commercial purposes belongs on a Team plan. Reading your own plan terms is part of the licence check, not an afterthought.

Marketplace animations are sold one by one by their creators. The upload and marketplace guidelines give purchasers the right to use bought animations freely across personal and commercial projects, to modify them, and to include them on a website, an app, or a client's project. The same guidelines prohibit transferring, redistributing, reselling, licensing, or sublicensing the downloaded file to a third party, and bar hosting it on other marketplaces or in products that resell similar resources. Bought is not owned outright. It is a use licence with a hard line at passing the file on.

Whichever of the three you are in, save the evidence at download time: the animation page, the licence name shown on it, and the date. Library pages change, plans change, and animations are sometimes removed. Your project record is the version that existed when you made the decision.

What the Licence Does Not Clear

A file licence covers the file. Four things sit outside it, and each one has caused real trouble in motion work.

1. Characters, logos, and brands inside the animation. Community libraries accept uploads from anyone. An animation of a famous character, a sports mark, or a brand mascot can sit under a permissive file licence while depicting rights the uploader never held. The licence grants what the licensor can grant; it cannot transfer a trademark. Keep uploaded character and logo animations out of client work unless you can clear the depicted rights separately. The same rule applies to the free icons guide and every other community library on this site.

2. The music and images bundled with a project. An animation built to sit next to a sound effect, or embedding a raster image, carries those assets under their own terms. The animation licence does not reach them. The music and sound effects guide covers the audio side of that check.

3. Your client's contract. If your agreement promises the client full ownership of every asset in the deliverable, a same-terms licence can conflict with that promise for the animation files, exactly as a share-alike font or icon licence can. Surface it before delivery, not after a dispute.

4. Performance and correctness in your player. A licence says nothing about whether the file plays well. Large JSON, embedded images, and unsupported effects cost real load time and real rendering bugs. The web animation performance guide covers the budget side of that decision.

A Pre-Flight Checklist for Lottie in Client Work

Run these six steps at download time. They take minutes and they are the whole difference between a file you can defend and a file you are hoping about.

1. Open the animation's own page, not a search result or a collection page. Confirm which of the three deals (free, premium, marketplace) applies to this file.
2. Read the licence named on the page. For free files, that is the Lottie Simple License; note its same-terms condition on distribution and derivatives.
3. Scan the animation itself for characters, logos, products, and people whose rights are not the uploader's to give. If it depicts a brand, treat it as unclear and pick another file.
4. Save the record: animation page URL, licence name, download date, and the file as downloaded, in the project folder.
5. Decide the delivery form. Inside a finished product is the granted pattern. Handing over raw files, building a template for resale, or compiling a collection each need a second look against the licence.
6. Test the file in the player your product ships, at production size and on a mid-range device, and check its weight in the page or app budget before it is designed in.

Frequently Asked Questions

Are Lottie animations free for commercial use?

The free animations on LottieFiles are, under the Lottie Simple License. The licence grants download, reproduction, modification, publication, and distribution, and names commercial purposes in the grant itself. The limits are specific: no collecting files to build a competing service, no redistributing the animations as standalone files, no reselling the originals, and derivatives must stay under the same licence terms. Always confirm the licence shown on the individual animation page, because the help centre notes that some animations carry extra restrictions from their creator.

Do I need to credit the animator?

No. The Lottie Simple License permits use without attribution, while strongly encouraging it. If you do include attribution, the licence asks that it be visible to the end user, so a credit buried in a code comment is not the spirit of the term. A credits screen, an about page, or a colophon in the product are the natural places.

Can I edit a free Lottie animation for a client?

Yes. Modification is inside the grant, and the format makes it practical: colours, timing, and text can be changed in the JSON or in an editor without the original project file. The condition is that derivative works must be distributed under the same licence terms, so an edited animation cannot be relicensed as your own proprietary asset. Inside a finished client product, editing is routine and covered.

Can I sell a template or product that includes free Lottie animations?

Selling a finished product that plays the animations is inside the grant: distribution and commercial use are both permitted, with the licence travelling with the files. Selling the animations themselves, or a package whose value is the raw editable files handed to the buyer, is the line the licence and the help centre both draw: no resale of the original files, no standalone redistribution, no competing collections. Templates sit close to that line, so read the current licence text against your exact delivery format, or get the animation custom-made.

What is the difference between Lottie JSON and dotLottie?

JSON is the original format: one animation as plain, readable text, supported by virtually every player, with any images embedded as data URIs and no built-in compression. dotLottie is a ZIP container that can hold several animations plus their image assets as separate files, compressed with Deflate, and adds theming and state machine interactivity, at the cost of needing a dotLottie player and being unreadable as text. The container does not change the licence of the animation inside it.

Is the Lottie format itself free to use?

Yes. Lottie is an open standard stewarded by the Lottie Animation Community under the Linux Foundation, and the players are open source libraries. That covers the format and the tooling. It does not make any particular animation free: each file carries its own licence, set by the library or creator you got it from. A free player plus a file you have no rights to is still a file you have no rights to.

Where else do licensing traps hide in motion work?

In three places. Sound: an animation timed to a track does not clear the track. Bundled images: a JSON that embeds raster artwork carries that artwork under its own terms. And depicted rights: characters and logos drawn by an uploader are not theirs to license. The illustrations guide works through the same depicted-rights problem for static artwork.

Sources Read for This Guide

• The Lottie Simple License, full text, lottiefiles.com/page/license (Design Barn Inc., 2021): the grant, the same-terms condition on distribution and derivatives, the competing-service exclusion, and the attribution position.
• LottieFiles Help Centre, Animation Licensing Basics, help.lottiefiles.com: the free, premium, and uploaded animation summaries, the standalone-redistribution and resale limits, and the per-animation licence warning.
• LottieFiles format documentation, docs.lottiefiles.com/en/format: the JSON and dotLottie comparison, extensions, MIME types, and container features.
• LottieFiles, Establishing an Open Standard for Vector Animation: the Bodymovin and Airbnb history, the Lottie Animation Community under the Linux Foundation, and the Lottie 1.0 specification.
• LottieFiles terms and upload guidelines: the commercial use definition and the marketplace purchaser rights and prohibitions.

Licences and library terms change. Every statement above reflects the documents as read for this guide in October 2026; check the live documents before relying on them for a new project.