Skip to content

About · Last updated August 28, 2026

About NudaUI

Copy-paste UI animations that work in any stack, built by one person, given away under MIT. Here is what that means in practice — and who is behind it.

What NudaUI is

NudaUI is a catalog of 1503 copy-paste UI animations spread over 81 categories — loaders, toasts, skeletons, hover cards, command palettes, waveform scrubbers, watch faces, and a long tail of effects most teams end up hand-writing at 11pm. Every entry is plain HTML and CSS, with a little vanilla JavaScript only where interactivity genuinely requires it.

There is no package to install. You open a component, copy the markup and the stylesheet, and paste them into whatever you are already building. That is the entire distribution model, and it is deliberate: the code becomes yours the moment it lands in your repo, so nobody can deprecate it, break it in a minor release, or make you migrate.

Why it exists

Most animation libraries assume you are building a React single-page app with a bundler and a design-system fork. That assumption leaves out an enormous amount of real software: Laravel and Django and Rails apps, Astro and Hugo sites, internal admin tools, WordPress themes, and the plain .html file somebody is still shipping to production. Those teams end up pulling 200 kB of JavaScript to get a loading spinner, or writing keyframes by hand and getting prefers-reduced-motion wrong.

NudaUI exists to remove that trade-off. The markup is the product, and markup is universal. If your stack can render a <div>, it can render every component here — unchanged, with no adapter and no build step.

How components are built

Every component in the registry follows the same rules, and they are enforced by tests rather than by good intentions:

  • No frameworks, no dependencies. Pure HTML and CSS; vanilla JS only when a component needs state. Nothing imports a runtime.
  • Namespaced classes. Every class is prefixed nuda-*, so nothing collides with Tailwind utilities or your own stylesheet.
  • Themed with custom properties. Colour, size, radius and timing read from CSS variables. Override them on :root or any parent — no Sass, no config fork.
  • Accessible by default. Motion-heavy components ship a prefers-reduced-motion fallback; interactive ones ship focus-visible styles, ARIA roles and keyboard handling.
  • GPU-friendly. Animations stay on transform and opacity, and flicker is kept under three flashes per second so nothing trips WCAG 2.3.1.
  • Responsive. Components work from a 320 px phone to a wide desktop without media-query surgery on your side.

Who builds it

NudaUI is designed, built and maintained by Santiago Gómez de la Torre Romero, a software engineer working in Spain. He is the sole creator, owner and maintainer of the project — there is no company behind it and no team to escalate to. Bug reports and component requests go to GitHub; everything else reaches him at contact@nudaui.dev.

Licensing and cost

Component code is MIT licensed. Copy it, modify it, ship it, sell it, fork the whole catalog — commercial use included, no permission needed. Attribution is appreciated and never required. Read the full terms at https://nudaui.dev/terms.

The site itself is free with no paid tier, no account system, and no usage tracking. There are no analytics scripts and no cookies — see the privacy policy for exactly what that means.

For AI agents and integrations

The whole catalog is available as JSON, so you never have to scrape the gallery. Start at the developer portal or read the OpenAPI 3.1 document directly. Guidance on when NudaUI is and is not the right tool lives at https://nudaui.dev/agent-instructions.md, and the grounding index is at https://nudaui.dev/llms.txt.

Every page on this site also answers Accept: text/markdown with a clean Markdown representation of itself, so an agent can read the content without paying for the markup.