Is WeTransfer Down? How to Check, Fix It, and Send Anyway

Nobody checks a status page calmly. By the time you're searching "WeTransfer is down," you've probably already refreshed the upload screen a few times and started drafting an apologetic message to whoever's waiting on the file. The good news: WeTransfer itself is rarely the actual problem. Per WeTransfer's own status page, the service has logged no incidents across its eight tracked components (website, uploads, downloads, email, mobile transfer, previews, and support) in the last 90 days as of this writing. Most "it's down" moments trace back to a browser, network, or file issue on one end of the transfer, not WeTransfer's servers.

This covers how to actually check status instead of guessing, the specific, non-obvious causes that make WeTransfer look broken when it isn't, the real fixes for a stuck upload or download, and what to do if the file genuinely has to go out right now regardless of what's wrong.

Is WeTransfer actually down right now?

Check status.wetransfer.com directly — it's WeTransfer's own Atlassian Statuspage instance, tracking uploads, downloads, email delivery, and the website separately, so you can see exactly which part is affected rather than a vague "is it down" verdict. If every component shows operational there, the problem is on your end: your browser, network, an extension, or the file itself, all covered below. If you need the file sent in the next few minutes and don't want to spend that time debugging, sending it through a different service sidesteps the question entirely — Affily works the same basic way, a link the recipient opens with no account required, covered further down.

How to check WeTransfer's real status

Third-party "is it down" checker sites are guessing from user reports and periodic pings — useful as a rough signal, but not the actual source of truth. WeTransfer's own status page is: it shows real incident history, not crowd-sourced complaints, and breaks status down by component instead of one blanket indicator. If uploads are affected but downloads aren't (or the reverse), the status page will say so specifically, which tells you whether it's even worth troubleshooting your own setup.

Worth knowing: a status page showing "all systems operational" doesn't rule out a problem specific to your account, your region, or a corporate network filtering WeTransfer's traffic. It rules out a broad outage — it doesn't rule out everything.

Why WeTransfer looks down when it isn't

• Browser extensions and ad blockers. Script blockers and ad blockers are a common, specific cause of uploads silently failing or the site not loading correctly — disable them one at a time and reload rather than assuming they're not involved.
• A VPN, firewall, or antivirus. Any of the three can interrupt an upload mid-transfer or block the site outright, especially on a corporate network. If you're on a work device, this is worth checking before anything else.
• An incorrect system clock. A surprisingly common, easy-to-miss cause of "your connection is not private" warnings that look like a site outage but are a local settings issue.
• Hitting the free plan's monthly allowance. WeTransfer's Free plan allows up to 10 transfers or 3GB total in any rolling 30-day period, per WeTransfer's own plan-limits documentation — once that's used up, new transfers get refused. That reads as "broken" to someone who doesn't know the allowance exists, when it's actually working exactly as designed.
• A file that's still being written. Uploading a video before it's finished exporting, or a file another program still has open, can fail in a way that looks like a platform problem rather than a timing one.
• An expired or mistyped link, on the download side. Not a WeTransfer failure — the transfer did its job and then aged out, or a character got dropped when the link was copied.

Fixing a stuck upload, download, or a site that won't load

Upload stuck, failing, or showing an error

• Confirm a stable connection and keep the device awake — sleep mode mid-upload is a frequent, easy-to-miss cause of a stalled transfer.
• Restart your computer or phone and the router. Per WeTransfer's own upload-troubleshooting documentation, this resolves the majority of mid-upload stalls.
• Try a different current browser or incognito mode, and disable extensions one at a time — particularly ad blockers.
• Make sure the file has finished exporting or rendering, isn't open in another program, and has a filename under 255 characters.
• On a corporate network, ask IT whether WeTransfer is blocked before assuming the service itself is broken.

Download stuck, failing, or the file won't open

• Check available storage space before assuming the download itself is broken — a full disk fails silently more often than it throws a clear error.
• Clear cookies and cache, then try a current browser or incognito mode.
• If the file downloaded but won't open, confirm it isn't 0 KB or unusually small — that points to a failed upload on the sender's end, not a problem with how you're opening it. Ask them to resend.
• External download managers aren't supported — use the browser's own download flow (Chrome, Edge, Firefox, or Safari).

The site or app won't load at all

• Check your system clock — an incorrect date or time is a common, non-obvious cause of a "connection is not private" warning that looks like the site is down.
• If you see a security warning in the URL, try removing "www" from the start of the address.
• Restart your device and modem/router, clear cookies and cache, and update your browser to the latest version.
• Temporarily disable antivirus, firewall, or VPN software, one at a time.

When WeTransfer really is down

Genuine outages are the least common cause on this list, but they happen, and when the status page confirms one, there's nothing to troubleshoot on your end — the only real move is waiting or sending the file another way. WeTransfer is good at that one job, moving a file from one person to another. It was never built to be the only path you have for getting something out the door, which is exactly the problem the moment that one path is unavailable and a client or teammate is waiting.

A video editor with a client deadline in twenty minutes doesn't have twenty minutes to debug a status page. The practical fix isn't finding a workaround for WeTransfer specifically — it's not depending on a single tool as the only way to deliver a file in the first place.

How Affily fits in

Affily sends files the same basic way WeTransfer does — upload, get a link, the recipient downloads with no account required — so it works as a direct fallback without asking anyone to learn a new process under deadline pressure. The free plan allows 10GB of transfers a month, more than three times WeTransfer's current 3GB monthly allowance, so hitting a quota isn't the first thing to rule out.

The bigger point isn't which service goes down less often — that's not a claim either company can make credibly, and every hosted tool has an occasional bad day. It's that a file transfer being the single point of failure for how work gets delivered is a fragile setup regardless of which specific tool it's built around. Affily Transfer keeps the send, the feedback, and the approval on the same page, so even the recovery path (resending after a failed transfer) doesn't mean starting the conversation about the file over from scratch — the revision history keeps track of which version is which. Starter runs $8/month billed yearly and adds branded delivery pages and timestamped feedback; every paid plan includes a 7-day free trial, and the free plan itself never asks for a credit card.

For the full walkthrough of sending and receiving files day to day, see our guide to how to use WeTransfer. If a single-tool outage is enough to make you want a standing backup rather than a one-time workaround, Swiss file transfer and Google Drive's actual sharing limits cover two other options worth knowing before the next time something breaks.

None of this means WeTransfer is unreliable — a 90-day clean status history says otherwise. It means a single tool being unavailable for an hour shouldn't be able to stop a deadline, and that's a planning problem, not a WeTransfer-specific one.