Troubleshooting
Slider Revolution Preview Not Working: Causes and How to Fix It

Short answer
A Slider Revolution preview usually breaks because an optimisation or caching plugin changes how scripts load, another plugin or theme conflicts, a firewall blocks the preview request, or PHP memory is too low. Check the browser console first, then disable script optimisation, test for conflicts and update the plugin and theme.
Key takeaways
- Check the browser console and network tab before changing anything.
- Script combine, defer and delay options are the most common cause.
- Test for plugin and theme conflicts on a staging copy.
- A 403 error points to a firewall, and a 500 error to a server problem.
- Hidden layers may be a device visibility or timeline setting, not a bug.
Why is the Slider Revolution preview not working?
The Slider Revolution preview usually fails because of a JavaScript conflict, an optimisation or caching plugin, a blocked admin-ajax request, an outdated plugin version, or a server limit such as low memory.
The preview loads your module inside the dashboard using the same scripts as the front end. If anything stops those scripts or the request that loads the preview, you see a blank box, a spinning loader or an error.
The fixes below run from quickest to most involved. Work through them in order and test the preview after each one.
Take a backup before changing plugins or server settings. Our guide on restoring a WordPress site from backup shows how to roll back if something goes wrong.
If you are new to browser tools, Google's guide to the Chrome DevTools Console shows how to open it and read JavaScript errors.
MDN's reference for the browser console API explains the warning and error levels you will see while debugging.
What does a broken preview look like?
A broken preview usually shows as a blank or grey area, an endless loading spinner, missing layers, or an error message instead of the animated slider.
The symptom gives a clue to the cause. Use the table below to narrow it down before you start changing settings.
| Symptom | Most likely cause | First thing to try |
|---|---|---|
| Endless spinner | Blocked or failed ajax request | Check the browser console and network tab |
| Blank or grey box | JavaScript error or script conflict | Disable optimisation and conflicting plugins |
| Layers missing | Responsive visibility or layer timing | Check device views and the timeline |
| Preview works, live page does not | Caching or minification on the front end | Exclude Slider Revolution scripts and clear cache |
| Error after an update | Version mismatch with theme or add-ons | Update the plugin, theme and add-ons together |
How do you check the browser console for errors?
Open your browser's developer tools, switch to the Console tab, then click preview again and look for red JavaScript errors that name a file or plugin.
In Chrome, right-click the page and choose Inspect, then open Console. Errors often mention the plugin or script that broke, which points straight to the conflict.
The Network tab helps too. Look for a request to admin-ajax.php that returns an error status such as 403 or 500.
The Chrome DevTools console guide explains how to read these messages if they look unfamiliar.
A 403 usually means a security rule blocked the request. A 500 points to a PHP error on the server.
Can caching or optimisation plugins break the preview?
Yes, optimisation plugins that combine, minify, defer or delay JavaScript are the most common reason Slider Revolution previews and sliders fail to load.
Slider Revolution depends on scripts loading in a specific order. When another plugin moves or delays them, the module cannot start.
Try this:
- Temporarily disable JavaScript combine, minify, defer and delay options.
- Clear every cache, including server cache and CDN cache.
- Test the preview again.
- If it works, turn options back on one at a time.
- Add Slider Revolution scripts to the exclusion list for the option that broke it.
Our guide on clearing cache in WordPress covers each cache layer.
LiteSpeed users can follow purging LiteSpeed Cache for that plugin's specific steps.
How do you find a plugin conflict?
Deactivate all plugins except Slider Revolution, test the preview, then reactivate plugins one by one until the preview breaks again.
This is the standard way to find conflicts, and it works for almost every WordPress plugin problem. Do it on a staging site if your site is busy.
Plugins that often clash with sliders include other slider plugins, script optimisers, lazy-loading tools and some security plugins.
If you cannot afford downtime on the live site, the free Health Check & Troubleshooting plugin lets you disable plugins only for your own session.
For a full walkthrough, see our guide to finding which plugin is causing a problem.
Could your theme cause the problem?
Yes, a theme that loads an old jQuery version, bundles an outdated copy of Slider Revolution, or adds conflicting scripts can stop the preview working.
Switch to a default theme such as Twenty Twenty-Four on a staging copy and test again. If the preview works, the theme is the cause.
Bundled copies are a common trap. Some themes ship an older Slider Revolution version and update it only when the theme updates.
Update the theme first, then check the Slider Revolution version under Plugins. If the theme copy lags far behind, contact the theme author for the current package.
Is a security plugin or firewall blocking the preview?
Security plugins and server firewalls can block the admin-ajax request the preview needs, especially when the request carries long or unusual data.
If the network tab shows a 403 error, check your security plugin's firewall log for blocked requests around the time you clicked preview.
Server-level tools such as ModSecurity can block the same request. Your host can check the server logs and whitelist the rule if needed.
Our guide on Wordfence blocking admin shows how to handle a common example of this problem.
Could PHP memory or version limits be the cause?
Yes, a low PHP memory limit or an outdated PHP version can make the preview request fail with a server error, especially on large modules with many layers.
Check Tools > Site Health > Info > Server for your PHP version and memory limit. Large sliders benefit from a higher memory limit.
You can raise the WordPress memory limit in wp-config.php with the WP_MEMORY_LIMIT constant, as described in the WordPress wp-config documentation. Your host may also cap memory at the server level.
If your PHP version is old, plan an upgrade. Our guide on updating the PHP version in WordPress explains how to do it safely.
What if the preview works but layers are missing?
If the preview loads but some layers do not appear, check each layer's visibility for the current device view, its timeline timing, and whether it sits outside the visible area.
Slider Revolution can hide layers on specific devices. A layer hidden on desktop will not show in the desktop preview.
Check the timeline too. A layer that starts after the slide ends, or exits immediately, never appears to the viewer.
Finally, look at the layer position. A layer dragged outside the canvas on one device view can vanish from sight on that view only.
How do you stop the problem coming back?
Keep Slider Revolution, its add-ons, your theme and WordPress updated together, test updates on staging, and keep the slider's scripts excluded from optimisation settings.
Many preview problems return after an update to a caching plugin, which can reset or change its exclusion lists. Check those lists after every major optimisation plugin update.
Write down what you excluded and why. A short note in your site documentation saves you from repeating the whole debugging process next time.
If you build many sliders, our guide on using Slider Revolution in WordPress covers good habits that keep modules light and stable.
What should you do if nothing fixes it?
Update Slider Revolution, its add-ons and your theme, clear every cache, then contact Slider Revolution or your theme author with the console errors and your system details.
Support teams solve problems faster with clear details. Include the plugin version, WordPress version, PHP version, theme name and a screenshot of the console errors.
Slider Revolution's own troubleshooting FAQ lists the checks its support team expects you to try first.
If you need the slider working right away, swap it for a static hero image while you wait. Visitors see a clean page, and you can debug without pressure.
Frequently asked questions
Why does the Slider Revolution preview keep loading forever?
An endless spinner usually means the preview request failed. Check the browser console and network tab for errors, then disable JavaScript optimisation, test for plugin conflicts and look for a 403 or 500 error from admin-ajax requests.
Can WP Rocket or LiteSpeed Cache break Slider Revolution?
Yes. Any optimisation plugin that delays, defers, combines or minifies JavaScript can stop Slider Revolution loading. Exclude the slider's scripts from those options and clear the cache after each change.
Why does my slider work in preview but not on the live page?
The live page goes through caching, minification and sometimes a CDN, while the dashboard preview does not. Exclude Slider Revolution files from optimisation, clear all caches and check the live page in a private browser window.
Do I need to update Slider Revolution to fix the preview?
Often, yes. Outdated versions can break after WordPress or PHP updates. If Slider Revolution came with your theme, update the theme first, since the theme author usually ships the newer plugin with it.
How do I find which plugin conflicts with Slider Revolution?
Deactivate every plugin except Slider Revolution, test the preview, then turn plugins back on one at a time. When the preview breaks again, the last plugin you activated is the likely conflict. Do this on a staging site if possible.
Sources
- Console overview Chrome for Developers
- Health Check & Troubleshooting WordPress.org Plugin Directory
- wp-config.php WordPress Developer Resources
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


