To run two Splide.js slides concurrently on the same Webflow page without malfunctions, you need to ensure each slider instance is properly initialized with a unique target and avoids conflicts in IDs or class selectors.
splide-1, splide-2) using the Element Settings Panel (the gear icon).
https://cdn.jsdelivr.net/npm/@splidejs/splide@latest/dist/css/splide.min.csshttps://cdn.jsdelivr.net/npm/@splidejs/splide@latest/dist/js/splide.min.js
new Splide('#splide-1', { type: 'loop', perPage: 1 }).mount();new Splide('#splide-2', { type: 'loop', perPage: 3 }).mount();
splide__track, splide__list, and splide__slide) are correctly nested within their respective wrappers and don’t share overlapping global classes.id—each slide must be self-contained and uniquely identified by ID.
To run two Splide.js sliders concurrently in Webflow, assign unique IDs to each slider wrapper, structure each one independently, and initialize them separately via custom script using distinct selector targets. Avoid global class or ID conflicts, and confirm both mount without errors.