# WeTransfer File Size Limit: Free vs Paid Caps and How to Send Larger Files

The WeTransfer file size limit caps free accounts at 3 GB across a rolling 30-day window, with download links expiring after three days. Paid subscriptions expand transfer capacity for larger media projects, but browser timeouts and ephemeral links still complicate client delivery. Understanding these thresholds helps teams choose between split archives, paid plan upgrades, and persistent workspaces for client delivery.

Source: https://fast.io/resources/wetransfer-file-size-limit/
Last reviewed: 2026-09-04

## WeTransfer File Size Limits Across Free and Paid Plans

Sending large project deliverables through temporary file transfer services introduces a predictable operational failure: the moment a transfer stalls halfway through an upload or a download link expires before a recipient downloads it, project schedules slip and production teams must restart the process from scratch. While WeTransfer popularized frictionless browser-based file sharing, its transfer caps and strict expiration schedules create friction for anyone handling modern video footage, camera raw images, audio stems, or multi-gigabyte software builds.

The WeTransfer file size limit defines the maximum allowable data payload per transfer, where WeTransfer caps free accounts at 3 GB while Ultimate subscriptions scale to higher volume thresholds. As of September 2026, WeTransfer structures its service around four primary tiers: Free, Starter, Ultimate, and Teams. Understanding these thresholds is critical before committing to an upload, because each plan pairs its maximum transfer size with specific monthly transfer caps and link expiration windows.

On the Free tier, WeTransfer caps free accounts at 10 transfers or 3 GB total in any 30-day rolling window. Once you reach 3 GB of cumulative upload volume within thirty days, additional uploads are blocked until older transfers age out of the rolling window. Furthermore, all download links generated on the Free tier expire automatically after 3 days. For over a decade, WeTransfer maintained a classic two-gigabyte transfer threshold with seven-day link expiration on its unauthenticated service. The current model requires that WeTransfer free accounts operate within this rolling allowance, while recipients can still download files without creating an account.

For individual creators requiring higher allowances, the Starter plan expands transfer capacity to three hundred gigabytes per transfer. Like the Free tier, Starter operates on a rolling 30-day window capped at 10 transfers or 300 GB of total data, and download links remain active for up to 3 days.

The Ultimate plan removes practical transfer ceilings for professional production teams, supporting file packages reaching one terabyte per individual transfer alongside unlimited monthly transmission volume. In addition to high payload capacity, Ultimate introduces custom link expiration dates, password protection, and the ability to recover expired links. The Teams plan extends these Ultimate features to collaborative organizations by adding centralized administration and shared team workspaces.

| Plan Tier | Max File Size Per Transfer | 30-Day Rolling Allowance | Download Link Expiration | Verified Status |
| --- | --- | --- | --- | --- |
| Free | 3 GB | 10 transfers or 3 GB total | 3 days | Verified September 2026 |
| Starter | 300 GB | 10 transfers or 300 GB total | 3 days | Verified September 2026 |
| Ultimate | 1 TB | Unlimited transfers | Custom or indefinite | Verified September 2026 |
| Teams | 1 TB | Unlimited transfers | Custom or indefinite | Verified September 2026 |

The rolling 30-day window is a critical mechanism that catches occasional senders off guard. Instead of resetting on the first day of each calendar month, the window tracks the exact timestamp of every upload. If you send one gigabyte on the fifth day of the month and another payload on the tenth, your transfer slots unlock on the fifth and tenth days of the subsequent month. When evaluating [file-sharing services](/alternatives/wetransfer/), teams must calculate not only individual file sizes but also cumulative monthly transmission volume.

## Why Large WeTransfer Uploads Fail Mid-Transfer

Users frequently encounter upload failures when attempting to transfer large files through a web browser. A common scenario involves an upload progressing smoothly nearly to completion, only to stall indefinitely or throw a generic connection error. Understanding why browser-based transfers fail reveals the inherent architectural limits of transmitting multi-gigabyte payloads through HTTP sessions.

First, standard browser uploads rely on continuous, uninterrupted HTTP socket connections. When transferring a large video file over consumer broadband, the upload may take twenty to forty minutes depending on upstream bandwidth. If an upstream network glitch occurs, such as packet loss on Wi-Fi or a brief DHCP lease renewal by an internet service provider, the browser drops the TCP connection. Because standard web transfers lack resilient chunked upload recovery, the platform cannot resume from the point of failure. The browser discards the partial payload, forcing the sender to restart from the beginning.

Second, operating system power management frequently interrupts long transfers. When a laptop is left unattended during a large upload, the operating system may dim the screen and enter system sleep mode to conserve battery. In sleep mode, the network interface card powers down, severing active browser WebSocket and HTTP connections. WeTransfer technical guidance highlights that sleep mode cancels in-progress transfers, advising users to keep their devices active and plugged into power.

