# EneUI vs Magic UI, animation blocks against a full catalog

Magic UI is a focused set of animated blocks. EneUI indexes it alongside 100k+ components from other libraries and serves the source over MCP, CLI and API.

> Page: https://ui.eneawork.it/alternatives/eneui-vs-magicui
> Markdown: https://ui.eneawork.it/alternatives/eneui-vs-magicui.md

Magic UI is a curated set: a few hundred animated components with a strong visual identity. EneUI is the index that contains it, plus everything else harvested from the ecosystem, queryable by an agent.

| Option | Components | Libraries | Licenza |
| --- | --- | --- | --- |
| EneUI | 111,985 | 1472 | MIT (components keep their source licence) |
| Magic UI | 247 | 2 | MIT |
| Aceternity UI | 204 | 2 | Custom (free w/ attribution, no resale) |

## When to pick it

- **EneUI**, You want Magic UI's blocks findable next to every other library, with one install path.
- **Magic UI**, You want one coherent animated design language and nothing else in the bundle.
- **Aceternity UI**, You want a different animated house style with its own pro templates.

## Verdict

They are not competitors at the same layer: Magic UI is a supplier, EneUI is the shelf that holds it. If your visual direction is already Magic UI, install from Magic UI; if you are choosing, search the shelf.

## FAQ

### How many components does this page cover?

112,436 components measured in the catalog, across 3 families.

### How were the counts measured?

By reading the catalog: every component carries its source library and the license declared upstream. The numbers are computed per request, not copied from a post.

### Can I install them with shadcn?

Yes, every component page shows the `npx shadcn add` command against our registry, with a free token.