A wedding photographer has just finished exporting previews, the cards are safely on the desk, and one problem remains: 40 GB of CR3 or ARW files must reach a client or second shooter by morning. The upload window is long, the hotel Wi-Fi is unreliable, and a simple shared link may leave the recipient with files they can't preview or even open.
Learning how to upload RAW files is therefore about more than moving large bytes to a server. A dependable workflow protects the originals, survives interruptions, preserves organization, and gives clients a usable way to review the photographs.
Table of Contents
- Why RAW Uploads Are Harder Than They Look
- Preparing RAW Files Before You Upload
- Choosing the Right Upload Method for Large Sets
- Delivering RAW Files Through SendPhoto Galleries
- Troubleshooting Common RAW Upload Errors
- Final Checklist and Archival Considerations
Why RAW Uploads Are Harder Than They Look
RAW files preserve substantially more sensor data than JPEG files, which gives photographers greater flexibility during editing. That flexibility has a storage cost. Sony lists full-frame RAW files at 100 MB uncompressed, 62 MB with lossless compression, and 52 MB compressed, while APS-C RAW files can be 43 MB uncompressed, 30 MB lossless, and 22 MB compressed in the cited camera documentation, summarized by this RAW format explanation.
At that scale, a modest shoot becomes a serious transfer job. 1,000 full-frame uncompressed RAW images total about 100 GB, while 1,000 compressed APS-C RAW images still require about 22 GB of transfer capacity. Compression choices can therefore change the storage and upload requirement by more than two times within the same camera class.
The recipient problem
A RAW file isn't automatically a client-ready photograph. Camera manufacturers use formats such as CR3, ARW, NEF, and other proprietary variants, and the recipient needs compatible software to interpret the sensor data. A Canon community discussion captures the practical issue: a RAW file isn't really an image for ordinary viewing until software converts it, which is why delivery workflows commonly pair originals with JPEG previews. See the Canon discussion of uploading RAW images for that distinction.
A client may download a folder successfully and still be unable to select images from it. File transfer has worked technically, but delivery has failed commercially. Clients usually need thumbnails, a clear gallery structure, and instructions for opening originals in Lightroom, Capture One, or another compatible application.
Why ordinary links struggle
Consumer file-sharing links are often designed around occasional documents or small image batches. Large RAW collections expose problems with browser memory, session expiration, hidden per-file limits, and weak retry behavior. Dragging hundreds of files into a browser can leave the photographer watching a progress bar that fails near completion, forcing the entire batch to start again.
The right question isn't “Where can these files be stored?” It's, “How will the recipient review, download, and use them after the transfer?” A professional workflow separates original RAW storage from client-facing previews, then connects both through an organized gallery.
Preparing RAW Files Before You Upload
The upload should begin with the memory card, not the browser window. Use a card reader or direct camera connection to copy files to a working drive, then organize the shoot, apply metadata, and create a backup before processing. Photography workflow guidance in the Digital Photography Workflow Handbook.pdf) treats ingest, tagging, and backup as the controls that protect RAW integrity.
A practical structure might look like this:
- Parent folder:
2024-06-15_Smith-Wedding - Camera folders:
RAW-AandRAW-B - Shoot segments:
01_Preparations,02_Ceremony,03_Portraits,04_Reception - Working exports:
PREVIEWSandSELECTS
The date-first naming convention sorts naturally and keeps the client name visible. Separate camera folders preserve the original card boundaries, which helps when a missing sequence or duplicated filename needs investigation.
Ingest, verify, and back up
Copy the complete card contents before culling. Compare file counts and inspect the destination folders before formatting any card. A second local copy should exist before the photographer begins editing or uploading, because a failed transfer must never be the only remaining copy of a shoot.
For memory-card emergencies, photographers can keep CTF Mobile Phones data recovery tips available as a practical reference. Recovery advice is most useful before a card is repeatedly written to, so prevention still matters more than rescue.
Metadata belongs in the preparation stage. In Photo Mechanic or Lightroom, apply a preset containing copyright, contact details, and basic keywords. Embed information into the files where the format and software support it, then confirm that the metadata appears as expected. Color labels and ratings can also help identify selects, but the receiving application may interpret them differently, so a separate SELECTS folder or preview collection is safer for client communication.
The video below can supplement the card-ingest and file-organization routine.
Native RAW or DNG
Native files such as CR3, NEF, and ARW retain the camera maker's original format and may preserve proprietary metadata or workflow features that certain applications expect. DNG offers a more archival-oriented alternative. The Library of Congress description of DNG identifies it as a publicly available archival RAW format built on TIFF 6.0 and used to store and interchange camera RAW images.
Adobe states that DNG files are generally 15–20% smaller than equivalent RAW files with minimal quality difference, as explained in its DNG versus RAW comparison. DNG can also embed the original RAW file inside itself. Conversion makes sense when archival consistency and reduced transfer size matter, but native RAW is the safer choice when a client's established editing pipeline depends on camera-specific data.
Choosing the Right Upload Method for Large Sets
A 50 GB wedding set needs a method that matches both the file volume and the network. Browser drag-and-drop is convenient, but it places too much responsibility on one browser session. Desktop uploaders generally provide better continuity, while ZIP archives trade individual-file flexibility for a more structured transfer.
| Method | Best For | Max Reliable Size | Resumable | Connection Sensitivity |
|---|---|---|---|---|
| Browser drag-and-drop | Small batches and quick previews | Small to moderate batches | Depends on the service | High |
| Desktop uploader | Multi-gigabyte RAW deliveries | Large sets supported by the platform | Usually, when the service supports it | Lower |
| Batch ZIP archive | Preserving folder structure in one package | Limited by archive and platform caps | Depends on the service | Moderate to high |
Browser uploads
A browser is acceptable for a small folder, particularly on stable fiber or cable internet. It becomes less attractive as the batch grows because hundreds of file handles, browser memory use, authentication sessions, and server-side timeouts all become failure points. Mobile hotspots add another layer of sensitivity because coverage and throttling can change during a long upload.
Uploading 50 to 100 files per batch is often more manageable than dragging an entire wedding directory into a browser. That approach doesn't make the browser resumable, but it limits the damage when a session fails.
Desktop uploaders
A desktop application is the practical workhorse for large deliveries. Resumable or chunked transfers divide the job into recoverable pieces, so a connection drop doesn't necessarily erase hours of progress. One independent analysis reports that resumable uploads can reduce failure rates by up to 70% compared with standard multipart uploads, while another finding in the same research area reports that chunked uploads can reduce downtime by over 40%. Those figures come from the Firebase Cloud Storage upload analysis, and actual results depend on the service and network.
Practical rule: For anything beyond a modest batch, choose resumable transfer over a single browser session.
Wired Ethernet is preferable to Wi-Fi for a long upload. Fiber usually offers the strongest margin, cable is often workable, and a mobile hotspot should be treated as a fallback unless the set is small or the upload can run unattended.
ZIP archives
A ZIP archive can preserve folder structure and reduce the number of upload operations. It also creates a single point of failure: if the archive becomes corrupt or exceeds a platform's file cap, the complete package may need to be rebuilt. RAW files often compress modestly because camera data may already use efficient encoding, so zipping shouldn't be assumed to produce a dramatic size reduction.
For a structured handoff, ZIP works well when the platform accepts the resulting archive and the recipient understands how to extract it. For client review, however, a gallery with previews is usually more useful than a downloadable archive alone. The bulk file upload guidance provides additional context for handling large batches.
Delivering RAW Files Through SendPhoto Galleries
A RAW delivery gallery needs two layers: the original files for download and converted previews for viewing. SendPhoto supports bulk uploads that can include RAW images, so the photographer can preserve the source files while giving the client a gallery experience built around previews rather than unsupported camera formats.
Start by creating a gallery for the shoot and selecting upload limits that accommodate the complete set. Upload the organized folders rather than a flattened stream. A wedding gallery can use folders such as Ceremony, Portraits, and Reception, which gives clients a navigable route through a large collection.
Configure viewing and downloads
Watermarks belong on the client-facing JPEG previews, not inside the original RAW data. A subtle preview watermark protects displayed work without altering the source file that a client or editor may need for post-processing. Original downloads should be enabled only when the agreement calls for them. Preview-only access may be appropriate during selection, while full-resolution original downloads suit an approved final handoff.
Set gallery permissions deliberately:
- Preview access: Let clients browse and mark favorites without requiring access to originals.
- Original downloads: Enable per-image or full-gallery downloads according to the delivery agreement.
- Password protection: Add a password when the gallery contains private family, wedding, or commercial material.
- Expiry controls: Set an expiry date so a large RAW library isn't hosted indefinitely.
- Delivery notes: Add a README-style text block explaining that CR3, ARW, and other RAW files need compatible software.
The SendPhoto getting started guide can help with the basic gallery setup.
Explain the file handoff
A client who has only handled JPEGs may not know what to do with a CR3 or ARW file. Delivery notes should state which applications can open the files, how to download the originals, and where the JPEG previews fit into the workflow. If the client only needs to choose favorites, the gallery preview should remain the primary interface.
This separation resolves the hidden delivery gap. The photographer uploads RAW bytes once, while the client receives a polished way to review images and a controlled path to the originals. SendPhoto is one gallery option for combining bulk RAW upload, preview presentation, passwords, watermark controls, download permissions, and expiring delivery links.
Troubleshooting Common RAW Upload Errors
Large RAW transfers usually fail for a recognizable reason. The fix depends on whether the problem comes from the network, the browser, the platform's limits, or the files themselves.
| Error Type | Root Cause | Fix |
|---|---|---|
| Timeout | Session or server-side transfer limit | Split the set into folder chunks or use resumable desktop transfer |
| Stalled progress | Connection interruption or weak retry handling | Restart through a resumable uploader rather than beginning again |
| Corrupted file warning | File exceeds a platform cap or archive integrity failed | Check per-file limits and verify files with checksums |
| Browser crash | Too many files loaded into one drag-and-drop session | Upload smaller batches |
| Throttled transfer | ISP or hotspot limits during sustained activity | Schedule overnight and use wired Ethernet where possible |
Per-file and per-transfer limits are often hidden until a large job reaches them. Recent transfer guidance recommends checking both limits, preserving folder structure, and using password or expiry controls. Some services advertise very large transfer capacities, but those limits vary materially between providers. The large RAW transfer guidance for files above 2 GB is useful for identifying those constraints before the upload begins.
A single 60 GB wedding set doesn't have to be one transfer. Split it into preparations, ceremony, portraits, and reception folders, or use a desktop uploader that resumes interrupted chunks. This makes it easier to identify the failed portion and reduces the likelihood that a server-side cap will block the entire delivery.
Checksum verification adds confidence when the files are critical. Generate checksums for the source folder, then compare them with the downloaded or uploaded copies when the platform and operating system support that workflow. A progress bar reaching 99% isn't proof of integrity, and a successful browser message isn't a substitute for opening representative files.
Final Checklist and Archival Considerations
A reliable RAW upload routine can be pinned beside the editing workstation:
- Ingest from the card: Copy the complete card contents through a card reader or direct camera connection.
- Verify the source: Compare file counts and inspect the folder tree before formatting cards.
- Apply structure: Use a date-based parent folder, camera-specific RAW folders, and shoot-segment subfolders.
- Add metadata: Embed copyright, contact information, and useful keywords before files leave the studio.
- Create a backup: Keep a second copy before culling, processing, or uploading.
- Choose the format: Retain native CR3, NEF, or ARW files, or convert to DNG when archival compatibility and smaller files justify it.
- Test the gallery: Upload a small batch and confirm previews, downloads, permissions, and file names.
- Launch the full transfer: Use a resumable desktop workflow for a large set and monitor the completed files.
- Confirm delivery: Download or inspect representative originals before treating the handoff as complete.
A digital asset management system can make the folder, metadata, backup, and retrieval stages easier to maintain. The DAM guide for photographers offers a useful framework for thinking beyond one-off transfer links.
DNG conversion can reduce equivalent RAW file sizes by 15–20%, according to Adobe's comparison, which can ease upload and client storage demands. Native RAW remains valuable when proprietary metadata or camera-specific editing behavior matters, so the archival decision should follow the client's software and the studio's preservation policy.
Before deleting local working files, maintain a 3-2-1 backup approach, with three copies, two media types, and one offsite copy. Cloud-native RAW workflows and edge processing may reduce upload friction over time, but file integrity, client compatibility, and organized delivery will remain the photographer's responsibility.
SendPhoto lets photographers upload full shoots in bulk, including RAW files and HD video, then deliver them through password-protected, mobile-ready galleries with previews, download controls, watermarks, and expiring links. Set up a controlled RAW handoff for the next client by visiting SendPhoto.