Thanks! Please check the following:
Please read carefully! All purchases are final. Refunds will not be provided under any circumstances.

System requirements
License agreement
Refund policy
Purchase process
Customer support

System requirements
All the stacks sold through this website require RapidWeaver and the Stacks plugin. They will not install or work with any other publishing platforms (like Flow, Drupal, Blocs or Wordpress).

We recommend you aim towards installing the latest version of RapidWeaver that your computer is capable of running (preferably RapidWeaver 7 or greater) and Stacks 3 or later. Both are a separate purchase if you do not own them already.

Stacks4Stacks generously provides you fully-functioning free demo versions of everything sold on this website. This enables you to fully test addons before committing to a purchase. There are no time or functionality limitations applied.

If you cannot get the free demo version to work, DO NOT proceed with purchasing the stack - because the purchased stack is unlikely to work any better for you. Please request technical assistance first.

License agreement

You may use a purchased stack an unlimited number of times in personal or commercial projects and request technical support.

We permit you to install stacks onto all computers that you own. You are permitted to make private archival backup copies (e.g. iCloud, Disk Blaze, Google Drive or Dropbox).

You may not resell, redistribute or make a stack available for download, remove copyright credits, license information, or claim the stack to be your own creation. This includes free stacks, demo stacks or paid stacks, in modified or unmodified states.

The software is provided "as is" without any implied or expressed warranty of merchantability or fitness for purpose. In no event shall the authors or copyright holders be liable for any claim, damages or other liability, whether in an action of contract, tort or otherwise arising from, out of or in connection with the software or the use or other dealings in the software.

Refund policy
By purchasing from this website, you agree that your purchase will be available immediately via digital download and that you waive your statutory right of withdrawal.

All purchases are final. Refunds cannot be provided (we physically cannot un-download or remove stacks from your computer) under any circumstances.

You are reminded to make use of the free demo versions already provided on the website, to fully evaluate stacks for compatibility and suitability before making a purchase.

If you cannot get the free demo version to work, DO NOT proceed with purchasing the stack - because the purchased stack is unlikely to work any better for you. Please request technical assistance first.

Be certain that the stack you are buying is actually the one you want, and that you don't already own it or are confusing it with another stack of similar name or functionality.

Purchase process
The checkout system is provided by Paddle. An attempt is made to display prices in your local currency, with relevant taxes applied.

To complete your order, you must supply a valid email address. Your purchase receipt and download link will be sent to this address you supply. If you do not receive your purchase shortly after completing it, please carefully check your spam or junk mail folders.

Your purchases are available to re-download at anytime, via this secure order lookup page.

Prices shown on the website include any applicable VAT or sales tax. You will be sent a full receipt by email. Charitable and bulk discounts may be available on request. Please get in touch if you have any queries about our pricing.

Our order process is conducted by our online reseller is the Merchant of Record for all our orders. Paddle provides all customer service inquiries relating to order processing. Paddle also provides an order lookup system, commonly referred to as your Paddle Account.

Customer support
If you have questions that relate specifically to a stack, you should make contact via the contact page.

General questions can be asked on the RapidWeaver Community Forums.
Recently updated to version 2, ProGallery continues to be one of the most popular stacks we sell from this website. Thousands of RapidWeaver users love the speed of ProGallery, the reliability of generated galleries, the ease and flexibility of setup, and the 'clutter-free' ethos towards media presentation. After all, it is your image and video content that demands maximum emphasis.

"Other gallery stacks have disappointed me. I've tried many and keep coming back to ProGallery. I love the simplicity. It just gets the job done. You have created exactly what I need and cannot give this stack enough praise. ProGallery has helped me win several photography contracts purely on the basis of my clients being able to see my work properly. For this I cannot thank you enough!" - Mike

"Still the best gallery plugin there is for RW. And Wills support is fab!!" - Emma

ProGallery is particularly well-suited towards the handling of larger image and video galleries. Built-in lazy-loading ensures that thumbnail images are only downloaded and displayed when within the viewable area of a webpage. Additionally when the lightbox is opened, images only get displayed on demand. The outcome of these techniques ensures you can have a high-quality gallery of several hundred megabytes or more in size (as demonstrated below) but website users will still be able to quickly and safely access your gallery.

