There is a moment, usually eighteen months after the job, when a photograph stops being a note to yourself and becomes evidence. A homeowner says the crack was not there before. An insurer wants to know the state of the sheathing on the day it was opened up. A general contractor withholds payment over work you know was finished.
At that moment, one question gets asked about your photograph that never came up before: has this image been modified?
If you drew an arrow on it, the answer is yes.
What “burning in” does
Most photo tools built for contractors let you mark up an image — an arrow at the damage, a box around the defect, a note with a measurement. Almost all of them do it by rendering those marks into the pixels and saving the result. Some keep the original alongside; plenty quietly replace it.
On screen the difference is invisible. In a dispute it is not:
- The file is no longer the file the camera produced. Its bytes changed after capture, and anybody looking closely can tell.
- Metadata is frequently stripped or rewritten in the process — capture time, coordinates, device. Exactly the fields that establish when and where.
- The mark-up itself becomes an assertion embedded in the record rather than a comment on it. Your foreman’s guess about the cause of the damage is now physically part of the photograph of the damage.
None of this makes an annotated photo worthless. It makes it a weaker artifact than the one you actually had, and you gave up the stronger one for a convenience.
Annotation belongs on a layer
The alternative is not complicated. Store the marks separately from the image and composite them for display.
The photograph is written once at upload and never rewritten. The arrows, boxes, text and measurements are a second record that points at it — this arrow, at these coordinates, drawn by this person, on this date. The viewer draws one over the other.
You get all of the same working benefits and none of the cost:
- Both versions exist, always. Send the annotated one to the crew who need to know where to look. Send the clean one to the adjuster. Neither is a reconstruction.
- Annotations are editable without touching the photo. Somebody drew the arrow in the wrong place; move it. The photograph is unaffected because it was never involved.
- The original keeps its metadata. Capture time and coordinates are intact because nothing rewrote the file.
- Who annotated what is its own record. Which is more useful than an anonymous arrow anyway.
Resolution is the other half of this
The second thing that quietly weakens a photo archive is downscaling. Storage costs money, so a lot of tools resize on upload — 2048 pixels wide is a common choice, and it looks perfectly good on a phone.
It also throws away the detail you would want to zoom into. The hairline crack, the serial number on the failed unit, the date stamp on the delivered material. None of that survives a resize, and you do not find out which photo needed it until the day somebody asks.
Full-resolution originals are expensive to keep. A busy crew adds tens of gigabytes a month and the archive is never deleted, because its permanence is the whole point. That cost is real and it has to be priced in rather than engineered away — but engineering it away is what a downscale is, and the person who pays for it is the contractor in the dispute two years later.
What to check in whatever you use
Whether or not that is us, three questions are worth asking your current tool:
- When I annotate a photo, can I still get the clean original back? Not a flattened copy — the file as uploaded.
- Do you downscale or compress on upload? “Unlimited photos” and “unlimited full-resolution photos” are different products.
- Are capture time and coordinates preserved on export? If the export strips them, your archive is only as good as your filing.
A photo archive is one of the few assets a small contractor accumulates that gets more valuable every year. It is worth being fussy about what it is made of.