Swiper autoplay loop behavior when autoplay disabled

Answer

No. With loop: true Swiper does not automatically transition slides unless the autoplay module is active. Loop only provides infinite wrapping via cloned slides for user‑driven navigation or explicit API calls.

Likely explanation of the observed flicker

• The flicker after the last slide is usually not an auto‑advance caused by loop.
• It most often stems from one of two sources:
  • Autoplay being enabled with a zero delay (autoplay: { delay: 0 }) – this starts the module and triggers immediate transitions.
  • The initial translate that Swiper performs when initializing loop mode, which moves from a cloned slide to the real first slide and can appear as a brief flash.

Steps to confirm and achieve a static‑but‑loopable slider

1. Disable autoplay correctly: either omit the autoplay property or set it to false.

   const swiper = new Swiper('.swiper', {
     loop: true,
     autoplay: false,   // or simply do not include autoplay
     // other options…
   });

2. After initialization, verify that the autoplay module is inactive:

   console.log(swiper.params.autoplay); // should be false or undefined
   console.log(swiper.autoplay?.running); // should be false

3. If you still see a flash on init, try setting speed: 0 temporarily to isolate the init translate:

   const swiper = new Swiper('.swiper', {
     loop: true,
     autoplay: false,
     speed: 0   // removes animation during init; re‑add after testing
   });

4. Restore the desired speed value once you confirm no unwanted transitions occur.

Missing diagnostic detail

To be certain whether the flicker originates from autoplay, please confirm how the autoplay is configured in your code (omitted, false, or { delay: 0 }). This detail changes the recommendation: if you are using { delay: 0 }, replace it with false or remove the property.