The responsive lightbox used in ProGallery supports both images and video; so think of it as two stacks for the price of one! Different sources can be configured to collect images or video for display within ProGallery. Our lightbox is purposefully kept visually uncluttered for more emphasis on your media. Captions and navigation controls are never layered over your lightbox images - a major flaw in some competing stacks.


This is a real working example of ProGallery, with the default settings applied. A total of 107 images are being loaded via a CSV file. The image formats are as follows...

JPG, 72 dpi, 500px wide, 333px tall, approximately 60 KB each.

Lightbox images:
JPG, 72 dpi, 1500px wide, 999px tall, approximately 500 KB each.

Retina lightbox images:
JPG, 72 dpi, 3000px wide, 1997px tall, approximately 1.6 MB each.

We have purposefully opted to use quite sizeable images, in order to exaggerate the lazy-loading effect and to demonstrate the retina display optimisations. Ordinarily retina images are optional and you will probably want to use smaller image file sizes to maintain decent loading speed for your end users on slower internet connections.


    CSV File "" Not Found.

    You might be trying to preview this page in RapidWeaver, but the CSV file to your gallery could not be located. This could simply be because the CSV file is on your web server, and RapidWeaver is unable to access it currently. You could try adding the CSV file as a resource in the RapidWeaver sidebar and then link to that instead. This will then let you test and view the gallery in RapidWeaver preview.

    Alternatively if you are seeing this error on your live (published) webpage, then the relative path you have specified to the CSV file is incorrect or the CSV file is not presented in a format that ProGallery understands. Please refer back to your documentation for complete setup instructions and examples of CSV files.

You may download the original CSV file here to see how the spreadsheet is structured and use this as a basis for your own ProGallery configuration. Right-click and select 'save as' if the file does not download for you straight away. Don't worry if the idea of CSV files sounds too complicated - you can also setup ProGallery to use images you drag-n-drop into RapidWeaver too! Continue reading for more information about the different sources available in ProGallery.


Follow these instructions for getting ProGallery setup in your website
  1. Once installed into Stacks, open your stack library and drag-and-drop a copy of the ProGallery stack into your webpage
  2. Click on the blue '+' button to add sub-stacks to your main ProGallery stack. You can choose to add singular images or video, provide the path to a directory of suitable images or link to a CSV file containing your gallery data
  3. Carefully follow any instructions shown in edit mode for configuring your gallery sources
  4. When you select the main ProGallery stack in edit mode, you can access all the style and behaviour settings for the thumbnail grid and the lightbox gallery
  5. Publish the website when done

You can safely use multiple ProGallery stacks on the same page, providing that each has a unique ID applied in the settings. The gallery ID must start with an uppercase or lowercase letter. The ID can contain numbers, hyphens or underscores, after the first character. The ID must not contain spaces, punctuation marks or other special characters. Simple is best.

Some gallery sources like 'directory of images' and 'CSV file' require that the page extension is changed to .php in the RapidWeaver page inspector. PHP is server-side code and the .php extension tells the web server that the page contains PHP code that requires processing as the page is served. Therefore any pages previously published with a .html extension to the same directory require deletion from the server, to prevent conflicts.

The 'directory of images' source is good to use for reusing images uploaded via a content management system or one of our free stacks like Droplet or FileMan. ProGallery is able to look for thumbnail and retina-optimised versions of your images. Image file names will get reused as the image titles. We are unable to provide free support for third-party file uploader or CMS stacks.

Instagram have recently announced that they are closing their API earlier than originally proposed. Access to read a basic profile / media will be blocked in early 2020. Instagram cite security as a reason, although we are aware that their effort to increase monetisation of the platform and collect more user data are other factors. It is likely this change will prevent ProGallery being able to fetch content from Instagram. Obviously other image sources in ProGallery are completely unaffected by this change - this only effects galleries which pull-in images from Instagram.

Relative paths for CSV files and directories

