Shocked emoji article

Shocked Emoji Unicode, HTML and Shortcode Values

Use the correct Unicode point, decimal entity, hexadecimal entity and common shortcode for 😲.

Shocked Emoji Unicode, HTML and Shortcode Values featured image

Shocked Emoji Unicode, HTML and Shortcode Values explains the practical meaning and use of 😲 in clear, everyday terms. The shocked emoji can represent astonishment, disbelief, admiration or concern, so choosing the right context matters.

Core values for the shocked emoji

The astonished face character 😲 uses Unicode code point U+1F632. Its HTML decimal entity is 😲, and its HTML hexadecimal entity is 😲. A commonly recognized shortcode is :astonished:, although shortcode support depends on the application.

All of these forms refer to the same conceptual character. The displayed artwork is selected by the operating system, browser or application.

Using the direct Unicode character

For ordinary HTML, messages and modern source files, the direct character 😲 is usually the simplest option. Save the document with UTF-8 encoding and include a UTF-8 charset declaration in HTML. This prevents the bytes from being interpreted using an older character set.

Direct characters are easy to read in source code, but some legacy pipelines handle entities more consistently.

Using HTML decimal and hexadecimal entities

The decimal form writes the code point as a base-10 number, while the hexadecimal form writes it in base 16. Browsers decode both into the same emoji. Entities can be useful inside templates or documentation that needs to show where a special character begins and ends.

Remember the terminating semicolon. Missing punctuation may cause the browser to display the text literally or interpret following characters incorrectly.

Shortcode behavior

Shortcodes are not part of Unicode. They are text conventions converted by specific platforms, editors or chat systems. The form :astonished: may become 😲 in one application and remain plain text in another. Test the destination before relying on automatic conversion.

For portable content, use the direct Unicode character or an HTML entity instead of assuming shortcode support.

Developer checks and fallbacks

Use UTF-8 throughout the page, database export or source file. Although this static site does not use a database, the same rule applies when content is copied into another system. Test on several devices when appearance matters, and provide a text label or alt description when the emoji is an important interface control.

When you need a fixed visual result rather than a character, export a transparent PNG from the generator.

Code examples in context

In an HTML paragraph, a developer can write the direct character or the decimal entity. Both should render as 😲 when the document uses UTF-8 and the browser has emoji support. The hexadecimal entity is equivalent and is often easier to compare with the Unicode notation because both display the value 1F632.

In documentation, escape the ampersand when you want readers to see the entity text rather than the rendered emoji. This distinction is important for copy buttons: the visible example and the copied value must match the user’s intent.

Technical mistakes to avoid

Do not omit the semicolon from an HTML entity. Do not assume :astonished: is universal, because shortcode conversion belongs to individual platforms. Avoid storing emoji in a file that is later saved with a legacy encoding, since the character may be replaced or corrupted.

For interface controls, pair the visual emoji with an accessible label such as β€œCopy shocked emoji.” A symbol alone may not explain the action clearly to every user.

Quick action: Copy 😲 or use the transparent PNG generator on the homepage when you need an image rather than text.