Course contentsShow
← Web Development
Lesson 1467 of 2,98226. Code Quality ToolsFree lesson

Workspace Settings vs User Settings

Understanding when to use project-specific workspace settings versus global user settings for linting and formatting.

Workspace Settings vs User Settings

You'll learn when to use global User Settings versus project-specific Workspace Settings for tools like ESLint, Prettier, and Stylelint in VS Code.

The Core Difference

VS Code lets you configure settings at two levels:

User Settings apply globally across all projects on your computer. Think of these as your personal preferences—like your favorite font size or theme—that you want everywhere you work.

Workspace Settings are stored inside a specific project folder (in .vscode/settings.json). These override User Settings and apply only when you're working in that project.

When to Use Each

Use User Settings for:

  • Personal editor preferences (theme, font, tab size)
  • Extensions you want enabled everywhere
  • Default formatting behavior across all projects

Use Workspace Settings for:

  • Project-specific linting rules that might differ from your defaults
  • Team-shared configurations (committed to version control)
  • Format-on-save behavior specific to a project's standards
  • Language-specific settings for that codebase

Practical Example

Your User Settings might have Prettier format on save for all projects. But one client project uses tabs instead of spaces. You'd add Workspace Settings for that project specifying tab indentation, and commit .vscode/settings.json so your whole team uses the same configuration.

The Analogy

User Settings are like your personal driving habits—you drive the same way regardless of which car you're in. Workspace Settings are like a company car policy—when you drive that car, you follow those specific rules.

Key Takeaway: Use User Settings for your personal preferences, Workspace Settings for project-specific rules that should be shared with your team via version control.