How to Add a Photo Gallery to Your School Website (2026): Events, Consent and Parents
A practical guide for school offices and communications leads: what to show on a public school website and what to keep private, consent and opt-outs, a Google Drive folder structure staff can keep up, step-by-step embedding, and sharing event photos with parents.

Short answer
Decide first what belongs on the public website (the school, displays, wide event shots with consent) and what goes to parents as a private link. Keep website-ready photos in a checked Google Drive folder per term, turn it into a gallery, and embed it on your site; it updates as checked photos are added.
Parents love seeing what happens at school: the sports day, the winter concert, the science fair, the trip. Most schools already have the photos, usually in a shared Google Drive folder that staff add to through the year. Getting them onto the school website is where it goes wrong: someone resizes and uploads each photo by hand, the page goes out of date by half-term, and nobody is quite sure which pupils' parents said no to photos online.
This guide is for school office staff, communications leads and anyone who runs a school website. It covers what to put on a public page and what to keep private, consent and opt-outs, a folder structure that staff can keep up, step-by-step setup from Google Drive, and notes for common school website platforms.
- Public page or private link? Decide first
- Consent, opt-outs and safeguarding
- What to show on a school website
- A folder structure staff can keep up
- Step by step: a website gallery from Google Drive
- School website platforms
- Sharing event photos with parents
- Through the school year
- Example: a primary school's setup
- Mistakes to avoid
Public page or private link? Decide first
Before any setup, decide which photos belong on the open website and which belong behind a link sent only to parents. Mixing the two is the source of most problems.
| Public website gallery | Private link for parents | |
|---|---|---|
| Who sees it | Anyone, including search engines | Only people you send the link to |
| Good for | Facilities, displays, events from a distance, artwork, trophies, buildings | Class photos, close-ups, performances, trips |
| Children's faces | Few, only with consent, no names | With consent; a password adds a layer |
| How long it stays | The whole year or longer | A few weeks, then it closes |
A useful rule: the website shows what the school does; the private link shows your child doing it.
Consent, opt-outs and safeguarding
This isn't legal advice, and the rules depend on your country and your school's own policy. Some common ground:
- In the UK, the Department for Education's guidance on photos and videos in schools, and the ICO's guidance for schools, expect schools to have a lawful basis for using pupils' images. For websites and social media that's usually consent, and pupils and parents should be able to opt out. If a parent later withdraws consent, the image should come off the website.
- In the US, many districts treat student photos as "directory information" under FERPA, which parents can opt out of. Some districts treat photos differently, so the district's annual notice is the document to follow.
- Everywhere: keep an up-to-date list of pupils who must not appear online, and check it before each upload. Your school's photography or safeguarding policy decides the details.
Practical safeguards for website galleries:
- No names next to children's photos, in captions or in file names.
- Group shots and wide shots rather than close-up portraits.
- No uniforms with the school crest and the child's full face together on a public page, if your safeguarding lead advises against it.
- Remove location data from photos taken on phones; see how to remove location from photos.
- Turn downloads off on public galleries, so photos aren't saved in full size from the website.
What to show on a school website
Galleries that work well on a public school site, with little or no risk:
- The school itself: classrooms, library, labs, playground, sports facilities. This is what prospective families want to see.
- Work and displays: artwork, design projects, science fair tables, the D&T showcase.
- Events from a distance: the stage set, the sports day field, the choir from the back of the hall.
- Achievements: trophies, certificates, the team photo where every family has consented.
- Open days and admissions: a tour gallery for families choosing a school.
A folder structure staff can keep up
The gallery on your website shows what's in a Google Drive folder, so the folder structure is the whole system. Something like:
| Folder | What goes in it | Becomes |
|---|---|---|
| Website · Our School | Buildings and facilities | The "Our school" gallery on the About page |
| Website · 2026-27 › 01 Autumn term | Checked, consented photos from autumn events | A section of the "This year" gallery |
| Website · 2026-27 › 02 Spring term | The same, for spring | The next section |
| Parents · Year 4 trip (private) | All trip photos for those families | A private link, not on the website |
| Staff · Unchecked | Everything straight from cameras and phones | Never shared |
The Unchecked folder is the important one: photos only move into a Website folder after someone has checked them against the consent list. Because the website updates from the folder, the check happens at the point where it matters.
Step by step: a website gallery from Google Drive
- Create the website folders above in a shared drive the office and the communications lead can both edit.
- Share the website folder as "Anyone with the link" (Viewer). Only the folders you share become visible; the rest of the school's Drive stays private.
- Create the gallery in GalleryLink by pasting the folder link. Pick a calm theme and a grid layout, turn downloads off, and leave the password off (website galleries can't use one, see below).
- Arrange it: subfolders become sections (Autumn term, Spring term). Put the newest term first if you prefer, and rename sections to read nicely ("Autumn term 2026" rather than "01 Autumn term") on the Studio plan.
- Copy the embed code from Share › Embed and paste it into an HTML or embed block on your website page.
- Write a short introduction above it on the page ("Highlights from this term's events") and publish.
- Check it on a phone, the way most parents will see it.
From then on, adding photos to the website means moving checked photos into the right term's folder. No website login, no resizing, no uploading.
School website platforms
School website platforms differ in how much custom code they allow, and many are set up by the platform provider or the district. Some general pointers:
- Look for an embed, HTML or custom code block in the page editor. That's where the embed code goes.
- If your editor doesn't allow embeds, or your district restricts them, add a button or an image linking to the gallery's own address. It opens as a full-screen gallery, which works just as well on phones.
- Ask your web provider or district web team whether external embeds need approving; some platforms keep an allow-list of embedded sites.
- Google Sites (common in schools on Google Workspace) has an Embed option on the Insert menu that takes embed code or a URL.
- Squarespace, Wix and WordPress have code or HTML blocks; our embedding guide has the exact steps.
Sharing event photos with parents
For the photos parents actually want (their child on stage, the class on the trip), a private gallery link works better than the website:
- One gallery per event or class, made from that event's folder.
- Send the link through your usual parent channel: the newsletter, the school app or email.
- Add a password if your policy wants one, and share it in the same message.
- Downloads on for these, so families can keep the photos, with "Download all" in one ZIP or one section at a time.
- A closing date (for example two weeks), so photos of children don't stay online indefinitely.
For a fuller walkthrough of sharing photos with every family, see how to share team photos with parents and delivering photos to every family in a team or class.
Through the school year
| When | Task | Who |
|---|---|---|
| Start of year | Refresh the consent and opt-out list; create the year's website folder | Office, safeguarding lead |
| After each event | Upload to Unchecked; check against consent; move website-ready photos into the term folder | Event lead or office |
| End of each term | Review the website gallery; remove anything a parent has asked to take down | Communications lead |
| End of year | Archive the year's folder; start a new one; keep "Our School" current | Office |
Example: a primary school's setup
Here's how a primary school of around 300 pupils might run it, with the office manager and one teacher sharing the work:
- One shared drive, "School photos", with three top-level folders: Staff · Unchecked, Website and Parents.
- Staff upload from phones straight into Unchecked › 2026-11 Sports day after each event. Nobody outside the office can see that folder.
- The office manager checks each event against the opt-out list on the same day, then moves ten or fifteen wide shots into Website › 2026-27 › 01 Autumn term, and the full set into Parents › Sports day 2026.
- The website's "School life" page has one embedded gallery for the year. It updates the moment photos land in the term folder, so the page always shows the latest events.
- Parents get a private link to the full sports day gallery in Friday's newsletter, with downloads on and a two-week closing date.
- A prospective-families page has a second, permanent gallery of the buildings, library and playground, made from Website · Our School.
The whole routine takes the office about ten minutes per event, and nobody touches the website itself during the year.
Mistakes to avoid
- Uploading straight from a phone to the website folder. Every photo should pass the consent check first.
- Names in file names. "jessica-smith-sports-day.jpg" can show as a caption. Rename before moving files.
- Close-up portraits on public pages. Keep those for private parent links.
- A password on a website gallery. Browsers block password screens inside another website, so the embed shows an "Open the gallery" button instead. Keep public galleries password-free, and private ones as links.
- Galleries that never close. Event galleries for parents should close after a few weeks; the website keeps only the curated highlights.
- One person holds the only login. Use a shared drive, so the gallery doesn't stop when one member of staff leaves.
Which plan this needs
A school can build and test a gallery for free; free galleries are shared for 24 hours. Galleries that stay on the website through the year, password-protected parent galleries and closing dates are part of Pro. Studio adds renaming sections for the website, creating many event galleries at once from one folder, and a month-by-month dashboard for busy schools. Everything on each plan is on the pricing page.
Related: GalleryLink for school and league photographers, a self-updating photo gallery for your website and sharing event photos with guests.