One Photo Dashboard, Many Websites: Live Embeds for Shopify and Consumer Sites

A traditional website gallery is often maintained inside the website builder. When the same campaign appears on a main site, a Shopify store, a dealer page, and a second brand site, that approach creates four separate copies to update. PhotoView.io changes the model: the portfolios and saved embed selections live in one dashboard, while each outside page displays a live PhotoView presentation.

The iframe is not a frozen export. It continues to read the public selection hosted by PhotoView. Show a photograph, hide one, or change the portfolio order in PhotoView, and every website using the affected live embed can reflect that decision without replacing the code on each site.

This makes PhotoView the publishing and curation layer for finished images. Photoshop, Topaz, Capture One, or another editor still prepares the photograph; Shopify and the other websites still handle commerce, navigation, copy, and conversion. PhotoView controls which finished images appear and in what order.

Reuse the same embed code when several placements should always mirror one another. For example, a photographer could place one Current campaign embed on a portfolio homepage, a Shopify brand page, and a distributor site. A single PhotoView visibility or ordering change then updates all three placements.

Create separate saved embed profiles when the destinations need different selections. A Shopify homepage may need six dramatic campaign photographs, a collection page may need the complete seasonal story, and a press page may need only approved editorial images. Each saved profile can select individual photographs, one portfolio, several portfolios, or the full public collection.

Name profiles by destination rather than by a vague subject. Main store — homepage, Main store — summer collection, Brand site — About, and Dealer portal — approved campaign are easier to operate than Gallery 1, Gallery 2, and Gallery 3.

A photographer with several specialty sites can keep a Wildlife portfolio embedded on a nature site, an Architecture portfolio on a commercial site, and a Portraits portfolio on a booking site. The sites retain their own design and marketing message, while PhotoView provides one place to review the images behind all three.

A travel or event business can reuse one live Destination spotlight across its public website, a registration page, a sponsor page, and a tourism partner site. When the approved image order changes, every placement stays aligned.

An artist can maintain separate embeds for Available work, Recent exhibitions, and Press selections. A gallery, personal site, and exhibition microsite can each use the appropriate feed without receiving access to the artist's PhotoView dashboard.

A nonprofit or community organization can create portfolios for Programs, Events, Volunteers, and Impact. Saved profiles can combine those portfolios differently for the main site, a campaign landing page, and a partner page while the staff curates the public imagery centrally.

Use a concise homepage embed as a live editorial window into the current campaign. Select a small set of strong photographs rather than turning the homepage into an archive. When a launch changes, update the selected PhotoView portfolio or profile and keep the Shopify placement intact.

A seasonal landing page can use a larger campaign embed for a lookbook or launch story. The product grid and purchase controls remain native Shopify content around it; the PhotoView embed supplies the visual narrative.

For stores that operate more than one regional or brand site, the same approved campaign embed can be placed on each storefront. If every storefront should match, reuse the code. If product availability or art direction differs by market, save one clearly named embed profile per storefront.

A collection page can place a PhotoView gallery between the collection introduction and the product grid to show the materials, location, people, or process behind the range. A dedicated collection portfolio keeps that story independent from the main campaign.

A product-story page can embed detail photographs, alternate environments, craftsmanship, before-and-after context, or installation examples. When every product has different imagery, use a dedicated portfolio and embed profile only where the editorial value justifies that extra structure; do not load a large generic gallery on every product page.

Wholesale, press, stockist, and trade pages can display a controlled public selection without exposing the PhotoView dashboard. Keep downloadable sales assets and protected client material in their appropriate private delivery flow rather than treating a public embed as a secure file room.

Start by mapping each body of work to a PhotoView portfolio. A useful plan might include Evergreen brand, Spring campaign, Product details, Behind the scenes, and Press approved. Set only the portfolios intended for public embedding to Public, and enable portfolio embed permission for each one.

When finished images come from desktop software, open Settings, Imports, and Smart Folders. Create a separate route for each local export folder and destination portfolio. PhotoView supports up to 12 routes in one watcher command, so one computer can monitor several independent publishing lanes.

A brand could export approved campaign files to PhotoView-Spring, product details to PhotoView-Details, and press images to PhotoView-Press. The watcher sends each finished file only to its assigned portfolio. Smart Folders automate delivery; the PhotoView dashboard remains the place to review visibility and presentation order.

Open Settings, then Sharing. Under Create an embed, choose New embed, give the profile a destination-specific name, and select the exact photographs or portfolios that placement should display. Save Settings, copy the iframe, and paste it into the matching page on the outside website.

On a Shopify theme that provides a Custom Liquid section in the intended template, add that section in the theme editor and paste the iframe there. If the active theme does not provide an appropriate Custom Liquid section, use the theme's supported code-editing workflow or work with a Shopify developer. PhotoView is supplying a standard live embed, not installing a Shopify app.

For WordPress, Squarespace, Webflow, Wix, or a custom site, place the iframe in the platform's supported HTML or embed block. Website builders differ, so preview the result in the actual published or staged page rather than assuming the editor canvas is exact.

After the iframe has been placed, routine curation no longer requires repasting it. One PhotoView action—such as showing a new approved photograph, hiding an expired image, or changing the order—updates the live PhotoView selection used by every matching placement.

A finished Smart Folder export can also travel through the workflow automatically: the watcher uploads it to its assigned portfolio, and an embed that includes that public, visible work can display it. Review the portfolio before relying on unattended publishing when brand approval, licensing, product availability, or launch timing matters.

The update is not a command that rewrites Shopify or another site's media library. The outside page continues to load the PhotoView-hosted iframe. That distinction is what allows several sites to stay synchronized without maintaining duplicate gallery content.

Imagine a studio managing a consumer brand site, a Shopify store, and two retailer pages. The Evergreen brand profile is reused on the consumer About page and both retailer pages. A Store homepage profile shows six current campaign photographs. A Spring collection profile shows the full seasonal portfolio only on the Shopify collection page.

When the studio hides an outdated Evergreen photograph, all three Evergreen placements change together. When it reorders the Spring portfolio, only the collection embed changes. When a new homepage hero selection is needed, the team edits the Store homepage profile without disturbing the retailer galleries.

This structure gives the team one source of truth without forcing every site to show identical content. Shared profiles create synchronization; separate profiles create control.

Use only public, web-ready photographs in embeds. Private link, Password, and client-portal portfolios are intentionally unavailable through readable embed URLs. An outside website receives the public presentation, not PhotoView account access or editing controls.

Keep each placement focused. A smaller editorial selection usually loads faster and gives visitors a clearer story than a complete archive. Confirm image licensing, remove expired campaign work, and use profile names that identify the owner and destination.

Before launch, test every placement on desktop and mobile. Check the surrounding page spacing, iframe height, loading behavior, order, captions, and hidden-image rules. Then make one harmless test change in PhotoView and confirm that every intended placement updates while unrelated profiles remain unchanged.