How to Share Product Images with Clients in 6 Steps

You've finished the retouching, the buyer needs the images today, and you're staring at a folder of files named IMG_4471, IMG_4472, and final-version-2. If you attach them, the client gets a heavy email, saves the wrong copy, and replies about a version you've already replaced. The reliable way to handle how to share product images with clients is different. Export a named, web-ready set, upload it once, set only the access rules the product needs, and send one browser link the client can open, zoom, and approve.

Treat the link itself as the deliverable, not as an afterthought once the files are done. Follow this order and the client reviews the set you intended, in the order you intended.

Prepare the Files Before You Touch the Tool

Export and name every file. Save each image as a web-ready JPEG, PNG, WebP, or GIF and name it by product and view, such as ceramic-mug-front.jpg or ceramic-mug-handle-closeup.jpg. Clear names let the client reference an exact image in feedback. The usual slip is leaving camera names in place, which makes revisions almost impossible to trace.
Select your files in the tool. Open the Image to Link tool and choose the approved files first. You pick your files before signing in, so gather the final set before you start rather than adding drafts as you go. Mixing rejected shots into the same selection is the fastest way to confuse an approval.
Complete the publish step. Finish the publish step the tool presents once you're signed in to your LinkShip account. Publishing converts your selection into the live link the client will open. Don't copy a link before this step is done, because an unfinished publish isn't the address your client needs.

Name, Restrict, and Send

Customize the link clearly. Give the link a name that identifies the client and product, and set a password, expiry date, or view limit only where your plan offers it for that content. Our workflow runs in four parts, upload a file, customize the link, share it, and track visits and downloads. The common mistake is leaving a generic name that doesn't tell the client which job they've opened.
Send the link, not the files. Copy the link into the email body, client portal, or message thread and leave the files out of the attachment field. A file that's still attached reaches the client even when the link is ready, and you've just created two competing copies. If you've set a password, send it through a separate message, since a password pasted beside the link defeats its purpose.
Test before you send, then track. Open the link on a desktop and a phone first, ideally in a private window where you're not signed in. After the client responds, check views and downloads so you know whether they've actually opened the set. Testing only while logged into your own account hides sign-in and permission problems your client will hit.

Practical rule: Never send a link you haven't opened the way the client will open it.

Run the Three-Point Check on the Live Link

Before the message leaves, confirm three things on the published link. First, the opening image loads promptly without a blank viewer. Second, the set appears in the intended order, with the hero shot first and detail views after it. Third, the product name and view are correct in the title, so the client isn't approving a blue variant while looking at the red one.

Finish your message with a short note that lists what's in the set and what you need back, such as approval by a named date or a comment on one specific variant. A bare link invites silence. A link with two sentences of context gets a decision.

Why Client Image Links Beat Email Attachments

Send one browser link to the approved image set instead of attaching the files. According to Google's Gmail attachment guidance, personal Gmail accounts allow up to 25 MB of total attachments per message, and when the combined size goes over that limit, Gmail removes the attachments and inserts a Google Drive link instead. The limit covers the whole message, so several smaller images can fail together, and work and school accounts may have administrator-defined limits that make delivery less predictable at each client.

Say a freelance product photographer sends twelve packshots to a buyer on a managed laptop, and the buyer asks for one revised image. With attachments, the photographer resends the email and the earlier copies stay in the inbox. With one link, a supported file is replaced at the same address on a paid plan.

Factor	Email attachments	LinkShip browser link
Size limit	25 MB total per Gmail personal message, over the limit Gmail inserts a Drive link	No email attachment total applies because files open from the shared link
Updating a revised image	Resend the email, earlier copies stay in inboxes	Replace a supported file at the same URL on paid plans
What the client needs	A mail client that handles attachments	A browser, no account or app install
Sender insight	None from the mail client	Views, devices, referrers and city-level location

Build an Image Set Clients Can Inspect

Start with a review set built for decisions, not every photo on the drive. Include a clean hero view, two or three angles, close-ups of the features a buyer compares, packaging or labels, and one image showing scale in a realistic context. Baymard's product image research found that 42% of users try to understand product size from images, yet 28% of benchmarked sites provide no in-scale image.

Add a short caption wherever an image alone is ambiguous. State dimensions, material, included accessories, colour variant, or whether a prop is shown for scale only. Keep crops, backgrounds, and colour treatment consistent so the client compares products, not editing choices. If you're building apparel imagery from scratch, an ai photoshoot for clothing brand workflow can supply clean on-model views, but those images still need the same scale, detail, and caption discipline before a client sees them.

Separate the Fast Preview From the Master

Prepare two tiers. The first is a fast preview at the dimensions clients need for review, sized for screens rather than the camera. The second is a higher-resolution master kept for production and close inspection. That split matters because Baymard's usability testing on image resolution and zoom found that 56% of users' first actions on product-detail pages were exploring images, while 25% of tested ecommerce sites provided insufficient resolution or inadequate zoom.

Check on the live link whether zoom works with pinch and keyboard input, and whether a download option is visible. A visually large image isn't necessarily detailed enough for a client to assess texture, labelling, finish, or defects.

Clients don't abandon a review because the gallery looks plain. They abandon it because they can't zoom in far enough to trust what they're seeing.

Make the Set Readable Without Sight

Write alt text for every image that tells a non-sighted client what they need to judge, covering fit, colour, material, texture, scale, and included parts. Match descriptive filenames to the captions so screen-reader users and sighted clients work from the same labels. Before sending to a client who relies on a screen reader, confirm the viewer exposes the alt text and captions in the order the images appear.

Keep version history in your own folder and send one controlled link. The client should never have to choose between competing copies.

Choose the Right Format and Size for Each Asset

Choose a format per asset rather than forcing one format onto every file.

