Galleries are an awesome way to show simple pictures in your posts. In this tutorial we will create a WordPress gallery that will show on the post on which we create it. We will also be able to decide the order of the images in our gallery.

The gallery will be attached to a single post so we will have to create a metabox for each post in the admin area where we will insert the gallery images. Interested? Let’s begin:)

All the code you find here can be used in any of your projects both personal and commercial.

We will make a class to handle our WordPress gallery (saving images, loading images, rendering images) and we will also create a class that could be a factory class which will create all the registered galleries. By doing that, we could have two or more galleries on each post. By using the OOP approach you can extend the initial class for the WordPress Gallery and create different gallery rendering.

Please do be patient since this is a long article and the galleries will work once we create the necessary JavaScript at the end of this article.

If you want to see what we are going to build, you have a video at the bottom of this article. Click here to see it.

WordPress Gallery

First, we will create our class that will handle the creation of the metabox and the rendering of the gallery.

We define our attributes that are used to create the metabox with the function add_meta_box. The attribute $id will be used for more than just create the metabox. We will create it when saving the galleries for meta keys in the database and also for using it within the JavaScript code.

In our constructor method we are assigning passed parameters to our attributes. If the title is empty, we will create it from the ID by capitalizing the first character. We do also check if the passed context and priority values are valid. Only if they are valid we will set them. I they are not valid, they will remain with the default value.

At the end of our constructor method we hook two of our methods to actions (one to add the metabox and one to save the metabox values). Let’s first define our method for adding the metabox:

We are defining possible post types on which our metabox will render. The post types can be easily extended using a general filter for the galleries or using a dynamic filter that can be used to specifically target only one metabox.

If the post type we are editing in the admin area matches the ones that are available to that metabox, we will add the metabox. Here we are using another method called render_meta_box_content. This method is used to display the metabox and all the information inside it. Let’s define that now.

Rendering the metabox

Feels intimidating? No need. I have commented the most important parts so that you can easily understand what each line does. Once we go into JavaScript, you will have a more clearer understanding on this.

Basically, we are generating a hidden WordPress Nonce field so that we can check on that before saving the data to make it more secure. After that we are getting the image IDs we have saved for that gallery. We use PHP function explode to generate an array from the provided string of image IDs. We check if there are any images and if there are, then we create a LI element with the image inside it for every image.

The HTML inside the LI element and the LI element alone are the same as provided in WordPress Media Library Modal. I decided to use that so that I can mimic the same style used in that modal. At the end of this method we render a button that will be used to open the WordPress Media Library so that we can choose between the images.

Saving the WordPress Gallery data

Now that we have our metabox output defined, we can focus on that second method in our constructor method. Remember it? The method name is save:

This is a generic save method since we first check for the nonce. If there is a nonce we verify it, if not we don’t save anything. If there is a nonce, then we are verifying it. If our nonce if verified we do check it is not an autosave and also if the user has the permission to edit the content.

Once everything is true and valid we are getting the posted data from our metabox (look at the hidden input we have set in the method render_meta_box_content – we are using that name). We are also sanitizing the field to remove any harmful data. The last thing, we are saving the metabox data (image IDs) in the post meta by using the dynamic meta key constructed from the metabox ID.

Rendering the WordPress Gallery

The last thing we have to do inside this class is to define a rendering method. This rendering method will be called inside our factory class. The method will receive the parameter $content which will contain the posts’ content and all other filtered content (if any). We will have to add our gallery inside that content and return it.

So to render our gallery we are first checking if the current post, article or any content has the post type that is allowed for our meta box. If that post type is allowed then we are getting the data from the database and create a gallery with the 3 column layout. The classes used here are the same classes WordPress uses when creating galleries. By doing that, we are ensuring that our gallery is somewhat compatible with WordPress galleries so if there is any JavaScript that is creating gallery pop-ups or similar, it will also affect our gallery.

WordPress Gallery Factory

