How to Use VS Code in Your Browser with vscode.dev

VS Code for the Web, at vscode.dev, is a free, zero-install version of the editor that runs entirely in your browser. You can read code, make quick edits, review pull requests, and browse repositories without downloading anything.

It is not a full replacement for the desktop app. There is no terminal, no debugger, and only a subset of extensions work. But for quick tasks on any machine with a browser, it is the fastest way to get into a codebase.

What you can do in vscode.dev

The browser editor covers the most common lightweight tasks:

• Browse and search code in any GitHub or Azure Repos repository
• Make quick edits and commit them directly from the browser
• Open local files and folders (in Chrome and Edge)
• Preview Markdown with syntax highlighting
• Use themes and web-compatible extensions
• Review pull requests with full syntax highlighting

What you cannot do in the browser: run code, use a terminal, debug, or run most language servers. For full development, switch to the desktop app or use GitHub Codespaces.

Open a GitHub repository

The fastest way to open a repo is with a URL. Type this pattern in your browser address bar:

plaintext

vscode.dev/github/owner/repo

For example, vscode.dev/github/microsoft/vscode opens the VS Code source code directly in the browser editor. You can browse files, search code, and make edits without cloning anything.

If you use Chrome or Edge, install the vscode.dev browser extension. Then type code in the address bar followed by a repository name to open it instantly.

From inside the editor, you can also use the Command Palette. Open it with F1, run Open Remote Repository..., and paste a GitHub URL.

Open local files and folders

In Chrome or Edge, vscode.dev can access your local file system through the File System API. Open a folder by going to File > Open Folder and selecting a folder on your machine.

Firefox and Safari do not support the File System API, so you cannot open folders locally in those browsers. You can still open individual files through File > New File and paste content in.

Language support in the browser

The coding experience varies by language because there is no compiler or language server running in the background.

The Language Status indicator in the Status Bar shows what level of support your current file has. Hover over it to see details.

Extensions in the browser

Only some extensions work in the browser sandbox. Theme extensions and syntax grammars usually work without changes. Extensions that need a file system, runtime, or native code are not available.

Open the Extensions view to browse and install. Extensions that cannot run in the browser show a warning icon and a "Learn Why" link.

When you install an extension in the browser, it saves to the browser's local storage. If you enable Settings Sync, your web extensions sync across browsers and the desktop app.

Continue working on the desktop

If you start in the browser and need a terminal or debugger, use the Continue Working On command. Open the Command Palette with F1, run the command, and choose to clone the repository locally, reopen on the desktop, or create a GitHub codespace.

Your uncommitted changes can travel with you through Cloud Changes, a VS Code service that stores your pending edits temporarily.

Save your work

When editing a remote repository, your changes save to the browser's local storage until you commit them. Open the Source Control view, write a commit message, and commit to persist your changes to the repository.

For local files, Auto Save works the same as the desktop app. Enable it from File > Auto Save.

Use on tablets and mobile

vscode.dev runs on iPads and Android tablets through the browser. The experience is best on larger screens. Mobile phones work but the small screen limits what you can do comfortably.

For more on the full desktop experience, see the VS Code overview. If you are comparing editor options, see Visual Studio vs Visual Studio Code.