Visual Studio Code for the Web
Visual Studio Code for the Web provides a free, zero-install Microsoft Visual Studio Code experience running entirely in your browser, allowing you to quickly and safely browse source code repositories and make lightweight code changes. To get started, go to https://vscode.dev in your browser.
VS Code for the Web has many of the features of VS Code Desktop that you love, including search and syntax highlighting while browsing and editing, along with extension support to work on your codebase and make simpler edits. In addition to opening repositories, forks, and pull requests from source control providers like GitHub and Azure Repos, you can also work with code that is stored on your local machine.
VS Code for the Web runs entirely in your web browser, so there are certain limitations compared to the desktop experience, which you can read more about below.
Relationship to VS Code Desktop
VS Code for the Web provides a browser-based experience for navigating files and repositories and committing lightweight code changes. However, if you need access to a runtime to run, build, or debug your code, you want to use platform features such as a terminal, or you want to run extensions that aren't supported in the web, we recommend moving your work to the desktop application, GitHub Codespaces, or using Remote - Tunnels for the full capabilities of VS Code. In addition, VS Code Desktop lets you use a full set of keyboard shortcuts not limited by your browser.
When you're ready to switch, you'll be able to "upgrade" to the full VS Code experience with a few clicks.
You can also switch between the Stable and Insiders versions of VS Code for the Web by selecting the gear icon, then Switch to Insiders Version..., or by navigating directly to https://insiders.vscode.dev.
Opening a project
By navigating to https://vscode.dev, you can create a new local file or project, work on an existing local project, or access source code repositories hosted elsewhere, such as on GitHub and Azure Repos (part of Azure DevOps).
You can create a new local file in the web just as you would in a VS Code Desktop environment, using File > New File from the Command Palette (F1).
You can open a GitHub repository in VS Code for the Web directly from a URL, following the schema:
https://vscode.dev/github/<organization>/<repo>. Using the VS Code repository as an example, this would look like:
GitHub Repositories allows you to remotely browse and edit a repository from within the editor, without needing to pull code onto your local machine. You can learn more about the extension and how it works in our GitHub Repositories guide.
Note: The GitHub Repositories extension works in VS Code Desktop as well to provide fast repository browsing and editing. Once you have the extension installed, you can open a repo with the GitHub Repositories: Open Repository... command.
You can also open GitHub repositories in
vscode.dev through your browser's search bar (aka omnibox) by installing the
vscode.dev extension for Chrome and Edge. Then, type
code to activate the omnibox, followed by your repository's name. Suggestions are populated by your browser search history, so if the repo you want doesn't come up, you can also type in the fully qualified
<owner>/<repo> name to open it, for example
If you're already in VS Code for the Web at https://vscode.dev, you can alternatively navigate to different repos via the Remote Repositories extension commands. Select the remote indicator in the lower left of the Status bar, and you'll be presented with the Open Remote Repository... command.
You can open Azure Repos just like Github repos in VS Code for the Web.
When you navigate to a URL with the schema
https://vscode.dev/azurerepos/<organization>/<project>/<repo>, you will be able to read, search the files in the repo, and commit your changes to Azure Repos. You can fetch, pull, and sync changes, and view branches.
You can open any repository, branch, or tag from Azure Repos in VS Code for the Web by prefixing
vscode.dev to the Azure Repos URL.
Alternatively, when you are on an Azure DevOps repository or pull request, you can press (.) to open it in VS Code for the Web.
More custom URLs
Like in the desktop, you can customize VS Code for the Web through a rich ecosystem of extensions that support just about every back end, language, and service.
vscode.dev includes URLs that provide shortcuts to common experiences.
We've explored a couple of URLs already (
vscode.dev/azurerepos). Here's a more complete list:
||More info above|
||More info above|
|Visual Studio Live Share||
||More info below|
|Visual Studio Marketplace||
||Example route to edit this extension|
||Office Scripts docs|
||Power Pages docs|
||More info below|
|VS Code for Education||
||VS Code for Education landing page|
|Azure Machine Learning (AML)||
Please note that some URLs must be entered in a specific way (for example,
vscode.dev/liveshare requires an active Live Share session). Please review each service's documentation for specific access and usage information.
There's more information on some of these URLs below.
You can share and experience color themes through VS Code for the Web through the URL schema:
Note: The color theme URL schema works for themes that are fully declarative (no code).
An extension can define multiple themes. You can use the schema
/theme/<extensionId>/<themeName>. If no
themeName is specified, VS Code for the Web will take the first theme.
As a theme author, you can add the following badge to your extension readme to allow users to easily try out your theme in VS Code for the Web (replacing
<extensionId> with your theme extension's unique identifier):
[![Preview in vscode.dev](https://img.shields.io/badge/preview%20in-vscode.dev-blue)](https://vscode.dev/theme/<extensionId>)
Visual Studio Live Share
Live Share guest sessions are available in the browser through the
https://vscode.dev/liveshare URL. The
sessionId will be passed to the extension to make joining a seamless experience.
Continue working in a different environment
In some cases, you will want to access a different environment that has the ability to run code. You can switch to working on a repository in a development environment that has support for a local file system and full language and development tooling.
The GitHub Repositories extension makes it easy for you to clone the repository locally, reopen it on the desktop, or create a GitHub codespace for the current repository (if you have the GitHub Codespaces extension installed and access to create GitHub codespaces). To do this, use the Continue Working On... command available from the Command Palette (F1) or click on the Remote indicator in the Status bar.
Saving and sharing work
When working on a local file in the web, your work is saved automatically if you have Auto Save enabled. You can also save manually as you do when working in desktop VS Code (for example File > Save).
When working on a remote repository, your work is saved in the browser's local storage until you commit it. If you open a repo or pull request using GitHub Repositories, you can push your changes in the Source Control view to persist any new work.
You can also continue working in other environments via Continue Working On.
The first time that you use Continue Working On with uncommitted changes, you will have the option to bring your edits to your selected development environment using Cloud Changes, which uses a VS Code service to store your pending changes. This is described further in the GitHub Repositories doc.
Use your own compute with Remote Tunnels
You may develop against another machine in VS Code for the Web using the Remote - Tunnels extension.
The Remote - Tunnels extension lets you connect to a remote machine, like a desktop PC or virtual machine (VM), via a secure tunnel. You can then securely connect to that machine from anywhere, without the requirement of SSH. This lets you "bring your own compute" to vscode.dev, enabling additional scenarios like running your code in the browser.
You may learn more about Remote - Tunnels in its documentation.
VS Code for the Web runs entirely in your web browser's sandbox and offers a very limited execution environment.
When accessing code from remote repositories, the web editor doesn't "clone" the repo, but instead loads the code by invoking the services' APIs directly from your browser; this further reduces the attack surface when cloning untrusted repositories.
When working with local files, VS Code for the Web loads them through your browser's file system access APIs, which limit the scope of what the browser can access.
Similar to GitHub Codespaces, VS Code for the Web can run on tablets, like iPads.
Language support is a bit more nuanced on the web, including code editing, navigation, and browsing. The desktop experiences are typically powered by language services and compilers that expect a file system, runtime, and compute environment. In the browser, these experiences are powered by language services running in the browser that provide source code tokenization and syntax colorization, completions, and many single-file operations.
Generally, experiences fall into the following categories:
- Good: For most programming languages, VS Code for the Web gives you code syntax colorization, text-based completions, and bracket pair colorization. Using a Tree-sitter syntax tree through the anycode extension, we're able to provide additional experiences such as Outline/Go to Symbol and Symbol Search for popular languages such as C/C++, C#, Java, PHP, Rust, and Go.
- Best: For many "webby" languages, such as JSON, HTML, CSS, and LESS, etc., the coding experience in vscode.dev is nearly identical to the desktop (including Markdown preview!).
You can determine the level of language support in your current file through the Language Status Indicator in the Status bar:
Since VS Code for the Web runs completely within the browser, some experiences will naturally be more constrained when compared to what you can do in the desktop app. For example, the terminal and debugger are not available, which makes sense since you can't compile, run, and debug a Rust or Go application within the browser sandbox.
Only a subset of extensions can run in the browser. You can use the Extensions view to install extensions in the web, and extensions that cannot be installed will have a warning icon and Learn Why link. We expect more extensions to become enabled over time.
When you install an extension, it is saved in the browser's local storage. You can ensure your extensions are synced across VS Code instances, including different browsers and even the desktop, by enabling Settings Sync.
When an Extension Pack contains extensions that do not run in the browser sandbox, you will get an informational message with the option to see the extensions included in the pack.
When extensions are executed in the browser sandbox, they are more restricted. Extensions that are purely declarative, such as most themes, snippets, or grammars, can run unmodified and are available in VS Code for the Web without any modification from the extension authors. Extensions that are running code need to be updated to support running in the browser sandbox. You can read more about what is involved to support extensions in the browser in the web extension authors guide.
There are also extensions that run in the browser with partial support only. A good example is a language extension that restricts its support to single files or the currently opened files.
File system API
Edge and Chrome today support the File System API, allowing web pages to access the local file system. If your browser does not support the File System API, you cannot open a folder locally, but you can open files instead.
You can use VS Code for the Web in Chrome, Edge, Firefox, and Safari.
Webviews might appear differently or have some unexpected behavior in Firefox and Safari. You can view issue queries in the VS Code GitHub repo to track issues related to specific browsers, such as with the Safari label and Firefox label.
There are additional steps you can take to improve your browser experience using VS Code for the Web. Review the Additional browser setup section for more information.
You can use VS Code for the Web on mobile devices, but smaller screens may have certain limitations.
Certain keybindings may also work differently in the web.
|⇧⌘P (Windows, Linux Ctrl+Shift+P) won't launch the Command Palette in Firefox.||⇧⌘P (Windows, Linux Ctrl+Shift+P) is reserved in Firefox.
As a workaround, use F1 to launch the Command Palette.
|⌘N (Windows, Linux Ctrl+N) for new file doesn't work in web.||⌘N (Windows, Linux Ctrl+N) opens a new window instead.
As a workaround, you can use Ctrl+Alt+N (Cmd+Alt+N on macOS).
|⌘W (Windows, Linux Ctrl+W) for closing an editor doesn't work in web.||⌘W (Windows, Linux Ctrl+W) closes the current tab in browsers.
As a workaround, you can use Ctrl+Shift+Alt+N (Cmd+Shift+Alt+N on macOS).
|⇧⌘B (Windows, Linux Ctrl+Shift+B) will not toggle the favorites bar in the browser.||VS Code for the Web overrides this and redirects to the "Build" menu in the Command Palette.|
|Alt+Left and Alt+Right should navigate within the editor but may incorrectly trigger tab history navigation.||If focus is outside the editor, these shortcuts trigger tab history navigation instead.|
Additional browser setup
There are additional browser configuration steps you can take when working with VS Code in a browser.
Opening new tabs and windows
In certain cases, you may need to open a new tab or window while working in VS Code for the Web. VS Code might ask you for permission to access the clipboard when reading from it. Depending on your browser, you may grant access to the clipboard or otherwise allow for pop-up windows in different ways:
- Chrome, Edge, Firefox: Search for "site permissions" in your browser's settings, or look for the following option in the address bar on the right:
- Safari: In the Safari browser, go to Preferences... > Websites > Pop-up Windows > the domain you're accessing (for example,
vscode.dev), and select Allow from the dropdown.