Client galleries for photographers

The gallery you send after the shoot.

welca puts your studio’s name over the photographs and hands your client a link that works on a phone the same evening. Around it sit the things you need afterwards: favourites, downloads, a record of who took what, and colleagues who can work in it with you.

Two columns on a phone, four on a laptop. Every photograph keeps the shape you shot it in — nothing is cropped to make a row come out even.

What your clients and their guests open

The cover is a photograph

No dark scrim, no headline printed across it. The gallery name sits in a bar underneath that sticks to the top of the window, so “download all” is still in reach eight hundred photos down.

A wall of photos, not a spinner

Every photo carries a thirty-character placeholder computed when it was uploaded. The grid arrives coloured and sharpens, instead of sitting there as grey rectangles.

Hearts, without an account

Anybody can heart photos and switch to a view of only those. The list lives in the browser, moves to another phone with one link, and reaches you grouped by the address the guest left.

Full screen, and a slideshow

Tap a photograph to open it full screen and swipe on, or let the gallery play through itself on a television at the venue.

Downloads, in return for an address

Guests leave an email address once and download from then on — a size for sharing, or the original for printing where you allow it. “Download all” arrives as one ZIP assembled in their browser, without a second copy prepared on the server.

A code to hold up

Every gallery has a share button that shows a QR code of its own address. At the event, the person next to you scans your screen.

What you work in

The grid is the workbench

Click to select, shift-click for a run, and a bar fixed to the bottom acts on the selection. The cover is chosen from the same grid, so photos live in one place rather than two.

Sections

Arrival, programme, party: file photos into named sections and put them in the order you choose, so your client reads the day the way it happened.

Presentation, set per gallery

Cover height, grid size, spacing and photo order are chosen per gallery and previewed in the studio before the link goes out.

Uploads go past the server

The browser puts JPEG, HEIC, RAW and video files straight into storage, in parts, so a whole day’s originals do not hang on one connection holding. Previews are made afterwards, in a queue that survives a restart.

Straight from your Synology

Paste a sharing link from your NAS and welca fetches the photographs from there — and again later, for whatever was added since. Nothing is installed on the NAS.

A password, a closing date, and who gets which size

Lock a gallery with a password, set the day it closes, and decide whether guests get the sharing size or the originals. Your client’s own addresses are recognised at the download gate.

Links you can take back

A quick-share link opens a draft for a client or a vendor without the password, for thirty days, and stops working the moment you withdraw it. The client’s link goes out by email when you press send — never because a gallery was published.

A page for the studio itself

An introduction, a portrait, a way to write to you and your legal pages — without listing a single client gallery, because that link belongs to the client you gave it to.

What you know afterwards

The selection, ready for Lightroom

The picks come to you grouped by guest, as a CSV, or as a list of filenames you paste straight into Lightroom’s search field.

Counting, not tracking

How often the gallery was opened, what was downloaded, which photographs drew the most attention. No pixels and no profiles — a count is enough to answer “did they get them?”

Two logs

Every download handed out carries the address that asked for it, and every change anybody in the studio makes is written down with a name and a time. Both export as CSV.

A studio is a team

Invite a second shooter as a member or an owner, credit photographs per photographer, and work in more than one studio from one sign-in.

What is different

Nothing in a gallery says welca

Your studio name, your studio address, your own page with a portrait, contact and legal text. The platform introduces itself here and nowhere else.

Galleries are not listed

Your studio page introduces you and stops there. A gallery is reached only by the link the client was given, because an event is not a public fact about the people in it.

Originals stay private, in the EU

Previews sit behind a CDN. The originals live in a separate, non-public bucket under EU jurisdiction and are only ever reachable through a link that expires — no public URL points at a full-resolution file.

It speaks the guest’s language

German or English, taken from the browser. There is no switch, because a link passed around at an event reaches people whose browsers already know what they read.

What it does not do yet

Written down plainly, so nothing above reads as a promise.

  • Developing a RAW file. A RAW imports as the full-size JPEG the camera wrote inside it, which is the frame as the camera rendered it.
  • Google Drive and NAS brands other than Synology. Today the import reads a Synology sharing link, including QuickConnect links.
  • Face matching. It is designed, and it does not ship before a privacy review says which version is lawful.
  • A domain per studio. Every studio lives under a path.

Start with one gallery.

Create a studio, upload a gallery, send the link.