clientgallery.io

Delivery

How to Send Photos to Clients From an iPhone

The quick ways all work. None of them leaves you a record of what you sent, a way to re-send it, or a place for the client to choose. Here is what Apple documents, and what to do instead.

Updated September 2026

You are standing somewhere with a phone full of client photos and about thirty seconds of patience. The options in front of you are Messages, AirDrop and Mail. All three will move an image from your hand to theirs, and for a single preview frame that is a perfectly reasonable thing to do.

The trouble starts when the same thirty-second habit becomes the delivery. This page does two things. First it sets out what Apple actually publishes about each of those routes, checked on 23 September 2026, and it is deliberately quiet where Apple is quiet. Second it walks the path that holds up: get the files off the phone without an automatic conversion, export them properly, and hand the client one link instead of a thread of attachments.

Your iPhone probably did not shoot a JPEG

Before you send anything, know what you are holding. Apple documents HEIF as the photo format and HEVC as the video format on its devices, and states that they offer better compression than JPEG and H.264. On supported models, High Efficiency is the default capture behaviour.

There is a documented alternative. In Settings, under Camera, under Formats, Most Compatible captures JPEG or H.264 instead. That is the whole of the choice Apple describes at capture time.

This matters for a client handoff because the format decision and the delivery decision get confused constantly. Switching to Most Compatible is a capture setting, not a delivery strategy. It changes what lands in your camera roll. It does nothing about whether you can prove, three weeks later, which eight photos you sent your client on a Tuesday.

The quick sends, and what Apple actually documents

Most advice on this subject is folklore repeated between photographers. The table below is restricted to what Apple published and what we could read on 23 September 2026. Where Apple says nothing, the table says so rather than filling the gap.

RouteWhat Apple documentsWhat it leaves you afterwards
MessagesThat you can send and receive photos, including Live Photos, videos and animated GIFs. Apple's Messages pages say nothing about image quality, compression or file size.A thread. No list of what was sent, no way to re-send in one action.
AirDropHow to send and receive between nearby Apple devices. Apple's AirDrop pages make no statement about quality, compression or metadata.Nothing at all. Both people also have to be in the same room with Apple hardware.
Mail on MacThat Mail inserts images at their actual size by default, and that when other sizes are available you can choose one from a pop-up menu.A sent folder. Whatever size you picked is now the client's copy.
Mail on iPhoneNothing this page will claim. Apple's iPhone Mail attachment page did not return its text to us on 23 September 2026, so we cite no behaviour for it.Same as above, with less certainty about what you sent.

Read that table carefully, because the silences are the interesting part. An absence of documentation is not a guarantee that nothing happens to a file. It is only an absence of documentation. If your delivery plan depends on a behaviour that the vendor never wrote down, your delivery plan is a rumour.

Why a quick send is not client delivery

Set the file question aside for a moment. Even if every one of these routes moved a perfect copy, they would still fail at the job, for four reasons that have nothing to do with pixels.

  • No record of what was sent. Three months later the client asks for "the one from the garden." You are now scrolling a message thread trying to reconstruct your own delivery.
  • No re-send. Clients lose files. They change phones, they clear a thread, they never saved the attachment in the first place. Every one of those turns into you doing the whole job again by hand.
  • No proofing round. A client picking favourites out of a message thread is picking from copies, in an interface with no way to mark anything. The picks come back as text. You then translate text into filenames.
  • A resized copy is indistinguishable once it lands. This is the one that bites. Nothing in an inbox or a thread tells anyone which version of a photo they are looking at. The client cannot tell, and neither can you, and they will take that copy to a print shop.

None of that is an argument that the quick routes are broken. They are fine for a teaser. They are not a handoff, and the difference only becomes visible at the exact moment it is expensive.

Step one: get the files off the phone without an automatic conversion

Apple documents that when you transfer media to a computer over USB, files may be converted automatically, and that enabling Keep Originals prevents that conversion so the original HEIF and HEVC files transfer instead.

That single setting is the difference between starting your edit from what the camera recorded and starting it from something the transfer decided to make for you. Turn it on before you plug in, not after you notice.

It also sets up the next step. When you upload to clientgallery.io from a browser, the browser compresses each photo into a proof JPEG of roughly 0.6 MB before it is hosted, which is what keeps a large gallery quick to open on the client's phone. Starting that upload from converted files rather than from your chosen export is how a delivery quietly stops being the one you intended.

Step two: export the file you meant to send

Once the photos are on the computer, exporting is a deliberate act rather than a side effect. Apple documents that Photos on Mac can export the untouched original, and that its export offers a JPEG quality setting, a size menu, a colour profile choice and an option for IPTC metadata.

