Guides
How to handle large artifact uploads
Uploading build output takes minutes.
4 min read
Uploading build output takes minutes.
Why it happens
Artifact upload is network-bound and compresses poorly for already-compressed content.
How to fix it
- Compress with zstd before uploading rather than relying on default handling
- Upload only the files needed downstream, not whole directories
- For very large artefacts, push to object storage directly instead
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.
Related
How to scale self-hosted runnersSelf-hosted runners either queue at peak or sit idle and expensive.How to use runner groupsAny repository can schedule jobs on any runner.How to design a runner label strategyLabels grew organically and nobody knows which to use.Hosted or BYOC: how to chooseYou are unsure whether to use hosted runners or deploy into your own cloud.