How to Share a Photography Portfolio with Clients Online

You're waiting on a decision, and the client isn't in the room. A couple wants to review wedding selects on a phone between meetings. An art director wants the same commercial edit a brand partner will open later tonight. A giant attachment stalls in the inbox. A printed book never reaches the third stakeholder.

How to share a photography portfolio with clients comes down to one curated browser link. Build a short presentation they can open during a call and review alone afterward.

1. Choose the 15 to 25 images that match this brief.

2. Export lightweight previews, not full-resolution originals.

3. Publish a PDF or a gallery as a single URL.

4. Add a line of project context and the feedback you want.

5. Open the link on your own phone, then send it.

What follows is the review habit behind that standard, how to pick a format, and how to separate public samples, private proofs, and final files.

Why Clients Expect a Shareable Portfolio Link

A curated browser link beats an email attachment and a printed book for a simple reason. Clients stopped sitting across a table to judge the work. A 2023 survey by Wonderful Machine found that before COVID-19, roughly three-quarters of photographers met clients in person. Afterward, roughly three-quarters reported meeting clients online. Before the pandemic, photographers presented print portfolios at in-person meetings at about the same rate as digital presentations. Online meetings became the dominant setting afterward.

Client behavior moved with that change. Before COVID-19, clients held nearly twice as many in-person portfolio reviews as online reviews. By the survey period, more than one-quarter were already running more online reviews than in-person ones. The useful standard is a digital portfolio someone can open on a video call, then review alone later, rather than a book, a heavy attachment, or a live deck that disappears when the call ends.

One address for every stakeholder

A wedding job often needs the couple, a planner, and a parent on the same edit. A commercial job may need a decision-maker, an art director, and a brand partner. Attachments fork. Someone forwards last week's PDF. A stable link keeps one sequence, one set of captions, and one version you can point people back to.

Interior clients judge photography the same way, often without you in the room. Portfolio advice from Jimmy Clemmons Photographer is a useful parallel for anyone who has to read images on a screen and still understand the space. Sequence and room context matter more than a dump of files.

Practical rule: Send the link you would leave on screen while you talk, and that still makes sense if the client opens it alone at 10 p.m.

A shareable URL also cleans up the follow-up. You resend the same address to a late stakeholder instead of rebuilding the presentation. Digital delivery isn't a spare copy of the book anymore. For many clients, it is the review.

Five Steps to Share Your Portfolio Link

Do the send in one sitting. The mistakes that waste a week usually happen before the link exists: too many frames, originals instead of previews, or a note that never says what you want back.

1. Select 15 to 25 images. Match the brief, not your favorite year of work. A hotel group hiring you for lobbies doesn't need the surf series. A couple booking a documentary wedding doesn't need every studio portrait you've ever liked. Cut until each frame argues for the job. If you can't explain why a picture is in the set, it isn't.

2. Export a lightweight presentation. Keep a separate high-resolution archive. The file you share should open quickly and stay in a simple order. For a first-contact PDF, a short table of contents and a few captions beat a designed spread that fights the pictures. Format's PDF guidance is blunt about this. Smaller files upload and download faster, and a tight edit reads as a portfolio rather than an archive.

3. Pick the viewer that matches the file. A PDF belongs in a document viewer. A set of stills belongs in an image viewer. PDF to Link turns the document into a browser URL. Image to Link does the same for JPEG, PNG, WebP, and GIF, including several images as one gallery link. Recipients open the URL in a browser. They don't install an app or create an account. You choose the files first, then sign in to publish.

4. Add context before you share. Name the project, say what the pictures are for, and state how you want a reply. "Please mark the ten frames you'd like in the pitch deck" is a review instruction. "Let me know what you think" is not. Put your contact line in the same note so nobody has to hunt for it. On paid plans you can set a password, an expiry date, and a view cap on supported shares. A password controls the link. It doesn't encrypt the file, and it doesn't recall a copy someone already saved.

5. Send it only after you open it. Check the URL on your phone and on a laptop. Confirm the first image is the one you want seen first. Then send a short message with the link, who else has it, and when you need a decision. If you later replace a supported individual PDF or image, paid plans keep the same public URL. Don't assume that replacement applies to a whole gallery or a zipped site. Those are handled separately.

