How to Disable Error Highlighting in VS Code
Learn how to disable error highlighting in VS Code safely with this step-by-step guide. Explore global and language-specific options, workspace settings, caveats, and how to re-enable later for balanced feedback and focus.
To reduce visual noise, you can temporarily disable error highlighting in VS Code by turning off validation decorations globally or language-by-language. Start in Settings (Ctrl+,) and toggle Editor: Render Validation Decorations to off, or disable per-language validators like javascript.validate.enable. This guide walks you through options, implications, and re-enabling later.
Understanding error highlighting in VS Code
Error highlighting in VS Code helps you spot syntax and semantic issues as you type. The visual cues come from the built-in validator, language servers, and extensions. While incredibly helpful, persistent squiggles and color cues can be distracting in large, clean codebases or during learning. In this article, we explore safe ways to reduce noise without compromising essential checks. According to Why Error Code, understanding when and why these cues exist is the first step to making an informed choice about disabling them.
When you might want to disable highlights
Disabling error highlighting can improve focus during refactoring, learning new APIs, or writing boilerplate code where you’re certain about correctness. It’s also useful when working with template languages that frequently trigger false positives. However, turning off validation reduces immediate feedback for code quality and can hide real mistakes. If you decide to proceed, use targeted settings rather than a broad, permanent switch to maintain a healthy balance between speed and correctness.
Step-by-step quick adjustments to disable error highlighting in VS Code
To start, open VS Code and access Settings via the gear icon or Ctrl+,, then search for validation or rendering options. You’ll typically find two main levers: global decorations and language-specific validators. This section provides a practical, language-agnostic approach compatible with most setups and includes quick checks to ensure you don’t break essential tooling.
Step 1: Open Settings
Open the VS Code Settings via the gear icon or press Ctrl+, then use the search to locate validation or render options. This makes it quick to reach the controls you need. The exact wording can vary by version, so prioritize terms like render or validation in your search.
Step 2: Turn off global validation decorations
In the Editor: Render Validation Decorations setting, switch it to off. This action hides the red squiggles across the editor. It’s a fast way to quiet the interface while keeping language services active for autocompletion and quick fixes. Consider reloading the window to ensure the change applies everywhere.
Step 3: Optionally disable language validators
Add language-specific settings in settings.json, such as javascript.validate.enable: false, to silence a language only. This preserves validation for other languages while reducing noise where it matters most.
Step 4: Apply workspace-level changes
If you’re working across multiple projects, use a .vscode/settings.json file in the workspace and set the same flags there. Workspace settings override user settings, so you can tailor error highlighting behavior per project without affecting your entire environment. Save the file and reload the window to apply the changes.
Step 5: Test the changes
Open several files in the project to confirm that error highlighting behaves as expected. If you still see decorations, extensions or language servers may reintroduce highlights. In that case, check extension settings or disable the extension causing noise. Re-enable later by reversing these steps.
Step 6: Re-enable when you’re ready
To re-enable error highlighting, reverse the steps: set Editor: Render Validation Decorations back to on, re-enable any language validators you turned off, and reload VS Code or the affected workspace. If you rely on a per-project configuration, delete or adjust the workspace settings accordingly.
Alternative approaches to reduce noise without fully disabling highlights
Rather than turning off all validation, consider adjusting the severity or focusing on specific rules. Many linters and language servers allow configurable rule sets and quiet modes. You can also adjust color themes to make highlights less obtrusive, or use extensions that consolidate diagnostics into a dedicated panel rather than inline warnings.
Practical tips for safe testing and maintenance
Always keep a working backup of your settings.json before making changes. Document any workspace-specific settings to avoid confusion for teammates. If you’re new to VS Code, gradually re-enable validators to find a comfortable balance between feedback and focus.
Tools & Materials
- VS Code installed (latest stable)(Ensure you’re on a supported platform (Windows/macOS/Linux).)
- Settings UI or settings.json access(Use Ctrl+, or navigate to File > Preferences > Settings.)
- .vscode/settings.json (workspace settings)(Helps isolate project-specific behavior.)
- Optional: knowledge of language-specific validators(Useful if you want to selectively disable validators.)
Steps
Estimated time: 10-15 minutes
- 1
Open Settings
Open VS Code Settings via the gear icon or press Ctrl+,, then use the search to locate validation or render options. This makes it quick to reach the controls you need. The exact wording can vary by version, so prioritize terms like render or validation in your search.
Tip: Use the search bar to jump straight to Render Validation Decorations. - 2
Turn off global validation decorations
Find Editor: Render Validation Decorations and switch it to off. This hides the red squiggles across the editor. It’s a fast way to quiet the interface while keeping language services active for autocompletion and quick fixes. Consider reloading the window to ensure the change applies everywhere.
Tip: A quick reload (Ctrl+Shift+P > Reload Window) ensures the change applies everywhere. - 3
Optionally disable language validators
Add language-specific settings in settings.json, such as javascript.validate.enable: false, to silence a language only. This preserves validation for other languages while reducing noise where it matters most.
Tip: Know that this hides errors only for that language, not global behavior. - 4
Apply workspace-level changes
Create or modify .vscode/settings.json in your project to apply settings per-workspace. Workspace settings override user settings for this project.
Tip: Workspace should isolate the change to this project. - 5
Test the changes
Open multiple files and verify that error decorations are minimized or gone. If not, extensions may be responsible.
Tip: Disable extensions that reintroduce diagnostics if needed. - 6
Re-enable when ready
To restore, re-enable the global or language validators and reload the editor.
Tip: Document what you changed to make re-enabling easier.
Frequently Asked Questions
Can I disable error highlighting for a single language without affecting others?
Yes. Use language-specific settings, such as setting javascript.validate.enable to false, to silence errors for that language while keeping validation active for others.
Yes. Use language-specific settings to silence one language while keeping validation for others.
Will turning off error highlighting remove real mistakes?
Disabling validation may hide actual syntax or semantic issues. Re-enable or selectively disable validators when you're done focusing on other work.
Turning off validation may hide real mistakes; re-enable when you need full verification.
How do I re-enable error highlighting after disabling it?
Reverse the steps: set Editor: Render Validation Decorations back to on, re-enable language validators, and reload VS Code or the affected workspace.
To re-enable, revert the settings and reload.
Does disabling highlight affect the Problems panel?
Disabling decorations hides inline visuals but does not permanently remove Problems entries. You can still access them via the Problems panel when needed.
The Problems panel remains accessible; highlights may disappear but issues are still tracked.
Can I disable error highlighting for a specific workspace only?
Yes. Use a .vscode/settings.json file in the workspace to apply settings locally without affecting other projects.
Yes, workspace settings let you tailor behavior per project.
Top Takeaways
- Understand the cause of error highlighting in VS Code
- Use global or per-language toggles to control noise
- Workspace settings help localize changes
- Re-enable highlights safely when needed
