The event went well, the photographer delivered, and now you have an email sitting in your inbox with a link to Google Drive. Inside are hundreds of images with names like IMG_5002, and your client wants them turned into a gallery on their website.
The most tempting option here is to just link that Drive folder straight to the gallery and you never have to download a thing. It's an understandable shortcut but usually creates more issues in the long run than it solves.
In this post we'll look at why cloud storage makes for a poor source for a website gallery and what to use instead. We'll also explain why the bigger issue is often the number of photos the client wants to show in the first place.
The Office Hours question
This discussion came up during our October 1, 2026, Office Hours livestream, when a viewer asked for advice on how to handle the situation we described above. Here's what she said:
The client has 300 images from the latest event in a Google Drive folder. Is there an easy way to create a gallery on their website that just links up to Google Drive, where I don't have to download all images and build a gallery?
In the chat she also added that the 300 photos came from 30 different events, all in the same folder, and the client wanted them in one giant gallery.
Nathan Ingram, the agency trainer at hosting.com, covered both halves of the problem:
The technical one: Can you, and should you, pull images from Drive?
The practical one: What do you do with 300 photos?
Let's go through his answers one by one and take a closer look.
Why is cloud storage a bad source for a website gallery?
With so many WordPress plugins out there, there's probably a way to use cloud storage to serve up a gallery. The better question, as Nathan put it, is whether you want to. Services like Google Drive, Dropbox, and OneDrive are excellent at storing files, but they aren’t designed to serve them to website visitors.
As Nathan explained it:
Given that images are often one of the biggest issues for site speed, I don't know that I want to pull from Google Drive, because it's not built for performance. It's built for storage.
That difference between storing and serving images shows up in a few ways.
What happens to page speed?
When a gallery pulls the original images straight from a storage folder, every visitor sees or downloads the files directly as the camera produced them: no resizing or compression.
Event photos from a modern camera or phone can easily be several megabytes each, and Nathan pointed out that some might be as large as 20 MB JPEGs. He explained that's a recipe for disaster when trying to load 50 of them into a gallery, let alone 300.
A gallery page built like that will be slow on a fast connection and close to unusable on mobile data. That hurts both the visitor experience and the client's search performance.
Images aren't resized and compressed
When you upload an image to WordPress, it automatically creates several smaller versions. That way, a gallery grid can load small thumbnails, and the full-size image only loads when someone opens it.
On top of that, optimization plugins can compress those files and convert them into modern formats like WebP and AVIF.
None of that happens when images live in someone's cloud storage folder. WordPress and your optimization plugins never see those images, so you don't get the smaller files, the compression, or the modern formats.
As Nathan put it, a good web gallery needs image sizing and compression to make the images web ready.
What else can go wrong?
Speed isn’t the only thing that suffers when your gallery depends on someone else’s storage folder.
This setup is inherently fragile. If someone changes the sharing settings, moves the folder, deletes a file, or leaves the organization and takes their files with them, images on the live site will likely break.
The worst part is that visitors are usually the ones who end up noticing first, and often they don't even report the broken images. The site fails to show off the client's best moments, and it quietly undermines the user experience.
Here's what to do instead
The fix is to bring the images into WordPress. There, they can be resized, compressed, converted, and served properly. Yes, it does mean you'll have to download the folder once, but that step makes everything else possible.
Here's what a solid setup looks like:
Upload the images to the WordPress Media Library, so the CMS can generate its smaller image sizes for thumbnails and grids.
Run them through an image optimization plugin to compress the files and convert them into a modern format (WebP or AVIF).
Display them with the WordPress Gallery block or a dedicated gallery plugin, depending on how much control you need over layout, lightboxes, and filtering.
Lazy-load images below the fold, so visitors only load photos as they scroll toward them.
With this setup, the gallery page loads quickly, and visitors can still click through to a larger version of any photo they want to see in detail.
And if you want more details, our guide to optimizing images for your website covers formats, compression settings, responsive sizing, and lazy loading.
Nathan also dedicated a full livestream to the image problem in WordPress, including how to control the extra image sizes the CMS creates and when lossy or lossless compression makes sense.
How many photos does a gallery really need?
Even with perfect optimization, there's still the question of what to do with 300 photos from 30 events.
This is where Nathan suggested stepping back from the technical question entirely. He said that visitors are simply not going to sit there and flip through 300 images. A gallery is there to show visitors the best of what happened, not to archive everything.
Getting to that point takes a conversation with the client and a plan for organizing the photos.
How to have that conversation with the client
Nathan's advice is to start with a simple call. Open with genuine appreciation for the work that went into the photos, and then shift the focus to the people who will use the gallery:
Let's talk about how a human is going to want to view these pictures. Most people are only going to view 8 or 10 of these and they're going to move on. And so, you want to suggest to them what kind of taxonomy do we need to put around these images to make this pile of photos actually accessible to people? What do people actually want to see here?
From there you can steer the conversation toward what visitors want to see, rather than what the client wants to include. A few points like these will help make your case:
A smaller, curated gallery loads faster and looks more polished.
Visitors are more likely to engage with a dozen strong photos than scroll past hundreds of similar ones.
The full set of photos can still live somewhere for people who were there and want every shot, such as a downloadable archive or a private share link.
Framed this way, curation becomes a service you're providing, not a limitation you're trying to impose.
How to organize the photos
Organizing the photos will vary from website to website and client to client, but the overarching method is similar.
Once the client agrees to curate and not put all the photos up at once, the next step is structure. For a multi-event collection, like our viewer's, Nathan suggesting picking a handful of the best images from each event.
You can then break the collection down even further into a separate gallery for each event, or one gallery page with filters for each event. Furthermore, you can group images by scene within each event gallery. It all makes it easier for visitors to browse the images they are looking for.
Using AI to do the sorting
Of course, curating 300 unnamed photos by hand is exactly what it sounds like: tedious, which is why the Google Drive shortcut from earlier is so tempting.
Fortunately, this is exactly the kind of task AI handles well, and it’s where Nathan’s agency now relies on it. He walked through the process he uses:
Download the whole folder to your computer. Check with the client first that all the photos are in, so you're not working from an incomplete set.
Point your AI tool at the folder and ask it to rename the images with descriptive names. That also helps with SEO and accessibility.
Ask it to sort the images into folders that make sense. Tell it you're building a gallery (or a series of galleries) for an event page. Give it hints if you can, such as which photos are from the dinner and which are of the speaker.
Ask it to select the best images from each group. For example, ask for the best 12 dinner photos to go into the WordPress gallery.
And this isn't a hypothetical workflow. Nathan said it's now standard practice at his agency:
When the client gives us a Google Drive full of media, Claude goes through and organizes it and figures out which of the best images to use and makes those suggestions. And it's usually right. We have to correct sometimes, but that's just part of our process now, and it works brilliantly.
Naturally, a human still makes the final call, but the AI does the grunt work in minutes instead of hours.
Build the gallery visitors want to see
While linking a website gallery to a cloud storage folder feels like it saves time, it hands visitors full-size images, leaves you with no way to optimize them, and depends on a folder you don’t control.
Bringing the images into WordPress, optimizing them, and curating them down to the best shots gives the client a faster, more polished gallery that people are more likely to look through.
So, the next time a client sends you a folder with hundreds of photos, treat it as the start of a conversation rather than a technical puzzle. And if you'd like more practical advice like this on anything related to agency work, WordPress, hosting, or AI, join Nathan live for Office Hours, every Thursday at 2 p.m. ET.
FAQ
Should I resize images before uploading them to WordPress?
It helps, but it isn’t essential. Since version 5.3, WordPress automatically scales down very large uploads (anything over 2,560 pixels wide or tall) and keeps the original file as a backup.
Resizing first still saves upload time and server storage, which adds up with hundreds of event photos. Your optimization plugin can handle compression from there.
Will uploading hundreds of photos slow down my WordPress site?
Not on their own. Images sitting in the Media Library don’t affect page speed.
What matters is how many images a page loads and how large they are. Disk space is the bigger consideration, since WordPress stores several sizes of every image, so check that the hosting plan has room before uploading a large archive.
Can I embed a shared Google Photos or Dropbox album instead?
An embedded album is more reliable than pulling individual files, but it has many of the same drawbacks.
The images still load from a third-party service you can’t optimize, and you’re limited to the layout and styling that service offers. The photos also aren’t part of the client’s site, so they won’t help it show up in image search.
If the album is meant as a full archive for attendees, link to it from the gallery page instead of embedding it.
Do we need permission to publish event photos on the website?
It’s worth checking two things before anything goes live.
First, confirm the client has the rights to use the photos online, since the photographer usually holds the copyright and their contract sets how the images can be used.
Second, consider the people in the photos, especially if children are included or attendees were told photos wouldn’t be shared publicly, because privacy rules like GDPR can apply. You can raise this during the curation conversation.