How do I animate an element when a Webflow page loads?
Add a Classic Interactions Page load trigger and a custom animation so an element moves and fades in when the page starts loading.
In Classic Interactions, add a Page load trigger and start a custom timed animation from When page starts loading. Page triggers do not offer appear presets. Set a first move and opacity as the initial state, then a later move and opacity for the visible state. Publish to see the motion on the live page. Use this panel when Page trigger is listed. The GSAP builder is separate.
Use Classic Interactions for Page load
Webflow documents Page load inside Classic Interactions. The same help article says Webflow Interactions with GSAP is a separate way to build animations. This guide follows the Classic Interactions panel only. If you do not see Page trigger and Element trigger, these control names will not match, and you should not force this sequence onto the GSAP builder.
Page load is a page trigger. It runs because the page state changed, not because someone hovered a button. Scroll into view is an element trigger, and it is a different guide. The scroll guide is the animation that plays when an element enters the screen. This page is the animation that plays from When page starts loading.
Select the element that should move. A hero heading is a clear target. Give it a class, such as Hero heading, before you build the animation. Actions can target that class later.
Add the Page load trigger
Open the Interactions panel. Click the plus icon to the right of Page trigger, then choose Page load.
On that trigger, open the section When page starts loading. Next to Action, choose Select an action, then choose Start an animation under Custom animation. That path is the same Page load control Webflow documents for a Lottie frame. Here the action is Move and Opacity, not a Lottie frame.
Pre-built animations are the appear and disappear presets, and the emphasis presets. Webflow says you can set those only on element triggers, not on page triggers. If you are looking for a one-click fade under Page load, it is not in that list. The fade has to be a custom animation.
Click the plus icon next to Timed animations. Name the animation in the top field. Hero heading load is enough. A shared name matters later: editing a named animation changes every trigger that uses it.
Build the hidden start and the visible end
Click the plus icon next to Actions. Choose Move under Transform. Set a small x offset, such as -24 px, as a concrete start for this hero. Under Timing, check Set as initial state. Click the plus icon next to Actions again. Choose Opacity under Style. Set Opacity to 0%. Check Set as initial state on that action too.
Those two actions are the state before the animation plays. The heading starts slightly to the side and fully transparent. The distance is an example for one hero, not a required value.
Then add the visible state. Click the plus icon next to Actions, choose Move under Transform, and set the x-axis to 0 px. Leave Set as initial state unchecked on this action, so it plays as the animation rather than as the hidden start. Add Opacity under Style at that same moment, and set it to 100%. You can place that Opacity on the timeline next to the 0 px Move so they happen together. Set a duration on those later actions so the change is visible. Click Save.
If the heading is already visible and then slides, the first Move or the first Opacity was not marked as the initial state. If it never appears, the 100% opacity action is missing, or it is still marked as the initial state. Preview on the canvas before you add a second element.
Aim the actions at the element
By default, an action affects the element that was selected when you created it. That is the right target for a single hero. If you reuse the animation and the actions still point at that original heading, another page can move the first hero instead of its own.
You can aim an action at all elements with the same class. Select the action, and in Affect choose the class rather than only the selected element. Give every hero that should share the motion the same class first. Webflow says the class option is not available on elements that have no class.
Do not look for Interaction trigger on this animation. Webflow says that Affect option is only available when the action is applied to the element that triggers the interaction, and it is not available for a page trigger. Page load has no element trigger to follow. Selected element, or the class, is the choice you have.
Changing the timeline changes every interaction that uses that named animation. If a scroll trigger and this page-load trigger share one animation, editing the distance edits both. Create a separate timed animation for the page load.
Preview, then publish
Play the page in the Designer and confirm the heading starts offset and faded, then settles. An initial opacity of 0% stays invisible until the trigger runs. Leave the Style panel opacity alone when the interaction is what hides the heading.
Page load runs when the page starts loading. It is not While page is scrolling, and it is not Page scrolled. Those are other page triggers in the same list. If the heading only moves after you scroll, the trigger is one of those.
To remove the trigger, hover it in the Interactions panel and click the trash icon. Deleting the trigger does not delete the timed animation. The animation stays available for another trigger.
Publish the site after the preview looks right. A page-load interaction that exists only in the Designer is not on the live page yet. The interactions guide is what to check when the Designer plays the motion and the published page stays still.
A page-load animation on a hero you already have is ordinary interaction work. The membership is one plan for every existing Webflow site: $999 per month, including 10 hours of Webflow work. Additional work is $75 per hour and starts only after you approve a written estimate.
Questions & answers
I wanted the fade when the visitor scrolls to the block. Is Page load the right trigger?
No. Page load runs from the page, when the page starts loading. Scroll into view is an element trigger that runs when that element enters the screen. Use the scroll guide for that case.
Where is the fade preset on Page load?
Webflow says pre-built appear and disappear animations are for element triggers only, not for page triggers. Page load needs a custom animation. Build the fade with Opacity under Style.
Affect does not list Interaction trigger. Did I break the animation?
No. Webflow says Interaction trigger is not available on animations started by a page trigger. Aim the actions at the selected element, or at the class, instead.
The motion plays in the Designer and the live page is still. What should I check?
Publish the site after you save the interaction. A trigger that exists only in the Designer is not on the live page yet. Also confirm you built this in Classic Interactions, not in the GSAP builder.
Sources & further reading
Need a hand with your Webflow site?
View membership
View membership