Converted templates keep their animations, fonts and videos
The Elementor template converter now carries entrance animations, hover states, keyframes, the template's own font files and hero videos into the converted site.
A template is more than its HTML. The sections fade in as you scroll, buttons change on hover, a headline is set in a font the designer bought, and the hero plays a short video behind the text. Until 0.8.0 the HTML to Elementor conversion kept the structure and the styling and lost most of the movement. This release carries it across.
Entrance animations and hover states
The converter now reads the animation classes and the @keyframes rules the template ships with and writes them into the section widget. A section that slides up when it enters the viewport does the same on the converted site; a card that lifts on hover still lifts. The keyframes are scoped to the widget, so two sections with an animation of the same name do not fight each other.
The animation library the template used, when it is one of the common ones, is loaded by the widget on the pages that need it and nowhere else.
The template's own font files
Many templates come with their fonts in a folder next to the CSS. The converter copies those files into the site's uploads and rewrites the @font-face rules to point at them. The site serves its own fonts from its own domain: no request to a font service, no consent banner for it, and the design looks the way it did in the template because it is the same file.
Fonts referenced from Google Fonts stay Google Fonts links, exactly as the template had them.
Hero videos
A <video> in the hero, muted, looping and playing inline, is one of the first things a customer notices when it is missing. The converter now brings the video file into the media library, keeps the poster image and the playback attributes, and puts the result in the widget as an editable media control. Replacing the video later is a matter of picking another file in Elementor.
Re-converting refreshes the draft
When you change the template, or when a later version of the Elementor template converter does a better job on a section, you run the conversion again. The re-conversion refreshes the existing draft instead of creating a second one, so the Activity list stays readable and nothing you published is touched until you publish again.
Cost
Converting stays free. It is the template compiler on the platform that does this work, not the model, so the extra fidelity does not show up on your statement. The pricing page lists what does.