Two exports usually cover a job. A viewing export for the gallery the client will scroll on a phone, and a delivery export of the finished files at full resolution. Keep them separate in your own folders, because the moment they mix, you are back to the problem where nobody can tell which copy is which.

Colour profile is the setting most often skipped and most often regretted, since the client is going to open these on a phone screen you have never seen. If that is the part you care about, it is a topic of its own.

Step three: send one link, not a pile of attachments

A gallery link solves the four failures above at once, because the thing you send is a location rather than a copy. Re-sending is sending the same link again. The record of what the client received is the gallery itself.

On clientgallery.io that is one plan at $10 a month or $100 a year. The client opens the link with no account and no app to install, which matters enormously when the client is a sixty-year-old father of the bride on a borrowed phone. Galleries sit on your own subdomain with no platform branding on them, and hosted galleries never expire.

Unlimited is meant here under fair use, and the ceilings are published rather than buried: 1,000 photos per gallery, 250 GB of proofs per paid account, and 5 GB on a free account. Full-resolution delivery is a separate paid step. You upload a full-resolution ZIP per gallery, it stays live for three days per handoff, it can be re-uploaded any time you need to hand it over again, and an account holds up to 100 GB of standing ZIPs. Proofs are for choosing and are sized for fast viewing. The ZIP is the real file.

There is also a record on the studio side. The account-wide dashboard counts gallery visits, unique visitors, photo views, favourites, picks sent, ZIP downloads, shares and time spent, along with a mobile, desktop and tablet split. Per gallery, the studio tile carries an opened indicator so you can filter for the clients who have not looked yet. That is the thing a message thread can never give you.

What the phone is genuinely good for here

Nothing above says the phone is useless in this workflow. It says the quick sends are the wrong shape for a handoff. The phone is excellent at the receiving end.

Your client will almost certainly open the gallery on a phone, choose favourites on a phone, and forward the link to a relative from a phone. Design for that. Cull before you publish so the scroll is short, write a gallery name a human can recognise in a notification, and tell them plainly how many to pick.

And send the link itself however you like. Messages is a fine way to deliver a URL. The point was never that texting your client is wrong. The point is what travels in the text: a link that stays current, rather than copies that immediately start drifting out of date.

Sources

Product figures on this page (price, gallery and account ceilings, proof size, full-resolution ZIP behaviour) are clientgallery.io's own, verified in the product on 23 September 2026.

Frequently asked

Does sending photos from an iPhone reduce their quality?

It depends entirely on the route, and Apple documents less than photographers assume. Apple's Messages pages say nothing about image quality, compression or file size, and its AirDrop pages say nothing about quality, compression or metadata. Mail on Mac is the one Apple is explicit about: it inserts images at their actual size by default and offers a size chooser from a pop-up menu when other sizes are available. Checked 23 September 2026.

Should I switch my iPhone to Most Compatible?

That is a capture setting, not a delivery plan. Apple documents HEIF and HEVC as the default High Efficiency capture on supported models, and Settings, Camera, Formats, Most Compatible captures JPEG or H.264 instead. It changes what lands in your camera roll. It does nothing about having a record of what you delivered.

Why do my photos change format when I move them to my computer?

Apple documents that when you transfer media to a computer over USB, files may be converted automatically, and that enabling Keep Originals prevents that conversion so the original HEIF and HEVC files transfer instead. Turn it on before you plug in.

Is AirDrop good enough to deliver a client shoot?

Apple's AirDrop pages describe only how to send and receive between nearby Apple devices, and make no statement about quality, compression or metadata, so this page makes no claim either way about the file. The practical objection is different: both people need to be in the same room with Apple hardware, and afterwards you have no record, no re-send and no place for the client to choose.

What does my client need to open the gallery?

A browser. The link opens on whatever device they own, with no account to create and nothing to install, which matters when the person you are delivering to is not the person who booked you. Uploads are compressed in the browser into proof JPEGs of roughly 0.6 MB each before they are hosted, so a long gallery still scrolls quickly on a phone.

How does the client get the real, full-resolution files?

As a separate paid step, not from the proofs. You upload a full-resolution ZIP for the gallery, it stays live for three days per handoff, and you can re-upload it any time the client needs it again. An account holds up to 100 GB of standing ZIPs. Proofs are sized for fast viewing; the ZIP is the file a print shop should see.

What does clientgallery.io cost, and what are the limits?

One plan at $10 a month or $100 a year. Unlimited under fair use, with the ceilings published rather than buried: 1,000 photos per gallery, 250 GB of proofs per paid account, and 5 GB on a free account. Hosted galleries never expire.

Your client galleries, under your name

Branded galleries, client selections and a Lightroom Classic workflow. Start with your first gallery, then compare the current plan. Full-resolution delivery is a separate handoff with its own limits and conditions.

Create your studio

Related guides

How to Send Photos to Clients From an iPhone