If you have configured ProGallery to use images or video from a CSV spreadsheet file or an image directory, it is important that the CSV file or content is stored on the same domain (e.g. and you link to the file using relative links. Relative links offer improved security and much faster retrieval of the data. Our published example above is using a CSV file stored on the Stacks4Stacks server, to build the image gallery you see. This current page you are reading now is stored in the /progallery/ directory. Our CSV file is stored over in the /resources/ directory. This is what it looks like in FTP:

So in the stack settings we entered ../resources/imagedata.csv as the link to the CSV file. The CSV file can have links to images stored anywhere, including on other domains. It's just the CSV file that has to live on the same domain as the website.

With relative links, a web browser tracks backwards from the location of the present page (e.g. You use ../ to determine how many levels the ProGallery page is from the root domain. Then navigate down into the /resources/ directory, where it will find our imagedata.csv file. And sure enough, if you go to in your web browser address bar, you will reach the same CSV file.

Again, relative paths are very fast and safe. Trying to access CSV files on other domains will often fail and some hosting companies will block it (as a security measure). There are many more explantations and tutorials online about relative links.

In summary, a relative link tells a web browser what the shortest route is to a file, from the current page. You use ../ to navigate out of directories (back to the website root), and then name the directories (e.g. /resources/2016/gallery/ to navigate down into directories. If the CSV file is within the same directory as the page is stored, just enter the filename as the link. For CSV files added as resources to RapidWeaver, no further action is required.

Custom triggers for light boxes

Perhaps you want to send clients links by email, that will take them directly to your website and launch a particular image or video automatically? Or how about the option to create custom buttons in your webpage to start the lightbox gallery? Both are feasible to do with ProGallery.

For linking to an individual image or video from an outside location (like an email, social media or another webpage), simply append a hash (#) character onto the webpage link, followed by your gallery ID, followed by the number of the item you want triggered on page load:

To create a custom link or button on the same page ProGallery is on, for triggering a lightbox, follow this markup pattern:

<a href="#mygallery1" class="proGalleryTrigger">Click Me!</a>

If you were configuring the link using the link dialogue window in RapidWeaver, then you would set the URL to #mygallery1 and add a custom class attribute with a value of proGalleryTrigger, as pictured below.

ProGallery custom lightbox trigger

NB: We use the 'proGalleryTrigger' class to scope our link or button better. It is a much more efficient method, it allows us to nullify normal link behaviour and it will stop confits with other stacks on the same page. Without this class, the trigger will not work for opening the ProGallery lightbox.

As before, replace 'mygallery' with your actual Gallery ID (configured in the ProGallery general Settings) and the number corresponds with the item number you want to open.

Lazy Loading

The option is provided in each image source to lazy-load thumbnail images. When enabled, each thumbnail will be rendered as a transparent GIF image (of a very small file size). When the gallery item is within the viewable area of the browser window, this tiny GIF image is dynamically replaced with the regular thumbnail image. Lazy Loading is good to use for very large uniform grid galleries, because it will greatly reduce the amount of images that initially load. However lazy loading is less suitable for masonry layouts, as the reflow of images can cause the ordering to frequently change. Likewise some social media sharing services (like Pinterest) may not be able to 'see' thumbnail images that are being lazy loaded. Generally we recommend lazy loading is only used if you are using a uniform grid gallery and you're finding your webpage takes an extended period of time to load.

Download and Pinterest sharing buttons

Added in ProGallery 2.2, you can enable the display of a simple download button and / or Pinterest sharing button. These buttons receive minimal styling and are positioned at the top left of the lightbox window. When the download button is clicked, the current (full-size) lightbox image will be downloaded to a users computer, in supported web browsers. Likewise when the Pinterest button is clicked, the current lightbox image link, webpage link and image description are passed over to the Pinterest website for sharing. Both download and Pinterest buttons should only be enabled for image galleries - neither of these buttons work for video; because embedded video (within the lightbox) is using iFrames, therefore the video source is not available. Download buttons only work for images hosted on the same domain, that your ProGallery stack is published to.