Quick answer: Game builds run from a few hundred MB for mobile to tens of GB for PC. Upload a zipped build to Share Large Video Files (up to 20 GB), require an NDA before download, give each tester or journalist a personal link so a leak can be traced to one link, limit downloads per person, and send a checksum so testers know the build is complete.
Files game developers send, and how big they get
| File | Format | Typical size |
|---|---|---|
| Android build | APK, AAB | 100 MB to 2 GB |
| PC build, zipped | ZIP, 7z | 1 to 50 GB |
| Engine project with assets | Unity or Unreal project folder | tens to hundreds of GB |
| Texture source files | PSD, EXR, TGA | 50 to 500 MB each |
| Press kit (trailer, screenshots, logos) | MP4, PNG, ZIP | 500 MB to 5 GB |
| Crash dumps and logs from testers | DMP, TXT, ZIP | 1 MB to 2 GB |
Can it go by email or chat?
Can you send a 5 GB zipped PC build (about 5 GB) as an attachment?
| App | Limit | Fits? |
|---|---|---|
| Gmail | 25 MB per email | No, send a link |
| Outlook.com | 20 to 25 MB per email | No, send a link |
| WhatsApp (document) | 2 GB per file | No, send a link |
| Telegram | 2 GB per file | No, send a link |
| Facebook Messenger | 100 MB per file | No, send a link |
| Discord (free) | 20 MB per file | No, send a link |
| Slack | 1 GB per file | No, send a link |
| WeTransfer (free) | 3 GB per transfer | No, send a link |
| Share Large Video Files | 20 GB per transfer | Send the link anywhere |
Limits from our file size limits by app table, checked against each service's help pages.
A workflow that works
- Zip the build (7z or ZIP) and make a SHA-256 checksum with the file hash checker.
- Upload it and tick Require an NDA before download with your playtest or embargo agreement.
- Set Download limits: per person to 1 or 2 and Who can open the link to confirmed emails.
- On your Transfers page, create a personal link for each tester or outlet; switch the main link off so only personal links work.
- Collect crash dumps and recordings from testers with a Request files link.
Recommended options
| Option (under More options) | Setting | Why |
|---|---|---|
| Require an NDA before download | On (playtests, embargoes) | A signed record from every tester |
| Personal links (Transfers page) | One per tester or outlet, main link off | A leaked link points to one person; revoke it alone |
| Download limits: per person | 1 or 2 | No spare copies to pass around |
| Where and on how many devices: Countries | Your test regions | Keeps a regional test regional |
| Available from | Embargo time (press kits) | Assets open when the embargo lifts |
| Expires after | Until the next build | Old builds disappear |
Set these once, press Save current next to Preset, and reuse the same options for every build with one tap.
Builds over the transfer limit
If a zipped build is over 20 GB, split it into parts with 7-Zip or the split file tool and send the parts in one or more transfers; testers join them and compare the checksum. Do not re-compress already-compressed assets: pak files, video and audio barely shrink, so a ZIP mainly keeps the folder together.
Frequently asked questions
How do I send a playtest build safely?
Require an NDA, use confirmed emails, limit downloads per person, and give each tester a personal link so you know which copy went where.
Can I tell which tester leaked a build?
Personal links record opens and downloads per link, so a link found online points to one recipient. Switch it off without affecting the others.
How do testers know the download is complete?
Send the SHA-256 checksum with the link; they compare it with the file hash checker after downloading.
Can I release a press kit at the embargo time?
Yes. Set Available from to the embargo; before then the link shows a countdown.
Ready to send?
Drop your files, get a link, done. Free up to 20 GB — no account needed.
Send files free