# Enable/disable and suppress inspections

Some inspections may report problems that you currently do not want to see. In this case, you can disable or suppress them.

## Disable inspections

When you disable an inspection, you turn it off. It means that the code analysis engine stops searching project files for the problem that this inspection is designed to detect. Note that when you disable an inspection, you disable it in the current [inspection profile](customizing-profiles.html); it remains enabled in other profiles.

Most inspections in CLion can be disabled. However, some inspections will keep highlighting your code regardless of the settings. For example, syntax errors are always highlighted.

Procedure: Disable an inspection in settings

1. Press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `⌘ Comma` (Xcode), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (ReSharper), `⌘ Comma` (ReSharper (macOS)), `Ctrl+Alt+S` (QtCreator), `⌘ Comma` (QtCreator (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open settings and then select `Editor | Inspections`.

2. Locate the inspection you want to disable and clear the checkbox next to it.

![Enable inspection](https://resources.jetbrains.com/help/img/idea/2026.2/cl_enable_inspection.png)

3. Apply the changes and close the dialog.

Procedure: Disable an inspection from the editor

1. Place the caret at the highlighted line and press `Alt+Enter` (Windows), `⌥ ⏎` (macOS), `⌥ ⏎` (IntelliJ IDEA Classic (macOS)), `⌥ ⏎` (macOS System Shortcuts), `Alt+Enter` (XWin), `Alt+Enter` (GNOME), `Alt+Enter` (KDE), `Alt+Enter` (Emacs), `Alt+Enter` (Sublime Text), `⌥ ⏎` (Sublime Text (macOS)), `⌥ ⏎` (Xcode), `Alt+Enter` (Visual Studio), `⌥ ⏎` (Visual Studio (macOS)), `Alt+Enter` (ReSharper), `⌥ ⏎` (ReSharper (macOS)), `Alt+Enter` (QtCreator), `⌥ ⏎` (QtCreator (macOS)), `Alt+Enter` (NetBeans), `Ctrl+1` (Eclipse), `⌘ 1` (Eclipse (macOS)) (or click ![the Show Context Actions icon](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.codeInsight.intentionBulb.svg)) to invoke a list of available context actions.

2. Click ![the More Actions button](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.moreVertical.svg) next to the inspection you want to disable and select Disable inspection.

![Disable an inspection in the editor](https://resources.jetbrains.com/help/img/idea/2026.2/cl_inspections_disable_editor.png)

Procedure: Disable an inspection from the Problems tool window

1. In the Inspection Results tab of the Problems tool window (appears once you run code analysis), right-click the inspection you want to disable and select Disable inspection.

2. Click ![the View Options button](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.show.svg) on the toolbar and select Filter resolved items to hide the disabled inspection alerts.

## Suppress inspections

When you suppress an inspection, the code analysis engine does not highlight the problem found by this inspection in a specific piece of code(file, statement, function, or line).

Most inspections in CLion can be suppressed. However, some inspections do not have this option. For example, syntax errors are always highlighted in the editor regardless of the settings. To learn whether a specific inspection can be suppressed, see [Inspectopedia](https://www.jetbrains.com/help/inspectopedia/JavaScript-and-TypeScript.html).

Procedure: Suppress an inspection from the editor

1. Place the caret at the highlighted line and press `Alt+Enter` (Windows), `⌥ ⏎` (macOS), `⌥ ⏎` (IntelliJ IDEA Classic (macOS)), `⌥ ⏎` (macOS System Shortcuts), `Alt+Enter` (XWin), `Alt+Enter` (GNOME), `Alt+Enter` (KDE), `Alt+Enter` (Emacs), `Alt+Enter` (Sublime Text), `⌥ ⏎` (Sublime Text (macOS)), `⌥ ⏎` (Xcode), `Alt+Enter` (Visual Studio), `⌥ ⏎` (Visual Studio (macOS)), `Alt+Enter` (ReSharper), `⌥ ⏎` (ReSharper (macOS)), `Alt+Enter` (QtCreator), `⌥ ⏎` (QtCreator (macOS)), `Alt+Enter` (NetBeans), `Ctrl+1` (Eclipse), `⌘ 1` (Eclipse (macOS)) (or click ![the Intention action icon](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.codeInsight.intentionBulb.svg) to use the intention action).

2. Click the ![](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.moreVertical.svg) button next to the inspection you want to suppress and select an action according to the required scope.

![Suppress inspection in the editor](https://resources.jetbrains.com/help/img/idea/2026.2/cl_inspections_suppress_editor.png)

For C/C++ code, CLion uses the `#pragma clang diagnostic` to suppress inspections. For example, when you suppress one of the [Clang-Tidy](clang-tidy-checks-support.html) inspections, `modernize-avoid-bind`, for a selected function, the following code appears above and below the declaration:

![Suppressing an inspection for a function](https://resources.jetbrains.com/help/img/idea/2026.2/cl_inspections_suppress_pragmas.png)

Clang-Tidy inspections have the additional Suppress for line option, which adds the [// NOLINT](https://clang.llvm.org/extra/clang-tidy/#suppressing-undesired-diagnostics) comment, forcing Clang-Tidy to ignore the current line:

![Suppressing an inspection for a lilne](https://resources.jetbrains.com/help/img/idea/2026.2/cl_inspection_suppress_nolint.png)

To re-enable a suppressed inspection, delete the `#pragma` lines or `// NOLINT` comments.

## Disable highlighting, but keep the fix

Inspections have [severities](configuring-inspection-severities.html) according to which they highlight code problems in the editor. You can quickly disable code highlighting for an inspection without opening the settings. In this case, the inspection remains enabled and provides a fix, but the severity changes to No highlighting (fix available).

Procedure:

1. Place the caret at a code element highlighted by an inspection in the editor and press `Alt+Enter` (Windows), `⌥ ⏎` (macOS), `⌥ ⏎` (IntelliJ IDEA Classic (macOS)), `⌥ ⏎` (macOS System Shortcuts), `Alt+Enter` (XWin), `Alt+Enter` (GNOME), `Alt+Enter` (KDE), `Alt+Enter` (Emacs), `Alt+Enter` (Sublime Text), `⌥ ⏎` (Sublime Text (macOS)), `⌥ ⏎` (Xcode), `Alt+Enter` (Visual Studio), `⌥ ⏎` (Visual Studio (macOS)), `Alt+Enter` (ReSharper), `⌥ ⏎` (ReSharper (macOS)), `Alt+Enter` (QtCreator), `⌥ ⏎` (QtCreator (macOS)), `Alt+Enter` (NetBeans), `Ctrl+1` (Eclipse), `⌘ 1` (Eclipse (macOS)).

A list with available fixes and context actions opens. Locate the inspection fix that is marked with ![Intention action icon](https://resources.jetbrains.com/help/img/idea/2026.2/app.expui.codeInsight.intentionBulb.png).

2. Click the ![](https://resources.jetbrains.com/help/img/idea/2026.2/app-client.expui.general.moreVertical.svg) button next to the fix to open the inspection's options and select Disable highlighting, keep fix.

The name of the inspection for which you are changing the severity is written above the inspection's options.

If you want to restore the highlighting, press `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `⌘ Comma` (Xcode), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (ReSharper), `⌘ Comma` (ReSharper (macOS)), `Ctrl+Alt+S` (QtCreator), `⌘ Comma` (QtCreator (macOS)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open the IDE settings and select `Editor | Inspections`. Find the necessary inspection in the list and change its severity as you like. For more information, refer to [Change inspection severity in all scopes](configuring-inspection-severities.html#change-severity).

## Change the highlighting level for a file

Procedure:

* By default, CLion highlights all detected code problems. Hover over the widget in the top-right corner of the editor and select another level from the Highlight list:

* None: turn highlighting off.

* Syntax: highlight syntax problems only.

* All Problems: (default) highlight syntax problems and problems found by inspections.

* You can also change the highlighting level  from the main menu. Select  or press `Ctrl+Alt+Shift+H` (Windows), `⌘ ⌥ ⇧ H` (macOS), `⌘ ⌥ ⇧ H` (IntelliJ IDEA Classic (macOS)), `⌘ ⌥ ⇧ H` (macOS System Shortcuts), `Ctrl+Alt+Shift+H` (XWin), `Ctrl+Alt+Shift+H` (GNOME), `Ctrl+Alt+Shift+H` (KDE), `Ctrl+Alt+Shift+H` (Emacs), `Ctrl+Alt+Shift+H` (Sublime Text), `⌘ ⌥ ⇧ H` (Sublime Text (macOS)), `⌘ ⌥ ⇧ H` (Xcode), `Ctrl+Alt+Shift+H` (Visual Studio), `⌘ ⌥ ⇧ H` (Visual Studio (macOS)), `Ctrl+Alt+Shift+H` (ReSharper), `⌘ ⌥ ⇧ H` (ReSharper (macOS)), `Ctrl+Alt+Shift+H` (QtCreator), `⌘ ⌥ ⇧ H` (QtCreator (macOS)), `Ctrl+Alt+Shift+H` (NetBeans), `Ctrl+Alt+Shift+H` (Eclipse), `⌘ ⌥ ⇧ H` (Eclipse (macOS))  .

## See also

### Concepts

[Static code analysis](code-inspection.html)

### Procedures

[Run inspections](running-inspections.html) [Intention actions](intention-actions.html)