Format	Compression	Best client use	Watch for
JPEG	Lossy	Catalogue and lifestyle photographs	No transparency, keep a lossless master for production
PNG	Lossless, with full alpha transparency	Transparent packshots, logos and annotated mockups	Check file size against the preview target
WebP	Lossy or lossless	Smaller web previews for recipients on modern browsers	Confirm older client systems can display it
GIF	Palette-based	Simple animated product demonstrations	Not the default for detailed product photography

That table follows the distinctions in MDN's guide to image file types, where JPEG uses lossy compression and suits photographs, PNG uses lossless compression with full alpha transparency, and WebP supports both lossy and lossless encoding. GIF is broadly supported for simple animation, but it isn't the right vehicle for detailed product photography.

Match the Format to the Job

Use JPEG for standard catalogue and lifestyle photos, where gradients and skin tones matter more than pixel-perfect edges. Use PNG for transparent packshots, logos, screenshots, diagrams, and annotated mockups where crisp edges carry the meaning. Use WebP when smaller previews help and recipients are on modern browsers, but check compatibility first if the client works on older corporate systems.

Say a transparent logo gets exported as JPEG. It loses its transparency and arrives on a solid background, so the packaging designer's mockup looks wrong before the client reads your note. That isn't a quality problem you can fix with a bigger file. It's a format problem.

Protect the Master and Test the Preview

Because JPEG and WebP copies can be lossy, a web delivery file is never your master. Keep the full-resolution original beside the preview for production use, and name both so nobody sends the preview to print.

Size the preview for the screen it'll appear on, not the camera's native dimensions. Oversized previews slow review on phones and make clients wait before they can compare variants. I'd test every set on an ordinary mobile connection rather than office broadband, because that's where a buyer between meetings will open it.

Set Access Rules and Fix Common Link Problems

Access settings decide who can open the link, for how long, and how many times. Password protection controls access to the sharing link on paid plans for supported content. It doesn't encrypt the file itself and it doesn't revoke copies a client has already downloaded, so don't promise more than it does.

Expiry dates end access on a set day, and view-count caps limit how many times the link can be opened. Both are paid settings. Availability depends on content type and plan, so confirm what your plan shows for each link before you promise a restriction to a client. If you want the fuller picture of how these controls combine, our guide to file access control lays out the options.

Reserve Restrictions for Content That Needs Them

Use these settings for unreleased packaging, prototypes, and pricing, where a forwarded link causes real harm. Public catalogue images rarely need a password, and adding one only creates friction for the people you want to approve quickly.

Sender habit: Apply the strictest control the content earns, and no stricter. Every extra barrier is a reason for the client to postpone the review.

Replacement works narrowly by design. On paid plans, supported individual image files can be replaced while the public URL stays the same, so a corrected photo reaches the client without a new email. Don't extend that to image galleries, ZIP archives, or audio collections, which follow separate rules.

Diagnose the Failures Clients Report

Symptom	Likely cause	Fix
Client is asked for a password	Password protection is turned on	Send the password separately from the link, not in the same message
Link shows as expired	The expiry date has passed	Set a new expiry date in the link settings and resend the same URL
Client sees a view limit message	The view-count cap has been reached	Raise the cap in the link settings, or create a new link if the cap cannot be changed
Client still sees an old image	The replacement was not saved, or the client already downloaded the earlier copy	Confirm the replacement in the tool, then ask the client to reopen the link, downloaded copies cannot be recalled
No replacement option for a set	The content is a gallery, ZIP archive or audio collection	Share a new link for the revised set, because replacement covers supported individual files only
Invited client cannot open the link	Their address is not on the email allowlist	Add the correct address to the allowlist, or confirm the right recipient

Print QR Codes and Track Client Engagement

A QR code is the print bridge for a link you've already built, not a separate deliverable. It works well on packaging proofs, trade show boards, sample tags, and printed lookbooks where the client is holding something physical.

Build the Code From the Finished Link

Export the approved images as a PDF lookbook. LinkShip QR codes belong to link and PDF projects, not to image links or galleries, and a code can't point at an existing LinkShip share.
Upload the PDF in the QR tool. Use the PDF tab of the Dynamic QR Code Generator, so the code opens the lookbook in a browser.
Style and download. Add a brand colour or logo if you want one, then download a 1024 or 2048 px PNG, or an SVG for large print.
Test-scan the printed proof with a phone at the distance a viewer would stand, not from your desk chair.
Print with a caption that tells the viewer what they'll open, such as the product name and the word gallery.

Saving QR designs and downloading codes are paid features on Tiny, Solo, Pro, and Pro Max plans. Free users shouldn't plan a print run around them.

Read Scans Separately From Clicks

Scans are recorded separately from link clicks, so you can compare a trade show banner against an email link without guesswork. LinkShip counts views and downloads, and paid plans add trends, countries, referrers and devices. Our overview of QR code analytics explains how that scan data is structured.

Put the code on the physical item clients will hold, then compare scans with clicks before you decide where the next print run goes.

Send Your First Client Image Link

Pick one product and build its review set now, a hero view, angles, close-ups, packaging, and one in-scale shot. Upload those images, set only the access rules the content needs, and send one link. When the set holds more than one image, it opens as a single gallery, so the client sees one address instead of a string of files.

Recipients open the link in a browser with no account or app install. When a photo changes, replace the supported individual file on a paid plan rather than resending the email, then open the link on a phone to confirm the new version is live.

After the first send, check views and devices. You'll learn whether the client opened the link at all, and whether they opened it on the device they'll use to approve the work.

Build your next product review as one trackable gallery link, set a password or expiry only where the content needs it, and replace a corrected photo without changing the address your client already has. Visit LinkShip to turn your first product image set into a link your clients can open, inspect, and approve from any browser.