The best way to send job photos to a customer is a curated per-job gallery link rather than a stream of texts, and it works because of a decision you make before you send anything: you are keeping two separate photo sets, not one. There is the complete archive, which exists to protect you and which the customer almost never sees, and there is the short edited update, which exists to reassure the customer and which is a small subset of the archive.
Almost every guide on this topic collapses those two into one workflow. Search the question and you get vendor blogs telling you to swap your text thread for their gallery link, and photography-industry posts about client proofing never written with a trades business in mind. One page currently ranking cites a 2024 Photographic Licensing Association study about freelance photographers and unauthorized image use, then admits in the next paragraph that the figures come from a different industry. That is the quality of advice sitting on this query.
Here is what actually decides whether your photo workflow is worth anything: what you shoot before you start, what you leave out of the set you send, and whether the channel you send through keeps the metadata that makes a photo a record instead of a picture.
Your photos are doing two jobs, and they conflict
One set of photos exists to answer the question "did you do the work and did you break anything." The other exists to answer "how is it going." They want opposite things.
The evidence set wants to be exhaustive, unedited, timestamped and boring. Every crack in the driveway. The state of the basement before you touched it. Nobody wants to look at it and that is fine, because its entire value is that it was complete on a date you can prove.
The update set wants to be short, sequenced and legible. Five photos that tell a story. If the customer has to ask what they are looking at, the update failed, and you will spend twenty minutes on the phone explaining a photo of an open wall.
Contractors who send the archive as the update create their own worst day. The customer scrolls past a shot of exposed subfloor taken mid-demo, panics, and calls. You have generated a support conversation with a photo you took to protect yourself. Every photo you send is a question you volunteered to answer.
So the rule underneath all six below: shoot for the archive, publish from it.
Rule 1: Shoot the pre-work walk before the tools come off the truck
This is the photo set with the highest expected value and the lowest send rate, and commercial crews already treat it as mandatory. In a thread on r/Construction that pulled over 1,100 upvotes, the top comment described the standard on commercial jobs: walk a 500 foot radius, photograph the entire work zone before work begins, and file a pre-work report.
The reason is not paranoia. It is that the accusation arrives after the fact and you cannot go back. One contractor in that same thread put the timing perfectly: "as I was taking pictures before we had the tools off the truck, the customer tried telling me 'That wasn't cracked before!'" He was still photographing when the claim was made.
The best framing came from a comparison to tow truck drivers, who walk the car with a rolling video and narrate what they see out loud, the date, the time, the plate, the visible damage, before touching anything. A painter in the thread described his version: he walks the job first, photographs existing paint on floors, windows and ceilings, then points it out to the customer directly.
That last step matters more than the photo. Showing the homeowner pre-existing damage on day one converts a future dispute into a shared observation.
Watch out
The pre-work set is the one you do not send in the update. If you email a homeowner nine photos of their existing scuffs before you start, you have opened a conversation about their house, not about your work. Shoot it, file it, and keep it in reserve.
Rule 2: Send a curated set, not the roll
The competing advice on this question is "send a gallery link instead of a text dump," which is half right and stops too early. A gallery of forty unsorted photos is still a dump. It just loads in a browser.
A useful update set for a residential job is roughly:
- One wide shot so the customer can orient themselves.
- Two or three shots of what changed since the last update.
- One close-up of something done well: a clean solder joint, a flashing detail, a level tile course.
- One shot of anything they will notice and worry about, with a caption that explains it before they ask.
That fourth item is where most of the phone calls disappear. A photo of a wall opened up with the caption "this is normal at this stage, closing back up Thursday" costs you eight seconds and saves the twenty minute call.
Sequence matters as much as selection. Group before, during and after so the same area appears next to itself. A contractor who started out as a construction site photographer described the structure he still uses: job number at the top, then before, during and after subfolders, and the whole organized set handed to the client at the end of the project. Handing over the organized record is a closing gesture almost nobody makes.
Cadence beats volume here, the same way it does with every other kind of client update. We went through the underlying evidence on that in our breakdown of how to keep customers updated during a job, and the finding holds for photos: predictability is what reduces inbound calls, not frequency.
Rule 3: Pick the channel by what you need the photo to survive
This is the part no contractor guide covers, and it changes what your photos are worth.
A photo's value as a record comes from its embedded EXIF metadata: the capture timestamp, the camera, and often the GPS coordinates. Sending platforms treat that metadata completely differently, and the differences are not intuitive. A 2026 test of twelve platforms by SammaPix found the following.
| Channel | Metadata for the recipient | Practical read |
|---|---|---|
| iMessage | Preserved, including GPS | The recipient gets your full original file |
| Preserved, including GPS | Same. No mail client strips EXIF | |
| WhatsApp, photo mode | Most EXIF stripped, GPS removed | Fine for reassurance, useless as a record |
| WhatsApp, document mode | 100 percent preserved | Sends your exact GPS whether you meant to or not |
| Facebook and Instagram | Stripped from the public copy | Anyone downloading your work gets a bare file |
| Signal | All metadata stripped, nothing stored | The strongest privacy option, the weakest record |
| Telegram | Not stripped by default | Preserves more than people expect |
Two things fall out of that table for a trades business.
First, if your archive lives in a chat thread, you have a metadata problem you cannot see. A green bubble MMS thread resizes images on the way out, and WhatsApp in normal photo mode drops the GPS. The picture still shows the work. It no longer shows where and when, which is exactly the part a disputed claim turns on. Your archive belongs in storage you control, and the chat thread is a copy, not the original.
Second, the table is a privacy warning in the other direction. Every job photo taken at a customer's house carries their address in the file, and iMessage, email and WhatsApp document mode all hand that over intact. Forward a job photo to a supplier or a prospect to show what you can do and you may be forwarding a customer's coordinates with it. Posting to Facebook or Instagram is safer there, because those platforms strip metadata from the copy the public can download. Even that is not absolute: Reddit had a bug, HackerOne report #1069039, where iPhone HEIC uploads preserved GPS in the converted file it served to everyone. Decide what the file should carry before you send it rather than trusting the pipe.
Tip
Practical version: send the customer a link or an iMessage. Keep the master copy in your own storage. Never treat a WhatsApp thread or a Facebook album as the place your evidence lives.
Rule 4: File by job number, and keep a copy you own
Ask contractors how they store photos and you get two answers that work and one that does not.
The one that does not is the phone camera roll. A commercial roofer described the endgame candidly: the photos clog his phone memory and every few months he does a major purge, with a separate folder for the promotional shots so the good ones survive the deletion. A landscaper in the same thread was blunter about the retrieval problem: "Keeping everything in your phone gallery or WhatsApp works... until you need one photo from 18 months ago."
The two that work are a shared album per job and a cloud folder per job. One operator described a complete Google Photos workflow: an album per job, extra albums for phases on larger jobs, photos deleted off the phone once filed, link sharing to clients and subs, and crew leads adding to his albums so daily progress lands without him chasing anyone. Another uses Dropbox filed by work type, city, year and customer surname.
On the by-job versus by-client question, operators converge fast. File by job. The Google Photos user above spelled out why: repeat customers turn a client folder into a jumbled mess for every department that has to touch it, and a job number keeps billing, purchase orders and photos on the same key. His scheme is a year plus a sequence, so 260001 is the first job of 2026. If you use a naming convention for individual files rather than folders, front-load the date so they sort chronologically, in the style of 2026-09-06-kitchen-north-wall.jpg.
One more thing worth building in early. A contractor warning about photo storage inside job software put it memorably: "The moment you marry a CRM, they make that shit unpleasant to divorce." Whatever job software you land on, keep a parallel copy in storage you own. The photos are a business asset with a ten year tail, and export is exactly the feature vendors deprioritize.
If your photos live in one place, your invoices in another and your job notes in a third, the archive only works when you personally remember to move files. We build custom CRM systems that tie photos to the job record automatically, so the crew shoots and the record assembles itself.
Rule 5: Put the photo permission in the contract
You will eventually want to post a finished job, and eventually a customer will not want you to. In a roofing sales group, a contractor described exactly that: a client asked him not to post pictures of their house on Facebook.
There is no clean industry answer to fall back on. A home inspector raised the same question about marketing use and reported that ASHI advises getting permission but would not commit on whether it is a legal requirement or simply CYA. That ambiguity is the reason to stop treating it as a judgment call.
Put a clause in the contract. Something along the lines of: the contractor may photograph the work for documentation, warranty and marketing purposes, and photographs will not identify the client's name or street address without separate written consent. Give the customer a line to opt out of the marketing half while keeping the documentation half, because you need the documentation regardless of how they feel about Instagram.
Three practical notes on this:
- Strip identifying detail from marketing photos by default. House numbers, plates, mail. That removes most of the objection before anyone raises it.
- Ask at handover, not mid-job. The customer is happiest the moment the work is finished and they can see it.
- Feeding a Google Business Profile compounds the consent question, because those photos are public and permanent. We covered using them in Google Business Profile photos that get calls.
Rule 6: Treat the photo set as accounts receivable
The most valuable use of your archive is not marketing. It is collections, and it is the angle nobody in the search results for this question writes about.
A contractor on r/Contractor posted about a long time customer who ghosted him on the final payment. He gave notice that they had 72 hours to pay or he would file a mechanics lien, they did not respond, and he filed. He was paid, start to finish, in about a week. The lien cost him just under $500. He listed three things that made it work: an online invoice with a daily pay option, a signed estimate with a deposit on a system that timestamped the signature, and "photos of the job from start to finish. Videos of the project from start to finish."
That is the whole argument for the archive in one post. The photos did not win a case in court. They made the case obviously unwinnable for the other side, which is why it took a week instead of a year.
The same pattern shows up in the dispute threads. Asked how to protect against post-completion complaints, the top answer on r/handyman put photos second only to a signed detailed contract, alongside dated change orders for every "one more thing."
So attach the photo set to the moment money changes hands. Milestone photos go out with the milestone invoice, not separately. That makes the invoice self-justifying and timestamps your position before there is a disagreement. If the final payment comes up short, the archive turns the conversation into arithmetic, which is the approach we laid out in what to do when a customer short pays the final invoice.
What this should actually cost you
Photo software pricing in this category is genuinely hard to pin down, and it is worth saying so plainly rather than repeating a number.
CompanyCam is the default recommendation in every contractor thread and earns it on the product: automatic timestamps, GPS tagging, project organization, annotations, before and after galleries. What is not clear is the price. Public sources disagree with each other and sometimes with themselves. One review roundup lists the Pro plan at $79 per user per month in one table and $24 to $49 per user per month in another. The fact that repeats consistently, and matches what operators say, is the seat minimum: most plans require three paid users.
That minimum is the actual decision point, and it is why the answer differs by size.
| You are | The photo stack that fits | Why |
|---|---|---|
| Solo, one truck | A shared album or cloud folder per job | Free, link sharing built in, no seat minimum to work around |
| Two or three people | Shared album per job, plus a naming convention everyone follows | The constraint is consistency, not features |
| Four or more, or crews on separate sites | A photo app that tags job, time and location automatically | You are now paying to remove the step where someone forgets |
| Running job software already | Photos inside the job record, plus a parallel copy you own | Avoids a second subscription and a second place to look |
The trigger for paying is not headcount on its own. It is the day photos stop reaching the right job because the person who took them is not the person who files them. Until then a paid photo tool is buying you organization you could get for nothing.
If you are also weighing a client portal so customers can look without asking, that is a different purchase with different economics, and we compared the realistic options in client portal software for contractors.
Note
Watch the free tier ceiling. Consumer cloud storage counts photos against the same allowance as your email and documents, and a photo heavy trade like roofing or restoration will hit it faster than a service trade will. Plan for the paid storage tier before the day your crew cannot upload.
The 20 minute setup
If you do nothing else this week, do this.
- Create a job number scheme. Year plus sequence. 260001, 260002. Use it on the estimate, the invoice and the photo folder.
- Make one folder or album per active job, named with that number and the address.
- Add your crew leads to the albums so they upload directly instead of texting you photos to file.
- Set the pre-work walk as a rule, not a habit. Nothing comes off the truck until the walk is shot. It takes four minutes.
- Add the photo clause to your contract template. One paragraph, one opt-out line for marketing use.
- Pick your update cadence and say it out loud at the start of the job. Two named days beats improvising.
- Attach the milestone photos to the milestone invoice. Same email, every time.
Steps 1 through 3 take about twenty minutes. Steps 4 through 7 are habits, and they are the ones that pay.
The short version
Send a curated per-job link, keep an uncurated archive, and never confuse the two. Shoot the pre-work walk before the tools come off the truck, because it is the only set that proves what was already broken. Choose the channel deliberately: iMessage and email preserve the original file, WhatsApp photo mode does not, and social platforms strip the metadata from the copy anyone can download. File by job number so repeat customers do not turn your archive into a pile. Get the marketing permission signed instead of assumed. And send the photos with the invoice, because the highest return on a job photo is not a referral, it is a payment that arrives without an argument.
The contractors who get this right are not the ones with the most expensive photo app. They are the ones who decided in advance which photos are evidence and which are communication, then stopped sending the first kind to people who asked for the second.