Pages limits

Who can use this feature?

Pages is available in public repositories with Free and Free for organizations, and in public and private repositories with Pro, Team, Enterprise Cloud, and Enterprise Server. For more information, see ’s plans.

Pages now uses Actions to execute the Jekyll build. When using a branch as the source of your build, Actions must be enabled in your repository if you want to use the built-in Jekyll workflow. Alternatively, if Actions is unavailable or disabled, adding a .nojekyll file to the root of your source branch will bypass the Jekyll build process and deploy the content directly. For more information on enabling Actions, see Managing Actions settings for a repository.

In this article

Pages is not intended for or allowed to be used as a free web-hosting service to run your online business, e-commerce site, or any other website that is primarily directed at either facilitating commercial transactions or providing commercial software as a service (SaaS). Pages sites shouldn't be used for sensitive transactions like sending passwords or credit card numbers.

In addition, your use of Pages is subject to the Terms of Service, including the restrictions on get-rich-quick schemes, sexually obscene content, and violent or threatening content or activity.

Pages sites are subject to the following usage limits:

  • You can only create one user or organization site for each account on .

  • Pages source repositories have a recommended limit of 1 GB. For more information, see About large files on .

  • Published Pages sites may be no larger than 1 GB.

  • Pages deployments will timeout if they take longer than 10 minutes.

  • Pages sites have a soft bandwidth limit of 100 GB per month.

  • Pages sites have a soft limit of 10 builds per hour. This limit does not apply if you build and publish your site with a custom Actions workflow.

  • In order to provide consistent quality of service for all Pages sites, rate limits may apply. These rate limits are not intended to interfere with legitimate uses of Pages. If your request triggers rate limiting, you will receive an appropriate response with an HTTP status code of 429, along with an informative HTML body.

If your site exceeds these usage quotas, we may not be able to serve your site, or you may receive a polite email from Support suggesting strategies for reducing your site's impact on our servers, including putting a third-party content distribution network (CDN) in front of your site, making use of other features such as releases, or moving to a different hosting service that might better fit your needs.

If you're a managed user account, your use of Pages is limited.

  • Pages sites can only be published from repositories owned by organizations.
  • Pages sites are always privately published, and you cannot change this visibility. For more information, see Changing the visibility of your Pages site.
  • You cannot create an organization site (a site published from a repository named <organization>..io)

For more information about Enterprise Managed Users, see About Enterprise Managed Users.

Using Pages to create a copy of an existing website as a learning exercise is not prohibited. However, in addition to complying with the Terms of Service, you must write the code yourself, the site must not collect any user data, and you must include a prominent disclaimer on the site indicating that the project is not associated with the original and was only created for educational purposes.