Delivering client photo galleries and keeping a dated record of the originals

Flat illustration of a camera, a monitor showing an original campaign photo and an archive folder, with a timestamp badge

A client gallery is how many photographers, and some illustrators and designers, let a client review, favourite and download a set of images. That is a delivery job. It is not the same as keeping a dated record of the originals you actually sent. The gallery is a shop window and a download desk. The archive is the set of files you can still open in a year, plus a way to check that those files are still the ones you delivered. A TimeBind is a dated, checkable record that an exact file existed no later than a recorded time and still matches. The fingerprint is made in the browser, and the file stays on your device. A live gallery is not, by itself, that record, and a TimeBind does not prove that you own the photographs.

There is no affiliate link on this page: TimeBinder has no affiliate arrangement with the tools mentioned. Our affiliate disclosure explains when we do use them.

Table of Contents

When a shoot, a retouch job or a design pack is ready to share, several different files often exist:

  • The working originals — typically RAW files, or a full-resolution TIFF, PSD or JPEG of each select, plus any layered retouch files.
  • The gallery versions — often smaller JPEGs, sometimes watermarked, sized for a browser.
  • The download pack — the zip or set of files the client is allowed to take away, which may or may not be the same size as your masters.

Those are not interchangeable. A watermarked preview is a poor stand-in for a master. A JPEG the client downloaded six months later may have been re-exported, renamed, or stripped of metadata. “Date modified” on a downloaded copy can change when the file is unzipped, copied or posted. See what happens to file dates when you copy, zip or download.

Platforms also have their own limits. A hosted gallery can be password-protected, taken down, or changed. Retention, download rules and storage of RAW files depend on the plan. If the only copy of a delivery lives in an account you later close, or in a link that expires, you will wish you had kept the pack yourself.

A portfolio site raises a similar issue — the public page is a copy, not the master — and is covered separately in illustrators: timestamp portfolio work before you post it online. This article is about the client-delivery path.

A delivery checklist you can keep up

You do not need a new ritual for every preview. You need a habit that is light enough to use on a busy week, and clear enough that you can still answer “which files did I actually send?”

1. Keep the masters off the gallery. The RAWs, layered retouches and full-resolution selects belong in an archive you control. The gallery can hold the versions the client is meant to see and, if you offer it, download. Do not treat the hosted album as the only copy.

2. Export the exact delivery set before you upload it. If the client is entitled to a zip of finished JPEGs, make that zip (or that small set of files) first, on your machine, and give it a boring, dated name: client-shortname-wedding-selects-2026-11-11.zip. That is the pack you will stand behind.

3. Date that exact pack. Fingerprint the zip, or up to 10 individual files, with TimeBinder before you upload it to the gallery or attach it to an email. Click here to start. How to timestamp a file has the steps. Your first Pooled TimeBind is free; after that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Then do not edit that zip again. If you later replace a retouch, that is a new pack and a new record.

4. Keep the certificate next to that exact file, in the same job folder, and copy the folder off-site. A certificate without the file is not useful; a file without the certificate is just another copy.

5. Then upload or share. Use a password or a private client area if the platform offers one. Set download limits if the contract says the client may take only a certain number of images. Send the link in a way you can later find — usually an email you keep.

6. After the client has downloaded, leave the dated pack alone. Favourites, re-edits and print orders can generate new files. Those are new versions. If a later dispute is about the original delivery, you want the pack you dated on the day you sent it, not a gallery that has since been updated.

If you only need to check whether two folders still match, the free SHA-256 file hash checker and the file comparison checker can help on your machine. A hash is not a dated record. A TimeBind is. For the general method, see how to prove a file existed before a date.

Sensible moments to date a pack: the first full delivery; a revised set after a paid re-edit; and, if it differs, the set that went to a printer or a publication. You do not need to date every casual preview.

A good gallery is still worth using. It can show that you hosted a set, that a link was sent, and, on some tools, that a download happened. Password protection, watermarks, right-click limits and download caps can reduce casual copying of previews. Those are real operational benefits.

They are also easy to over-read.

A gallery record typically does not:

  • Show that the RAW or master JPEG in your archive is still the file you delivered, or that it existed no later than a particular time.
  • Survive an account closure, a lapsed plan, or a changed download policy, in a form you can hand to someone else.
  • Prevent a client from re-exporting, screenshotting, or posting a downloaded file.
  • Prove authorship, ownership, or copyright. A TimeBind does not do that either. If the question is whether someone copied a published image, start with how to prove someone copied your content and keep the honest limit in view: a dated file record shows that an exact file existed and still matches, not who owns it.

If a later conversation is about which version went out, you want your dated pack and, if you have it, the email or invoice that referred to that pack. The gallery is supporting context, not the whole answer.

Two storage mistakes show up often, months later.

The first is leaving RAW files only on a card or a single disk, and treating the online gallery as “the backup” of the finished work. Official SmugMug plans include unlimited full-resolution JPEG storage, but RAW storage is an add-on. Other hosts have their own caps. Even when JPEGs are stored “unlimited”, you still want an off-site copy you control. A hosted album is not a substitute for a backup you can restore if the account is gone.

The second is updating the gallery in place after a re-edit, and losing a clean copy of what was first delivered. If the contract or the conversation later turns on the original set, an overwritten album will not help. Keep the dated first pack, and date the revision separately.

For designers sending mixed packs rather than a photo gallery, protect your design before sending it to a client is the closer checklist. For sending a large delivery pack safely and keeping proof of what went out, see sending large files to clients safely. For the habit of dating work before it is shown more widely, see timestamp before you disclose and the creator timestamping hub.

Mistakes that leave you without the pack you sent

  • Uploading straight from a scratch folder, then tidying or overwriting those files. You will not be sure what the client received. Export a named pack first, and date it.
  • Dating a watermarked preview set, then sending a different, unmarked zip. The fingerprint is for the exact bytes. Date the pack the client actually gets.
  • Relying on the gallery as the only RAW or master archive. Check whether your plan even stores RAW files. Keep masters yourself.
  • Letting a delivery link be the only record that something was sent. Keep the email, the invoice, and the dated pack.
  • Treating a TimeBind as proof you own the photographs. It dates a file and lets you check that it still matches. It does not decide authorship or copyright.

Frequently Asked Questions

  1. Should I timestamp every photo in a gallery?

    Usually no. Date the delivery pack — a zip of the finished selects, or a small set of the files that would matter later. You can also date a zipped folder of the RAWs for that job if you want an earlier milestone, but you do not need a separate record for every preview JPEG.

  2. The client says the download looks different from what they remember. What helps?

    A dated copy of the exact pack you uploaded, plus any email that pointed to it. A gallery that has since been updated is weaker evidence of the original delivery. The free SHA-256 checker can show whether a file the client still has matches your archived pack.

  3. Does a password-protected gallery replace a TimeBind?

    No. A password limits who can open the link. It does not record that a particular file existed no later than a given time, and it does not let you check a copy years later against that record.

  4. What if I already uploaded the gallery and never dated the pack?

    If you still have the exact files you uploaded, you can date them now. That record will show they existed no later than today’s date, not the date of the original upload. It is still better than having no fingerprint at all. For the next job, date the pack before you upload it.

  5. Does this prove I took the photographs?

    No. A TimeBind shows that an exact file existed no later than a recorded time and still matches. It does not prove authorship, ownership or copyright, and it does not detect AI.

Date the next delivery pack, free

Your first Pooled TimeBind is free, with no credit card required. After that, TimeBinds start from US$5, and an ASAP TimeBind is US$15. Click here to start, or see plans and pricing.