Setting up O3DE from GitHub

Getting the source for Open 3D Engine (O3DE) from GitHub is a great way to set up your development environment. This method lets you easily sync future engine updates and make contributions to the open source project base. For instructions on setting up O3DE from GitHub, check out the following video or the tutorial on this page.

The video and written instructions in this section guide you through the following steps:

  • Configure credentials for Git LFS.
  • Fork and clone the O3DE GitHub repo.
  • Build the O3DE engine.
  • Register the engine.


The GitHub setup instructions assume that you have:

  • Git client installed (1.8.2 or later required, 2.23.4 or later recommended).

Configure credentials for Git LFS

The O3DE GitHub repo uses the Git Large File Storage (LFS) system for storing large binary files. The following instructions will prepare your PC to authenticate and download these files automatically when you clone, fetch, or pull from the repo.

To configure for Git LFS

  1. Verify that Git LFS is installed.

    git lfs install

    If the output from this command is “Git LFS initialized”, then you already have Git LFS installed. If you didn’t have Git LFS installed, this command will install it for you.

    sudo apt install git-lfs
  2. Verify that you have a credential manager set up for Git. Recent versions of Git install a credential manager to store your credentials so that you don’t have to enter them for every request.

    git config credential.helper

    Common examples of results to this git config command include manager-core, wincred, osxkeychain, and cache. However, if you don’t see anything in response to this command, you can install Git Credential Manager Core as your credential manager.

  3. Create a GitHub personal access token with repo and read:org scope.

    1. Go to .

      (GitHub menu equivalent: Settings > Developer Settings > Personal Access Tokens)

    2. Choose Generate new token.

    3. (Optional) Add an entry under Note. This is only for your reference. You can use it as a personal reminder of what the token is for.

    4. Under Select scopes, select the following:

      • repo (all)
      • read:org (under admin:org)
    5. Choose Generate token. Keep the token handy (but private!) for use in later steps.

    This token can be used in place of your GitHub password, so protect it just as you would your GitHub password!

Fork and clone

All contributions to the O3DE repo are expected to be staged in a fork before submitting a pull request. Refer to the documentation on Contributing to O3DE Code Sources in the O3DE Contributor Guide for details about the contribution workflow.

To fork and clone O3DE on your PC from GitHub

  1. Create a fork of the O3DE GitHub repo from . Alternatively, if you are working as a member of a team that has already created a fork, you can skip this step and use your team’s existing fork.

    Create a fork using the Fork button on the O3DE GitHub repo

    For general instructions and help with creating and using forks in GitHub, see the GitHub Guide on Forking Projects .

  2. Clone your forked repo. Use your preferred Git UI or a command line to clone the repo in a directory of your choice. You will need your GitHub username and the personal access token that you created earlier.

    1. Clone the repo from a fork.

      # Cloning from your personal fork.
      git clone
      # Cloning from your team's fork.
      git clone
    2. If you are shown a Connect to GitHub dialog box, sign in to GitHub as instructed, using either your browser or your personal access token.

      GitHub sign in dialog box

    3. Enter your credentials for the LFS endpoint in the next sign in dialog box. Use your GitHub username and your personal access token for the password.

      Credential manager asking for LFS credentials

    4. Verify you have the LFS files.

      When the clone operation completes, verify that you have all of the files from the LFS endpoint. You should no longer receive credential prompts.

      # Change to the directory name that was created when you cloned the engine repo.
      # The default is o3de.
      cd o3de
      git lfs pull
  3. Add a remote to track the upstream repo. This will enable you to pull updates from the O3DE repo directly into your local clone.

    git remote add upstream

    Verify the upstream repository. You should see the URL for the fork as origin, and the URL for the original repository as upstream.

    git remote -v


    origin<FORK>/o3de.git (fetch)
    origin<FORK>/o3de.git (push)
    upstream (fetch)
    upstream (push)
  4. (Optional) If you don’t expect to make changes to these files, ignore this step. Otherwise, update the LFS URL to include your fork. This lets you push changes to files in the LFS. For complete instructions and the DISTRIBUTION to use, open the .lfsconfig file at the root of the repository.

    git config lfs.url https://<DISTRIBUTION><FORK> 

    You might be prompted to re-authenticate the next time that you pull or push. Remember to use your GitHub personal access token, and not your GitHub password.

    If you wish to revert this change, you can run the following command:

    git config --unset lfs.url 
  5. Any time that you want to sync the latest files from the repo and LFS, you can merge changes from the upstream branch you are working with. The default branch is development.

    git fetch upstream
    git merge upstream/development
  6. In a typical contributor workflow, you will primarily work from a branch off of your fork’s development branch. You can use the git switch command to create your local working branch and set it to track the upstream development branch.

    git fetch upstream
    git switch -c <NEW_WORKING_BRANCH> upstream/development

    When set up to track an upstream branch, you can use the git pull command whenever you want to sync the latest changes from upstream.

    git pull

For more information and examples of common contributor workflows, refer to O3DE Code Contribution GitHub Workflow in the Contributor Guide.

To complete setup, proceed to the engine build and registration instructions that match your platform.