This guide is intended to help you become more productive with IntelliJ IDEA, and provides an overview of the most important features, together with tips, tricks, and the hottest shortcuts.
User interface
The IntelliJ IDEA Editor is special in a number of ways, most notable being is that you can invoke almost any IDE feature without leaving it, which allows you to organize a layout where you have more screen space because auxiliary controls like toolbars and windows are hidden.
Accessing a tool window via its shortcut moves the input focus to it, so you can use all keyboard commands in its context. When you need to go back to the editor, press⎋⎋⎋EscapeEscape, Escape.
Below is a list of shortcuts that invoke the tool windows you will most often need:
| Tool Window | Shortcut |
|---|---|
| Project | ⌘1⌘1⌥ 1⌥ 1 |
| Version Control | ⌘9⌘9⌘9⌥ 9⌥ 9 |
| Run | ⌘4⌘4⌘4⌥ 4⌥ 4 |
| Debug | ⌘5⌘5⌘5⌥ 5⌥ 5 |
| Terminal | ⌥F12⌥F12⌥F12⌥ F12⌥ F12 |
| Editor | ⎋⎋⎋EscapeEscape, Escape |
When you want to focus on the code, try the Distraction Free Mode. It removes all toolbars, tool windows, and editor tabs. To switch to this mode, on the main menu select View | Enter Distraction Free Mode.
An alternative to the Distraction Free Mode may be hiding all tool windows by pressing ⇧⌘F12⇧⌘F12⇧⌘F12^ ⇧ F12^ ⇧ F12. You can restore the layout to its default by pressing this shortcut once again.
The Navigation Bar is a compact alternative to the Project tool window. To access the Navigation Bar, press ⌘↑⌥↖⌥⌘B⌥ Home⌥ Home.
Most components in IntelliJ IDEA (both tool windows and pop-ups) provide speed search. This feature allows you to filter a list, or navigate to a particular item by using a search query.
When you don't know the shortcut for an action, try using the Find action feature by pressing⇧⌘A⇧⌘A⌘3^ ⇧ A^ ⇧ A. Start typing to find an action by its name, see its shortcut or call it.
For more details, refer to Guided Tour around the User Interface, Editor, and Tool Windows.
Editor basics
Since in IntelliJ IDEA you can undo refactorings and revert changes from Local History, it makes no sense to ask you to save your changes every time.
The most useful Editor shortcuts are:
| Action | Description |
|---|---|
| Move the current line of code | ⇧⌘↑⇧⌘↑⌥↑^ ⇧ Up^ ⇧ Up ⇧⌘↓⇧⌘↓⌥↓^ ⇧ Down^ ⇧ Down |
| Duplicate a line of code | ⌘D⌘D^ D⌘ D |
| Remove a line of code | ⌘⌫⌘Y⌘D^ ⇧ L |
| Comment or uncomment a line of code | ⌘/⌘/⌘/^ Slash⌥ Semicolon |
| Comment a block of code | ⌥⌘/⌃⇧/⌃⇧/^ ⇧ Slash^ ⇧ Slash |
| Find in the currently opened file | ⌘F⌘F^ F^ ⌥ S |
| Find and replace in the current file | ⌘R⌘R^ H⇧ ⌥ 5 |
| Next occurrence | ⌘GF3⌘KF3F3 |
| Previous occurrence | ⇧⌘G⇧F3⇧⌘K⇧ F3⇧ F3 |
| Navigate between opened tabs | ⇧⌘]⌃→⌘F6⌥ Right⌥ Right ⇧⌘[⌃←⇧⌘F6⌥ Left⌥ Left |
| Navigate back/forward | ⌘[⌥⌘←⌘[^ ⌥ Left^ ⌥ Left ⌘]⌥⌘→⌘]^ ⌥ Right^ ⌥ Right |
| Expand or collapse a code block in the editor | ⌘ ⌘ ⌘ ^ NumPad Plus^ NumPad Plus ⌘-⌘-⌘-^ NumPad -^ NumPad - |
| Create new... | ⌘N⌘N⌘N⌥ Insert⌥ Insert |
| Surround with | ⌥⌘T⌥⌘T⌥⌘Z^ ⌥ T^ ⌥ T |
| Highlight usages of a symbol | ⌘F7⌘F7⇧⌘U^ ⇧ F7^ F7 |
To expand a selection based on grammar, press⌥↑⌘W⌃⇧↑^ W^ ⌥ W. To shrink it, press ⌥↓⇧⌘W⌃⇧↓^ ⇧ W^ ⇧ W.
IntelliJ IDEA can select more than one piece of code at a time. You can select/deselect any piece of code via ⌃G⌃G⌃G⌥ J⌥ J, or by clicking a code selection and pressing ⌃⇧G⌃⇧G⌃⇧G⇧ ⌥ J⇧ ⌥ J.
For more details, refer to Editor.
Code completion
When you access Basic Completion by pressing⌃Space⌃Space⌃Space^ Space⌥ Slash, you get basic suggestions for variables, types, methods, expressions, and so on. When you call Basic Completion twice, it shows you more results, including private members and non-imported static members.
The Smart Completion feature is aware of the expected type and data flow, and offers the options relevant to the context. To call Smart Completion, press ⌃⇧Space⌃⇧Space⌥⇧Space⇧ ⌥ Space^ ⇧ Space. When you call Smart Completion twice, it shows you more results, including chains.
To overwrite the identifier at the caret, instead of just inserting the suggestion, press ⇥⇥⇥Tab. This is helpful if you're editing part of an identifier, such as a file name.
To let IntelliJ IDEA complete a statement for you, press⇧⌘⏎⇧⌘⏎⇧⌘⏎^ ⇧ Enter^ ⇧ Enter. Statement Completion will automatically add the missing parentheses, brackets, braces and the necessary formatting.
If you want to see the suggested parameters for any method or constructor, press ⌘P⌘P⌃⇧Space^ ⇧ Space⇧ ⌥ P. IntelliJ IDEA shows the parameter info for each overloaded method or constructor, and highlights the best match for the parameters already typed.
The Postfix Completion feature lets you transform an already typed expression to another one, based on the postfix you type after a dot.
For more details, refer to Auto-Completing Code.
Navigation
Recent files
Most of the time you work with a finite set of files, and need to switch between them quickly. A real time-saver here is an action called Recent Files invoked by pressing ⌘E⌘E⌘E^ E. By default, the focus is on the last accessed file. Note that you can also open any tool window through this action:
Navigate to Class is available by pressing ⌘O⌘N⇧⌘T^ Comma⇧ ⌥ G and supports sophisticated expressions, including camel humps, paths, line navigate to, middle name matching, and many more. If you call it twice, it shows you the results out of the project classes.
Navigate to File works similarly by pressing⇧⌘O⇧⌘N⇧⌘R^ ⇧ N^ X, Ctrl F, but is used for files and folders. To navigate to a folder, end your expression with the Slash character.
Navigate to Symbol is available by pressing ⌥⌘O⌥⇧⌘N⌥⌘O^ ⇧ ⌥ N^ ⇧ ⌥ N and allows you to find a method or a field by its name.
Structure
When you are not switching between files, you are most probably navigating within a file. The simplest way to do it is to press⌘F12⌘F12⌘O^ F12^ F12. The pop-up shows you the structure of a file, and allows you to quickly navigate to any of them:
Select in
If you need to open a file in a particular tool window (or Finder/Explorer), you can do so via the Select In action by pressing⌥F1⌥F1⌥F1⌥ F1⌥ F1:
Navigation shortcuts include:
| Action | Shortcut |
|---|---|
| Search everywhere | Double Shift |
| Navigate to class | ⌘O⌘N⇧⌘T^ Comma⇧ ⌥ G |
| Navigate to file | ⇧⌘O⇧⌘N⇧⌘R^ ⇧ N^ X, Ctrl F |
| Navigate to symbol | ⌥⌘O⌥⇧⌘N⌥⌘O^ ⇧ ⌥ N^ ⇧ ⌥ N |
| Recent files | ⌘E⌘E⌘E^ E |
| File structure | ⌘F12⌘F12⌘O^ F12^ F12 |
| Select in | ⌥F1⌥F1⌥⌘W⌥ F1⌥ F1 |
| Navigate to declaration | ⌘B⌘BF3F12^ ⌥ G |
| Navigate to type hierarchy | ⌃H⌃HF4⌥ H^ H |
| Show UML pop-up | ⌥⌘U⌥⌘U⌥⌘U^ ⌥ U^ ⌥ U |
For more details, refer to Navigating Through the Source Code.
Quick pop-ups
Quick Pop-ups are helpful for checking additional information related to the symbol at the caret. Below is a list of pop-ups you should know if you want to be more productive:
| Action | Shortcut |
|---|---|
| Documentation | F1⌃J⌥Button2 Click^ Q^ Q |
| Quick definition | ⌥Space⇧⌘I⌥Space^ ⇧ I^ ⇧ I |
| Show usages | ⌥⌘F7⌥⌘F7⌥⌘F7^ ⌥ F7^ ⌥ F7 |
| Show implementation | ⌥⌘B⌥⌘B^ ⌥ B |
Quick Pop-ups are available for symbols in the editor; however, they are also available for items in any other list via the same shortcuts.
Refactoring basics
IntelliJ IDEA offers a comprehensive set of automated code refactorings that lead to significant productivity gains when used correctly. Firstly, don't bother selecting anything before you apply a refactoring. IntelliJ IDEA is smart enough to figure out what statement you're going to refactor, and only asks for confirmation if several choices are possible.
To undo the last refactoring, switch the focus to the Project tool window and press⌘Z⌘Z⌘Z^ Z^ ⇧ Minus.
| Action | Shortcut |
|---|---|
| Rename | ⇧F6⇧F6⇧F6⇧ F6⇧ F6 |
| Extract variable | ⌥⌘V⌥⌘V⌥⌘L^ ⌥ V^ ⌥ V |
| Extract field | ⌥⌘F⌥⌘F⌥⌘F^ ⌥ F |
| Extract a constant | ⌥⌘C⌥⌘C^ ⌥ C^ ⌥ C |
| Extract a method | ⌥⌘M⌥⌘M⌥⌘M^ ⌥ M^ ⌥ M |
| Extract a parameter | ⌥⌘P⌥⌘P⌥⌘P^ ⌥ P^ ⌥ P |
| Inline | ⌥⌘N⌥⌘N⌥⌘I^ ⌥ N^ ⌥ N |
| Copy | F5F5F5 |
| Move | F6F6⌥⌘VF6F6 |
| Refactor this | ⌃T⌥⇧⌘T⌃T^ ⇧ ⌥ T^ ⇧ ⌥ T |
A real time-saver is the ability to extract part of a string expression with the help of the Extract refactorings. Just select a string fragment and apply a refactoring to replace all of the selected fragment usages with the introduced constant or variable.
For more details, refer to Refactoring Source Code.
Finding usages
Find Usages helps you quickly find all pieces of code referencing the symbol at the caret (cursor), no matter if the symbol is a class, method, field, parameter, or another statement. Just press ⌥F7⌥F7⇧⌘G⇧ ⌥ F7⌥ F7 and get a list of references grouped by usage type, module, and file.
If you want to set custom options for the Find Usages algorithm, press ⌥⇧⌘F7⌥⇧⌘F7⌥⇧⌘F7^ ⇧ ⌥ F7^ ⇧ ⌥ F7, or click the first button on the right panel with search results.
If what you're looking for is plain text, use Find in Path by pressing ⇧⌘F⌃⇧F⌃H^ ⇧ F^ ⇧ F.
For more details, refer to Finding Usages.
Inspections
Inspections are built-in static code analysis tools that help you find probable bugs, locate dead code, detect performance issues, and improve the overall code structure.
Most inspections not only tell you where a problem is, but also provide quick fixes to deal with it right away. Press ⌥⏎⌥⏎⌘1⌥ Enter⌥ Enter to choose a quick fix.
The editor lets you quickly navigate between the highlighted problems via keyboard shortcuts. Press F2F2⌘.F2F2 to go to the next problem, and ⇧F2⇧F2⇧⌘.⇧ F2⇧ F2 to go to the previous one.
Inspections that are too complex to be run on-the-fly are available when you perform code analysis for the entire project. You can do this in one of the following two ways: by selecting from the main menu, or by selecting to run an inspection by its name.
Note that while inspections provide quick-fixes for code that has potential problems, intentions help you apply automatic changes to code that is correct. To get a list of intentions applicable to the code at the caret, press⌥⏎⌥⏎⌘1⌥ Enter⌥ Enter.
For more details, refer to Code Inspection.
Code style and formatting
IntelliJ IDEA automatically applies a code style you've configured in the Code Style settings as you edit, and in most cases you don't need to call the Reformat Code action explicitly.
Useful formatting shortcuts:
| Action | Shortcut |
|---|---|
| Reformat code | ⌥⌘L⌥⌘L⇧⌘F⌥ F8 |
| Auto-indent lines | ⌃⌥I⌥⌘I⌘I^ ⌥ I^ ⌥ I |
| Optimize imports | ⌃⌥O⌥⌘O⇧⌘O^ ⌥ O^ ⌥ O |
Note that by default, IntelliJ IDEA uses regular spaces for indents instead of tabs. If you have files with lots of indents, you may want to optimize their size by enabling the Use tab character option in the Java code style settings.
For more details, refer to Reformatting Source Code.
Version control basics
To check out a project from a Version Control System (VCS), click Checkout from Version Control on the Welcome Screen , or in the main menu.
To quickly perform a VCS operation on the current file, directory, or an entire project, use the VCS operations pop-up by pressing ⌃V⌃V⌃V⌥ Back Quote⌥ Back Quote
Once you've configured the VCS settings, you'll see the Version Control tool window. You can switch to it anytime by pressing⌘9⌘9⌘9⌥ 9⌥ 9.
The Local Changes tab of the Version Control tool window shows your local changes: both staged and unstaged.
Useful VCS shortcuts:
| Action | Shortcut |
|---|---|
| Version Control tool window | ⌘9⌘9⌘9⌥ 9⌥ 9 |
| VCS operations pop-up | ⌃V⌃V⌃V⌥ Back Quote⌥ Back Quote |
| Commit changes | ⌘K⌘K^ K^ K |
| Update project | ⌘T⌘T^ T^ T |
| Push commits | ⇧⌘K⇧⌘K⇧⌘K^ ⇧ K^ ⇧ K |
Annotation (available from both the quick list, the main and the context menus) allows you to see who and when changed a line of code for any file.
For more details, refer to Version Control with IntelliJ IDEA.
Branches
To perform an operation on a branch, either select from the main or context menu, the , or the widget on the right of the status bar.
Note that for multiple repositories, IntelliJ IDEA performs all VCS operations on all branches simultaneously, so you don't need to switch between them manually.
Shelves, stashes and patches help you when you need to store some of the local changes without committing them to the repository. You can then switch to the repository versions of the files, and then come back to your changes later.
For more details, refer to Managing Branches.
Make
By default, IntelliJ IDEA doesn't automatically compile projects on saving. To compile a project, select from the main menu, or press⌘F9⌘F9⌘BF7^ F9.
For more details, refer to Compiling Applications.
Running and debugging
Once you've created a Run/Debug configuration by selecting from the main menu, you are able to run and debug your code.
| Action | Shortcut |
|---|---|
| Run | ⌃R⇧F10⇧⌘F11^ F5⇧ F10 |
| Debug | ⌃D⇧F9⌘F11⌥ F5⇧ F9 |
When in the debug mode, you can evaluate any expression by using the Evaluate expression tool, which is accessed by pressing ⌥F8⌥F8⌘U⌥ F8⌥ F8. This tool provides code completion in the same way as in the editor, so it's easy to enter any expression.
Sometimes, you may want to step into a particular method, but not the first one which will be invoked. In this case, use Smart step into by pressing ⇧F7⇧F7⌥F5⇧ F7⇧ F7 to choose a particular method.
| Action | Shortcut |
|---|---|
| Toggle breakpoint | ⌘F8⌘F8⇧⌘BF9^ F8 |
| Step into | F7F7F5F11F7 |
| Smart step into | ⇧F7⇧F7⌥F5⇧ F7⇧ F7 |
| Step over | F8F8F6F10F8 |
| Step out | ⇧F8⇧F8F7⇧ F11⇧ F8 |
| Resume | ⌥⌘RF9F8F5F9 |
| Evaluate expression | ⌥F8⌥F8⌘U⌥ F8⌥ F8 |
If you want to "rewind" while debugging, you can do it via the Drop Frame action. This is particularly helpful if you mistakenly stepped too far. This will no revert the global state of your application, but will at least let you revert to a previous stack frame.
Any breakpoint can be quickly disabled by clicking on the gutter while holding ⌥. To change breakpoint details (e.g. conditions), press⇧⌘F8⇧⌘F8⇧⌘F8⌥ F9^ ⇧ F8.
For more details, refer to Running and Debugging.
Reloading changes and hot swapping
Sometimes, you need to insert minor changes into your code without shutting down the process. Since the Java VM has a HotSwap feature, IntelliJ IDEA handles these cases automatically when you call Make.
Application servers
To deploy your application to a server:
- Configure your artifacts by selecting (done automatically for Maven and Gradle projects).
- Configure an application server by clicking the page of the Settings/Preferences dialog.
- Configure a run configuration by selecting , then specify the artifacts to deploy and the server to deploy them to.
You can always tell IntelliJ IDEA to build/rebuild your artifacts (once they have been configured) by selecting .
When you need to apply changes in the code to a running application, in addition to Make, you can use the Update action by pressing ⌘F10⌘F10⌘F10^ F10^ F10. This action is only available for the Exploded artifact type. Based on your choice, it can update resources or update classes and resources. When the Update action is applied in the Debug mode, it uses HotSwap; otherwise, it uses Hot redeployment.
For more details, refer to Working with Application Servers.
Working with build tools (Maven/Gradle)
Once you've imported/created your Maven/Gradle project, you are free to edit its
pom.xml
or build.gradle files directly in the editor. Any changes to the
underlying build configuration will eventually need to be synced with the project model in IntelliJ IDEA.
If you want the IDE to synchronize your changes immediately, do the following:
- For
pom.xmlenable the Import Maven projects automatically option in (Windows and Linux) or (macOS). - For
build.gradle, enable the Use auto-import option in of the Settings/Preferences dialog.
For manual synchronization, use the corresponding action on the Maven/Gradle tool window toolbar:
.
Note that any goal or task can be attached to be run before a run configuration.
For more details, refer to Build Tools.
Migrating from eclipse or netbeans
If you are considering the possibility to migrate from Eclipse or NetBeans to IntelliJ IDEA, refer to the migration guide for Eclipse or NetBeans.
Whats next
We strongly advise you to read the documentation. Also you might find it useful to refer to the Java tutorials under Java SE, and also to the tutorial on Java EE.
