Recommended Free Tools
If Angular Material is not working, first identify whether the failure is installation, component recognition, styling, or animation. For an Angular CLI project, the documented setup starts with ng add @angular/material; then verify one Material component in a minimal example before changing the rest of your app.
Identify what “not working” means
The fix depends on where the failure occurs. Note the exact build or browser-console error, the component and selector involved, your Angular and @angular/material versions, and whether the app uses standalone components or NgModules. Classify the symptom before changing configuration:
- Install or build failure: the package or project setup may be incomplete, or the error may identify a specific configuration problem.
- Component not recognized or rendered: check the component import and template selector.
- Component appears but looks wrong or unstyled: check the global theme and styles.
- Only transitions or animation-dependent behavior are missing: check animation setup for your Angular version.
The title alone does not identify a root cause, and the right instructions can vary by project structure and version.
Confirm the Angular Material setup
For an Angular CLI-managed project, the official getting-started guide documents ng add @angular/material as the setup entry point. The schematic installs Angular Material and the Component Dev Kit (CDK), and asks about theme and typography setup. Review the selected project and the changes it makes rather than assuming the command was applied to the intended workspace.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
The current guide also describes adding Roboto and Material Symbols font references to index.html and basic global CSS. Those details reflect that guide’s setup; they should not be treated as universal requirements for every existing app or every Material version. See the current Angular Components getting-started guide.
Match the component import to its template
A Material component must be available in the context that uses its template. In the current guide’s standalone example, MatSlideToggle is imported from @angular/material/slide-toggle, added to the component’s imports, and paired with the <mat-slide-toggle> selector.
For the component that is failing, check both sides:
- Import the exact Material component into the standalone component or NgModule that owns the template.
- Check that the selector in the template is spelled correctly and belongs to that component.
Do not assume that importing a component somewhere else in the application makes it available to every template. The official slide-toggle example provides a small reference case.
Rank #3
Check the theme when components render without the expected appearance
If the component’s host element is present but its visual treatment is missing or incorrect, check whether a prebuilt or custom theme is configured in the app’s global styles. Theme selection is part of the official setup, and custom theme guidance should match the Material version installed in the project. The Angular Material v16 guides include component-style customization material; consult version-matched documentation rather than copying theme setup across generations without checking it.
Check animation setup only when animation is the symptom
If the issue is specifically missing transitions or animation-dependent behavior, inspect the animation configuration for the Angular and Material versions in use. The current setup guide includes an animation configuration choice, while older versioned instructions may describe module-based setup such as BrowserAnimationsModule or NoopAnimationsModule. Do not copy those older instructions into a newer project without confirming that they apply to its version. The Angular Material v18 getting-started guide and v16 getting-started guide provide version-specific context.
Reduce the problem to a minimal example
Use the official slide-toggle example as a smoke check. Add the component import and selector to a small component, then run the development server and inspect the page:
- In a standalone component, import
MatSlideTogglefrom@angular/material/slide-toggleand add it to that component’simports. - Place
<mat-slide-toggle>Toggle me!</mat-slide-toggle>in its template. - Run
ng servefrom the Angular workspace and check the local development page for the toggle.
If this minimal case fails, investigate project setup or dependency/configuration errors indicated by the build or console. If it works, compare the failing component’s import, template context, theme scope, and relevant configuration with the minimal case. This narrows the search; it does not prove that every possible defect has been ruled out.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Use documentation for the installed generation
The title does not specify Angular or Material versions, and the setup guides do not establish a compatibility matrix or a particular version mismatch. Check the versions recorded in your project before applying version-specific advice. Current standalone-style examples and older module-based setup instructions are not interchangeable by default. The Angular Material v5 guide is historical documentation, not a universal checklist for current projects. For schematic-specific context from another version, see the Angular Material v17 schematics guide.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
