Phoenix Fire Button
<button class="phoenix-fire-btn">
<div class="fire-particles">
<div class="particle p1"></div>
<div class="particle p2"></div>
<div class="particle p3"></div>
<div class="particle p4"></div>
<div class="particle p5"></div>
<div class="particle p6"></div>
<div class="particle p7"></div>
<div class="particle p8"></div>
</div>
<div class="flame-rings">
<div class="flame-ring fr1"></div>
<div class="flame-ring fr2"></div>
<div class="flame-ring fr3"></div>
</div>
<div class="phoenix-core">
<span class="phoenix-icon">🔥</span>
</div>
<div class="ember-trail">
<div class="ember e1">✨</div>
<div class="ember e2">⭐</div>
<div class="ember e3">✨</div>
</div>
</button>About Phoenix Fire Button
Phoenix Fire Button is a button built with a keyframe animation, gradient fills, transforms, layered shadows and CSS filters. Its stylesheet runs to 187 lines across 28 rules, declaring 27 distinct properties. It styles hover state explicitly, so the component responds to interaction rather than sitting still. The animation is driven by keyframe sequences named phoenix-glow, particle-float, flame-ring-pulse, phoenix-dance, trail-orbit and ember-sparkle, 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
- Landing pages where one moving element earns attention rather than competing for it, where a phoenix and fire button fits the surrounding design
- A single prominent button rather than a row of them, since the phoenix-glow animation runs continuously and several at once compete with each other
- Palettes built around red, orange and gold, where this button can be dropped in without retheming
- Places where one control is meant to be memorable, since 187 lines of CSS is a real investment for a single element
- Cases where you want the finished effect rather than a base to build on, given how much the CSS is doing
How it works
The base rule sets the shape with border-radius, display, height and position. 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 phoenix-glow, particle-float, flame-ring-pulse, phoenix-dance, trail-orbit and ember-sparkle. Changing the animation-duration is usually the only edit needed to make it faster or calmer.
Accessibility
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
Everything this component uses has been supported across browsers for years, so no fallback is needed.
Related components
Frequently asked questions
Phoenix Fire Button
<button class="phoenix-fire-btn">
<div class="fire-particles">
<div class="particle p1"></div>
<div class="particle p2"></div>
<div class="particle p3"></div>
<div class="particle p4"></div>
<div class="particle p5"></div>
<div class="particle p6"></div>
<div class="particle p7"></div>
<div class="particle p8"></div>
</div>
<div class="flame-rings">
<div class="flame-ring fr1"></div>
<div class="flame-ring fr2"></div>
<div class="flame-ring fr3"></div>
</div>
<div class="phoenix-core">
<span class="phoenix-icon">🔥</span>
</div>
<div class="ember-trail">
<div class="ember e1">✨</div>
<div class="ember e2">⭐</div>
<div class="ember e3">✨</div>
</div>
</button>What is inside Phoenix Fire Button
Phoenix Fire Button is a CSS button built with a keyframe animation, gradient fills, transforms, defined in 187 lines across 28 selectors.
Techniques used
Animations defined: phoenix-glowparticle-floatflame-ring-pulsephoenix-dancetrail-orbitember-sparkle
CSS properties in this component
align-itemsanimationanimation-delayanimation-durationbackgroundborderborder-colorborder-radiusbottombox-shadowcolorcursordisplayfilterfont-sizeheightjustify-contentleftopacityoverflowpositionrighttoptransformtransitionwidthz-indexAccessibility check2 to fix
- 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.
These notes are generated by reading this component's own source, so they describe what it actually does rather than what a template says. Copy the code above in HTML, CSS, Tailwind and adapt it freely.