How To use Live Share with Visual Studio Code

Updated on September 1, 2021

James Quick

How To use Live Share with Visual Studio Code


Live Share is an extension for Visual Studio Code that enables real-time collaboration between developers. It gives users the ability to share a session with someone else, allowing them to edit code as well as share a server and debugging session.

As you progress through this article you will see screenshots from two different computers to demonstrate a working example of how Live Share works.

For clarification purposes, this tutorial will refer to the person who sends the session invite as the inviter and the person who accepts the invite as the invitee.


Before you begin this guide you’ll need the following:

  • A Microsoft or GitHub account.
  • Download and install the latest version of Visual Studio Code.

Step 1 — Downloading the Extension

Note: Modern versions of Visual Studio Code now include Live Share by default. There is also a Live Share Extension Pack that combines Live Share and Live Share Audio extensions. This tutorial will focus on the Live Share extension.

The first step to taking advantage of Live Share is to install it as an extension. In VS Code, you can open up the extensions tab, search for Live Share, click install, and then reload when the install is finished.

Visual Studio Code extension tab displaying VS Live Share

After that, you’ll need to sign in. As of now, you can choose to log in with a Microsoft or GitHub account.

To sign in, use the Sign In button in the bottom status bar with the person icon.

Step 2 — Sharing and Joining a Session

After you’re all signed in, you’re ready to create a session to share with others. Be sure to only share live sessions with people you trust. As you’ll see, you will be granting users certain access that can be detrimental if used incorrectly.

Start by clicking your username in the bottom status bar and choose Start Collaboration Session from the available options. Alternatively, you can open the Command Palette (CMD+SHIFT+P on Mac, CTRL+SHIFT+P on Windows) and type Start Collaboration Session

Command Pallete open with Start Collaboration Session selected

You’ll be notified that your invite link has been copied to the clipboard.

Notification of link being copied to clipboard

Share this link with someone to invite them to your session.

From the invitee point of view, to accept an invite, click your username in the bottom status bar and choose Join Collaboration Session. Alternatively, you can open the Command Palette and type Join Collabation Session.

Command Pallete open with Join Collaboration Session selected

When prompted, enter the collaborative session link sent to you by the inviter. The inviter will be notified when someone joins the session.

Notification that someone has joined the session

By default, joining a session will automatically have the invitee follow the inviter as they navigate code. This will happen until the invitee makes a move themselves. From there, both sides are free to navigate and edit as they see fit. Additionally, both sides will see a marker showing where the other editor is as shown here.

An example of cursors indicating the position of the invitee and inviter in the document

You can also select a piece of code for it to be highlighted on the other user’s computer. You can use this to draw their attention to a section of code for example.

An example of highlighted lines of code visible to the other user

Step 3 — Limiting Collaborators

By default, when sharing a session with someone, they will have access to edit all of the files within the workspace. It’s one thing to trust someone to edit specific files, but opening up your entire workspace to them may not be preferred.

Thankfully, Live Share gives you the ability to limit what files collaborators can view and edit.

Create a .vsls.json file to limit collaborators. The basic configuration will look something like this:

    "$schema": "http://json.schemastore.org/vsls",
    "gitignore": "none",
    "excludeFiles": [],
    "hideFiles": []

The two keys we care most about are excludeFiles and hideFiles. excludeFiles is an array of file names that you don’t want users to have access to. hideFiles is similar except collaborators will be able to see hidden files under certain circumstances. Read the documentation on controlling file access and visibility for more details about security.

Step 4 — Sharing a Server

It can be challenging to share with others when working on an application locally. You could check the code into GitHub and have the other person clone, but then they still have to install dependencies and start the server themselves. With Live Share you can start the server locally and the other person can get access to the same running application.

As the inviter, start your server as normal. Then, click the username in the bottom status bar and choose Share Server. Alternatively, open the Command Palette and type Share Server.

Command Pallete open with Share Server selected

As the invitee, you then can navigate to localhost on the proper port to see the server.

An example of a project running on localhost available to the invitees

Step 5 — Sharing a Terminal

There may be a scenario where you’d like to teach someone commands in the terminal, such as how to navigate the file system, working with npm, starting your dev server, etc. As with the earlier features, this can be complicated to do remotely. Live Share also includes a terminal sharing feature to solve this problem.

Sharing a terminal is similar to sharing your server. Similar to the other features, select the Share Terminal option. After that, choose between read only or read/write permissions for collaborators.

Command Pallete open with Share Terminal selected

After the terminal has been shared, collaborators will be able to view (and edit, if applicable) the terminal. This screenshot displays the invitees view of the terminal after the inviter echoed a message to the screen:

An example of an invitee terminal displaying a message from the inviter

From here, you could show the invitee how to start a development server, build system, or anything else that might be relevant.


There are a lot of useful features included in this extension that. With Visual Studio Code quickly becoming a favorite editor for web developers, this extension potentially changes the way we approach teaching, mentoring, collaboration, debugging, etc.

Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.

Learn more about us

About the authors
Default avatar
James Quick


Still looking for an answer?

Ask a questionSearch for more help

Was this helpful?
Leave a comment

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up

Join the Tech Talk
Success! Thank you! Please check your email for further details.

Please complete your information!

Featured on Community

Get our biweekly newsletter

Sign up for Infrastructure as a Newsletter.

Hollie's Hub for Good

Working on improving health and education, reducing inequality, and spurring economic growth? We'd like to help.

Become a contributor

Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.

Welcome to the developer cloud

DigitalOcean makes it simple to launch in the cloud and scale up as you grow — whether you're running one virtual machine or ten thousand.

Learn more
DigitalOcean Cloud Control Panel