Why Does WeTransfer Show an Error and Fail to Load?
If WeTransfer shows an error page instead of the file-transfer interface, the most common cause is that part of the site was blocked before it could load. WeTransfer's own error message points to three likely culprits — a firewall, a proxy, or your browser set-up — and adds that the site requires a JavaScript-enabled browser. The fastest first step is to refresh the page; if the error returns, work through the checks below. This applies to the web version of wetransfer.com in a desktop or mobile browser, not to the mobile apps.
What the error actually means
The message you see is a partial-load failure, not a rejected upload or a problem with your files. WeTransfer loads core parts of its interface as separate resources. When one of those resources can't be fetched, the page falls back to an error screen even though the rest of the site may be reachable.
That distinction matters: your files were never sent, so there is nothing to recover or resend. You are fixing access to the page, not repairing a transfer.
Check these in order
1. Refresh the page
A single blocked or timed-out request is often transient. Reload once before changing any settings. If the page loads normally, no further action is needed.
2. Confirm JavaScript is enabled
WeTransfer states plainly that a JavaScript-enabled browser is required. If JavaScript is disabled — through a browser setting, an extension such as a script blocker, or a managed corporate policy — the interface cannot render and you will keep hitting the error.
- Test in a private/incognito window with extensions disabled. If it works there, an extension is the likely cause.
- If it fails in incognito too, check your browser's site settings for JavaScript permissions on wetransfer.com.
3. Rule out a firewall or proxy
This is the most common cause on corporate, school, or public networks. A firewall or proxy can block the specific requests the page depends on while still allowing the domain itself to resolve.
| Situation | What to try |
|---|---|
| Office or campus network | Try a different network, such as a phone hotspot, to confirm the network is the blocker |
| VPN or corporate proxy in use | Disconnect the VPN or switch proxy profiles, then reload |
| Browser-level proxy or security extension | Disable it temporarily and reload |
| Works on hotspot, fails on office Wi-Fi | Ask your IT team to allow the resources WeTransfer needs |
If the page loads on a phone hotspot but not on your usual network, the network is the cause and browser changes won't help.
4. Try a different browser or device
A second browser isolates whether the problem is your browser profile or the network. If a different browser on the same network also fails, the network or proxy is the more likely cause.
If it still won't load
WeTransfer directs users to its help center when the problem persists. Contact support from a network where the site does load, and include:
- The exact error text you see
- Your browser and version
- Whether you are on a corporate, school, or public network
- Whether a VPN or proxy is active
- Whether the page loads on a different network or browser
That set of details lets support tell a network block apart from a browser problem without a round of back-and-forth.
Quick reference
- Refresh first — the error is often a one-off failed request.
- JavaScript must be on — the site will not work without it.
- Firewall, proxy, and browser settings are the named causes in WeTransfer's own message.
- Test on another network to separate a network block from a browser issue.
- Use the help center if the error persists, with the details listed above.