We have our main WordPress gallery class defined. By using a factory we can easily set more than one gallery on a post or similar. We could define several galleries and by using our dynamic filters, we can decide which gallery to show on which post type. This factory will create our galleries and also it will enqueue any script or style that is needed for our galleries.

We will enqueue only admin script and style so that our metabox galleries are render as intended. The front side will be handled by your theme or another plugin such as Jetpack so I will leave you decide how to style your galleries.

As with any class, we first define our attributes:

  • $gallery_defaults – the defaults that can be used when instantiating our galleries
  • $galleries – array with every gallery we want to create
  • $loaded_galleries – array with every instantiated gallery

In our constructor method we hook the method do different actions and one filter. First we hook into the action init to get all the galleries that were added via our filter that we will define in the method collect_galleries. Next step is to enqueue all the scripts and styles that are needed for our galleries to work in the admin area.

After that we hook into the action admin_init so that we are sure that the metabox is created only in the admin area. The only filter into which we hook our method is the filter the_content where we will render galleries.

We are enqueueing our scripts and styles using the URL as if we are using a plugin. If you are using this code in your theme, then you should use the method get_template_directory_uri()Both files will be defined after we create our whole WordPress gallery factory class.

Our method collect_galleries is used to collect all galleries that are added in the filter sortable_wordpress_galleries. We are almost done. Now we need to render those galleries in the admin area and also in the content.

In the method create_galleries we are hooking the method load_galleries to the actions inside the edit screens. These method will be used to instantiate every gallery that was collected. By instantiating our galleries, our metaboxes will be created.

The last part is the part where we render our galleries. We are first making sure that our galleries are loaded. Once that is done, we are going through all the loaded galleries and call their method render and passing the $content to them. Each gallery can have a different class and have a different rendering method so by doing it in this way, we are sure that our galleries will be rendered as intended.

Style for our metaboxes

The style is really minimum since we are using classes that the WordPress Media Uploader modal is using. We just have to define some simple CSS rules to display our images in the metabox correctly. This is our style:

JavaScript functionality

This is the last part of this tutorial. If you have made it this far, I congratulate you already! This is the last piece of code that will connect everything. After this you can view a few of the examples on how to add different galleries. Let’s finish this!

I will separate our script file into several parts so that you could easily understand every bit of the code. First, we will create the function that will be used to open the WordPress Media Uploader and also add images to our input and WordPress gallery metabox.

We are passing two parameters to our function:

  • $imageContainer – gallery container of our metabox
  • $imageInput – the hidden input of our metabox

Here we define a variable file_frame that will hold our WordPress Media Uploader pop-up. Since we do not want the pop-up to get initialized every time we click on the button, we are checking if the variable file_frame is already set. If it is set, then we will open the previously opened WordPress Media Uploader.

If file_frame is not set, then we need to define the WordPress Media Uploader pop-up. We initialize it and allow multiple selection. After that we define a function that will get called once the frame is open. Once it is open, we get the selection object and the image IDs from our hidden input. We are immediately creating an array of the image IDs from the hidden input by splitting the value with each comma (,).

For each image ID we create a WordPress Media attachment and fetch the data for that attachment. The last thing we do is add the attachment to the selection. Now every time the WordPress Media Uploader is open, all our images will be selected so that we do not have to select them all again.

Now that we defined what our file_frame will do when it is opened, we need to define also the function that will get triggered when we select all the images and click the insert button. When we click the insert button this will happen:

  • get all the attachments from our selection
  • create an empty array attachmentIDs that will hold all the selected image IDs
  • delete all the images in our gallery container so that we have an empty container when setting new ones
  • for every selected item that is an image we push its ID to our array attachmentIDs, create an image out of it and append it to our gallery container
  • once we passed through all our selected items, we set the value of our hidden input by joining all the IDs with commas
  • last part is to call the remove function to attach that functionality to newly added images

Once everything has been set we just need to open our WordPress Media pop-up. We have two functions which are used in the above code that have to be defined. We will now define the function sortable_gallery_image_create that is used to create the image out of the attachment object.