Shared PDFs are open to anyone who has the link unless you password-protect them. Say that out loud in the email when more than one person will forward the message.

Choosing Between PDF, Gallery, and Browser Links

No single format wins every job. Pick by who is looking, whether you're in the room, and how often the edit will change.

First contact is usually a PDF

Canon's portfolio guidance treats a PDF as something you can present remotely and send to a prospective client. That fits a pitch the client will open without you. Keep the layout plain. Add a caption only where the picture needs a job title, a location, or a usage note. An elaborate grid, giant type, and full-bleed color blocks pull attention off the photography. Canon flags that distraction directly.

Use two editions if you present live and also leave a file behind. The meeting version can be sparse, because you supply the pace. The leave-behind needs enough context that a partner who missed the call can follow the sequence. A table of contents helps on a longer document. A link back to your booking page belongs at the end, not on every spread.

Galleries and links earn their place later

A gallery is the better container once the set is large and the client will swipe on a phone. You still curate. You don't hand over the shoot folder. A browser link is the delivery method for both the PDF and the gallery. It is what you paste into the calendar invite, drop in chat, and reopen on the call.

What doesn't work is treating the link as a substitute for editing. A beautiful viewer full of unsorted frames still reads as unfinished. If email keeps stripping your files, the fix is the link itself, which is the point of sharing image files without email attachments. Change the underlying presentation when the selects change, and tell the client the address stayed the same so they don't keep an old download.

Preparing Preview Images for Fast Loading on Phones

The link is only as good as the files inside it. Photography pages are heavy by nature, and a lot of review now happens on a phone between other tasks.

Cloudflare's account of mobile traffic puts mobile devices and tablets at 51.3% of internet usage in October 2016, ahead of desktop by number of connections. The same write-up cites research that 53% of mobile visits are likely to be abandoned when a page takes longer than three seconds to load, and that 39% of users stop engaging when images take too long to appear. Images were about 41% of transmitted web data in 2023. In tested browser conditions, WebP cut page-load time by about 21% compared with JPEG.

Previews are not the print files

Don't attach full-resolution originals to the review email. The client can't start looking until a huge transfer finishes, and you've also handed over files you may not be ready to release.

Google's image guidance is the working spec for previews. Match resolution to the screen, pick a format and a quality level, and let the browser skip assets it doesn't need. Export an sRGB JPEG or WebP near the largest width you expect someone to view. JPEG quality above 85 grows the file quickly with little visible gain, so around 85 is a sensible start for client previews. Progressive JPEG helps because a large frame appears in passes instead of popping in only after the whole file arrives.

Build three derivatives, then stop.

• Thumbnail: for the grid, so the first screen fills fast.

• Tablet width: for the frame most clients pinch open.

• Desktop width: for the laptop on the call, still far below a print original.

Lazy-load anything below the first screen. Name files or captions with the project and the shot ID so feedback says "Lobby 14" instead of "IMG_4402."

Hold production files until sign-off

Adobe's reproduction notes separate what people look at from what a printer needs. JPEG is the usual file for ordinary viewing and many digital uses. TIFF or PNG waits for an agreed large-print or specialist job. Confirm RGB, CMYK, or both, and use the printer's ICC profile when you have one. Ship a file list and a contact line with the final package.

The viewer carries the light previews. A separate delivery, issued after selection, carries the approved high-resolution files. That split is what keeps a phone review from feeling like a download chore.

Protecting Proofs and Final Files with Staged Access

One link for the whole relationship is how unfinished work leaks. A public sample, a private proof, and a final delivery are different jobs. They should not share one permission set.

Most gallery advice stops at "add a password." That isn't enough. A password keeps strangers out. It doesn't stop an authorized viewer from downloading or forwarding files, which is why proof-gallery practice should separate download rights from the right to look. Avoid passwords built from the client's name, the venue, or the shoot date. Those are the first guesses, and they're already in the email thread.

Match the control to the stage

• Public sample portfolio. Anyone with the link can look. Use finished, cleared work only. This is the URL on your card, your site, and your pitch. Downloads stay off. Nothing unreleased lives here.

