GitHub Actions Runner Specs: vCPU, RAM & Disk by Size
How much CPU, memory, and disk does each GitHub Actions runner give you? Here are the numbers.
Standard GitHub-hosted Linux runners are modest; larger runners scale up but bill from minute one. Match your job to the smallest size that fits.
Linux runner specs
| Runner | vCPU | RAM | Disk |
|---|---|---|---|
| ubuntu-latest (standard) | 4 | 16 GB | ~14 GB free |
| Larger 4-core | 4 | 16 GB | More |
| Larger 8-core | 8 | 32 GB | More |
| Larger 16-core | 16 | 64 GB | More |
Right-sizing
A lint job does not need 16 cores. Use the smallest size that keeps the job fast - you pay per minute regardless of utilization. Try the runner-size recommender.
Managed runners
Latchkey offers small (2 vCPU / 8 GB), medium (4 vCPU / 16 GB), and large (8 vCPU / 32 GB) at roughly a third of GitHub-hosted per-minute cost.
Frequently asked questions
GitHub Actions Runner Specs: vCPU, RAM & Disk by Size?
Standard GitHub-hosted Linux runners are modest; larger runners scale up but bill from minute one. Match your job to the smallest size that fits.
Right-sizing?
A lint job does not need 16 cores. Use the smallest size that keeps the job fast - you pay per minute regardless of utilization. Try the runner-size recommender.
Managed runners?
Latchkey offers small (2 vCPU / 8 GB), medium (4 vCPU / 16 GB), and large (8 vCPU / 32 GB) at roughly a third of GitHub-hosted per-minute cost.