{"meta":{"title":"GitHub-hosted runners reference","intro":"Find information about GitHub-hosted runners, including their specifications and customization options.","product":"GitHub Actions","breadcrumbs":[{"href":"/en/actions","title":"GitHub Actions"},{"href":"/en/actions/reference","title":"Reference"},{"href":"/en/actions/reference/runners","title":"Runners"},{"href":"/en/actions/reference/runners/github-hosted-runners","title":"GitHub-hosted runners"}],"documentType":"article"},"body":"# GitHub-hosted runners reference\n\nFind information about GitHub-hosted runners, including their specifications and customization options.\n\n## Supported runners and hardware resources\n\nRanges of GitHub-hosted runners are available for use in public and private repositories.\n\nFor lists of available runners, see:\n\n* [Standard runners for **public** repositories](#standard-github-hosted-runners-for-public-repositories)\n* [Standard runners for **private** repositories](#standard-github-hosted-runners-for--private-repositories)\n\nGitHub-hosted Linux runners support hardware acceleration for Android SDK tools, which makes running Android tests much faster and consumes fewer minutes. For more information on Android hardware acceleration, see [Configure hardware acceleration for the Android Emulator](https://developer.android.com/studio/run/emulator-acceleration) in the Android Developers documentation.\n\n> \\[!NOTE]\n> The `-latest` runner images are the latest stable images that GitHub provides, and might not be the most recent version of the operating system available from the operating system vendor.\n\n> \\[!WARNING]\n> Beta and Deprecated Images are provided \"as-is\", \"with all faults\" and \"as available\" and are excluded from the service level agreement and warranty. Beta Images may not be covered by customer support.\n\n### Standard GitHub-hosted runners for public repositories\n\nFor public repositories, jobs using the workflow labels shown in the table below will run with the associated specifications. With the exception of single-CPU runners, each GitHub-hosted runner is a new virtual machine (VM) hosted by GitHub. Single-CPU runners are hosted in a container on a shared VM—see [GitHub-hosted runners reference](/en/actions/reference/runners/github-hosted-runners#single-cpu-runners). Use of the standard GitHub-hosted runners is free and unlimited on public repositories.\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n
Virtual machine / containerProcessor (CPU)Memory (RAM)Storage (SSD)ArchitectureWorkflow label
Linux15 GB14 GB x64 \n ubuntu-slim\n
Linux416 GB14 GB x64 \n ubuntu-latest,\n ubuntu-24.04,\n ubuntu-22.04\n
Windows416 GB14 GB x64 \n windows-latest,\n windows-2025,\n windows-2025-vs2026,\n windows-2022\n
Linux416 GB14 GB arm64 \n ubuntu-24.04-arm,\n ubuntu-22.04-arm\n
Windows416 GB14 GBarm64\n windows-11-arm\n
macOS414 GB14 GB Intel \n macos-15-intel,\n macos-26-intel\n
macOS3 (M1)7 GB14 GB arm64 \n macos-latest,\n macos-14,\n macos-15,\n macos-26\n
\n\n### Standard GitHub-hosted runners for private repositories\n\nFor private repositories, jobs using the workflow labels shown in the table below will run on virtual machines with the associated specifications. These runners use your GitHub account's allotment of free minutes, and are then charged at the per minute rates. See [Actions runner pricing](/en/billing/reference/actions-minute-multipliers).\n\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
Virtual MachineProcessor (CPU)Memory (RAM)Storage (SSD)ArchitectureWorkflow label
Linux15 GB14 GB x64 \n ubuntu-slim\n
Linux28 GB14 GB x64 \n ubuntu-latest,\n ubuntu-24.04,\n ubuntu-22.04\n
Windows28 GB14 GB x64 \n windows-latest,\n windows-2025,\n windows-2022\n
Linux28 GB14 GB arm64 \n ubuntu-24.04-arm,\n ubuntu-22.04-arm\n
Windows28 GB14 GB arm64 \n windows-11-arm\n
macOS414 GB14 GB Intel \n macos-15-intel,\n macos-26-intel\n
macOS3 (M1)7 GB14 GB arm64 \n macos-latest,\n macos-14,\n macos-15,\n macos-26\n
\n\nWorkflow logs list the runner used to run a job. For more information, see [Viewing workflow run history](/en/actions/monitoring-and-troubleshooting-workflows/viewing-workflow-run-history).\n\n### Limitations for arm64 macOS runners\n\n* All actions provided by GitHub are compatible with arm64 GitHub-hosted runners. However, community actions may not be compatible with arm64 and need to be manually installed at runtime.\n* Nested-virtualization is not supported due to the limitation of Apple's Virtualization Framework.\n* Networking capabilities such as Azure private networking and assigning static IPs are not currently available for macOS larger runners.\n* The arm64 macOS runners do not have a static UUID/UDID assigned to them because Apple does not support this feature. However, Intel MacOS runners are assigned a static UDID, specifically `4203018E-580F-C1B5-9525-B745CECA79EB`. If you are building and signing on the same host you plan to test the build on, you can sign with a [development provisioning profile](https://developer.apple.com/help/account/provisioning-profiles/create-a-development-provisioning-profile/). If you do require a static UDID, you can use Intel runners and add their UDID to your Apple Developer account.\n\n### Single-CPU runners\n\nSingle-CPU GitHub-hosted runners are available in both public and private repositories. These runners—specified using the workflow label `ubuntu-slim`—offer a lower-cost option for running lightweight operations. This type of runner is optimized for automation tasks, issue operations and short-running jobs. They are not suitable for typical heavyweight CI/CD builds.\n\n`ubuntu-slim` runners execute Actions workflows in Ubuntu Linux, inside a container rather than a full VM instance. When the job begins, GitHub automatically provisions a new container for that job. All steps in the job execute in the container, allowing the steps in that job to share information using the runner's file system. When the job has finished, the container is automatically decommissioned. Each container provides hypervisor level 2 isolation.\n\n> \\[!NOTE]\n> The container for `ubuntu-slim` runners runs in unprivileged mode. This means that some operations requiring elevated privileges—such as mounting file systems, using Docker-in-Docker, or accessing low-level kernel features—are not supported.\n\nA minimal set of tools is installed on the `ubuntu-slim` runner image, appropriate for lightweight tasks. For details on what software is installed on the `ubuntu-slim` image, see the [README file](https://github.com/actions/runner-images/blob/main/images/ubuntu-slim/ubuntu-slim-Readme.md) in the `actions/runner-images` repository.\n\n#### Usage limits\n\nSingle-CPU runners follow the same concurrency model as other GitHub-hosted standard runners. See [Actions limits](/en/actions/reference/limits#job-concurrency-limits-for-github-hosted-runners). The concurrency for the runners is determined by your plan.\n\nThe job timeout for single-CPU runners is 15 minutes. If a job reaches this limit, the job is terminated and fails.\n\n### Larger runners\n\nCustomers on GitHub Team and GitHub Enterprise Cloud plans can choose from a range of managed virtual machines that have more resources than the [standard GitHub-hosted runners](/en/actions/how-tos/using-github-hosted-runners/using-github-hosted-runners/about-github-hosted-runners#supported-runners-and-hardware-resources). These machines are referred to as \"larger runners.\" They offer the following advanced features:\n\n* More RAM, CPU, and disk space\n* Static IP addresses\n* Azure private networking\n* The ability to group runners\n* Autoscaling to support concurrent workflows\n* GPU-powered runners\n\nThese larger runners are hosted by GitHub and have the runner application and other tools preinstalled.\n\nFor more information, see [Using larger runners](/en/actions/using-github-hosted-runners/about-larger-runners).\n\n## Administrative privileges\n\nThe Linux and macOS virtual machines both run using passwordless `sudo`. When you need to execute commands or install tools that require more privileges than the current user, you can use `sudo` without needing to provide a password. For more information, see the [Sudo Manual](https://www.sudo.ws/man/1.8.27/sudo.man.html).\n\nWindows virtual machines are configured to run as administrators with User Account Control (UAC) disabled. For more information, see [How User Account Control works](https://docs.microsoft.com/windows/security/identity-protection/user-account-control/how-user-account-control-works) in the Windows documentation.\n\n## IP addresses\n\nTo get a list of IP address ranges that GitHub Actions uses for GitHub-hosted runners, you can use the GitHub REST API. For more information, see the `actions` key in the response of the `GET /meta` endpoint. For more information, see [REST API endpoints for meta data](/en/rest/meta/meta#get-github-meta-information).\n\nWindows and Ubuntu runners are hosted in Azure and subsequently have the same IP address ranges as the Azure datacenters. macOS runners are hosted in GitHub's own macOS cloud.\n\nSince there are so many IP address ranges for GitHub-hosted runners, we do not recommend that you use these as allowlists for your internal resources. Instead, we recommend you use larger runners with a static IP address range, or self-hosted runners. For more information, see [Using larger runners](/en/actions/using-github-hosted-runners/about-larger-runners) or [Self-hosted runners](/en/actions/hosting-your-own-runners/managing-self-hosted-runners/about-self-hosted-runners).\n\nThe list of GitHub Actions IP addresses returned by the API is updated once a week.\n\n## Communication requirements for GitHub-hosted runners\n\nA GitHub-hosted runner must establish connections to GitHub-owned endpoints to perform essential communication operations. In addition, your runner may require access to additional networks that you specify or utilize within an action.\n\nTo ensure proper communications for GitHub-hosted runners between networks within your configuration, ensure that the following communications are allowed.\n\n> \\[!NOTE]\n> Some of the domains listed are configured using `CNAME` records. Some firewalls might require you to add rules recursively for all `CNAME` records. Note that the `CNAME` records might change in the future, and that only the domains listed will remain constant.\n\n**Needed for essential operations:**\n\n```shell copy\ngh.1s.fan\napi.github.com\n*.actions.githubusercontent.com\n```\n\n**Needed for downloading actions:**\n\n```shell copy\ncodeload.github.com\n```\n\n**Needed for uploading/downloading job summaries, logs, workflow artifacts, and caches:**\n\n```shell copy\nresults-receiver.actions.githubusercontent.com\n*.blob.core.windows.net\n```\n\n**Needed for runner version updates:**\n\n```shell copy\nobjects.github.com\nobjects-origin.githubusercontent.com\ngithub-releases.github.com\ngithub-registry-files.githubusercontent.com\n```\n\n**Needed for retrieving OIDC tokens:**\n\n```shell copy\n*.actions.githubusercontent.com\n```\n\n**Needed for downloading or publishing packages or containers to GitHub Packages:**\n\n```shell copy\n*.pkg.gh.1s.fan\npkg-containers.githubusercontent.com\nghcr.github.com\n```\n\n**Needed for Git Large File Storage**\n\n```shell copy\ngithub-cloud.githubusercontent.com\ngithub-cloud.s3.amazonaws.com\n```\n\n**Needed for jobs for Dependabot updates**\n\n```shell copy\ndependabot-actions.githubapp.com\n```\n\n**Needed for downloading release assets:**\n\n```shell copy\nrelease-assets.github.com\n```\n\n**Needed for VNet:**\n\n```shell copy\napi.snapcraft.io\n```\n\n## File systems\n\nGitHub executes actions and shell commands in specific directories on the virtual machine. The file paths on virtual machines are not static. Use the environment variables GitHub provides to construct file paths for the `home`, `workspace`, and `workflow` directories.\n\n| Directory | Environment variable | Description |\n| --------------------- | -------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| `home` | `HOME` | Contains user-related data. For example, this directory could contain credentials from a login attempt. |\n| `workspace` | `GITHUB_WORKSPACE` | Actions and shell commands execute in this directory. An action can modify the contents of this directory, which subsequent actions can access. |\n| `workflow/event.json` | `GITHUB_EVENT_PATH` | The `POST` payload of the webhook event that triggered the workflow. GitHub rewrites this each time an action executes to isolate file content between actions. |\n\nFor a list of the environment variables GitHub creates for each workflow, see [Store information in variables](/en/actions/learn-github-actions/variables#default-environment-variables).\n\n### Docker container filesystem\n\nActions that run in Docker containers have static directories under the `/github` path. However, we strongly recommend using the default environment variables to construct file paths in Docker containers.\n\nGitHub reserves the `/github` path prefix and creates three directories for actions.\n\n* `/github/home`\n* `/github/workspace` - **Note:** GitHub Actions must be run by the default Docker user (root). Ensure your Dockerfile does not set the `USER` instruction, otherwise you will not be able to access `GITHUB_WORKSPACE`.\n* `/github/workflow`"}