SPECIAL PRICING
BLACK FRIDAY SALE
PERSONAL $99
TEAM $349
ENDS DEC 1
GET IT NOW
ANGULAR MATERIAL

Customize Angular Material without fighting its design

Angular Material gives you solid components, but customizing the default design is difficult. BuilderKit removes the Material look and replaces it with a clean, modern UI using plain CSS, while keeping the same APIs and behavior.

The after side is the same Material template with BuilderKit styles, nothing else.

What customizing Angular Material usually looks like

Material's supported path is its theming API. One mat.theme include sets the color palettes, the typography and the density, and every component reads its styles from the generated system variables. Each component also has an overrides mixin for its own tokens: a card's container color, its shape, its title size.

That is the right way to theme Material, and it does exactly that: it themes Material. Every token is a knob on a Material Design component, so you get a rounder, bluer Material card, never a different card. Reaching past the tokens into component classes is explicitly unsupported, because the DOM structure and class names are private and change between versions.

@use '@angular/material' as mat;

html {
color-scheme: light dark;

@include mat.theme((
color: (
primary: mat.$azure-palette,
tertiary: mat.$orange-palette,
),
typography: Inter,
density: 0,
));

@include mat.card-overrides((
elevated-container-color: var(--mat-sys-surface-container),
elevated-container-shape: 24px,
title-text-size: 1.25rem,
));
}

How BuilderKit customizes Angular Material

BuilderKit does not override Material, it replaces the visual layer. Every Material component is restyled with plain CSS under one #bui scope, with the look driven by CSS variables, so there is no Sass theme to configure and nothing fighting the defaults.

BuilderKit ships as source in your project, so when something needs to change you edit the CSS file for that component directly. Colors come from one provider call, covered in the theming docs.

import { provideTheming } from '@/app/core/theming';

export const appConfig: ApplicationConfig = {
providers: [
provideTheming({
scheme: 'system',
primary: '#3E63DD',
error: '#E5484D',
neutral: '#8B8D98',
}),
],
};

Everything stays Angular Material

Same imports and APIs

The same Material imports, component APIs and behavior you already use.

Same accessibility

Keyboard, focus and ARIA come from Material, CDK and Aria, unchanged.

Runtime theming

Theme color and light or dark scheme switch at runtime, no rebuild needed.

Frequently Asked Questions

Answers to the most common questions about how BuilderKit customizes Angular Material, what stays the same, and how it is kept up to date.

Yes, while the suggested use case is to use one of the templates as a starting point for new projects, BuilderKit can also be integrated into existing Angular applications. The refined Angular Material styles can be applied to upgrade the look and feel of your current components, and individual blocks or templates can be adapted for use within your app’s structure. The agent skill also handles installing BuilderKit into an existing project for you.
No. BuilderKit doesn't include any custom primitive Angular components. Instead, it provides refined styles for the standard Angular Material components. These styles enhance the appearance of the existing components you already use, giving them a more modern and polished design without requiring any changes to the components themselves.
Every Angular Material component is restyled with plain CSS inside one #bui scope. The styles target what Material renders and read colors, radii and spacing from CSS variables, so there is no Sass theme to configure and no fork of Angular Material. Everything ships as source in your project, so when something needs to change you edit the CSS file for that component.
No. You import MatButton, MatTable and the rest from @angular/material exactly as before and use the same inputs, outputs and directives. BuilderKit adds the styles, not a layer in between, so there is no second API to learn and nothing to migrate when Angular Material moves on.
Yes. Keyboard navigation, focus management and ARIA attributes come from Angular Material, the CDK and Angular Aria, unchanged. BuilderKit only changes the visual layer and keeps focus states visible in both light and dark schemes.
BuilderKit comes with its own theming system that is separate from Angular Material’s built-in theming. It supports both light and dark modes out of the box, can be customized to fit your brand colors, and allows changing colors at runtime for dynamic theme switching. However, it does not integrate directly with Angular Material’s theming API, so you cannot use Material themes to change the appearance of BuilderKit components.
Advanced Components follow the same design system. Colors, spacing and typography are fully aligned with BuilderKit’s tokens, so they support the same light and dark modes and runtime theme changes.
Regularly. BuilderKit tracks Angular and Angular Material releases, and the components, blocks and templates get updates between them. Every release is listed in the changelog.
BuilderKit lives in your project as source, so an update is a pull of the repository and a copy of the changed files into your app. If you use the agent skill, your agent does this for you.

Start building modern Angular apps

With BuilderKit, you have everything you need to create polished, scalable Angular applications with better structure and faster development.