VS Code for Beginners: Setup, Extensions & Shortcuts in 2026

A friendly setup guide to Visual Studio Code in 2026. Install it the right way, configure the essential settings, learn the must-know keyboard shortcuts, and add the few extensions that actually matter on day one.

VS Codebeginner
11 min read

According to every developer survey of the last seven years, Visual Studio Code is the most popular code editor on Earth — and in 2026 that lead has only grown thanks to first-class AI integration and a colossal extension ecosystem. The good news for beginners: it is free, cross-platform, and gentle to learn. The trap: it is also deep, and most beginners barely scratch its surface.

This guide is the setup-and-shortcuts walkthrough I wish someone had given me on day one. We will install VS Code, set up settings sync, learn the dozen keyboard shortcuts that will save you hours every week, configure the integrated terminal and Git panel, and make the editor feel like home. By the end you will be moving twice as fast as before.

Installing and First Launch

Download from code.visualstudio.com — there are native builds for macOS, Windows, and Linux. On macOS, drag to /Applications. On Windows, run the installer (check "Add to PATH" and "Add 'Open with Code' to the context menu"). On Linux, your distro probably has a .deb, .rpm, or Flatpak.

The first thing to do after installing: open the Command Palette with Cmd+Shift+P (Mac) or Ctrl+Shift+P (Windows/Linux), type "Shell Command: Install 'code' command in PATH", and run it. Now you can launch VS Code from any folder with code . — a habit that becomes instinctive.

Sign In and Sync Settings

Click the little person icon at the bottom-left and sign in with GitHub. Enable Settings Sync (Command Palette → "Settings Sync: Turn On"). Now your settings, keyboard shortcuts, extensions, and snippets follow you to any machine you log into. If you ever switch computers, you are five minutes away from your full setup.

Pick a theme you actually enjoy looking at — the Command Palette → "Color Theme" lists the built-ins, and the marketplace has thousands more. The font choice matters too: install a programmer font with ligatures (JetBrains Mono, Fira Code) and set it in Settings → "Editor: Font Family."

The Layout in 60 Seconds

Five regions you will use every day:

  • Activity Bar (far left) — switches between Explorer, Search, Source Control, Run/Debug, Extensions.
  • Side Bar — shows whichever activity you picked.
  • Editor Group (center) — your tabs and split panes.
  • Panel (bottom) — Terminal, Problems, Output, Debug Console.
  • Status Bar (very bottom) — current branch, errors/warnings count, language, encoding, line/column.

Toggle the side bar with Cmd+B, the panel with Cmd+J, the activity bar with Cmd+Shift+P → "View: Toggle Activity Bar." Get fluent at hiding and showing them — screen real estate is precious.

The Shortcuts That Actually Matter

