Settings persistently store states that control the behavior and appearance of IntelliJ Platform-based IDEs. On this page, the term "Settings" means the same as "Preferences" on some platforms.
Plugins can create and store Settings to capture their configuration in a way that uses the IntelliJ Platform Persistence Model. The User Interface (UI) for these custom Settings can be added to the IDE Settings dialog.
Settings can affect different levels of scope. This document describes adding custom Settings at the Project and Application (or Global, IDE) levels.
See Settings Tutorial for step-by-step instructions for creating a simple set of custom Settings.
See Inspecting Settings on how to gather information in the IDE instance for Settings dialog.
Extension Points for SettingsCustom Settings implementations are declared in the plugin.xml file using one of two extension points (EP), depending on the level of the Settings. Many attributes are shared between the EP declarations.
Application and Project Settings typically provide an implementation based on the Configurable interface because they do not have runtime dependencies. See Implementations for Settings Extension Points for more information.
For performance reasons, it is recommended to declare as much information as possible about a 'Settings' implementation using attributes in the EP element in the plugin.xml descriptor. If it is not declared, the component must be loaded to retrieve it from the implementation, degrading UI responsiveness.
Declaring Application SettingsThe application-level settings are declared using com.intellij.applicationConfigurable extension point.
An example <applicationConfigurable> EP declaration is shown below. The declaration indicates the settings are a child of the tools settings group, the implementation FQN is com.example.ApplicationSettingsConfigurable, the unique ID is the same as the implementation fully qualified name (FQN), and the (non-localized) title displayed to users is "My Application Settings". See Settings Declaration Attributes for more information.
<extensions defaultExtensionNs="com.intellij"> <applicationConfigurable parentId="tools" instance="com.example.ApplicationSettingsConfigurable" id="com.example.ApplicationSettingsConfigurable" displayName="My Application Settings"/> </extensions>
To localize the display name, instead of the displayName attribute, use key and bundle attributes pointing to a key in a message bundle. The same applies for projectConfigurable extensions.
The project-level settings are declared using com.intellij.projectConfigurable extension point.
An example <projectConfigurable> EP declaration is shown below. Similar to the application setting example above, but it includes the additional attribute nonDefaultProject indicating these settings do not apply to the default project. See Settings Declaration Attributes for details.
<extensions defaultExtensionNs="com.intellij"> <projectConfigurable parentId="tools" instance="com.example.ProjectSettingsConfigurable" id="com.example.ProjectSettingsConfigurable" displayName="My Project Settings" nonDefaultProject="true"/> </extensions>
Settings Declaration AttributesReaders are encouraged to review the Javadoc comments for Configurable because the attribute information applies to ConfigurableProvider as well as Configurable, as noted. This section provides some additional clarification of those comments.
The attributes supported by com.intellij.applicationConfigurable extension point and com.intellij.projectConfigurable extension point are in the table below:
Attribute
Required
Attribute
Value
Implementation
Basis
instance
yes (1)
FQN of implementation. See The Configurable Interface for more information.
Configurable
provider
yes (1)
FQN of implementation. See The ConfigurableProvider Class for more information.
ConfigurableProvider
nonDefaultProject
yes
Applicable only to the com.intellij.projectConfigurable (project Settings) EP.
true = show Settings for all projects except the default project.
false = show Settings for all projects.
Configurable
displayName
yes (2)
The non-localized Settings name visible to users, which is needed for the Settings dialog left-side menu.
For a localized visible name omit displayName and use the key and bundle attributes.
Configurable
ConfigurableProvider
key and bundle
yes (2)
The localization key and bundle for the Settings name visible to users.
For non-localized visible names omit key and bundle and use displayName.
Configurable
ConfigurableProvider
id
yes
The unique, FQN identifier for this implementation.
The FQN should be based on the plugin id to ensure uniqueness.
Configurable
ConfigurableProvider
parentId
yes
This attribute is used to create a hierarchy of Settings. This component is declared one of the specified parentId component's children. Typically used for placing a Settings panel within the Settings Dialog menu. Acceptable values for parentId are given in Values for Parent ID Attribute.
groupId is deprecated. (3)
Configurable
ConfigurableProvider
groupWeight
no
Specifies the weight (stacking order) of this component within the group of a parent configurable component. The default weight is 0, meaning lowest in the order.
If one child in a group or a parent component has non-zero weight, all children will be sorted descending by their weight. If the weights are equal, the components will be sorted ascending by their display name.
Configurable
ConfigurableProvider
dynamic
no
This component's children are dynamically calculated by calling the getConfigurables() method.
Not recommended because it requires loading additional classes while building a Settings tree. If possible, use XML attributes instead.
Configurable.Composite
childrenEPName
no
Specifies the FQN name of the Extension Point that will be used to calculate the children of this component.
Configurable
(1) Either instance or provider must be specified depending on the implementation.
(2) Either displayName or key and bundle must be specified depending on whether the displayed Settings name is localized.
(3) If both groupId and parentId are specified, a warning is logged. Also, see default entry in Values for Parent ID Attribute.
The table below shows all Settings groups and their corresponding value for the parentId attribute. See the previous section for all supported attributes.
Group
parentId Value
Details
Appearance & Behavior
appearance
This child group contains Settings to personalize IDE appearance, such as: changing themes and font size. Also, it covers Settings to customize behavior such as keymaps, configuring plugins, and system Settings such as password policies, HTTP proxy, updates, and more.
Build, Execution, Deployment
build
Child group containing Settings to configure project integration with different build tools, modify the default compiler Settings, manage server access configurations, customize the debugger behavior, etc.
Build Integration
build.tools
A subgroup of build. This subgroup configures project integration with build tools such as Maven, Gradle, or Gant.
Editor
editor
Child group containing Settings to personalize source code appearance, such as fonts, highlighting styles, indents, etc. It also contains Settings to customize the editor's appearance, such as line numbers, caret placement, tabs, source code inspections, setting up templates, and file encodings.
Languages and Frameworks
language
Child group containing Settings related to specific language frameworks and technologies used in the project.
3rd Party Settings
tools
Child group containing Settings to configure integration with third-party applications, specify the SSH Terminal connection Settings, manage server certificates and tasks, configure diagrams layout, etc.
Super Parent
root
The invisible parent of all existing groups. Not used except for IDEs built on top of the IntelliJ Platform, or extensive suites of Settings. You should not place settings in this group.
other
Do not use
default
If neither parentId nor groupId attribute is set, the component is added to the other Settings group. This is undesirable; see other group description.
Catch-all
Deprecated
other
The IntelliJ Platform no longer uses this group. Do not use this group. Use the tools group instead.
Project-related Settings
Deprecated
project
The IntelliJ Platform no longer uses this group. It was intended to store some project-related settings. Do not use this group.
Implementations for Settings Extension PointsImplementations for com.intellij.applicationConfigurable extension point and com.intellij.projectConfigurable extension point can have one of two bases:
The Configurable interface, which provides a named configurable component with a Swing form. Most Settings providers are based on the Configurable interface or one of its sub- or supertypes.
The ConfigurableProvider class, which can hide a configurable component from the Settings dialog based on runtime conditions.
Configurable Interface
Many Settings in the intellij-community code base implement Configurable or one of its subtypes, such as SearchableConfigurable. Readers are encouraged to review the Javadoc comments for Configurable.
Implementations must meet several requirements for constructors.
Application Settings implementations, declared using the applicationConfigurable EP, must have a default constructor with no arguments.
Project Settings implementations, declared using the projectConfigurable EP, must declare a constructor with a single argument of type Project.
Constructor injection (other than for Project) is not allowed.
For a Configurable implementation correctly declared using an EP, the implementation's constructor is not invoked by the IntelliJ Platform until a user chooses the corresponding Settings displayName in the Settings Dialog menu.
The IntelliJ Platform may instantiate a Configurable implementation on a background thread, so creating Swing components in a constructor can degrade UI responsiveness.
Configurable
The instantiation of a generic Configurable implementation is documented in the interface file. A few high-level points are reviewed here:
The Configurable.reset() method is invoked immediately after Configurable.createComponent(). Initialization of Setting values in the constructor or createComponent() is unnecessary.
See the Constructors section for information about when a Settings object is instantiated.
Once instantiated, a Configurable instance's lifetime continues regardless of whether the implementation's Settings are changed, or the user chooses a different entry on the Settings Dialog menu.
A Configurable instance's lifetime ends when OK or Cancel is selected in the Settings Dialog. An instance's Configurable.disposeUIResources() is called when the Settings Dialog is closing.
To open the Settings dialog or show a specific Configurable, see ShowSettingsUtil.
Configurable Marker Interfaces
Implementations based on Configurable can implement marker interfaces, which provide additional flexibility in the implementation.
Configurable.NoScroll
Do not add scroll bars to the form. By default, a plugin's Settings component is put into a scrollable pane. However, a Settings panel can have a JTree, which requires its own JScrollPane. So the NoScroll interface should be used to remove the outer JScrollPane.
Configurable.NoMargin
Do not add an empty border to the form. By default, an empty border is added for a plugin's Settings component.
Configurable.Beta
(2022.3) Adds Beta label next to settings page title in Settings tree.
Configurable
There are classes in the IntelliJ Platform specialized in particular types of Settings. These subtypes are based on com.intellij.openapi.options.ConfigurableEP. For example, allows adding Settings via EditorSmartKeysConfigurableEP registered in com.intellij.editorSmartKeysConfigurable extension point.
Existing implementations of Configurable in the IntelliJ Platform that can serve as a reference are:
ConsoleConfigurable (application configurable)
AutoImportOptionsConfigurable (project configurable)
ConfigurableProvider Class
The ConfigurableProvider class only provides a Configurable implementation if its runtime conditions are met. The IntelliJ Platform first calls the ConfigurableProvider.canCreateConfigurable(), which evaluates runtime conditions to determine if Settings changes make sense in the current context. If the Settings make sense to display, canCreateConfigurable() returns true. In that case the IntelliJ Platform calls ConfigurableProvider.createConfigurable(), which returns the Configurable instance for its Settings implementation.
By choosing not to provide a Configuration implementation in some circumstances, the ConfigurableProvider opts out of the Settings display and modification process. The use of ConfigurableProvider as a basis for a Settings implementation is declared using attributes in the EP declaration.
Examples:
29 April 2025
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4