Let visitors share on social networks
Decide when on-site Facebook, X, and LinkedIn share actions help—what gets shared, public vs vault boundaries, galleries vs photo pages, and placement—then use portfolio Enable Sharing docs for the exact setting location.
Why visitor-initiated sharing is useful
Someone is already looking at your work. A light share or copy link action lets them take that URL into Facebook, X (Twitter), LinkedIn, or a message thread—without you operating those networks for them.
This is amplification, not audience creation. It does not replace RSS, email, or Open Web Distribution.
When buttons help vs when they clutter
| Helpful | Clutter |
|---|---|
| Public showcase galleries and flagship photo pages | Quiet personal experiments you only send privately |
| Fundraising or press stories meant to travel | Dense UI on every archival frame |
| Clear next step after the click (series, contact, print) | Share icons competing with buy/download before the image is felt |
If the gallery is meant to feel like a quiet viewing room, keep sharing off. If it is meant to travel, turn it on for that collection.
Which networks are worth enabling
ArtInStack surfaces common actions (copy link plus networks such as Facebook, X, and LinkedIn). Worth enabling when your audience actually uses them—or when press and partners expect a LinkedIn-friendly URL. You do not need every network for every gallery; the product control is collection-level Enable Sharing, not a per-network matrix.
Prioritize:
- Copy link — always valuable when sharing is on.
- Networks your clients and peers already open daily.
- Skip worrying about networks your audience abandoned.
What gets shared
Visitors share a public URL (photo detail or the page they are on), not a private file from your vault. The outbound post is theirs; your brand appears in the link and in the link preview that URL produces.
Photo visibility and what can be shared
| Surface | Share chrome |
|---|---|
| Public portfolio with Enable Sharing on | Share / copy in lightbox and/or photo detail when those UIs exist |
Photo detail requires Enable Page View (and related public rules) for a durable /photo/{id} URL | Prefer both when you want shares to land on a rich page |
| Confidential, hidden, or vault-only | No public share path |
Private client delivery links never get public share buttons.
Public vs private / vault content
| Public site | Vault / project |
|---|---|
| Optional Enable Sharing | Never treated as social distribution |
| Previews and SEO can apply | Text-only on purpose |
Do not enable sharing to “make a private gallery feel viral.” Use client delivery tools instead.
Recommended placement (galleries vs photos)
| Choice | Use when |
|---|---|
| Collection-level Enable Sharing (lightbox + photo UI) | The whole public gallery is safe to travel |
| Strong photo detail pages | You want shares to land on one image with caption, EXIF, or prints |
| Both | Default for flagship showcase work |
| Gallery public, sharing off | Viewing is welcome; amplification is not the goal |
Turn sharing on under portfolio Settings → Visibility & SEO → Enable Sharing. Photo detail and lightbox docs show how that appears on the live site.
Strategy
Ask for shares around moments (launch, exhibition, campaign), not on every thumbnail. Pair with strong previews so the outbound card looks intentional. For followable studio presence without asking every visitor to do the work, use Open Web Distribution.