Skip to main content
The integrated code editor window displays translated code with full syntax highlighting. Themes are configured per output language, so you can use different color schemes depending on whether you are viewing C++, Python, or any other supported language.

Selecting a theme

1

Open Project Settings

In the Unreal Engine menu bar, go to Edit → Project Settings.
2

Navigate to Node to Code theming

Select Plugins → Node to Code from the left panel, then scroll to the Theming → Language Specific Themes section.
3

Expand the language theme map

Open the theme map for your target language — for example, C++ Themes — to see the list of available themes.
4

Set the active theme

In the Node to Code code editor window, use the theme selector dropdown in the toolbar to choose from the themes defined in the map for the current language.

Built-in themes

All 21 built-in themes are available for every supported language (C++, Python, JavaScript, C#, Swift, Pseudocode) and are pre-populated in each language theme map.
The Unreal Engine theme is designed to match the UE5 editor color scheme and is a good starting point for developers who spend most of their time inside the Unreal Editor.
ThemeStyle
SpacedustDark teal/blue with vibrant orange and teal accents
UbuntuDeep purple background with Ubuntu-inspired green and red
RenaissanceDark charcoal with warm orange, deep reds, and olive green
Unreal EngineUE5 editor dark theme with blue keywords and gold strings
Midnight CodeVS Code-inspired dark with soft blue keywords and sage green numbers
Midnight NeonVery dark charcoal with neon cyan text and vivid accents
Mono AmberMonochromatic amber palette on a dark brown background
Beige EarthLight beige background with earthy muted tones
Beige Earth DarkDark earthy variant with deep brown background
Citrus DelightDark charcoal with bright orange, gold, and lime accents
Cuppa JoeDeep espresso background with warm coffee-toned syntax colors
Cyber NightNear-black background with neon teal, purple, and pink
Forbidden ForestDark forest shadow with mystical purple and amber
Night SkyDeep blue-black with soft starlight text and cosmic purple
Midnight ByteNear-black with electric blue, cyan-mint, and purple
Pixel PhosphorDark charcoal with retro phosphor greens and amber
Night ShiftWarm dark charcoal with coral reds and copper tones — no cool colors
StealthHigh-contrast dark monochrome in shades of gray
Mono WhiteLight monochrome on a soft white background
Studio BlueLight background with classic Visual Studio blue, red, and green
CrispSoft white background with muted purple, rust, and steel blue

Custom themes

Each language theme setting (CPPThemes, PythonThemes, etc.) is a TMap of theme name to color definition. You can add your own entries directly in Project Settings without writing any C++.
1

Open the theme map for your language

In Project Settings → Node to Code → Theming → Language Specific Themes, expand the theme map for the language you want to customize (e.g., C++ Themes).
2

Add a new map entry

Click the + button to add a new key-value pair. Enter a unique name for your theme as the key.
3

Configure the color values

Expand the new entry and set each color field. All fields accept FColor values (RGBA hex).
4

Select your theme

Open the Node to Code editor window and choose your new theme from the theme selector dropdown.

Color fields

Each theme is defined by an FN2CCodeEditorColors struct with the following fields. All values are FColor (RGBA).
FieldToken type
NormalTextDefault/unclassified text
KeywordsLanguage keywords (class, void, if, return, etc.)
OperatorsOperators (+, -, *, ->, ::, etc.)
StringsString literals
NumbersNumeric literals
CommentsSingle-line and multi-line comments
PreprocessorPreprocessor directives (#include, #define, etc.)
ParenthesesParentheses ()
CurlyBracesCurly braces {}
SquareBracketsSquare brackets []
BackgroundEditor background color
Custom themes you add in Project Settings are stored in NodeToCode.ini and are project-local. They are not shared between machines unless you check in your Saved/Config directory or distribute the ini file.

Build docs developers (and LLMs) love