How do I use Kawaii Heart Button in my project?

Copy whichever of HTML, CSS and Tailwind matches your setup and paste it in. There is no build step, no dependency and no framework requirement. The three formats produce the same component, so pick the one that fits and ignore the rest.

How do I change the animation speed?

Edit the animation-duration on the rule that references heartbeat. A larger value slows it down, and removing the animation property stops it entirely while leaving the rest of the styling intact.

Does the animation respect reduced motion settings?

Not as written. Wrap the animation in a prefers-reduced-motion query if motion sensitivity matters for your audience, which takes three lines and is worth doing.

How do I change the colours?

Edit the colour stops inside the gradient declaration. Keeping the same number of stops preserves the transition, and changing their positions changes where the colours meet.

Can I use Kawaii Heart Button commercially?

Yes. The code is free to use in personal and commercial projects, with no attribution required and no licence to accept.

What makes Kawaii Heart Button different from a plain button?

It uses keyframe animation, transitions, transforms and gradients, where a default button uses none of them. That is the whole difference: the behaviour is the same and the presentation is not.

Kawaii Heart Button

0 viewsmedium

Background:

<button class="kawaii-heart-btn">
  <span>♡</span>
  <span>Like</span>
</button>

Was this helpful?

About Kawaii Heart Button

Kawaii Heart Button is a button built with a keyframe animation, gradient fills, transforms and layered shadows. Its stylesheet runs to 29 lines across 4 rules, declaring 17 distinct properties. It styles hover state explicitly, so the component responds to interaction rather than sitting still. The animation is driven by a keyframe sequence named heartbeat, which you can retime or remove without touching the rest of the styling. Every format shown on this page is the same component, so you can take HTML, CSS and Tailwind depending on how your project is set up. Nothing is minified and nothing depends on a framework.

When to use

Sites with a strong established look, where a neutral control would sit awkwardly, where a kawaii and cute button fits the surrounding design
A single prominent button rather than a row of them, since the heartbeat animation runs continuously and several at once compete with each other
Palettes built around pink, white and red, where this button can be dropped in without retheming

How it works

The base rule sets the shape with border-radius, display and padding. The fill is a gradient rather than a flat colour, so it is a single background declaration with no image to load. Movement is done with transforms rather than by changing position or size, which is what keeps it smooth: transforms are composited and do not force the browser to lay the page out again. State changes are eased with a transition, so hovering does not snap. The looping motion comes from heartbeat. Changing the animation-duration is usually the only edit needed to make it faster or calmer.

Accessibility

Keyboard navigation

Supported

Screen reader

Friendly

ARIA

Native element semantics, no extra attributes needed

Built on a native <button> element, so keyboard focus and screen reader semantics work without extra attributes. No focus style is defined. Add one before shipping, or keyboard users lose track of position. Animates without a prefers-reduced-motion guard. Wrap the animation in that query if motion sensitivity matters to your audience. Those are 2 things to fix before this ships in front of users.

Browser support

Chrome

26+

Firefox

16+

Safari

Edge

12+

Everything this component uses has been supported across browsers for years, so no fallback is needed.

Related components

steampunk brass button holographic cube button magnetic field button blockchain hash button sound wave button anime manga button

Frequently asked questions