By file type
How to send a large game build
Zip the build and send it as a transfer link, so testers get exactly the build you made. Store pipelines have their own size rules, but a playtest or a publisher review usually needs a plain download first, often several gigabytes, far beyond what email or chat accepts.
The limits, in numbers
| Steam | No stated build limit; pack files of 1–2 GB advised | Steamworks documentation |
|---|---|---|
| Apple App Store | 4 GB maximum uncompressed app | App Store Connect Help |
| Google Play | 34 GB in total, compressed; warning over 200 MB on mobile data | Play Console Help |
| Slack | 1 GB per file | Slack Help Center |
| Yungle, free | Up to 10 GB per transfer, kept 7 days, no account |
Limits from each company’s own help pages, checked on 13 October 2026. They change; the linked page is the authority.
How to send it
- 1Zip the build folder, so every file and the folder layout arrive as you made them.
- 2Drop the zip on yungle.co, or upload it from your build server with the command-line tool.
- 3Send the link to testers. You can see who has downloaded it.
Questions, answered.
Ask us something elseCan I upload builds from CI?
Yes. Yungle has a command-line tool and an API, so a build job can upload the artefact and post the link when it finishes.
Why does Steam suggest small pack files?
Steam patches by changed file. Change one byte in a 25 GB pack file and players download all 25 GB again, so smaller packs make updates smaller.
Is the build kept private?
Every file is always encrypted and only people with the link can download it. Add a password for builds under NDA.
Send your first file in ten seconds.
10 GB, free, right now — no account, no card, no ads. Pay us only when you want your work to stay put.
- Cancel anytime
- iDEAL, card or SEPA
- Export or delete everything, yourself