Photo transfer

How it works

Phones hide the roll from a browser until the user grants access. HEIC from a phone does not open everywhere. A JPEG export loses edits. Burst sets and Live Photos are packages, not one file. Wifi beats cellular for a wedding roll. Resume matters because locks and radios kill long posts.

A second shooter exports 1,200 JPEGs, 6 GB, from a phone on venue Wi-Fi. The browser upload resumes twice and finishes. HEIC originals stay on the phone because the desk asked for JPEG. A later request for originals is a second transfer, not a missing download.

How it differs

Photo transfer is not RAW transfer. RAW is the sensor file. JPEG is a render. Sending one does not send the other.

Cloud photo libraries that 'optimize storage' upload a preview and keep the original on the device. The recipient of the library link may not get the file you think you shared.

Duplicate filenames across two card dumps overwrite on a case-insensitive desk. Prefix the card number.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• Count the finished object, not the first byte, before you close the ticket.