Embed Lottie Player – Add Interactive Lottie Animations with Block Support vs tsParticles WP Block

You can embed any LottieFiles animations, .json or .dotlottie files to your WordPress Posts, Pages, Widgets, and more. This plugin is packed with many useful features. You can show your Lottie files exactly the way you want. This plugin has a huge number of options that you can use to achieve your desired goal. This WordPress plugin empowers you to easily integrate Lottie animations into your website with customizable features to enhance user interaction and design. You can easily configure controls, autoplay, looping, links, and player alignment to seamlessly integrate animations into your website pages. With the pro version, unlock advanced functionalities including the ability to upload both .json and .lottie file formats directly to the Lottie Player. Enable hover interactions, choose playback modes, set animation direction and counts, and adjust playback speed and interval for precise control over animation behavior. Increase user experience by opening links in new tabs, and adding interactivity options like scroll synchronization, cursor movement effects, and click-triggered animations. Additionally, you can display captions below the player and customize their appearance with various styling options including text alignment, typography, colors, padding, and margins. With its features, this plugin offers a comprehensive solution for integrating and customizing Lottie animations to elevate the visual appeal and interactivity of your WordPress website. Plugin Demo | Documentation | Get Pro Version Lottie Player Features File: Enter both the .json and .lottie file url. Controls: You can show controls to allow users to interact with the player. Autoplay: You have the option to enable autoplay, allowing the animation to start automatically. Loop: You can enable looping, making the animation repeat seamlessly. Link: You can add a link to the player, allowing users to navigate to a specific URL. Width and Align the player: You can set the width for the player to match your desired design. Also, can align the player to the left, center, or right within its container. Customize the player controls: Adjust the Height, Background Color, Icons Color, Icons Hover Color, Icon Active Color, Tracker Color, and Thumb Color to fit your website’s style. Lottie Player Pro Features Upload File: Upload both the .json and .lottie file formats to use with Lottie Player. Hover: The hover feature lets you enable interaction when the mouse hovers over the player. Mode: You can choose from different playback modes to control how the animation behaves. Direction: You can set the animation’s direction, such as forward or backward. Count: This feature allows you to specify the number of times the animation should play. Speed: You can adjust the playback speed of the animation. Interval: This option enables you to set an interval between animation loops. Open link in a new tab: Enable to open the link in the new tab. Interactivity: Set different Interactions such as Sync with scroll, Scroll relative to the container, Scroll with offset, Sync animation with cursor position, Sync animation with cursor horizontal movement, Play animation on click, Play animation when visible. Caption: Show caption below the player. Caption Styles: Customize the caption’s appearance, including Text alignment, Typography, Colors(text and background), Padding, and Margin. How to use Lottie Player First, install the Lottie Player block plugin. Add the Lottie Player block from the block category called “Widgets” in the Gutenberg editor. You can change block settings from the right-side settings sidebar. Enjoy! For installation help click on Installation Tab User Feedback ⭐⭐⭐⭐⭐ Perfecto ❛❛Genial para meter animaciones lottie❜❜ –juandemingo ⭐⭐⭐⭐⭐ Amazing Plugin! ❛❛This is a fantastic plugin to configure Lottie Animations. Simple and easy to use but still very customizable. The support team helped me a lot while i built my site. Thank you very much guys❜❜ –bueroblanko ⭐⭐⭐⭐⭐ Recommended ❛❛Currently, we have little choice when we need to embed a Lottie animation into a WordPress website built with the block editor. Luckily, this plugin is far above average and offers many options to finetune your animation. (Tip: You can even use it to embed a Lottie animation with the Divi builder – simply create a sidebar, insert the animation there, and then bring it into your page using Divi’s sidebar module.)❜❜ –Martin Sauter – Did you like this plugin? Dislike it? Have a feature request? Please share your feedback with us Check out the Parent Plugin of this plugin- B Blocks – A blocks collection and page building tool for Gutenberg. Check out our other WordPress Plugins- Html5 Video Player – Display videos as single and playlist in multiple skins. PDF Poster – Display/Embed PDF files with different styles. Html5 Audio Player – Listen audios with awesome visuals. StreamCast – Customizable radio player with different skins. 3D Viewer – Embed 3D models and 3D products with interaction. Advanced Post Block – Show posts and custom posts in different layouts. Blocks This plugin provides 1 block. Lottie Player – Lottie player for display lottie files. Source Code You can find the source code, report bugs, and contribute to the development of this plugin on our GitHub repository: Embed Lottie Player on GitHub Third-Party Libraries This plugin bundles the following third-party JavaScript/PHP libraries. @dotlottie/player-component Source: https://www.npmjs.com/package/@dotlottie/player-component GitHub: https://github.com/dotlottie/player-component License: MIT – https://github.com/dotlottie/player-component/blob/master/LICENSE Purpose: Web component used to render and play dotLottie animations in the editor and front end. @lottiefiles/lottie-interactivity Source: https://www.npmjs.com/package/@lottiefiles/lottie-interactivity GitHub: https://github.com/LottieFiles/lottie-interactivity License: MIT – https://github.com/LottieFiles/lottie-interactivity/blob/master/LICENSE Purpose: Adds scroll and cursor interactivity to Lottie animations. Freemius Lite SDK Source: https://bplugins.com/ GitHub: https://github.com/bPlugins/freemius-lite-sdk License: GPL-2.0-or-later – https://www.gnu.org/licenses/gpl-2.0.html Purpose: Provides an opt-in consent form for usage tracking and analytics to help improve the plugin. No data is sent before explicit user consent. External Services: Communicates with api.bplugins.com (activation events) and wp.freemius.com (opt-in processing) only after user opt-in. See bPlugins Privacy Policy and Freemius Privacy Policy. bpl-tools Source / GitHub: https://github.com/bPlugins/bpl-tools License: GPL-2.0-or-later – https://www.gnu.org/licenses/gpl-2.0.html Purpose: Shared utility library providing admin dashboard components and common Gutenberg editor controls. External Services: The library may connect to bPlugins, WordPress.org, and Freemius services for product data and checkout functionality. See full details: https://github.com/bPlugins/bpl-tools#external-requests–why-they-are-made

