Choosing a WordPress Gallery Plugin
Core already groups images and opens them in a lightbox. A gallery plugin earns its place through layout, albums and performance, and the last one is where most of them fail.
Check what core does first. The Gallery block arranges attachments in a responsive grid, and since WordPress 6.4 the Image block offers an expand-on-click lightbox that works for images inside a gallery. For a portfolio page of a dozen photographs, that is the whole job. A plugin is worth installing when you need a layout, an organisational level or a behaviour that core does not have.
What a plugin actually adds
| Capability | In core? | Notes |
|---|---|---|
| Column grid | Yes | Responsive, no plugin needed |
| Lightbox | Yes, basic | No captions panel, no thumbnails strip, no slideshow |
| Masonry and justified layouts | No | The most common genuine reason to install one |
| Albums, or galleries of galleries | No | Matters as soon as you have more than a few sets |
| Filtering and sorting by tag | No | Useful for large portfolios |
| Mixed image and video | No | Check how video is embedded and what it costs |
| Watermarks and right-click blocking | No | Deterrent only, never protection |
| EXIF display | No | Photography sites ask for this constantly |
| Selling prints or downloads | No | This is an ecommerce job, not a gallery job |
Be honest about which rows you need. Installing a gallery suite for a column grid adds a stylesheet, a script and a settings screen to solve a problem core already solved.
Performance is the real criterion
This is where gallery plugins separate, and where the demos never help you, because a demo has ten optimised images and your site has three hundred holiday photographs straight from a phone.
Four things to check on a real gallery page:
- Which file is served for a thumbnail. The plugin should request a generated size, not the original scaled down in the browser. Load the page, open the network panel, and look at the actual bytes. A 4 000-pixel original rendered at 300 pixels is the single biggest cause of slow gallery pages, and the mechanics are in optimising images in WordPress.
- How many image sizes it registers. Some plugins add four or five of their own on top of core's. Every size multiplies your uploads directory, and the cost is paid on every future upload.
- Whether lazy loading survives. Plugins that build galleries with their own markup sometimes strip the loading attribute, so all thirty images download immediately.
- Whether it reserves space. Thumbnails without width and height push the page around as they load, which is the layout shift problem covered in fixing cumulative layout shift.
A gallery plugin that fails all four turns a fast site into a slow one on exactly the pages you most want people to browse, and no amount of caching fixes weight. The wider picture is in how to speed up a WordPress site.
Storage decides whether you can leave
Gallery plugins store their work in one of three ways, and the difference only becomes visible when you want to change plugin.
As core attachments referenced by a block. The gallery is a block in the post content pointing at media library IDs. Best case: remove the plugin and you still have images, captions and a list, just without the fancy layout.
As a plugin post type. Each gallery is a post, inserted into pages by shortcode or block. Removing the plugin leaves the galleries in the database and the shortcode visible as text on the page. Recoverable with work.
In the plugin's own tables. Fast queries, complete lock-in. Nothing else knows those tables exist, so migration means a bespoke export, and most backup and staging tools will carry the rows without understanding them.
None of these is wrong, but ask which one applies before you build two hundred galleries in it. The related question is where the files themselves live: a plugin that keeps images inside the media library leaves you with a normal WordPress site, while one that manages its own upload folders does not.
Accessibility, which nobody checks
Galleries are unusually easy to get wrong here, and it is worth thirty seconds of testing:
- Alt text must come through from the media library into the rendered markup. Some plugins drop it.
- The lightbox must be keyboard operable. Tab to an image, press Enter, then navigate and close with the keyboard alone. A lightbox you cannot escape without a mouse is a real barrier.
- Focus must return to the thumbnail you opened, not to the top of the page.
- Captions should be text, not baked into the image.
Matching the plugin to the site
- A dozen photos on an about page. Core Gallery block. Nothing else.
- A photographer's portfolio. Justified or masonry layout, albums, EXIF, and a lightbox with a thumbnail strip. Pair it with a theme built for images, as in WordPress photography themes.
- An event or venue archive. Albums and filtering matter more than layout polish, because the volume grows every month.
- A shop showing product photography. Use the product gallery your ecommerce plugin provides rather than layering a second gallery system over it.
- Selling images. You need an ecommerce plugin with digital downloads. A gallery plugin with a shopping bolt-on is usually weaker at both halves.
Install onto a page you can throw away first, per how to install a WordPress plugin, and build a gallery with thirty real images before deciding.
Common mistakes
- Uploading originals. Resize before upload. No plugin setting compensates for a hundred phone photographs at full resolution, and oversized files also produce the softness described in fixing blurry images.
- Running two gallery plugins. Two stylesheets, two lightbox scripts, and a fight over which one captures the click.
- Relying on right-click blocking. The image is already in the visitor's browser. Watermark if it matters.
- Judging the plugin on the demo. Test with your own worst-case set.
- Putting a hundred images on one page. Paginate the gallery, or split it into albums.
- Removing the plugin without checking the pages. Shortcode debris and empty containers stay behind, so audit before uninstalling, per deleting a WordPress plugin completely.
Verify
Build one gallery of about thirty full-size photographs on a draft page. Load it logged out on a phone-sized viewport and note the total transferred weight and the largest single file. Confirm thumbnails are served as generated sizes rather than originals. Open the lightbox with the keyboard, navigate, close it, and check focus returned. Then view source and confirm the alt text you entered is present in the markup.
Frequently asked
- Not for a simple grid. The core Gallery block arranges images in columns and the Image block offers an expand-on-click lightbox. Plugins are for justified and masonry layouts, albums, filtering and sales.
- Almost always full-size originals loaded as thumbnails. A grid of thirty images at three megabytes each is ninety megabytes, whatever the plugin. Check the actual file served, not the displayed dimensions.
- It depends on storage. Galleries saved as blocks or as core attachment groups survive as plain images. Galleries stored in the plugin's own tables and inserted by shortcode leave empty brackets on the page.