In this function we create the output for one image. The HTML here is the same as we did the one in our class Sortable_WordPress_Gallery and method render_meta_box_content. The only difference here is that we populate it from the parameters we pass into this function.

The removal function is attaching the function to every element with the class .remove-sortable-wordpress-gallery-image. When we click on that element we are getting the attributes values:

  • attachment ID from data-id on LI element (parent of our .remove-sortable-wordpress-gallery-image element),
  • gallery ID from data-gallery on the clicked element

We also get the hidden input of our gallery by constructing the ID from the gallery ID and _input suffix. After that we remove our LI that was holding the image and the clicked element, we split the IDs from the hidden input to array and we get the index of the attachment ID in the array. If the index is 0 or higher then we remove it from the array. Once it is removed, we join all the other IDs to a string and set the value back to the hidden input.

Now all our functionality is done. The only part to do is to create a call on the button for adding images.

We are making sure that the document is ready and that all has been already rendered. We get the image buttons by the class .add-sortable-wordpress-gallery and we also call the function to attach the removal functionality of each of the images that are already there. For each of those buttons we get the gallery ID and the hidden input ID. We also get the image container and make the children of that container sortable.  For our ordering to be possible, we need to update the sequence of our IDs in the hidden inputs’ value. This is done by calling a function once the sorting is done.

When the sorting is done, we get all the children elements inside that image container and for each of those elements we get their IDs and push them to an empty array. Once every elements’ ID has been pushed, we join the array elements by commas and set that new value to our hidden input.

Last thing is to create a click trigger on the button to open our WordPress Media pop-up by calling the previously defined function sortable_image_gallery_media.

Now we have our WordPress Gallery done and we can use them as we want.

WordPress Gallery Examples

Here are some of the examples on how to add WordPress Gallery metaboxes.

Only one Gallery

Two Galleries

Show second Gallery only on Page



Galleries can be really useful from time to time. In this tutorial we have learned how to create a simple sortable WordPress gallery that can be easily extended if needed. By using the OOP approach and a dynamic way of assigning values in JavaScript we can have more than one gallery on the same page and yet use the same code.

Have you ever created your own gallery? Do you have some galleries you like or plugins that you use for creating galleries? Share everything in the comments below!

Become a Sponsor

Posted by Igor Benic

Web Developer who mainly uses WordPress for projects. Working on various project through Codeable & Toptal. Author of several ebooks at


  1. Thx again man! Great article!!!!


  2. This is totally awesome! Thank you!


  3. Thank you very much! I spent the last two days trying to make work something like this. I’ll tweet about it ASAP. You have very useful tutorials.


  4. Please help me understand this part:

    add_action( ‘add_meta_boxes’, array( $this, ‘add_meta_box’ ) );

    How does that array() part works?

    I mean, should not it be like:

    add_action( ‘add_meta_boxes’, $this->add_meta_box() );


    1. Hi Kamrul,

      the second parameter of the add_action is expected to be a function. The add_action is using the function call_user_func_array to call the passed function to execute:

      You can look at the first examples to see what is going on here.

      Basically, the $this part is referencing the object with the method. Since this is added inside of the same object with the function, we can pass $this.

      The second parameter is then the method inside of that object which is being called.


  5. Great tutorial! I’ve been looking for a long time a gallery tutorial such as this one.

    I saw that the gallery is displayed in the front end just after the main content. I would like to choose where to display the gallery in my PHP post template. How could I achieve it?

    Thanks a lot!


    1. This code is for the gallery metaboxes on the back end. You can use a similar logic to render the gallery used here, to load it on the front.


      1. Mathieu Préaud June 10, 2020 at 10:29 am

        Thanks Igor for the reply. I’m not an expert in PHP but I understand that to retrieve the gallery in the front end outside of the_content() we need to create a new function, right?. Is there any chance you can help with this? Thanks a lot!


  6. Awesome tutorial!

    If for example the metaboxes are only displayed on pages, how could we filter to display them in admin on a specific page template (like page-template.php)?

    Thanks a lot.


Leave a reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.