The web-based editor

Use the web-based editor from your repository or pull request to create and commit changes.

Note: The web-based editor is currently in beta preview. You can provide feedback in our Discussions.

About the web-based editor

The web-based editor introduces a lightweight editing experience that runs entirely in your browser. With the web-based editor, you can navigate files and source code repositories from GitHub, and make and commit code changes. You can open any repository, fork, or pull request in the editor.

The web-based editor is available to everyone for free on

The web-based editor provides many of the benefits of Visual Studio Code, such as search, syntax highlighting, and a source control view. You can also use Settings Sync to share your own Visual Studio Code settings with the editor. For more information, see "Settings Sync" in the Visual Studio Code documentation.

The web-based editor runs entirely in your browser’s sandbox. The editor doesn’t clone the repository, but instead uses the GitHub Repositories extension to carry out most of the functionality that you will use. Your work is saved in the browser’s local storage until you commit it. You should commit your changes regularly to ensure that they're always accessible.

Opening the web-based editor

You can open any GitHub repository in the web-based editor in either of the following ways:

  • Press . while browsing any repository or pull request on GitHub.
  • Change the URL from "" to "".

Codespaces and the web-based editor

Both the web-based editor and Codespaces allow you to edit your code straight from your repository. However, both have slightly different benefits, depending on your use case.

web-based editorCodespaces
CostFree.Costs for compute and storage. For information on pricing, see "Codespaces pricing."
AvailabilityAvailable to everyone on for organizations using GitHub Team or GitHub Enterprise Cloud.
Start upThe web-based editor opens instantly with a key-press and you can start using it right away, without having to wait for additional configuration or installation.When you create or resume a codespace, the codespace is assigned a VM and the container is configured based on the contents of a devcontainer.json file. This set up may take a few minutes to create the environment. For more information, see "Creating a Codespace."
ComputeThere is no associated compute, so you won’t be able to build and run your code or use the integrated terminal.With Codespaces, you get the power of dedicated VM on which you can run and debug your application.
Terminal accessNone.Codespaces provides a common set of tools by default, meaning that you can use the Terminal exactly as you would in your local environment.
ExtensionsOnly a subset of extensions that can run in the web will appear in the Extensions View and can be installed. For more information, see "Using extensions."With Codespaces, you can use most extensions from the Visual Studio Code Marketplace.

Continue working on Codespaces

You can start your workflow in the web-based editor and continue working on a codespace, provided you have access to Codespaces. If you try to access the Run and Debug View or the Terminal, you'll be notified that they are not available in the web-based editor.

To continue your work in a codespace, click Continue Working on… and select Create New Codespace to create a codespace on your current branch. Before you choose this option, you must commit any changes.

A screenshot that shows the "Continue Working on" button in the UI

Using source control

When you use the web-based editor, all actions are managed through the Source Control View, which is located in the Activity Bar on the left hand side. For more information on the Source Control View, see "Version Control" in the Visual Studio Code documentation.

Because the web-based editor uses the GitHub Repositories extension to power its functionality, you can switch branches without needing to stash changes. For more information, see "GitHub Repositories" in the Visual Studio Code documentation.

Create a new branch

  1. If the current branch is not shown in the status bar, at the bottom of your codespace, right-click the status bar and select Source control.
  2. Click the branch name in the status bar. The branch in the status bar
  3. In the drop-down, either click the branch you want to switch to, or enter the name for a new branch and click Create new branch. Choose from the branch menu Any uncommitted changes you have made in your old branch will be available on your new branch.

Commit your changes

  1. In the Activity Bar, click the Source Control view. Source control view
  2. To stage your changes, click + next to the file you've changed, or next to Changes if you've changed multiple files and you want to stage them all. Source control side bar with staging button highlighted
  3. Type a commit message describing the change you've made. Source control side bar with a commit message
  4. To commit your staged changes, click the check mark at the top the source control side bar. Click the check mark icon
  5. Once you have committed your changes, they will automatically be pushed to your branch on GitHub.

Create a pull request

  1. After you've committed changes to your local copy of the repository, click the Create Pull Request icon. Source control side bar with staging button highlighted
  2. Check that the local branch and repository you're merging from, and the remote branch and repository you're merging into, are correct. Then give the pull request a title and a description. Source control side bar with staging button highlighted
  3. Click Create.

Working with an existing pull request

You can use the web-based editor to work with an existing pull request.

  1. Browse to the pull request you'd like to open in the web-based editor.
  2. Press . to open the pull request in the web-based editor.
  3. Once you have made any changes, commit them using the steps in Commit your changes. Your changes will be committed directly to the branch, it's not necessary to push the changes.

Using extensions

The web-based editor supports Visual Studio Code extensions that have been specifically created or updated to run in the web. These extensions are known as "web extensions". To learn how you can create a web extension or update your existing extension to work for the web, see "Web extensions" in the Visual Studio Code documentation.

Extensions that can run in the web-based editor will appear in the Extensions View and can be installed. If you use Settings Sync, any compatible extensions are also installed automatically. For information, see "Settings Sync" in the Visual Studio Code documentation.


If you have issues opening the web-based editor, try the following:

  • Make sure you are signed in to GitHub.
  • Disable any ad blockers.
  • Use a non-incognito window in your browser to open the web-based editor.

Known limitations

  • The web-based editor is currently supported in Chrome (and various other Chromium-based browsers), Edge, Firefox, and Safari. We recommend that you use the latest versions of these browsers.
  • Some keybindings may not work, depending on the browser you are using. These keybinding limitations are documented in the "Known limitations and adaptations" section of the Visual Studio Code documentation.

Did this doc help you?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

Or, learn how to contribute.