A slider is the one part of a WordPress site that quietly rots. You build it in March with your six best products and your three newest posts. By September, two of those products are discontinued, one is sold out, and the slide labelled “latest” is half a year old. Nothing errors. Nothing looks broken. It is simply wrong, and it stays wrong until somebody remembers to open the slider editor. A dynamic WordPress slider fixes that by not storing slides at all. It stores a question about your content, and asks that question again whenever your content changes.
This post is about the difference between those two kinds of slider, and which half of the work actually costs money. I build and sell WordPress plugins and WordPress themes, including Noyan Content Slider, so I have an obvious interest here — which is why I want to be blunt about the split. The visual builder, the video slides, the animations and the Elementor slides are all free. The paid add-on does one job, and it is the job in the first paragraph.
Why hand-built sliders go stale
A hand-built slider is a snapshot. You choose the items, type the headings, upload the images, and it keeps showing exactly that until a human changes it. Fine for a message that does not change. A slow leak for anything tied to inventory or publishing.
The sold-out product problem
On a shop, the homepage slider is the most expensive real estate on the site, and a hand-built one has no idea what is in stock. A visitor clicks the slide, lands on the product and reads “out of stock” — your best placement spent teaching somebody you do not have what they came for. Prices do the same: the slide says one number because you typed it, the product page says another because you ran a sale.
The “we’ll update it later” problem
Every hand-built slider comes with an unwritten maintenance task: open the editor, delete the old slides, add the new ones. Nobody schedules it. On client sites I have handed over, this is usually the first thing to fall off the back of the process — invisible work with no deadline. So the honest question is not “which slider looks best in the demo” but what happens to this slider in six months, when the person who built it has moved on?
What a dynamic WordPress slider actually does differently
A dynamic WordPress slider inverts the relationship. Instead of “here are five slides”, you define “the five most recent posts in the Guides category, skipping anything with no featured image”. The slider resolves that against your live content. Publish a post, and it appears. Sell out of a product, and it drops out. Retire a term you built a taxonomy slider from, and its slide goes with it. Nobody opens the slider editor again, because there is nothing in there to update.
The trade-offs are real:
- You give up per-slide control. If slide three needs a bespoke headline and a different button colour, a query will not give you that. Hand-build it.
- You depend on your own content hygiene. A dynamic WordPress slider is a mirror. If half your posts have no featured image and your excerpts are auto-generated mush, the slider shows exactly that.
- You add a database query to the page. Fine if it is cached properly, a problem if it is not — and correct cache invalidation is the hardest part of doing this yourself.
Be clear about this: most “premium slider features” are free
The free Noyan Content Slider on WordPress.org is not a crippled trial. Before you pay for anything, this is what you already have at no cost:
- A visual drag-and-drop builder with a live canvas — you type headings directly onto the slide.
- Six slider types, including image galleries, full-width hero sliders, section sliders and content carousels.
- Draggable heading, text, button and image layers.
- Video slides: MP4, YouTube and Vimeo, plus Reels.
- Elementor template slides — build a layout as an Elementor template, including one from a template kit, and use it as a slide.
- Every animation and every arrow style. There is no locked style set.
- Caption controls, overlay controls and custom classes for your own CSS.
- 30 templates to start from.
I am labouring this because my own shop description got it muddled for a while. If somebody tells you video slides or Elementor slides are the paid feature, they are reading an old page.
What the $29 Pro add-on adds
Noyan Content Slider Pro is an add-on, not a replacement. It installs alongside the free plugin and needs it to run. Nothing you have already built changes, and every free feature keeps working. What it adds is the dynamic engine — the part that turns a slider into a query.
The query, built in dropdowns
You point the slider at any public post type — posts, pages, portfolio items, events, products, whatever custom type your site registers — then narrow it down by taxonomy terms included or excluded, author, a date window, an explicit list of IDs, or an offset that skips the first few, and order by date, title, menu order, comment count, random or ID. Items with no featured image can be skipped, or given one fallback image. Matching content appears on the canvas as you set the dropdowns, with a running count of how many items match before you save — guessing whether a query returns four items or forty is one of the fiddliest parts of doing this by hand.
Terms and products as slides
A taxonomy slider makes each term a slide, using the term’s own image, picking up WooCommerce category images automatically and borrowing the featured image of a term’s newest post where it has none. A product slider can be built from featured products, on-sale products or one product category, ordered by price, sales or rating. Out-of-stock items can be hidden, so the sold-out slide problem disappears rather than being managed, and catalogue-excluded products never appear. Slides carry live prices, sale and sold-out badges and star ratings read from the product, and Add to cart uses WooCommerce’s own AJAX.
Dynamic tags, scheduling and filter chips
Because slides are generated, the text is written once and filled per item: title, excerpt, a formatted date, taxonomy terms, a custom field, the price, and the item’s index out of the total, so “Guide 3 of 12” writes itself. You also choose what the subtitle carries, whether the description uses the excerpt or the start of the content, and what the button says. Slides can be scheduled to show from a date and hide after one, which is how you queue an announcement without being awake for it. Filter chips put a row of taxonomy terms above the slider; a tap re-queries it in place through the same cache and templates.
Caching that clears itself
This is the least glamorous feature and the one I would defend hardest. Query results are cached, and the cache clears itself whenever matching content is published, edited or deleted, or when a product’s price or stock changes. That is what makes the whole idea safe: you can set a long cache window without ever serving a stale slider. A dynamic WordPress slider with a dumb cache is worse than a hand-built one — now it is both out of date and unpredictable.
Pro also records views and clicks per slide over the last 30 days, so “is anybody reaching slide four” gets a number instead of a hunch. Import and export and a countdown widget for section slides come with it.
Free or Pro: the straight comparison
| Capability | Free | Pro add-on ($29) |
|---|---|---|
| Visual builder, live canvas, draggable layers | Yes | Same |
| Six slider types, all animations, all arrows | Yes | Same |
| Video slides, Reels, Elementor template slides | Yes | Same |
| Captions, overlays, custom classes | Yes | Same |
| Templates | 30 | 33 more |
| Slides generated from a WordPress query | No | Yes |
| Taxonomy and WooCommerce product sliders | No | Yes |
| Dynamic tags, per-slide scheduling, filter chips | No | Yes |
| Self-clearing query cache, per-slide insights | Not applicable — no queries to cache | Yes |
Building a dynamic WordPress slider yourself
If you write PHP, none of this is magic, and you should know what you would be buying. The core is a shortcode that runs a WP_Query, loops out slide markup and hands the container to whatever slider library you already load. An afternoon gets a working version. The afternoon is not the cost. These are.
The query is the easy part
For “the six most recent Guides posts, skipping the newest one, only ones with an image”, the arguments are roughly post_type, posts_per_page of 6, offset of 1, a tax_query on the category taxonomy, ignore_sticky_posts, and a meta_query requiring _thumbnail_id to EXIST. Two things to know: the featured-image check is a meta join rather than a free filter, so it is the first thing to check if the query gets heavy, and offset quietly breaks pagination — irrelevant in a slider, relevant the day you reuse the function somewhere paginated.
Cache invalidation is the expensive part
Store the result in a transient keyed on a hash of the query arguments — an md5 of the encoded arguments is the usual shape — then work out how to kill it again. save_post, transition_post_status, deleted_post and the term hooks (created_term, edited_term, delete_term) cover editorial changes. On a shop you also want woocommerce_product_set_stock, woocommerce_variation_set_stock, woocommerce_product_set_stock_status and woocommerce_product_object_updated_props for price edits, plus woocommerce_scheduled_sales for sales that start or end while nobody is logged in.
Then comes the part that catches people. Because the key is a hash, you cannot find your own transients later: delete_transient wants the exact name, and on a site with a persistent object cache your transients are not rows in the options table at all, so the DELETE … WHERE option_name LIKE query everybody reaches for deletes nothing and reports success. Keep an index of the keys you created, or put a version number inside every key and bump it to orphan the lot. Both are the sort of thing you only remember after a slider has shown last month’s posts for a week behind a page cache.
The small stuff that is not small
- Featured image gaps. Decide, in code, whether a post with no image is skipped or gets a fallback.
- Excerpt discipline. Auto-excerpts run to whatever length the content gives them, so slides end up uneven. wp_trim_words gets you a clean word boundary; choosing the right length per slider type is the actual work.
- WooCommerce add to cart. Live prices are easy. A button that really updates the mini-cart means enqueuing Woo’s own add-to-cart script, giving your markup the classes and data attributes its handler looks for, and refreshing the cart through the fragments filter. Stock status, catalogue visibility and sale badges are each a separate check.
- Ownership. It is yours to maintain, including the next time WooCommerce changes a template.
That list is the honest value of the add-on: $29 against an afternoon of building and an open-ended maintenance commitment. If you enjoy that work, do it yourself; the sketch above is enough to start from.
When a hand-built slider is still the right answer
Plenty of the time. A homepage hero carrying three carefully written brand messages should be hand-built, because there is nothing to query — the slides are the content. Same for a landing page of bespoke layouts. There, the free plugin is the whole answer, and a query engine buys you nothing but a settings screen you never open.
A checklist before you put any slider on a page
Independent of which plugin you use, these are the things I check on every build:
- Does the first slide need to be a slider at all? I build on the assumption that slide one is the only slide guaranteed to be seen. If your key message is on slide three, treat it as unpublished.
- Is the first image sized for the space it occupies? The opening slide is usually the largest element the browser has to fetch. Reserve its height in CSS so the page does not jump while it loads; the themes I sell do it for you.
- Does it work without autoplay? Some visitors ask their operating system to reduce motion, and a slider that respects that will not animate for them. No slide should carry information that only appears if the thing moves.
- Can you tab through it? Arrows and pagination need to be operable from the keyboard.
- What does it look like with one item? This is where a dynamic WordPress slider embarrasses you — a filtered query legitimately returns a single result, and the design has to survive that.
- What does it look like on a narrow screen? Not “does it shrink”, but does the text still read and is the tap target still a tap target.
Frequently asked questions
Do I need the free plugin to use Pro?
Yes. Pro is an add-on to the free Noyan Content Slider and installs alongside it, so keep both active.
Can I use a dynamic WordPress slider without WooCommerce?
Yes. The query engine works with any public post type — posts, pages, portfolios, events, custom types — and taxonomy sliders work with any taxonomy. The product options simply do not apply without WooCommerce.
Is a dynamic WordPress slider slower than a hand-built one?
It has to answer a question a static slider does not, which is why the results are cached. What decides whether a slider feels slow, though, is almost never the query. It is the first image: its dimensions, its file format, and whether the browser knows how tall the slide will be before the image arrives. Fix that before you look at database work.
Will a product slider show items that are out of stock?
Only if you want it to. Out-of-stock items can be hidden from the query, and products excluded from the catalogue are never shown. When you do show them, the sold-out badge comes from the product itself rather than from something you typed.
What are the requirements?
WordPress 6.0 or newer, PHP 7.4 or newer, and the free plugin active alongside it. Both are ordinary plugin installs.
Choosing between free and Pro
The line I use is simple. If you wrote the words on the slide on purpose, hand-build it and use the free plugin — no query knows what you meant. If the slide’s content has an author and a publish date, or a price and a stock level, the slider should be asking your site about it rather than repeating what it was told. That is the whole argument for a dynamic WordPress slider, and it is why the add-on exists.
If you are not sure which side of that line your site falls on, describe the page to me and I will tell you straight — get in touch. The answer is often “you do not need to buy anything”, and I would rather say that before you spend $29 than after.
WordPress and WooCommerce developer. 200+ projects delivered for clients in 20+ countries. I write about what things actually cost and what actually breaks.
Get a free quote →Keep reading
WordPressBuild a Taxi Booking Website in 2026 (What It Needs)
If you run cars, whether that is two drivers or twenty, the site you probably have is a brochure with…
Read the post
WordPressHow to Speed Up a WordPress Website in 2026 (What Actually Works)
A practical, ordered guide to what actually speeds up a WordPress website in 2026, from server response time and images…
Read the post
Elementor ProWordPress Website Development in 2026: What the Process Actually Looks Like
How a WordPress website actually gets built - the six stages, what you are responsible for, the mistakes that cost…
Read the post