Why RAW files are big and why that matters

RAW files are unprocessed sensor data: more detail and latitude for editing than JPEG, but much larger. A single RAW can be 25–80 MB or more depending on camera and resolution; a full shoot can be tens or hundreds of GB. Sending them means moving large single files or large batches without losing quality. Compressing or re-encoding defeats the point—you lose the flexibility and quality that make RAW useful. So the goal is transfer at full size, not “squeeze it to fit.”

Why email doesn’t work

Email attachment limits are typically 20–25 MB per message. One RAW can exceed that; a set of RAWs is out of the question. Email is not a realistic option for RAW delivery. You need a method built for large files.

What works for RAW over 2 GB

Link-based transfer
Upload the file or folder to a service that supports large transfers. You get a link; the recipient downloads. No attachment limit. What matters:

Per-file limit – Can you send a single 5 GB or 10 GB file? Some services cap single files (e.g. 2 GB or 5 GB) even if the total transfer is higher. For big single RAWs or packed ZIPs, check the per-file cap.
Per-transfer limit – Total size per “send” (e.g. 10 GB, 50 GB, 250 GB). A batch of RAWs or a ZIP of a full shoot must fit within this.
Retention – How long the link stays valid. Give the recipient enough time to download; remind them before expiry if needed.

Cloud storage with sharing
Upload to Google Drive, Dropbox, OneDrive, Proton Drive, or similar. Create a share link to the file or folder; send the link. Suited if you already use that cloud. Check the plan’s storage and any per-file or bandwidth limits. For very large single files (e.g. 10 GB+), confirm the provider allows it.

Dedicated transfer services
Services built for “send large files” often support high per-file and per-transfer limits (e.g. tens to hundreds of GB). Many offer optional password and expiry. Use when you want a one-off delivery without maintaining a shared folder.

What to avoid

Compressing RAWs to “fit” – ZIP may shrink RAWs a little, but the real problem is size. Compressing to meet email or a low cap usually means you’re not sending full quality. Prefer a service that allows the full size.
Converting to JPEG to send – That’s a delivery format, not “sending RAW.” Fine for previews; not for handing off originals.
Assuming “unlimited” without checking – Read the per-file and per-transfer limits. “Unlimited” sometimes means “no fixed cap” but with other constraints (e.g. retention, speed, or account type).

Practical checklist

Single file over 2 GB – Use a service whose per-file limit is above your file size (e.g. 5 GB, 10 GB, or no stated per-file cap).
Batch (folder or ZIP) – Check per-transfer limit and retention. Send one link if possible; otherwise split into multiple transfers.
Sensitive or client work – Prefer HTTPS, optional password on the link, and expiry. Check the provider’s privacy policy if it matters.
Recipient – Tell them the link and expiry. If the link is password-protected, send the password separately (e.g. different channel or message).

Summary

To send RAW photo files bigger than 2 GB: don’t use email and don’t compress away the quality. Upload to cloud storage or a transfer service that supports large per-file and per-transfer sizes, get a link, and send the link. Check both per-file and per-transfer limits, set an expiry that gives the recipient time to download, and use optional password protection if the content is sensitive. The right tool is the one that allows your actual file sizes and batch sizes without squeezing them down.