DROP logoDROP中文
DROP / FILE TRANSFER NOTES

How to send original photos and verify the downloaded files

Send the image files from the camera export or project folder. A thumbnail lets the editor recognize a shot. To check that the original arrived intact, download the file and compare its SHA-256 with the sender’s copy.

By DROP · Reviewed · Published
Send a file

What should I send from the field?

  1. Select the originals you want the editor to keep. If filenames repeat across camera cards, keep the card folders and select their parent folder in a browser that supports folder upload. Each DROP transfer allows up to 10 GB in total and 1,000 files.
  2. Upload the batch and sign in to get the download link. Send the link with the expected file count and the expiry shown on the transfer. If you also need a quick reference, include a small contact sheet named separately.
  3. The recipient can open the active link without an account and download the originals individually or in one ZIP. Extract the ZIP into a new folder and check the files before moving them into the project archive.

Will 1,000 original photos fit in one download link?

Count the files in the export folder and check their combined size. DROP accepts up to 1,000 files totaling up to 10,000,000,000 bytes per transfer. At 8 MB per photo (8,000,000 bytes), 1,000 photos fit. Select one XMP sidecar as well and the count reaches 1,001. At 12 MB each, those 1,000 photos already total 12 GB.

We selected 1,000 different 4,000 × 3,000 JPEG test charts in a local copy of DROP. Together they weighed 229,106,347 bytes. A client in a fresh, signed-out browser downloaded one ZIP. All 1,000 filenames and SHA-256 hashes matched. With the same photos plus one XMP, the file picker showed the 1,000-file limit before uploading. Real camera exports can be much larger than these color charts.

For a large shoot, keep each card’s images and sidecars together and split the delivery at a card or project boundary. Our offline checker counts a folder and its subfolders, including hidden files. Compare its totals with the browser selection before sending. Send the editor the deadline shown on each link along with the batch name.

Check the 1,000-file ZIP and the rejected 1,001-file selection (JSON)

Check a photo folder locally with Python (English and Chinese instructions)

How do I compare my photo with the downloaded copy?

Here is an example for a file named Frame-01.tif. Open a terminal in the folder containing the file. On macOS, run shasum -a 256 Frame-01.tif. On Windows, open PowerShell and run Get-FileHash -LiteralPath Frame-01.tif -Algorithm SHA256.

Do this once on the sender’s original and once on the recipient’s extracted file. Compare the full 64-character hash, ignoring letter case. If the hashes differ, check the filename, card folder and export version together. For a full batch, repeat for every expected file.

PowerShell command reference

Why did a 69 MB TIFF show up as 72.0 MB?

Our first TIFF was 72,000,140 bytes. The upload queue divided by 1,024 twice and rounded to 69. The recipient view divided by one million and showed 72.0. Both screens labeled the result MB. The file had the same SHA-256 at both ends.

On 20 November 2026 we sent 14 synthetic TIFF charts and one PNG, totaling 1,008,005,931 bytes. We repeated the browser handoff with a fresh signed-out recipient. In each run all 15 files in the ZIP matched the originals by name, size and SHA-256. We used the released app and isolated storage on one Mac. Delivery time across networks needs a separate test on the sender’s and recipient’s connections.

Download the two test results and all 15 file hashes (JSON)

Generate the same test charts and verify a ZIP with Python

Read as Markdown · RSS