If you serve photography clients across more than one language, the gallery space has a quiet limitation that's easy to miss until you run into it. Most hosted gallery platforms run their entire interface in a single language, period. Your French-speaking client and your English-speaking client see the same buttons, the same checkout, the same email confirmations. You can translate around the edges, like cover letters or intro pages, but the actual buying experience stays in whatever language the platform was built in.
WordPress lets you do the real version. Build the gallery system in your client's language end to end, including the part that matters most: the cart, checkout, account, and confirmation pages. Here's how it fits together.
What "multilingual" actually means for client galleries
There are two layers of language on a gallery site, and most photographers only think about one of them.
The first is the interface language. The buttons, labels, error messages, and form fields the gallery plugin itself ships with. "Add to cart," "Continue to checkout," "Enter your email," "Order confirmation," that kind of thing. These come from the plugin and need to be translated by whoever built it (or by translators contributing to it).
The second is the website language. The pages around your galleries: homepage, about page, pricing, blog. This is what most translation plugins are designed to handle.
A complete multilingual photography site needs both. The interface in your client's language, and the rest of the site in their language too.
Sunshine ships with translations in 19 languages
Sunshine Photo Cart's interface is already translated into Bulgarian, Czech, Danish, Dutch, English (UK), Finnish, French, German, Hebrew, Hungarian, Italian, Norwegian Bokmål, Polish, Portuguese (Brazil and Portugal), Russian, Spanish (Spain and Mexico), and Swedish.
Translations come from the community, so the full list and contribution links are available if your language isn't there yet or could use improvements.
For a single-language site this is the easy part. WordPress has a Site Language setting under Settings, General. Pick the language there, and Sunshine plus the rest of WordPress switches over together. Done.
Multilingual sites: pair Sunshine with a translation plugin
If you serve clients across multiple languages on the same site, you need to actually run your site in two or more languages at once. WordPress doesn't do this out of the box. You need a translation plugin.
The two I've directly tested with Sunshine and confirmed work well are:
- Polylang, which has a free version that handles most photography sites. Lightweight, well maintained.
- WPML, paid only, but more robust for larger sites or translation team workflows.
Those are the two I can vouch for, but they're not the only options. There are many multilingual plugins on WordPress.org, and most of them work the same way: you set up your site's languages, create translated versions of each page, and a language switcher widget lets visitors pick.
Sunshine recognizes translated versions of its core storefront pages (galleries, cart, checkout, account, favorites, and terms) so visitors land on the right language version of each page automatically. There's nothing to configure inside Sunshine for that to happen. Translate your Sunshine pages in your translation plugin and Sunshine picks up the link.
More on this in the Multilingual sites documentation.
Skip translating the galleries themselves
Gallery content usually shouldn't be translated. Photo titles, image captions, and gallery names are typically descriptive of the photos themselves, and translating them per-language is more confusion than help. A gallery called "Sarah and James, June Wedding" doesn't need a French translation. A photo titled "The First Look" doesn't either.
What needs translation is the frame around the photos: the storefront language, the buttons, the price labels, the checkout flow. That's the part the visitor reads, decides on, and acts on. The photos themselves cross language lines fine.
That's good news, because it bounds your translation workload. You're translating something like 20 to 30 pages of storefront content, not hundreds of gallery pages.
[brightspot_single]
Make the language switcher easy to find
If a visitor lands on the wrong language page, they should be one click away from the right one. Most translation plugins offer language switchers (flags, dropdowns, or small buttons) that let visitors pick.
Don't bury it in the footer. Put the switcher somewhere obvious, usually the top right of the header or alongside your main navigation. Visitors who can't find the language switcher will leave instead of hunting for it.
If you can detect the visitor's browser language and default them to the right page, even better. Most translation plugins support this with a checkbox.
Why you'd want to do this on WordPress
Multilingual client galleries are one of those capabilities that's much harder on hosted gallery platforms than on a WordPress site you control. Hosted platforms run their whole interface in one language, period. WordPress is built around translation as a first-class concept, and most plugins (including Sunshine) follow that lead.
Pair a translated WordPress site with Sunshine's translated interface and a translation plugin like Polylang or WPML on top, and you've got a genuinely multilingual storefront. The same site can serve a wedding photographer's couple in Quebec and their family in California, and both feel like the site was built for them.
Thanks for reading. If you're already on WordPress, the Multilingual sites documentation covers setup details. New to Sunshine? You can download it free and pair it with the translation plugin of your choice.