You do not need to memorise all 400. These twelve cover 90% of daily work (Mac shown; on Windows/Linux replace Cmd with Ctrl):

  • Cmd+P — Quick Open. Type any filename to jump to it. The single most-used shortcut.
  • Cmd+Shift+P — Command Palette. Run any command by name.
  • Cmd+B — toggle side bar.
  • `Cmd+`` — toggle integrated terminal.
  • Cmd+/ — toggle line/block comment.
  • Cmd+D — select next occurrence of current word (multi-cursor).
  • Cmd+Shift+L — select all occurrences.
  • Option+Up/Down — move current line up/down.
  • Shift+Option+Up/Down — duplicate current line.
  • Cmd+Shift+K — delete current line.
  • Cmd+G — go to line number.
  • F2 — rename symbol (refactor across the whole project).

Spend a week consciously using these and they will be permanent. Print them on a sticky note if you have to.

Multi-Cursor Editing: The Superpower

VS Code's killer feature. Hold Option (Mac) / Alt (Windows) and click anywhere to add a cursor. Now every keystroke happens at every cursor.

Cmd+D adds the next occurrence of the current selection to your cursors — perfect for renaming all instances of a variable in a function. Cmd+Shift+L selects every occurrence at once. Once you internalise multi-cursor, manual repetitive editing feels prehistoric.

The Integrated Terminal and Source Control

Press Cmd+\`` to open the terminal — it opens in your project folder by default. You can split it (Cmd+`), run multiple shells side by side, and pick your default shell (zsh, bash, PowerShell, fish) in settings.

The Source Control panel (Ctrl+Shift+G) is a full visual Git client — stage hunks, write commit messages, push, pull, view diffs inline. Once you are comfortable with Git on the command line, the panel is great for staging parts of files (click the + next to a hunk).

Settings: settings.json Is Your Friend

VS Code has a beautiful Settings UI (Cmd+,), but the underlying file is settings.json. Open it from the Command Palette → "Preferences: Open User Settings (JSON)". A starter set worth dropping in:

jsonjson
{
  "editor.fontSize": 14,
  "editor.fontFamily": "JetBrains Mono, Menlo, monospace",
  "editor.tabSize": 2,
  "editor.formatOnSave": true,
  "editor.minimap.enabled": false,
  "files.autoSave": "onFocusChange",
  "workbench.editor.enablePreview": false,
  "terminal.integrated.fontSize": 13
}

formatOnSave plus a formatter (Prettier, Black, gofmt) means you stop thinking about whitespace forever. Disabling preview tabs makes new files open in real tabs instead of replacing each other.

Workspaces and Per-Project Settings

Drop a .vscode/settings.json into any project folder and those settings apply only there — perfect for project-specific formatters, linters, or tab widths. Commit it to git so your whole team gets the same editor behaviour. A .vscode/extensions.json does the same for recommended extensions.

For multi-folder projects, save a .code-workspace file (File → Save Workspace As). Opens all the folders together, with shared settings.

Common Mistakes Beginners Make

  • Hoarding extensions. Each one slows VS Code down. Install only what you actively use; uninstall anything you have not touched in a month.
  • Ignoring keyboard shortcuts. If you find yourself reaching for the mouse to open a file, you are wasting time. Use Cmd+P.
  • Not enabling format-on-save. Saves arguments in code review and keeps diffs clean.
  • Editing settings only via the UI. The JSON is faster, copy-paste-able, and shareable across machines.
  • Skipping the integrated terminal. Switching to a separate terminal app every minute is friction. Use `Cmd+``.

Quick Reference

  • Quick Open: Cmd+P. Command Palette: Cmd+Shift+P.
  • Open VS Code from terminal: code . (after installing the shell command).
  • Toggle terminal: Cmd+\``. Toggle side bar: Cmd+B. Toggle panel: Cmd+J`.
  • Multi-cursor: Option+click, Cmd+D (next), Cmd+Shift+L (all).
  • Rename symbol: F2. Go to definition: F12. Find references: Shift+F12.
  • Format file: Shift+Option+F. Format on save: settings.
  • Settings: Cmd+, (UI) or "Preferences: Open User Settings (JSON)".
  • Profiles: switch entire setups (work/personal/web/data) — bottom-left gear → Profiles.
Rune AI

Rune AI

Key Insights

  • Install the code shell command on day one and use code . to open projects.
  • Sign in with GitHub and turn on Settings Sync so your setup follows you.
  • Cmd+P (Quick Open) and Cmd+Shift+P (Command Palette) are the two most-used shortcuts.
  • Multi-cursor (Option+click, Cmd+D) is the editor's superpower — learn it.
  • Commit .vscode/settings.json and .vscode/extensions.json so your team shares conventions.
RunePowered by Rune AI

Frequently Asked Questions

VS Code vs Cursor vs Zed in 2026?

VS Code is still the default and the safest bet. Cursor is a VS Code fork with built-in AI; Zed is a from-scratch editor with great performance. All three are excellent — pick whichever feels best, the muscle memory is mostly transferable.

Is VS Code really free?

Yes, MIT-licensed open source (the upstream is called "Code – OSS"). Microsoft's distributed build adds telemetry and a few proprietary extensions; the open VSCodium build strips those.

Can VS Code replace JetBrains IDEs?

For most languages, yes. For very deep IDE workflows (large Java/Kotlin/.NET enterprise codebases), JetBrains still has the edge. For everything web, Python, Go, Rust, or scripting, VS Code is at least as good.

How do I share my settings with the team?

Commit `.vscode/settings.json` and `.vscode/extensions.json` to your repo. New teammates get prompted to install the recommended extensions on first open. **My VS Code feels slow.** Disable extensions one by one (`Developer: Show Running Extensions`) to find the culprit. Disable the minimap and large-file features. Profile with "Developer: Startup Performance."

Conclusion

VS Code is one of those rare tools where a one-hour investment in setup and shortcuts pays off every working day for years. Install the shell command, turn on settings sync, learn the twelve shortcuts above, and try multi-cursor on your next refactor. You will not look back.