Third, specific browser engines and extensions interfere with large data streams. WeTransfer explicitly documents a persistent issue on Apple Safari where uploads can hang at almost any point during transmission. While switching to Chrome or Firefox often mitigates this specific browser bug, browser extensions present additional risks. Content blockers, privacy extensions, and aggressive local antivirus scanners inspect outbound data packets. When an upload payload contains massive data streams, extension memory buffers can overflow or mistakenly classify persistent outbound streams as suspicious, severing the session.

Fourth, file system locks and storage sources cause silent upload crashes. Selecting files stored on external USB drives, network shares, or syncing cloud directories like iCloud Drive introduces latency. If the external drive enters a power-saving spin-down state, or if a cloud sync engine attempts to synchronize the file while the browser reads it, the browser loses read access to the source file descriptor. Moving project files to a local solid-state drive before initiating an upload eliminates this read-lock hazard.

## How to Send Files Exceeding Transfer Caps

When project files exceed standard free transfer thresholds and upgrading to a paid tier is not an immediate option, technical teams rely on manual workarounds to deliver data. While these methods require additional preparation, they allow senders to package multi-gigabyte payloads within standard transfer boundaries.

The most reliable manual technique is archive splitting. By compressing a project directory into multi-part archive volumes, you can divide a large directory into chunks that fit comfortably under the free transfer threshold. On macOS and Linux systems, you can execute this directly from the terminal using standard utilities without third-party software.

To split a large directory into archive segments of two gigabytes each, change to the target directory and run:

```bash
tar -cvf - /path/to/project-assets | split -b 2000m - project_part_
```

This command creates sequential chunks named `project_part_aa`, `project_part_ab`, and so forth. Senders can transmit each chunk in an independent transfer session. Once the recipient downloads all segments into a single folder, they recombine and extract the archive with a single terminal command:

```bash
cat project_part_* | tar -xvf -
```

Windows users can accomplish the same result using graphic compression utilities such as 7-Zip. Within the 7-Zip interface, select the asset folder, choose Add to Archive, and set the split volumes field to a two-gigabyte threshold. The tool generates sequential `.7z.001` and `.7z.002` volumes that the recipient can extract using the same utility.

A second approach involves per-asset directory segregation. In video and photography workflows, raw project footage is rarely a single monolithic file; it consists of individual takes, audio stems, and project files. By organizing assets into discrete day-one, day-two, or b-roll folders, senders can dispatch multiple independent transfers. However, on WeTransfer Free, this approach quickly consumes the monthly allowance. Sending multiple separate archives rapidly uses up the account's monthly transfer quota.

A third alternative is proxy generation. When sharing video assets for creative review or rough-cut approval, delivering uncompressed ProRes or camera raw media is often unnecessary. Exporting lower-bitrate ProRes Proxy review copies compresses a full production shoot into lightweight files that upload in minutes. Once stakeholders approve the edit, final master files can be handed off through dedicated delivery workspaces.

## Why Link Expiration Deadlines Create Client Friction

Transfer size limits represent only half the logistical challenge of temporary file sharing; link expiration creates equal, if not greater, project friction. Free and Starter uploads on WeTransfer remain available to download for up to 3 days before the platform permanently purges them from its storage servers.

This short availability window frequently conflicts with real-world business timelines. If a freelance editor sends a client deliverable on a Friday afternoon, a client opening the email on Tuesday morning encounters an expired link error. The sender must re-upload the entire package, which consumes additional upstream bandwidth and delays review cycles. Unless the sender subscribes to the Ultimate plan, which offers link recovery and custom expiration settings, expired files cannot be restored once deleted.

Beyond expiration timelines, the recipient download experience introduces notable friction. WeTransfer packages multi-file transfers into a single ZIP archive. For recipients on mobile devices, tablets, or constrained office laptops, downloading and decompressing massive multi-file ZIP archives presents several hurdles:

First, web browsers lack resilient download managers. If a recipient loses their internet connection near the end of a multi-gigabyte ZIP download, the browser cannot resume the download. The recipient must start over, consuming double the bandwidth and generating support tickets for the sender.

Second, default operating system archive utilities frequently fail on large or complex archives. The native macOS Archive Utility and Windows Explorer ZIP tool occasionally fail to unpack archives exceeding standard file system buffers, throwing error codes or corrupting deep folder structures. Recipients must search for and install third-party decompression utilities like The Unarchiver or 7-Zip just to access their deliverables.

Third, monolithic ZIP files prevent selective retrieval. A client who needs only a single PDF agreement or updated logo must download the entire multi-gigabyte package, wait for extraction, and browse the directory manually. This lack of asset-level previewing or streaming turns basic file handoffs into cumbersome administrative chores for clients.

## When to Choose Persistent Workspaces Over Ephemeral Transfers

While ephemeral file transfer utilities serve well for occasional, disposable file throws, modern creative and business teams require persistent collaboration environments. Temporary transfer links were engineered in an era of static web handoffs, whereas today's production pipelines demand ongoing version tracking, access governance, and branded presentation.

