| name | kendo-themes |
| description | Styling reference for Kendo and Telerik UI components with Kendo theme packages. Relevant for Kendo/Telerik appearance, theme installation, CSS/SCSS token properties and theme customization, design tokens, swatches, Tailwind token mapping, component selectors, and visual consistency between Kendo components and application UI. |
Styling Kendo and Telerik Components
Kendo themes define the styling layer for Kendo and Telerik components: theme packages, design tokens, CSS custom properties, Sass variables/maps, swatches, and component selectors.
Overview
Kendo and Telerik components (Angular, React, Vue, jQuery, Blazor) get their look from Kendo theme packages. A theme applies design tokens — colors, spacing, typography, radii, elevation, and motion — to every component automatically. Appearance changes happen either globally (change tokens, affect all components) or per-component (target specific selectors).
Consumer Application
└── Kendo / Telerik Components (Angular, React, Vue, jQuery, Blazor)
└── Theme Package (styling layer)
└── Design System Tokens (colors, spacing, typography…)
6 themes available — choose the package that matches the target design language:
| Theme | Package |
|---|
| Meridian | @progress/kendo-theme-meridian |
| Bootstrap | @progress/kendo-theme-bootstrap |
| Material | @progress/kendo-theme-material |
| Fluent | @progress/kendo-theme-fluent |
| Default | @progress/kendo-theme-default |
| Classic | @progress/kendo-theme-classic |
All themes share the same design token foundation — colors, spacing, radii, elevation, motion, typography, and iconography — so token-based customizations are portable across themes.
Installation
Install the theme package alongside the Kendo or Telerik framework package when it is not already present:
npm install --save @progress/kendo-theme-meridian
Replace meridian with default, bootstrap, material, fluent, or classic to match the target design language.
Importing the Theme
For components to pick up their styles, import the theme once in the application entry point. There are two paths: CSS (precompiled, runtime-customizable via CSS custom properties) or Sass (compile-time customization, requires a build step).
CSS Import (Recommended Starting Point)
Import the precompiled CSS — all components are styled immediately:
import "@progress/kendo-theme-meridian/dist/all.css";
The compiled CSS is still customizable at runtime through CSS custom properties such as --kendo-color-*, --kendo-spacing-*, and component-scoped variables — no Sass build required.
Sass Import
Use Sass for compile-time control over the generated styles:
@use "@progress/kendo-theme-meridian/scss/all.scss" as *;
To include styles for only selected components, use scss/index.scss and include component mixins explicitly:
@use "@progress/kendo-theme-meridian/scss/index.scss" as *;
@include kendo-button--styles();
@include kendo-grid--styles();
@include kendo-combobox--styles();
Each component exposes a kendo-{component}--styles() mixin.
Customization
Two levels of customization control component appearance — broad design-wide changes and surgical per-component overrides.
1. Global: Design Tokens
Override design tokens to change the look of all components at once. This is the primary customization layer — colors, spacing, radii, elevation, motion, and typography.
For colors, start with semantic tokens (primary, surface, error, etc.), CSS custom properties, and prebuilt swatches.
CSS Custom Properties (runtime, no build step — works with precompiled CSS):
:root {
--kendo-<token>: <value>;
}
Sass (compile-time, via @use ... with ()):
@use "@progress/kendo-theme-<theme>/scss/all.scss" as * with (
$kendo-<map>: (
<key>: <value>,
),
$kendo-<variable>: <value>
);
Token names, defaults, and CSS variable patterns are in the reference table below.
2. Per-Component: CSS Selector Overrides
When global tokens are not enough, target specific components using CSS selectors. Kendo and Telerik components use predictable class composition:
| Primitive | Pattern | Example |
|---|
| Base | .k-{component} | .k-button |
| Sub-component | .k-{component}-{part} | .k-button-icon (inside button markup) |
| Variant | .k-{modifier} | .k-button-solid, .k-button-lg |
| State | .k-{state} | .k-hover, .k-focus, .k-disabled |
Compose them:
.k-{component}.k-{component}-{fillMode}.k-{component}-{themeColor}.k-{state} {
<property>: var(--kendo-<token>);
}
.k-{parent} .k-{descendant} .k-{component} .k-{component}-{part} {
<property>: var(--kendo-<token>);
}
Variants can represent: theme color (primary, secondary, etc.), fill mode (solid, outline, flat), size (component-specific, e.g. sm, md, lg), roundedness (sm, md, lg, full), or direction (horizontal, vertical). Available sizes vary per component — consult components.json for exact values.
Selector rule: Use design tokens (var(--kendo-color-*), var(--kendo-spacing-*)) in overrides rather than hardcoded values. This keeps customizations consistent when switching themes or swatches.
For the full per-component styling guide, see components.md. Use components.json for compact component metadata (_component, _option, components, theme_options), or query it via node ./scripts/list_components.mjs and node ./scripts/get_components.mjs.
Design Tokens Reference
Each token group below is customizable through CSS custom properties or Sass maps. Colors are the most common starting point — changing --kendo-color-primary instantly rebrands every component that uses it.
| Token Group | CSS Variable Pattern | Sass Map | Reference |
|---|
| Colors | --kendo-color-{name} | $kendo-colors | colors.md |
| Spacing | --kendo-spacing-{step} | $kendo-spacing | spacing.md |
| Border Radii | --kendo-border-radius-{size} | $kendo-border-radii | radii.md |
| Elevation | --kendo-elevation-{level} | $kendo-elevation | elevation.md |
| Translucency | --kendo-translucency-base | $kendo-translucency-base | translucency.md |
| Motion | --kendo-duration-{name}, --kendo-easing-{name} | $kendo-durations, $kendo-easings | motion.md |
| Typography | --kendo-font-size, --kendo-font-family, etc. | Individual variables | typography.md |
| Iconography | Size classes (.k-icon-{xs..xxxl}) | $kendo-icon-size | |
Extensibility
Matching Kendo Components to Your Design System
When the application has its own design system and Kendo components need to match:
- Override Kendo tokens to align with your design system values (colors, spacing, typography)
- If token-level changes are not enough, target component selectors and apply your tokens directly:
.k-button.k-button-solid.k-button-primary {
background-color: var(--your-ds-primary);
border-color: var(--your-ds-primary);
color: var(--your-ds-on-primary);
}
Building Custom UI That Matches Your Components
When building custom UI alongside Kendo components:
- Reuse Kendo design tokens — never hardcode colors, spacing, or other values
- Reference tokens via CSS custom properties so everything stays in sync
.my-custom-card {
background-color: var(--kendo-color-surface);
border: 1px solid var(--kendo-color-border);
border-radius: var(--kendo-border-radius-md);
padding: var(--kendo-spacing-4);
box-shadow: var(--kendo-elevation-2);
font-family: var(--kendo-font-family);
}
Tailwind CSS Integration
Kendo components and Tailwind work side-by-side with no conflicts. The common pattern is Tailwind for layout and app-level styles, Kendo theme for component styles.
Three approaches depending on which system owns the design tokens:
- External source: A shared set of custom properties (from a design system or brand guidelines) feeds both Tailwind and Kendo.
- Tailwind-first: You already have a Tailwind
@theme — override Kendo CSS properties to follow it: --kendo-<token>: var(--<tw-token>);
- Kendo-first: You start from a Kendo swatch — point Tailwind at Kendo tokens:
--<tw-token>: var(--kendo-<token>);
See tailwind-integration.md for the full semantic mapping guide and best practices.
Further Reading
