Fireworks Emoji Unicode, HTML and Shortcode Reference

Unicode Code Point

The fireworks emoji is officially registered at Unicode code point U+1F386, part of the Miscellaneous Symbols and Pictographs block introduced in Unicode 6.0 (2010).

HTML Entities

Format	Value
Decimal entity	🎆
Hex entity	🎆

Either entity can be placed directly into HTML markup and will render as 🎆 in any modern browser without needing a special font.

CSS Usage

To insert the emoji via CSS, use the code point inside a content property on a pseudo-element:

Shortcode

Many chat platforms and markdown-based tools support the shortcode :fireworks:, which automatically converts to 🎆 when rendered.

Quick Copy Reference

• Emoji: 🎆
• Unicode: U+1F386
• HTML Decimal: 🎆
• HTML Hex: 🎆
• Shortcode: :fireworks:

Every one of these formats can be copied instantly using the code chips at the top of the homepage.

Unicode Code Point and Character

The fireworks character is assigned code point U+1F386. Unicode gives the symbol a stable identity, while each platform supplies its own artwork. A source file saved as UTF-8 can normally contain 🎆 directly. When an environment does not reliably preserve UTF-8 text, an escape sequence or HTML entity can represent the same character.

HTML Decimal and Hexadecimal Entities

The decimal HTML entity is 🎆 and the hexadecimal form is 🎆. Both render the same character in normal HTML text. Include the semicolon at the end. Entities are useful in generated markup, documentation and systems where typing the glyph directly is inconvenient, but modern UTF-8 pages can generally use the emoji itself.

JavaScript and JSON

In modern JavaScript, you can store the literal character in a string. A Unicode code point escape can also be written as \u{1F386} in environments that support the brace form. JSON commonly stores the literal UTF-8 character or a surrogate pair escape. Ensure the server and file are encoded consistently so the value does not become replacement characters.

CSS Content

For generated content, CSS can use a hexadecimal escape such as content: "\1F386";. Add a space after the escape when the next character could be interpreted as another hexadecimal digit. Generated content should remain decorative because screen-reader handling varies and essential information should exist in the HTML.

Encoding and Rendering Problems

• Use UTF-8 in the HTML meta charset and when saving source files.
• Confirm the HTTP Content-Type header also declares UTF-8.
• Use an emoji-capable fallback font in CSS.
• Update older operating systems when the glyph displays as an empty box.
• Do not confuse visual variation with a different Unicode character.

Technical Reference Summary

Character: 🎆. Unicode: U+1F386. Decimal value: 127878. HTML decimal: 🎆. HTML hexadecimal: 🎆. Common shortcode: :fireworks:. Shortcodes are platform conventions rather than part of Unicode, so support depends on the application. The Unicode value remains the reliable cross-platform identifier.

Database and API Storage

Applications should store the character in a Unicode-capable column and use UTF-8 throughout the connection, database and response. In MySQL installations, utf8mb4 is generally required for characters outside the Basic Multilingual Plane. A mismatch between the page, API and database can turn the emoji into question marks even when the original input was correct.

Testing Across Environments

Test the literal character, decimal entity and code point escape in the actual environment that will publish the content. A browser, email client, content management system and mobile app may each process text differently. Automated tests can compare the stored code point with 0x1F386 rather than comparing screenshots, because vendor artwork is expected to vary.

When debugging, inspect the encoded bytes and response headers before changing the visible character. Most failures come from an encoding boundary, an outdated font or accidental double-escaping. Keeping the source file and transport layer consistently UTF-8 prevents the majority of problems.