The gallery is edited, the client is waiting, and the delivery link looks ready to go. Then the upload stops halfway through, a final video refuses to attach, or an email bounces because the message is larger than the receiving system allows. The frustrating part is that the photographer may never have been told which restriction failed.
A file size limit is rarely one number. Per-file caps, total gallery storage, upload-frequency rules, browser behavior, operating-system constraints, and email attachment ceilings can all affect the same handoff. A wedding photographer sending many medium-to-large images faces a different risk from a commercial photographer delivering a single long video, even when both platforms advertise the same maximum upload size.
Table of Contents
- Why File Size Limits Matter on Delivery Day
- The Technical Layers Behind Every File Size Limit
- Comparing Platform Limits Photographers Actually Hit
- Email Attachment Ceilings That Block Client Handoffs
- How SendPhoto Handles Storage and Gallery Limits
- A Practical Workflow for Delivering Large RAW and HD Video Files
Why File Size Limits Matter on Delivery Day
A photographer can work through a full event without seeing any warning from the camera, editing workstation, or export application. The trouble often begins after the creative work is finished. A gallery may contain thousands of edited images, several large video files, and alternate exports for print, web, and social use. The delivery platform then applies its own rules, which may concern the size of one file, the total gallery, or the number of uploads allowed within a period.
The advertised maximum usually answers only one question: how large can an individual file be? It may not answer whether the account has enough storage for the complete shoot, whether the project allows enough files, or whether repeated batches trigger an upload quota. Those limits matter more for wedding and event work, where delivery volume is spread across many files rather than concentrated in one unusually large asset.
The limit chain photographers actually face
A reliable handoff has to survive several checkpoints:
- The source file: RAW images and high-resolution video can be much larger than the client's viewing copy.
- The export: Quality settings, dimensions, metadata, and codec choices change the size of every deliverable.
- The upload service: The service may impose a per-file limit, a storage allowance, a gallery limit, or an upload-frequency restriction.
- The browser and device: Large requests can fail because of unstable connections, memory handling, or outdated browser behavior.
- The client's delivery path: Email systems impose their own message and attachment ceilings, even when the original gallery is perfectly valid.
That chain explains why compressing files can help but won't solve every failure. A smaller archive may pass the per-file test while still exceeding the recipient's total storage or the sender's upload allowance. Photographers preparing files for limited local or travel storage can also use this practical guide to compress files for RV storage, provided the archive format and client requirements remain compatible.
Practical rule: Check the limit that applies to the complete handoff, not just the largest file in the folder.
Before delivery day, the useful questions are straightforward. What is the maximum per-file size? How much total storage remains? Does the platform limit file counts, galleries, or uploads within a period? Can clients download the original files, and will the delivery method work for video as well as still images? A platform that answers only the first question leaves the photographer exposed to the failure most likely to matter.
The Technical Layers Behind Every File Size Limit
A file can fit comfortably on a workstation and still fail during delivery because each layer in the path has different capabilities. The filesystem stores the file, the operating system exposes it, the application applies settings, the browser sends the request, and the email system may impose another ceiling when the photographer shares the result.
Filesystem capacity isn't the same as upload capacity
On Linux, file-size ceilings are often determined by the filesystem's on-disk format rather than the application layer. Legacy ext2 and ext3 limits vary by block size. With a 4 KiB block size, the maximum file size is 2^41 bytes, about 2 TB, while XFS supports files up to 2^63 bytes, about 8 EB. These figures come from openSUSE's filesystem documentation.
That distinction can matter in infrastructure decisions. Moving a workflow from ext3 to XFS can remove a hard 2 TB filesystem cap without changing upload code. A 32-bit operating system, however, creates an independent practical ceiling of about 2 TB, regardless of the filesystem's theoretical capacity. Storage design can therefore remove one obstacle while leaving another intact.
Application settings create the practical ceiling
Most photographers won't encounter an ext3 or XFS limit directly. They encounter the much lower threshold configured by the service receiving the upload. Microsoft 365 for the web allows PowerPoint edits up to 2 GB, but its documentation also notes a 60-second download timeout and a 100 MB cap for most embedded media. Those details show why transfer time and embedded assets can become the bottleneck before the storage layer does. The figures are documented in Microsoft's file-size FAQ.
Nextcloud provides another useful example. Its default upload limit is 512 MB, and its documentation says the limit can only be raised as far as the filesystem and operating system allow. It also identifies hard client-side ceilings below 2 GB on 32-bit operating systems and older browsers. A service can therefore expose a generous server setting while the client still fails earlier.
Browser and email behavior finish the chain
Browsers have to hold, transmit, and recover large requests over ordinary networks. A technically valid file can fail when a connection drops, a session expires, or the browser can't handle the request reliably. The bandwidth efficiency guidance is useful here because delivery speed and file size are connected operational concerns, not separate technical topics.
Email adds a separate system with separate rules. Even when a gallery accepts a large asset, an attachment can be rejected by the sender, the recipient, or the message server. The practical lesson is simple: the filesystem maximum is an infrastructure fact, not a promise that a client can receive the file smoothly.
Comparing Platform Limits Photographers Actually Hit
Photographers often compare services by looking for one large number. That approach misses the way delivery accounts are constrained. A platform can allow a large individual upload while limiting total user storage, organization storage, project counts, daily uploads, or the number of files accepted in a rolling period.
OpenAI's public FAQ illustrates the pattern. It lists a 512 MB per-file ceiling, a 2 M-token cap for text and document files, a practical CSV limit of about 50 MB, and a 20 MB image limit. It also lists usage caps of 25 GB per user, 100 GB per organization, 80 files every 3 hours, and 3 uploads per day for free users. These figures appear in the file uploads FAQ.
Those rules don't map neatly onto a photographer's workflow, but they expose the planning problem. A photographer may pass the image-size test and still run out of account storage. Another may have enough storage but hit a file-count or upload-frequency rule during a large batch.
A working comparison
| Platform | Per-File Cap | Total Storage | Key Bottleneck |
|---|---|---|---|
| OpenAI file uploads | 512 MB, with lower limits for some formats | 25 GB per user and 100 GB per organization | Format-specific ceilings, storage, and upload frequency |
| Dropbox | 2 TB | Plan-dependent | Account plan and total storage |
| Box | 250 MB on free personal accounts to 150 GB on Enterprise Plus | Plan-dependent | Plan-specific per-file cap |
| Google Forms | Not a single universal workflow cap | 10 GB total upload cap in practice | Total form upload storage |
| Email delivery | Depends on account and server | Message-based rather than gallery-based | Attachment and message size |
Dropbox documents a 2 TB maximum file upload size, while Box's published limits range from 250 MB for free personal accounts to 150 GB for Enterprise Plus. Google Forms users can encounter a 10 GB total upload cap. These comparisons come from the documented product limits summarized in the file upload FAQ, but the important conclusion is broader than any one service. A per-file cap doesn't describe the complete delivery experience.
Match the platform to the shoot
For a small portrait handoff, a service with a generous per-file allowance may be adequate. A wedding gallery needs room for the entire collection, dependable batch uploads, and client review tools. Event photographers also need to consider upload frequency because they may prepare several galleries or repeated selections in a short period.
Photographers comparing services can use this guide to free photo hosting for photographers as one planning reference, then verify the current account rules before committing a live client delivery. The platform that fits a single commercial asset may not fit a multi-folder wedding archive.
The first limit to fail is usually the one the workflow uses most heavily, not the one shown most prominently on the pricing page.
Email Attachment Ceilings That Block Client Handoffs
Email remains useful for a handful of finished images, invoices, approval notes, or a gallery link. It becomes unreliable when a photographer treats the inbox as a delivery system for a complete shoot. The message contains more than the visible attachment, and different account types enforce different ceilings.
Microsoft states that internet email accounts such as Outlook.com or Gmail have a 20 MB email size limit, while Exchange accounts have a default limit of 10 MB. The limit includes both the attachment and the message itself, as explained in Microsoft's guidance on reducing Outlook attachment size.
Microsoft also states that Outlook.com supports sending files up to 25 MB, creating an apparent difference between attachment guidance and total internet-email message size. The distinction matters because the sending path, account type, and message overhead can change what succeeds. The separate Microsoft explanation of Outlook.com attachment size documents that distinction.
What Gmail does with larger files
Gmail personal accounts allow 25 MB for sending and 50 MB for receiving. Files over 25 MB are automatically uploaded to Google Drive and shared as a link, according to this email file-size guide. That behavior is more useful than a hard bounce, but it changes the handoff. The client receives a link rather than a conventional attachment, and access can depend on permissions, account settings, and link availability.
Google Workspace Enterprise Plus increased to 50 MB for sending and 70 MB for receiving in February 2026, but the larger allowance is disabled by default and must be enabled by an administrator. A photographer can't assume that a client's organization has activated the setting.
A practical email decision
Email works when the recipient needs a small number of final files and the sender knows the account rules. It's a poor choice for a full gallery, RAW archive, or HD video handoff.
- Use an attachment: Send a small preview, a single approved image, or a document that comfortably fits the recipient's message limit.
- Use a gallery link: Deliver a complete shoot, a large selection, RAW files, or video through a system designed for browsing and downloads.
- Use a cloud link carefully: Confirm that the recipient can open the link without requesting access, and explain whether the link permits viewing, downloading, or both.
Photographers who regularly send video through Gmail can consult this video attachment guide for Gmail, but the core workflow remains unchanged. Email is a notification and link-sharing channel. It shouldn't carry the weight of a gallery platform.
How SendPhoto Handles Storage and Gallery Limits
SendPhoto uses a gallery-based model rather than treating every delivery as a loose collection of cloud files. The free plan includes 5 GB of storage and one active gallery, while paid tiers scale from 20 GB to 500 GB, include unlimited galleries, and offer additional branding options. Those figures are part of the publisher's stated product offering and should be checked against the current plan details before a purchase.
The practical distinction is organization. A photographer can prepare a gallery for a wedding, portrait session, commercial project, or event instead of asking a client to explore an unstructured folder. SendPhoto supports bulk uploads of full shoots, including RAW images and HD video, and provides mobile-ready galleries that clients can open without creating an account.
Plan around the complete shoot
A photographer choosing a tier should start with the active workload, not the largest individual file. The free plan can suit a small, temporary gallery. Paid storage from 20 GB upward gives a studio more room for simultaneous work, while higher tiers up to 500 GB are more appropriate for photographers retaining larger bodies of client material in the account.
A simple planning sequence helps:
- Estimate the live gallery volume. Include stills, video, alternate exports, and files waiting for client approval.
- Reserve room for overlap. A new project may arrive before an older gallery is cleaned up.
- Separate active delivery from archive storage. A gallery platform can handle presentation and access, but long-term archival requirements may call for a separate storage system.
- Choose gallery structure before upload. Folders, tags, search, and batch edits make curation easier once the files are in place.
Control access after the upload
The storage model matters because delivery isn't finished when the progress bar reaches the end. Password protection, custom watermarks, expiring links, download controls, and automatic cleanup help a photographer control how long files remain available and how clients use them. Favorites and selections also make review more manageable, particularly when the client needs to identify chosen images rather than download everything immediately.
SendPhoto is one option for photographers who need bulk gallery delivery, mobile access, client selections, and controlled downloads in the same workflow. Its tier structure makes the relevant question less about an isolated file size limit and more about how much active client work the account must hold at once.
A Practical Workflow for Delivering Large RAW and HD Video Files
Large delivery jobs become predictable when the photographer makes decisions before opening the upload window. The process should protect image quality, preserve the original files when required, and prevent the client from receiving a confusing mixture of previews, finals, and working assets.
Prepare the files
Export viewing copies with dimensions and quality appropriate to the client's use. Keep full-resolution or RAW files in a clearly named folder when the contract calls for them, and don't force every client to download originals when a web-ready selection is all they need.
Next, batch-organize the project. Separate ceremony, reception, portraits, product angles, or video deliverables into folders that match the client's mental model. Consistent names reduce support messages because the client can locate the intended files without decoding a camera-generated sequence.
Choose the delivery shape
A single gallery is convenient when the project is coherent and the account has enough available storage. Splitting a large wedding into preparation, ceremony, reception, and film galleries can make review easier when the complete project would be unwieldy. The decision should follow the client's use case, not an arbitrary folder habit.
For HD video, upload the full-resolution file when the client needs an archival master or final production asset. Use a compressed preview when the immediate task is approval, then provide controlled access to the master after selection. Download controls can prevent clients from pulling every version before they know which files they need.
Upload, test, and explain
A photographer should test the upload path before delivery day, especially for a project containing video. Stable transfer matters more than a theoretical maximum, and the guide to speeding up file transfers provides relevant workflow considerations. Expiring links suit time-sensitive proofing, while password protection and clear download instructions reduce accidental sharing.
A short client message should state what the gallery contains, which folders are final, how selections work, and whether downloads are web-ready, full-resolution, or both. Photographers who want broader guidance can also browse secure file transfer resources when evaluating delivery practices beyond a single platform.
The repeatable checklist is simple:
- Export deliberately: Create the version the client needs.
- Organize before uploading: Use meaningful folders and names.
- Split only with purpose: Divide a project when review or storage benefits.
- Control access: Set passwords, expiration, watermarks, and download permissions.
- Send a clear link: Explain the gallery structure and download choices.
The right file size limit is the one that supports the complete handoff. Photographers who check storage, file counts, upload behavior, browser reliability, and the client's receiving method before delivery avoid most last-minute surprises.
SendPhoto provides photographers with bulk photo and video gallery delivery, storage tiers from 5 GB on the free plan to higher paid capacities, client selections, password protection, expiring links, download controls, and mobile-ready access without requiring clients to create an account. Visit SendPhoto to set up a delivery workflow that treats the whole gallery, not just one file, as the unit that matters.