A WordPress block plugin

A proper slider block.

GlidePress puts a Swiper-powered slider in the block editor and then stays out of the way. No admin screens, no options table, and no assets on pages that don’t use it.

WordPress 6.5+ · PHP 7.4+ · Swiper 12 · GPL-2.0

See it in action or read the details ↓

01 — Content Put any blocks inside a slide
02 — Responsive Separate mobile, tablet and desktop settings
03 — Accessible Keyboard and screen-reader ready
04 — Lightweight Loads only where a slider exists

Live, not a video — this page runs the same Swiper 12 bundle the plugin ships.

Four effects, one dropdown

Transitions are picked per slider in the block sidebar. Each demo below is interactive — drag it, click the arrows, or focus it and use the arrow keys.

SlideOne
SlideTwo
SlideThree
Slide. The default, and the only effect that supports several slides per view.
FadeOne
FadeTwo
FadeThree
Fade. A cross-fade. The sensible choice for hero banners.
FlipOne
FlipTwo
FlipThree
Flip. A 3D card flip. Use sparingly.
CreativeOne
CreativeTwo
CreativeThree
Creative. Layered depth-and-slide. The fancy one.

The boring parts, handled

Responsive tiers
Slides per view and spacing are set separately for mobile, tablet and desktop. The breakpoints are fixed at 768 px and 1024 px, so your theme can rely on them.
Accessibility
Keyboard navigation and screen-reader announcements come from Swiper’s A11y module. Inactive slides are made inert, which keeps their links out of the tab order instead of merely hiding them.
Autoplay that behaves
Optional looping autoplay pauses on hover and stands down entirely for anyone with prefers-reduced-motion set. That includes the demos on this page.
Styling controls
Arrow and pagination colours, sizes and radii, equal-height slides, and an overflow “peek” mode that shows a sliver of the neighbouring slides.
Nothing loads for nothing
These are static blocks — no server-side rendering, no database options, no settings screen. Scripts and styles are enqueued only on pages that actually contain a slider.
Suspicious by default
The slider’s configuration lives in post content, so the frontend treats it as untrusted: options are rebuilt from an allowlist rather than handed to Swiper as parsed JSON.

It lives in the block editor

Two blocks: GlidePress Slider and GlidePress Slide. A slide takes whatever blocks you put in it — images, headings, buttons, columns — and everything is configured from the sidebar you already know. There is no settings page to go looking for, because there is no settings page.

  • Live preview while you edit
  • Wide and full alignment support
  • Any inner blocks inside a slide

Check the accessibility yourself

Press Tab until the slider below has focus, then use and . Slide changes are announced to screen readers. This isn’t special demo behaviour — every GlidePress slider works this way.

Try itFocus me, then press →
KeyboardThat was the keyboard module
Screen readersAnd this change was announced

Also: pagination is never hidden from assistive technology while it contains focusable buttons, and a slider saved without an ARIA label falls back to a localised default rather than nothing.