# File and project-wide analysis

IntelliJ IDEA analyzes your code in the file that is currently opened in the editor and highlights detected problems as you type.  It also automatically [checks your entire project
for errors](#project-wide-analysis).

Additionally, you can run an inspection or a group of inspections in the selected scope of files [manually](running-inspections.html#run-inspections-manually). In this case, you will get a comprehensive report of all detected problems.

## Current file

The IDE continuously checks your code and searches for problems. When IntelliJ IDEA analyzes your code, it uses the inspections defined in the currently selected [inspection profile](customizing-profiles.html). The widget in the top-right corner of the editor displays the number of problems of each [severity](configuring-inspection-severities.html) detected in the current file:

![Inspection widget](https://resources.jetbrains.com.cn/help/img/idea/2026.2/ws_inspection-widget.png)

> **Tip:**
> The widget has a simplified view. To enable it, hover over the widget, click ![the More button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.actions.more.svg), and select Compact View.

Click the widget to open the list of problems in the File tab of the [Problems tool window](problems-tool-window.html). You can also access the Problems tool window by selecting `View | Tool Windows | Problems` or by pressing `Alt+6` (Windows), `⌘ 6` (macOS), `⌘ 6` (IntelliJ IDEA Classic (macOS)), `⌘ 6` (macOS System Shortcuts), `Alt+6` (XWin), `Alt+6` (GNOME), `Alt+6` (KDE), `Alt+6` (Emacs), `Alt+6` (Sublime Text), `⌘ 6` (Sublime Text (macOS)), `Alt+6` (NetBeans), `Alt+6` (Visual Studio), `⌘ 6` (Visual Studio (macOS)), `Alt+6` (Eclipse), `⌘ 6` (Eclipse (macOS)).

For each problem, you can see the suggested quick-fix by pressing `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)), `Alt+Enter` (NetBeans), `Alt+Enter` (Visual Studio), `⌥ ⏎` (Visual Studio (macOS)), `Ctrl+1` (Eclipse), `⌘ 1` (Eclipse (macOS)) or by clicking ![Show Quick Fixes](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app-client.expui.codeInsight.intentionBulb.svg).   To jump to the corresponding line in the editor, press `F4` (Windows), `⌘ ↓` (macOS), `F4` (IntelliJ IDEA Classic (macOS)), `F4` (macOS System Shortcuts), `F4` (XWin), `F4` (GNOME), `F4` (KDE), `F4` (Emacs), `F4` (Sublime Text), `F4` (Sublime Text (macOS)), `F4` (NetBeans), `F4` (Visual Studio), `⌘ ↓` (Visual Studio (macOS)), `F12` (Eclipse), `F3` (Eclipse (macOS)) or double-click the problem in the tool window.

Click ![Open Editor Preview](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.previewVertically.svg) to be able to view and fix problems right in the tool window.

![File tab in Problems tool window](https://resources.jetbrains.com.cn/help/img/idea/2026.2/problems-toolwindow-reference.png)

The color stripe in the scrollbar also marks the detected code problems and helps you quickly access the corresponding lines without scrolling the file. Hover over a mark on the stripe to see the detected problem in a tooltip. Click a mark to jump to the corresponding line.

[Video](https://resources.jetbrains.com.cn/help/img/idea/2026.2/using-inspections.mp4)

### Navigate to detected problems

You can jump from one highlighted problem to another within a file by clicking ![the Next Highlighted Error button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.actions.findAndShowNextMatches.svg) ![the Next Highlighted Error button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.actions.findAndShowPrevMatches.svg) in the widget or by pressing `F2` (Windows), `F2` (macOS), `F2` (IntelliJ IDEA Classic (macOS)), `⌃ Comma` (macOS System Shortcuts), `F2` (XWin), `F2` (GNOME), `F2` (KDE), `F2` (Emacs), `F2` (Sublime Text), `F2` (Sublime Text (macOS)), `F2` (NetBeans), `Alt+Page Down` (Visual Studio), `⌥ Page ↓` (Visual Studio (macOS)), `F2` (Eclipse), `⌘ .` (Eclipse (macOS)) or `Shift+F2` (Windows), `⇧ F2` (macOS), `⇧ F2` (IntelliJ IDEA Classic (macOS)), `⌃ ⇧ Comma` (macOS System Shortcuts), `Shift+F2` (XWin), `Shift+F2` (GNOME), `Shift+F2` (KDE), `Shift+F2` (Emacs), `Shift+F2` (Sublime Text), `Shift+F2` (Sublime Text (macOS)), `Shift+F2` (NetBeans), `Alt+Page Up` (Visual Studio), `⌥ Page ↑` (Visual Studio (macOS)), `Shift+F1` (Eclipse), `⌘ ⇧ .` (Eclipse (macOS)) accordingly. By default, the IDE will navigate you to problems according to their [severity](configuring-inspection-severities.html): errors > warnings > weak warnings > server problems > typos.

You can configure IntelliJ IDEA to take you through the problems one by one regardless of their severity. Hover over the widget in top-right corner of the editor, click ![the More button](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.actions.more.svg), select 'Next Error' Action (F2) Goes Through, and enable All Problems.

![Configuring navigation between highlighted lines](https://resources.jetbrains.com.cn/help/img/idea/2026.2/navigate-inspection-lines.png)

## Project errors (Java only)

Apart from viewing all problems in a single file, you can take a look at all problems detected across your entire project by using the project-wide analysis.

> **Note:**
> Project-wide analysis is a different functionality than [project analysis](project-analysis.html).

Currently, the project-wide analysis works only in Java projects. It might work incorrectly in projects that combine Java with other languages, such as Kotlin or Scala.

Procedure: Install the Project Wide Analysis plugin

This functionality relies on the [Project Wide Analysis](https://plugins.jetbrains.com/plugin/26698-project-wide-analysis)  plugin, which   you need to install and enable.

> **Note:**
> The Project Wide Analysis plugin is not available in IntelliJ IDEA without the Ultimate subscription.

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)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open settings and then select `Plugins`.

2. Open the Marketplace tab, find the Project Wide Analysis plugin, and click Install (restart the IDE if prompted).

Procedure: Enable project-wide analysis

By default, the analysis is disabled. To enable it:

1. Open the Problems tool window by selecting `View | Tool Windows | Problems` from the main menu or by pressing `Alt+6` (Windows), `⌘ 6` (macOS), `⌘ 6` (IntelliJ IDEA Classic (macOS)), `⌘ 6` (macOS System Shortcuts), `Alt+6` (XWin), `Alt+6` (GNOME), `Alt+6` (KDE), `Alt+6` (Emacs), `Alt+6` (Sublime Text), `⌘ 6` (Sublime Text (macOS)), `Alt+6` (NetBeans), `Alt+6` (Visual Studio), `⌘ 6` (Visual Studio (macOS)), `Alt+6` (Eclipse), `⌘ 6` (Eclipse (macOS)).

2. Switch to the Project Errors tab and click the ![Enable Project-Wide Analysis](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.projectWideAnalysisOff.svg) icon on the left toolbar.

![Enabling the project-wide analysis](https://resources.jetbrains.com.cn/help/img/idea/2026.2/project-wide-analysis-enable.png)

The first time you run the analysis, it will take longer than normal. Once the analysis is finished, you will see a list of all problems detected in the project.

> **Tip:**
> IntelliJ IDEA automatically sets the number of threads that are used for the analysis. If you want to set the number yourself, 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)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)), select Advanced Settings, and specify the required value in the Thread count used by Project-Wide analysis field. After that, restart the IDE.

For each problem, you can see the suggested quick-fix by pressing `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)), `Alt+Enter` (NetBeans), `Alt+Enter` (Visual Studio), `⌥ ⏎` (Visual Studio (macOS)), `Ctrl+1` (Eclipse), `⌘ 1` (Eclipse (macOS)) or by clicking ![Show Quick Fixes](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app-client.expui.codeInsight.intentionBulb.svg).   To jump to the corresponding line in the editor, press `F4` (Windows), `⌘ ↓` (macOS), `F4` (IntelliJ IDEA Classic (macOS)), `F4` (macOS System Shortcuts), `F4` (XWin), `F4` (GNOME), `F4` (KDE), `F4` (Emacs), `F4` (Sublime Text), `F4` (Sublime Text (macOS)), `F4` (NetBeans), `F4` (Visual Studio), `⌘ ↓` (Visual Studio (macOS)), `F12` (Eclipse), `F3` (Eclipse (macOS)) or double-click the problem in the tool window.

Click ![Open Editor Preview](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.expui.general.previewVertically.svg) to be able to view and fix problems right in the tool window.

To disable the project-wide analysis, click ![Disable Project-Wide Analysis](https://resources.jetbrains.com.cn/help/img/idea/2026.2/app.actions.projectWideAnalysisOn.svg) on the left toolbar of the Problems tool window.

When the project-wide analysis is disabled, the Project Errors tab of the Problems tool window displays the results of the latest build.

Procedure: Configure the project-wide analysis

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)), `Ctrl+Alt+S` (NetBeans), `Ctrl+Alt+S` (Visual Studio), `⌘ Comma` (Visual Studio (macOS)), `Ctrl+Alt+S` (Eclipse), `⌘ Comma` (Eclipse (macOS)) to open settings and then select `Advanced Settings`.

2. Configure the following options:

* Thread count used by Project-Wide analysis: IntelliJ IDEA automatically sets the number of threads that are used for the analysis. If you want to set the number yourself, specify the required value. After that, restart the IDE.

* Analysis delay after change: use this option to set a delay before the code analysis. The default delay is `1000` milliseconds.