Adding a gallery to a WordPress page takes about thirty seconds. Adding one that is fast, accessible, looks right on a phone, and will not quietly drag down your Core Web Vitals takes a few more decisions — and those decisions have changed since the advice you will find in most older tutorials. This is the 2026 version: the methods, and the right-way checklist that turns a quick gallery into a good one. The thirty-second part is easy; the decisions around it are what this covers.
It pulls together threads from across our galleries cluster into one practical walkthrough. The deeper questions — which method, which layout, which plugin — link out as we go.
The decision before you start
Before adding anything, decide which of three methods fits, because that choice shapes everything after. Use the native Gallery block for a small, static gallery in a post you will not reuse. Use a dedicated gallery plugin when you need layouts, a good lightbox, filtering, reuse, or performance control. Use a page-builder widget when you are building the page in Elementor/Divi/Bricks and the gallery is simple. We cover the trade-offs in native block vs plugin and gallery vs page-builder. Pick the method that matches your gallery’s job; the rest of this guide applies whichever you choose.
Method 1: the native Gallery block
- In the block editor, add a Gallery block (the + button, search “Gallery”).
- Upload or select your images; drag to reorder.
- Set the number of columns and choose whether to crop to uniform size or keep proportions.
- Set link behaviour (to media file enables a basic lightbox in many themes).
- Add alt text to each image in the block sidebar — do not skip this.
Fine for a few photos in a post; you hit its ceiling (no reuse, basic lightbox, limited layouts) as soon as you want more.
Method 2: a gallery plugin
- Install and activate your chosen gallery plugin.
- Create a gallery in the plugin (upload images, set captions and alt text, choose a layout).
- Insert it into your page via the plugin’s block or shortcode.
- Configure the layout, lightbox, and any filtering or protection you need.
- Reuse the same gallery on other pages by inserting it again — no rebuild.
This is the path when the gallery is a managed thing rather than a one-off. The reuse point is the quiet advantage — build once, place anywhere.
Method 3: a page-builder widget
In Elementor, Divi, or Bricks, drag the gallery widget onto the page, select your images, and style it with the builder’s controls. Fast and integrated for a simple gallery within a page you are already building — but watch the documented Elementor full-size-thumbnail issue (check image sizes in the Network tab) and the general widget limits covered in the page-builder comparison.
The 2026 right-way checklist
Whichever method you used, these are what separate a quick gallery from a good one — and the items that have changed from older advice:
- Alt text on every meaningful image — for accessibility and image SEO (see alt text that ranks).
- Don’t lazy-load the first row — the reversal from old “lazy-load everything” advice; the first row is often above the fold and contains your LCP image.
- Modern formats (WebP/AVIF) — serve them with fallbacks for the ~30% weight saving.
- Responsive sizes — so phones get phone-sized images, not the desktop master.
- The right layout for your images — grid, masonry, or justified per the layout guide.
- An accessible lightbox — keyboard, focus, screen reader (see the accessibility checklist).
Do this now. Add your gallery by the method that fits, then run the checklist on it before you move on: alt text present, first row not lazy-loaded, modern formats serving, responsive sizes, a layout that suits your images, an accessible lightbox. Spending five minutes on the checklist is the difference between a gallery that helps your page and one that quietly hurts its speed and rankings. The thirty-second version skips all six; the right-way version does not.
Choosing a layout and going mobile
Two of the checklist items deserve a sentence more. The layout should follow your images — consistent shapes suit a grid, mixed orientations suit justified, volume suits masonry. And everything should be verified on a phone, because most visitors are on one and a gallery that looks right on desktop can be slow or awkward on mobile (the mobile performance guide covers this). These are not afterthoughts to the “add a gallery” task; they are part of doing it right in 2026.
Common mistakes
- Uploading full-resolution camera files and displaying them small — wasted weight.
- Lazy-loading the whole gallery including the first row — the LCP killer.
- Skipping alt text — invisible to search and screen readers.
- Forcing mixed-orientation images into a cropping grid — losing compositions.
The reassuring part is that a good gallery plugin handles most of the checklist by default — responsive sizes, correct lazy-loading, modern formats, an accessible lightbox, the layouts — so “the right way in 2026” becomes the out-of-the-box way rather than six things to remember per gallery. FotoGrids covers those fundamentals in its free tier (six layouts, the immersive lightbox, responsive images, lazy-loading), and if you are moving galleries over from another plugin, its free migration assistant imports them from NextGEN, Envira, Modula, and FooGallery so you do not rebuild by hand.
Key takeaways
- Three methods: native block (simple), plugin (managed), page-builder widget (simple, in-builder).
- The right-way checklist: alt text, don’t lazy-load the first row, modern formats, responsive sizes, right layout, accessible lightbox.
- The “don’t lazy-load the first row” rule is the key change from older tutorials.
- A good plugin makes the right way the default rather than six things to remember.
What is the easiest way to add a gallery to WordPress?
The native Gallery block in the editor — add the block, upload images, set columns, done. It is ideal for a small, static gallery in a post. For anything you will reuse, want a good lightbox for, or need advanced layouts or filtering on, a dedicated gallery plugin is the better path.
What is the right way to add a gallery in 2026?
Beyond just placing it: add alt text to every image, do NOT lazy-load the first row (it often holds your LCP image), serve modern formats (WebP/AVIF) with responsive sizes, choose a layout that suits your images, and use an accessible lightbox. These few decisions separate a gallery that helps your page from one that quietly hurts its speed and rankings.
Should I use the native block or a plugin to add a gallery?
Use the native block for a small, static gallery in a single post. Use a plugin when the gallery is something you manage — when you need advanced layouts, a good or accessible lightbox, filtering, reuse across pages, proofing, or performance control. A good plugin also works inside the block editor, so the upgrade is a block swap.