Standard cloud storage drives like Google Drive, Dropbox, and OneDrive address file persistence, but they introduce their own operational friction. Consumer sync clients consume local drive space, complex folder permissions confuse external clients, and recipients are frequently forced to log in or create proprietary accounts before viewing materials.

Fast.io provides an alternative built around persistent [shared workspaces](/product/workspaces/) and intelligent client delivery. Instead of uploading files to a temporary holding queue that self-destructs after three days, files live in organized, organization-owned workspaces. Teams configure dedicated workspaces for specific clients, ongoing projects, or production teams, maintaining complete administrative oversight over digital assets.

For external distribution, Fast.io replaces ephemeral transfer links with durable [branded shares](/product/sharing/). Senders can create Send, Receive, or Exchange shares configured with custom expiration or maintained indefinitely. When delivering assets to clients, senders can present a branded portal with custom logos and backgrounds. Clients access files directly in their browser without being forced to create an account or install desktop synchronization software.

Fast.io addresses large-file transmission challenges through several built-in capabilities:

1. Chunked Upload Architecture: Uploads are processed in segmented blocks. If an internet connection drops mid-transfer, the system resumes from the last confirmed block rather than forcing a restart from the beginning. This provides reliable transmission for massive video archives and raw asset catalogs.

2. Per-File Version History: When revisions occur, updating a file does not break the client share link or create redundant copies like 'v2_edit_FINAL.mov'. The workspace retains a complete version history, allowing teams to review or restore previous iterations while clients always access the current release.

3. Media Streaming and In-Browser Previews: Video assets support HLS streaming, enabling clients to stream high-resolution footage directly within their browser without waiting for multi-gigabyte downloads.

4. Workspace Intelligence: When Intelligence Mode is enabled on a workspace, uploaded documents and media assets are indexed for full-text and semantic search. Team members and external collaborators can query workspace contents using natural language to locate specific assets instantly.

Fast.io operates on a transparent subscription model. Every organization starts with a 14-day free trial, which requires a credit card. Paid subscriptions include Starter, Business, and Growth plans, providing team seats, terabyte-scale storage, and credits for workspace intelligence:

| Subscription Plan | Monthly Rate | Storage Capacity | Team Seats |
| --- | --- | --- | --- |
| Starter | $29 monthly | 1 TB | 5 seats |
| Business | $99 monthly | 10 TB | 20 seats |
| Growth | $299 monthly | 50 TB | 50 seats |

For production teams that regularly handle high-volume creative assets, moving from expiring transfer links to persistent workspaces eliminates the cycle of broken links and re-upload headaches.

## Frequently asked questions

### What is the maximum file size you can send on WeTransfer for free?

On the Free tier, WeTransfer caps free accounts at 3 GB per transfer within a 10-transfer monthly allowance across a rolling 30-day window. Once this limit is reached, users must wait for previous transfers to exit the rolling window before sending additional files.

### How do I send files larger than the free transfer cap on WeTransfer without paying?

To send files exceeding the free allowance without purchasing a subscription, you can split large directories into multi-part archive volumes using tools like 7-Zip or command-line tar and split. By dividing the payload into chunks under the free transfer threshold, you can send them in separate transfers. Keep in mind that sending multiple chunks consumes your rolling allowance on Free accounts.

### Why does WeTransfer fail when uploading large files?

Large WeTransfer uploads typically fail due to network interruptions, device sleep mode, browser memory constraints, or file system locks. Standard browser uploads require a continuous HTTP connection; any temporary drop in Wi-Fi or upstream bandwidth cancels the transfer without the ability to resume. Additionally, uploading directly from external hard drives or cloud-sync folders can trigger timeout errors.

### How long do WeTransfer download links stay active before expiring?

Free and Starter uploads on WeTransfer remain available to download for up to 3 days from the exact moment of sending. After three days, files are permanently deleted from WeTransfer servers. Senders on the Ultimate plan can configure custom expiration dates, keep links active indefinitely, or recover expired transfers.

### Can you resume an interrupted upload on WeTransfer?

Standard web browser uploads on WeTransfer cannot be paused or resumed after a connection failure. If an upload stalls or disconnects, the entire transfer must be restarted from the beginning. Senders dealing with unstable connections often benefit from dedicated workspace platforms that implement chunked upload resumption.

### How does a persistent workspace differ from a WeTransfer transfer?

WeTransfer functions as a temporary transit pipeline where files are held for a few days before being permanently deleted. A persistent workspace, such as Fast.io, acts as an ongoing home for project files. Workspaces maintain per-file version history, provide durable branded share links that do not expire after three days, and allow recipients to stream video or preview documents without downloading entire multi-gigabyte archives.

## About Fast.io

Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server at https://mcp.fast.io/mcp, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli.