Secure file sharing for game studios is about moving builds and unreleased assets to people outside your version control without them leaking. RocketShare encrypts each file in your browser before upload, so the server never holds a readable build, and lets you add a password, a download limit and an expiry date. Publishers, QA vendors, outsource artists and press download in a browser without an account or install.
RocketShare is a browser-based file transfer service that encrypts file contents end-to-end (zero-knowledge) before upload. It is based in the Netherlands and stores files in Amsterdam.
What studios send outside the pipeline
| Handoff | Typical contents | Typical size |
|---|---|---|
| Vertical slice or milestone build | Zipped PC/console build | 5–100 GB |
| Press or influencer preview build | Packaged build, press kit | 10–80 GB |
| Outsource art handoff | FBX/OBJ meshes, 4K/8K texture sets (PNG, EXR, TGA), Substance files | 2–50 GB |
| Audio delivery | WAV stems, Wwise/FMOD banks | 1–20 GB |
| Trailer and cinematic masters | ProRes or high-bitrate MP4 | 5–200 GB |
| Pitch and greenlight material | Deck, gameplay capture | 0.5–10 GB |
There is no per-file size limit beyond your plan quota, a transfer can contain up to 10,000 files, and folder structure is kept, so an asset pack with /Textures, /Meshes and /Materials arrives as you organised it.
Confidentiality in game development
Almost every external handoff in games is covered by an NDA: publishers and platform holders for milestone builds, press under embargo, contractors for unannounced IP. Leaks of builds and story content are a real and recurring problem, and most come from shared links and accounts rather than broken encryption.
End-to-end encryption means a breach of RocketShare's storage exposes only encrypted data. It cannot stop an authorised tester from sharing a build, so keep watermarked builds and NDAs in place. This page is not legal advice.
Workflow: sending a build securely
- Strip codenames from file names. File names, folder paths and the transfer message are stored in plaintext; only file contents are encrypted.
build-m3.zipis safer thanProjectNightfall-reveal-trailer-final.zip. - Drag the archive or folder into rocketshare.app. Files are encrypted on your machine with AES-256-GCM and uploaded in parts; failed parts retry automatically. Keep the tab open until the upload completes: there is no resume after closing it.
- Restrict access. With an account, set a password, a download limit (for example 1 per press contact) and an expiry of up to 90 days on Pro, or 1 day for a short embargo window.
- Send each recipient the link yourself, with the password via a separate channel. The key sits after
#in the link and never reaches the server. RocketShare's optional "send via email" passes the key through the server to build the email (not stored or logged). - Recipient downloads the archive; decryption streams to disk, so large builds do not fill browser memory. The link stops working once the download limit is reached, and encrypted files are deleted automatically after expiry.
Which plan fits your studio
| Plan | Monthly data | Transfers / month | Max expiry | Price |
|---|---|---|---|---|
| Free (account) | 4 GB | 10 | 7 days | $0 |
| Starter | 350 GB | 40 | 60 days | $7/month |
| Pro | Unlimited (fair use, 10 TB) | Unlimited | 90 days | $18/month |
| Teams | Unlimited per seat (fair use) | Unlimited | 90 days | $20/seat/month, from 3 seats |
A solo developer sending occasional builds fits Starter. A studio sending weekly builds to QA or 50 GB press builds fits Pro. Producers and leads who each send handoffs can share Teams billing; quotas are per seated member, not pooled. Yearly billing gives two months free; see pricing.
Limits to know
- No API, CLI or CI integration, so you cannot push builds from a build server automatically.
- No per-recipient tracking. One link per transfer; to tell recipients apart, send separate transfers.
- No versioning, sync or shared team storage. Keep Perforce, Git LFS or Plastic for your pipeline.
- No virus scanning, since the server cannot inspect contents.
- No apps, two-factor authentication or SSO. Browser only.
If you need a desktop app with resumable transfers, see RocketShare vs Filemail. For quick encrypted sharing of smaller files, see RocketShare vs Wormhole. The encryption design is documented on the security page.