OneDrive will take a 250GB file without blinking. What stops a client delivery is everything around the file.
The limits on paper
- Per-file upload: 250GB — the same cap applies whether you upload via the desktop app (sync) or the web. That's a big single-file ceiling; size is rarely the real problem.
- Free storage: 5GB, shared with Outlook.com attachments.
- Path length: 400 characters max for a full file path; a single file or folder name maxes at 255 characters.
- Invalid characters in names (asterisks, backslashes, and a few others) can block upload and sync.
So the limit that catches people isn't "your file is too big." It's the quota, the permissions, and what the free tier leaves out. The 250GB number is a red herring for most client work.
What "share" actually does in OneDrive
Sharing in OneDrive means you give someone a link to a file or folder in your cloud. The practical limits:
- The file has to fit in your storage. A 5GB free account holds a handful of big files, and everything you upload competes for that space. A single 5GB deliverable nearly fills the entire free pool.
- The recipient's access is governed by sharing settings (who can open it, whether they can edit). On work or school accounts, admins can restrict sharing to your own domain or to specific people, so a link may not work for an outside client at all. "Anyone with the link" links can also be forced to expire — Microsoft lets admins cap their lifetime, and some organisations, like the University of Bath, now default new shared links to expire after 180 days.
- It's a standing link into your folder — the file stays there, not a one-off delivery.
That last point is the crux. OneDrive sharing is a team-folder model: a file lives in your drive, people open it over time. It's great for that. It's a poor fit for "here's your master, download it and I'm done."
Sending a 5GB deliverable
| OneDrive (free) | OneDrive (paid / work) | A transfer link | |
|---|---|---|---|
| Send a 5GB file | Tight — 5GB total pool | Fine, if in quota | Sized for the file |
| Recipient needs an account | Often (or a working share link) | Depends on sharing settings | No account |
| Link / access model | Standing link into your folder | Domain-restricted possible | One-off delivery |
| Expiry you control | Limited | Admin-set | You choose (incl. no expiry) |
For a one-off 5GB client send, OneDrive's free tier is borderline — the file nearly fills the whole pool, and the recipient's access depends on your sharing settings. A dedicated transfer link sized for the file, with no account needed on their end and the expiry in your hands, is the cleaner tool.

When OneDrive is right — and when it isn't
OneDrive is the right tool when: you and a client or team are working together on files over time, you need the desktop sync, and the files live in a shared folder. That's what it's built for. The standing-link model is a feature here, not a bug.
It's the wrong tool when: you're doing a one-off delivery — a master, a render, a project handoff — where the client just needs to download and you don't need them logged into your cloud. The quota, the account friction, and the standing-link model all work against a one-shot send.
The quick test: if you want the file out of your cloud and into their hands, in one download, with no account on their side — you don't need a shared folder, you need a transfer link.
For a delivery-first alternative, see Beautifully Delivered. And for the Drive version of the same problem, How to Share a File That's Too Big for Google Drive.
