Arts Horizontal Scroll for Elementor

Yes. There is no Pro version and nothing in the widget is locked – what you install is the whole product. If it earns its keep, there's a donate link.

No. The free Elementor plugin is the only requirement.

No. The browser itself moves the panels – the plugin doesn't run animation code on every scroll step and doesn't load a heavy animation library. Its whole frontend footprint is a few kilobytes of CSS and JavaScript. Browsers that don't support the underlying CSS feature yet – Firefox today, older Safari – load a small polyfill on demand; everywhere else the motion is pure CSS.

By default the section switches to a vertical stack on touch devices – panels become normal full-width blocks in the page flow. You can turn that off to keep the horizontal scroll, or force the vertical layout below any breakpoint with the responsive Layout control.

Yes – panels are real Elementor Containers, Flexbox or Grid alike. Anything you can build in a Container works, including nested layouts.

No. The pin offset control sets where the section sticks, so it pins below your header instead of sliding behind it. The WordPress admin bar is accounted for automatically.

Yes – that's the default way to use it. The widget is a regular section in the page flow: place it anywhere between normal vertical content, and the page scrolls as usual before and after it. Several sections on one page work too; each runs independently.

No. The plugin never intercepts wheel, touch, or keyboard input. The page scrolls exactly as it always did; the section maps a stretch of that scroll to horizontal movement.

It's built to stay out of the way. It doesn't bundle an animation library that could collide with your theme's scripts. Scroll snap is neutralized on the section itself, so Elementor Pro's Scroll Snap keeps working on the rest of the page. Smooth-scrolling libraries like Lenis are picked up automatically – the engine reads the native scroll position, which is exactly what they animate.

Effects that fire on becoming visible work as-is: entrance animations, lazy-loaded images and backgrounds, video autoplay-on-visible, counters and progress bars all trigger as their panel scrolls into view. Elementor Pro's Scrolling Effects – on elements and on backgrounds – are corrected automatically: instead of freezing while the section is pinned, they follow the element's ride across the stage, from entering on one side to leaving on the other. Effects set to "Entire Page" read the page's own scroll, as always. Pro Sticky and Position: Fixed still don't apply inside the panels – a moving track can't hold a fixed element.

An entrance animation works fine – the section fades or slides in, then pins and scrubs as usual. Elementor Pro's Scrolling and Mouse Effects on the widget itself also run, but they move the whole pinned scene as one block – usually you want them on elements inside the panels instead, where they follow the horizontal ride. Two settings do break the pin: Pro's Sticky, and Position set to absolute or fixed. The section visibly stops working the moment either is applied, and switching it back off restores everything.

Yes. Link to any element inside a panel – the panel's own container or anything nested in it – with a normal CSS ID, and the page scrolls to the position where that panel is on stage: on click, and when the page loads with the link already in the URL. Where the pinned scroll isn't running (touch stacking, a vertical Layout breakpoint, a browser without support), anchors scroll normally instead – nothing to configure.

With Elementor Pro's menu widget, yes. Point menu items at panels – or anything inside them – with normal # links: clicking scrolls to that panel on stage, and while the section scrubs, exactly one menu item stays highlighted: the one whose panel is in view. Elementor Pro on its own toggles items independently and often lights two at once; inside the section the plugin arbitrates that down to a single, correct highlight. Your vertical anchors before and after the section behave as usual.

Yes. The section publishes a small stable surface: a named CSS scroll timeline, state variables to gate on, per-panel range variables, and a JavaScript timeline API that works the same whether the browser is native or polyfilled. Your own scroll-driven animations can ride the same scroll as the track – the README in the GitHub repository documents the full contract.