Large photo transfer

How it works

Thousands of small files want a ZIP or a folder manifest. A single TIFF for print wants the large-file path. HEIC versus JPEG is a format choice you make before the transfer. Wi-Fi or a cabled ingest beats a phone radio.

A 25 GB wedding roll is zipped to 24 GB and uploaded overnight. The couple's selects, 40 JPEGs, go by a separate link the same evening. The roll is the archive delivery. The selects are the preview. One link for both would have made the couple wait on 25 GB.

How it differs

Large photo transfer is not RAW-only. It includes JPEG rolls. RAW pages cover sidecars. This page covers volume.

Consumer share links that downscale photos 'for preview' are not this delivery. Disable the proxy if the contract is full resolution.

Duplicate detection that skips same-size files can drop a second card's IMG_0001. Turn it off or prefix names.

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.
• On a real ticket, write down the door, the byte count, and the clock.
• For large photo transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive large photo transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.