Official tsParticles WordPress Plugin Easily create highly customizable particle, confetti and fireworks animations and use them as animated backgrounds for your website. Ready to use components available also for Web Components, Vue.js (2.x and 3.x), Angular, Svelte, jQuery, Preact, React, Riot.js, Solid.js, Inferno. Official tsParticles website with options editor: https://particles.js.org Official Social Channels: GitHub Discord Telegram Reddit Twitter Breaking Changes Removed @tsparticles/updater-color and @tsparticles/updater-stroke-color, consolidated into @tsparticles/updater-paint Removed @tsparticles/move-base and @tsparticles/move-parallax, consolidated into @tsparticles/plugin-move Default options updated: removed fpsLimit, changed particles.color to particles.paint.color Bug Fixes Fixed default options alignment with engine v4 API (particles.color → particles.paint.color) Fixed missing plugin-lch-color and duplicate plugin-oklch-color in source loaders Fixed missing toggle attributes for various packages in block.json Fixed alignment between package.json dependencies, block.json toggles, and source loaders (all 151 toggleable packages now match) New Features Added toggleable support for all new v4 packages: Effects: filter, particles, shadow Interactions: external-cannon, external-destroy, external-drag, external-parallax, external-particle Paths: branches, brownian, fractal-noise, grid, levy, random, spiral, zig-zag Plugins: background-mask, blend, easing-bounce, easing-elastic, easing-gaussian, easing-sigmoid, easing-smoothstep, hex-color, hsl-color, hwb-color, interactivity, lab-color, lch-color, manual-particles, move, named-color, oklab-color, oklch-color, poisson-disc, responsive, rgb-color, themes, trail, zoom Presets: ambient, confetti-cannon, confetti-explosions, confetti-falling, confetti-parade, hyperspace, matrix, meteors, party Shapes: infinity, matrix, ribbon, squircle Full integration with the v4 plugin architecture (easings, color space plugins, emitter shapes, exports) = 3.0.0 BREAKING CHANGES Removed all tsParticles load methods to keep only a single one using a single object parameter Removed support for shape deprecated properties like shape.image, shape.polygon, shape.stroke the stroke property can be found in the particles section, not in the shape object the image and polygon properties, like any other shape, are part of the shape.options object Stroke now is a single object only like all the other particles properties Removed multiline text shape, the text shape now supports that Simplified some functions, using objects or removing unused overloads, this is breaking for v2 shapes Moved some properties to private since they were public by mistake (this shouldn’t affect many, the properties were mainly used in the engine) Removed obsolete random properties in options objects Removed emitters shapes from the plugin files, every emitters shape now has a dedicated package Major Changes All the components for Front End frameworks were removed from this repository, each one now has its own repository. This is mainly for maintainability. It’s easier to support multiple Front End frameworks versions in a dedicated repository instead of a multipurpose monorepository. Vue.js 2.x and 3.x were kept split because they have many differences. Angular (@tsparticles/angular): https://github.com/tsparticles/angular (v3 under development) Astro (@tsparticles/astro): https://github.com/tsparticles/astro (v3 under development) Ember (@tsparticles/ember): https://github.com/tsparticles/ember (v3 under development) Inferno (@tsparticles/inferno): https://github.com/tsparticles/inferno (v3 under development) jQuery (@tsparticles/jquery): https://github.com/tsparticles/jquery (v3 under development) Lit (@tsparticles/lit): https://github.com/tsparticles/lit (v3 under development) Preact (@tsparticles/preact): https://github.com/tsparticles/preact (v3 under development) React (@tsparticles/react): https://github.com/tsparticles/react (v3 under development) Riot (@tsparticles/riot): https://github.com/tsparticles/riot (v3 under development) Solid (@tsparticles/solid): https://github.com/tsparticles/solid (v3 under development) Svelte (@tsparticles/svelte): https://github.com/tsparticles/svelte (v3 under development) Vue.js (@tsparticles/vue): https://github.com/tsparticles/vue (v3 under development) Web Components (@tsparticles/webcomponents): https://github.com/tsparticles/webcomponents (v3 under development) WordPress (@tsparticles/wordpress): https://github.com/tsparticles/wordpress (v3 under development) Removed all presets from this repository for a single one (https://github.com/tsparticles/presets) in the @tsparticles organization, this will make easier to contribute to specific presets or create new ones. (Renaming them to @tsparticles/preset- #3977) All the previous packages will be deprecated when v3 will come out. Using only the new naming system is the main focus of v3. All the official packages will have @tsparticles/ organization in the package name, replacing tsparticles- prefix, except for tsparticles package which will remain the same. Moved editor to its own repository: https://github.com/tsparticles/editor Pjs package now supports all the legacy pjs options only. This will make this package a wrapper for old pjs users. You can’t use tsParticles options in pjs calls. Pjs package is no longer part of @tsparticles/slim bundle, only included in @tsparticles/all. Text shape is no longer part of @tsparticles/slim bundle, included in tsparticles. Emoji shape is now part of @tsparticles/slim bundle. Bug Fixes Fixed bug when using particles groups Fixed pool on particles destroyed by updaters Fixed out modes, bounce was not checking the direction of the update request Fixed issue with change theme when an existing canvas is used Fixed updates on particles destroyed by updaters, that section wasn’t using the memory pool for reusing old particles instead of creating new ones. Fixed memory leak in destroyed particles by updaters, the z array wasn’t filtered, thanks to @longnguyen2004, closes #5101 Fixed light interaction, particle shadow wasn’t calculated correctly Improved resize event and density formula Fixed trails config Fixed flat output in @tsparticles/confetti Improved sounds plugin Fixed position in emitters after respawn New Features Added new EventType particleDestroyed Replaced text shape with emoji shape in @tsparticles/confetti Reworked @tsparticles/fireworks a bit for better output with the new v3 trails Added range values to life duration and delay of emitters Added two new bundles @tsparticles/basic: minimum plugins for having circular dots moving in the canvas, common package for all bundles, and presets after this is released. Packages included: @tsparticles/engine @tsparticles/move-base @tsparticles/shape-circle @tsparticles/updater-color @tsparticles/updater-opacity @tsparticles/updater-out-modes @tsparticles/updater-size @tsparticles/all: a package that includes all the plugins, it’s not a best practice to use this, but the easiest way for trying every feature available for sure. It will be used mainly in the website. Added event on config added to the engine Added flat options to @tsparticles/confetti options Creating support for effects, like bubble that wasn’t a real shape Added linear easing Created new emitters shapes: Canvas, Path and Polygon Created trail effect plugin, this one is a real trail drawn in the canvas, it works also in transparent backgrounds. It requires more resources since it’s drawn calculating last N positions and not redrawing a semi-transparent canvas on itself, supports also fade. Added pop click interaction Added limit mode (breaking changes on limit options) Added possibility to replace color and opacity for emitters shapes Added more options for customizing noises values (only Simplex and Perlin paths) Added curl noise path plugin Created Simplex and Perlin noise packages from their path plugins, they can be used in multiple packages without duplication (Curl Noise path for example) Added new emoji shape, better performance than text shape Added clear flag to the root object, enabled by default, if disabled, the canvas won’t be cleared = 2.11.0 Bug Fixes Removed console log, closes #5003 Fixed getPositionOrSize function Fixed some shapes New Features Added refresh flag for loading plugins, this will prevent multiple refresh of the instance Added animated gif support to image drawer (use it with caution, gifs are heavy) Added setLogger and getLogger functions, this will prevent console.log mistakenly left in the code. Added export plugins, previous export functions were removed (barely used), and a 3 new plugins are available. The available exports plugin are: Image, JSON, Video. The first two were already present, the third one is new. Added new rounded polygon shape Other Changes Removed fallbacks for requestAnimationFrame, they’re useless. Added tree shaking capabilities Added ESLint no-console rule, to avoid other issues likes #5003, getLogger must be used when needed some logs. How do setLogger and getLogger functions work? If you want to customize the log of tsParticles you can call setLogger(logger) function, passing a ILogger object. The setLogger function prevents undefined properties assigning the default one. `ts setLogger({ debug: console.debug, error: console.error, info: console.info, log: console.log, verbose: console.log, warning: console.warn, }); ` This assigns all the log functions console functions, but you can use empty functions (() => {}) to disable every function. If there’s a console.log left like in #3552, #3528 or #5003, you can disable the log property of the setLogger parameter to get rid of it, so you don’t have to wait the next release. The getLogger function, returns the object set using setLogger, every plugin MUST use getLogger() for logging things, so mistakes can be fixed easily, even errors can be muted or redirected to your favorite logging platform. If you want to log something use this code: `ts getLogger().log(“tsParticles is awesome”); ` = 2.10.0 New Features Added max speed value to collisions options Added range values to spiral shape options, added widthFactor value Added new arrow shape Added new cog shape Added mode to more coordinates options Added error prefix to standardize error messages Added image preload and name to shape options. Preload an image with a name, so it can be retrieved using only that in the options. Added compatibility with another old particles.js library (deprecated but some samples can be found around) Added new path plugin, using svg paths as a source Added delta to path generators Added delay options to particles values animations (opacity, size, color, stroke), closes #4985 Bug Fixes Fixed typo in fireworks bundle exported types Fixed presets without particles count Improved container reset Fixed window resize fired during the initialization Improved spiral shape Fixed ICoordinates types Fixed some load functions that weren’t async Fixed some shapes particle init Other Changes Improved image shape Changed despawn confetti action using opacity animation, was life duration, closes #4978 All the components for Front End frameworks were removed from this repository, each one now has its own repository. This is mainly for maintainability. It’s easier to support multiple Front End frameworks versions in a dedicated repository instead of a multipurpose monorepository. Vue.js 2.x and 3.x were kept split because they have many differences. Angular (ng-particles): https://github.com/tsparticles/angular Astro (astro-particles): https://github.com/tsparticles/astro Ember (ember-tsparticles): https://github.com/tsparticles/ember Inferno (inferno-particles): https://github.com/tsparticles/inferno jQuery (jquery-particles): https://github.com/tsparticles/jquery Lit (lit-tsparticles): https://github.com/tsparticles/lit (WIP) Preact (preact-particles): https://github.com/tsparticles/preact React (react-particles): https://github.com/tsparticles/react Riot (riot-particles): https://github.com/tsparticles/riot Solid (solid-particles): https://github.com/tsparticles/solid Stencil (`stencil-particles): https://github.com/tsparticles/stencil (WIP) Svelte (svelte-particles): https://github.com/tsparticles/svelte Vue.js 2.x (vue2-particles): https://github.com/tsparticles/vue2 Vue.js 3.x (vue3-particles): https://github.com/tsparticles/vue3 Web Components (web-particles): https://github.com/tsparticles/webcomponents WordPress (wordpress-particles): https://github.com/tsparticles/wordpress Removed all presets from this repository for a single one (https://github.com/tsparticles/presets) in the @tsparticles organization, this will make easier to contribute to specific presets or create new ones. Added global variables to window object, so they are always accessible Migrating output to ES2021, it’s widely used and supported = 2.9.3 Bug Fixes Fixed some plugins, they weren’t loading correctly the options = 2.9.2 Bug Fixes Added missing shapes to confetti bundle Fixed issue with emitters plugin that spawned an unwanted emitters, fixes #4905 = 2.9.1 Bug Fixes Fixed missing plugins in wordpress component Fixed confetti bundle package.json Fixed confetti.create function in confetti bundle = 2.9.0 New Features Creating confetti bundle, easier confetti animations usage. Removed confetti function from the preset, this bundle replaces this feature. Creating fireworks bundle, easier fireworks animations usage. Minor Changes Added version to the Engine object. Added color and colorOffset properties to split options. Changed default particles number value to 0, the previous default value was meaningless. You must specify a number now, it’s easier to implement emitters plugin since you can declare just the emitters property without specifying 0 particles. If you need any number, you declare it ignoring the default value. = 2.8.0 New Features Reworked move.trail options, created a fill property that is an object with color and image, closes #4882 Bug Fixes Fixed polygon mask position issues Fixed polygon mask scaling issues = 2.7.1 New features Added loop options to sounds audio values Added volume buttons to sounds plugin Other Changes Moved out some plugin specific code from the engine to the dedicated plugin 2.7.0 Bug Fixes Fixed issue with animation random size, multiplying again the pixel ratio Added missing export EventType Fixed Engine package exports New Features Added shape options to circle, added range (min/max object) values to polygon and star shape options Changed default file for slim and full bundles, using the bundled file Added support for multiple shape drawers declared at once instead of adding a shape drawer multiple times Added ranged values in stroke width and opacity properties Added loops count to color animations Improved density values, now is 1:1 with number on 1080p resolution with pixel ratio of 1 (this is not a breaking change since nothing breaks, but it changes the behavior of existing values) Density values now has width/height values instead of area/factor, for compatibility reason width is mapped to area and height to factor. Created sounds plugin, with mute/unmute icons Added explosion sounds to fireworks preset Circle Options In particle.shape now it’s possible to set another option to the circle shape, angle. The new property accepts a number or a { min: number; max: number } object, when only number it’s going to be { min: 0, max: }. This creates partial circles starting from min to max, both values must be specified in degrees. If this value is ignored the default value is: { min: 0, max: 360 } (the full circle). Examples ` … shape: { type: “circle”, options: { circle: { angle: 180 } } } … ` This examples creates horizontal half circles ` … shape: { type: “circle”, options: { circle: { angle: { min: 90, max: 270 } } } } … ` This examples creates vertical half circles Density options The density options are changed a bit, instead of area/factor values, the width/height values are introduced and mapped respectively. The default values are changed to width 1920 and height 1080, so on a FullHD resolution on device pixel ratio 1 the particles number is the one specified in the options. Since width and height are multiplied together, they can be swapped and nothing changes. The formula for the density is: (canvasWidth * canvasHeight) / (densityWidth * densityHeight * devicePixelRatio^2) Notes on existing configurations Since many configs had a density.area value of 800, you’ll see less particles, just a few less. If you have also a factor value, you won’t notice any difference. When only area is set, if you want to keep the previous configuration, set factor to 1000. Since the default factor (height) value is 1080 now, the difference should be barely noticeable. 2.6.0 Bug Fixes Improved angular component id management Fixed multiline text shape (and relative demo) Fixed issues with links colors and themes, fixes #4841 New Features Added new resize object to interactivity options, can change the debounce delay, fixes #4803 WordPress plugin is now localizable, closes #4807 Other Changes Fixed dependencies charts on README …