• Private proof link. Low-resolution or watermarked frames, downloads disabled. Password, expiry, and a view cap fit this stage, with the password on a paid plan for supported LinkShip shares. Collect selects here. Wedding, portrait, boudoir, and unreleased brand work all belong behind this gate, because the pictures are personal or not yet public.

• Final delivery. Issue it only after selection or sign-off. Narrower permissions, a shorter expiry if the contract is time-boxed, and the high-resolution files you agreed to hand over. Don't upgrade the proof link into the master archive.

A password on the proof is a door, not a vault. If downloads are on, an authorized guest can still forward the files.

Write the stages into the contract in plain language. State whether proofs may be shared with family or with an agency, how long access lasts, and the date final files become available. When the retouch changes, replace the proof content or send a new restricted link. Don't leave last week's unapproved frames at the old address if that address is still being forwarded.

For the control side of passwords, expiry, and who opened what, file access control is the operational detail. Use it to decide the stage. Don't treat it as a reason to put every job behind the same lock.

Checking Accessibility Before You Send the Link

A client who can't read the caption, reach the next image, or hear what the picture is will judge the interface instead of the photography. WCAG 2.2 requires a text alternative for non-text content so the information can be turned into speech, braille, symbols, or simpler language. You can run the checks below in a few minutes before you hit send.

Write the alt text the picture needs

Describe subject and context. "Architectural exterior photographed at dusk" tells a screen-reader user what the frame is. "DSC_2041.jpg" tells them nothing. Keep it short.

• Decorative frames that repeat a nearby caption get empty alt text, so the software doesn't announce them twice.

• Complex images, including composites, diagrams, and before-and-after retouching, need a longer description next to the picture, not crammed into the alt attribute.

• Approval labels such as "Selected" or "Hold" must exist as real text, not only as a colored dot on the photo.

Check contrast, keyboard, and zoom

Ordinary text needs a contrast ratio of at least 4.5:1. Large text needs at least 3:1. White captions dropped straight on a bright sky fail both. Put captions, metadata, navigation, and approval labels on a neutral bar.

Then use the keyboard only.

1. Tab from the link, through the controls, to the last image. The order should match the visual order.

2. Confirm a visible focus ring. If you can't see where you are, neither can a client who doesn't use a mouse.

3. Zoom the page and check that captions don't overlap the picture or fall off the screen.

4. Turn on a screen reader and listen to one image, one caption, and one button. If the button says "button" with no name, fix the label.

These checks aren't a redesign. They're how you make sure the decision is about the photograph.

Using QR Codes on Printed Portfolio Cards and Tracking Scans

Print still starts conversations. The card, the exhibition label, and the leave-behind should land on the same portfolio URL you already trust, not on a second, stale copy of the work.

The QR Code standard defines versions from 21 × 21 modules up to 177 × 177. Larger versions hold more data and look denser on a small card. Error correction comes in four Reed–Solomon levels. L restores about 7% of codewords, M about 15%, Q about 25%, and H about 30%. Higher correction survives scratches and a logo sitting on the code, and it leaves less room for a long URL. Encode the short portfolio link. Don't encode a paragraph about the project.

Print a test before you print a stack

Scan the actual artwork at the size you will print, under the light where people will stand. A code that works on your monitor can fail on coated card stock in a dim booth. Quiet zone, contrast, and size matter more than a decorative frame around the mark.

Point the code at the public sample, not at a proof gallery. Proofs are for named clients. A card on a table is for anyone who walks by.

Track the print channel on its own. If the public sample is a PDF on LinkShip, add a print-ready code from that project's QR card, or upload the PDF in the PDF tab of the QR Code Generator. If the sample lives on your own website, paste that address into the generator. A code can't point at an existing LinkShip share link. QR scans are counted separately from ordinary link clicks. That split tells you whether the exhibition card is doing work or whether people only arrive from the email. QR code analytics is the place to read that difference before you reorder cards.

The next step is small enough to finish today. Publish one portfolio link, generate a code for it, print a single test card, and scan that card on two phones before you hand any out.

Create a client-ready photography portfolio with Image to Link, or share a finished PDF pitch with PDF to Link. Test the link on a phone and in a private browser window, then send it with the project context and the feedback you need.