Frowning Face Emoji

A yellow face with simple, open eyes and a wide, steep frown. Where most sad emoji add tears, closed eyes, or dramatic gestures, ☹️ is just a face that's unhappy. No embellishment. No performance. Just the frown.

Emojipedia describes it as conveying "moderate concern or disappointment and affectionate sadness, as when missing a loved one." That "moderate" qualifier is important. ☹️ isn't devastated. It isn't sobbing. It's the face you make when plans get cancelled, when the weather turns gray, when someone says something that lands wrong. It's sadness at room temperature.

What makes ☹️ historically unusual is its age. The character U+2639U+2639 was approved in Unicode 1.1 in 1993 under the name "White Frowning Face," making it one of the oldest characters in the emoji system. It existed as a text symbol, a dingbat, for over two decades before being retroactively included in Emoji 1.0 (2015). The "white" in the original name refers to the outlined style (as opposed to a filled "black" version), not skin color, though Samsung's early designs actually rendered it as a white face.

The simplicity of ☹️ is both its strength and its limitation. It communicates sadness clearly but leaves all the nuance to the reader. Is it genuine sadness? Gentle disappointment? Passive-aggressive displeasure? The frown doesn't specify. That ambiguity makes it surprisingly versatile.

In texting, ☹️ fills the gap between "I'm fine" and a full emotional breakdown. It's the emoji equivalent of a quiet sigh. People use it when they're disappointed but not devastated, when they're sad but don't want to make a big deal of it.

The passive-aggressive dimension is real and worth noting. A standalone ☹️ with no accompanying text can read as guilt-tripping: "oh, you're busy tonight? ☹️" lands very differently from "oh no, I was looking forward to it 😢." The frown without tears reads as reproachful rather than sad, especially to younger users. Research on emoji perception shows that simple, unadorned faces are more likely to be read as passive-aggressive by Gen Z than by older generations.

On social media, ☹️ appears most often in captions about mild disappointments: sold-out tickets, rainy days, cancelled plans, Monday mornings. It's the low-stakes sad face. For heavier emotions, people reach for 😢 (crying face) or 😭 (loudly crying). ☹️ stays in the shallow end of sadness.

One subtle use: ☹️ as a request for comfort. Sending a bare ☹️ to a partner or close friend is an invitation to ask "what's wrong?" It's less demanding than spelling out the problem, which makes it an indirect way to open a conversation about something that's bothering you.

☹️ is rarely flirty on its own, but it can signal romantic interest when used to express disappointment about not seeing someone. "Wish you were here ☹️" from a crush is softly romantic. The frown's simplicity makes it feel sincere rather than performative, which gives it a different emotional weight than more dramatic sad faces.

• •Romantic if: expressing sadness about not seeing you specifically
• •Friendly if: reacting to general bad news or cancelled plans
• •Passive-aggressive if: standalone after you declined something, with no other text
• •Genuine if: paired with an explanation of why they're sad

☹️ has one of the longest histories of any emoji. Its codepoint U+2639U+2639 was encoded in Unicode 1.1 (1993), the same era as the World Wide Web's early expansion. At the time, it was just a dingbat, a simple pictographic character for documents and early digital communication, sitting in the same block as playing card suits and weather symbols.

For over twenty years, ☹️ lived as a text symbol. It appeared in documents, was used in early internet forums as a graphical frown, and coexisted with the ASCII emoticon :-(:-( that served the same purpose. When Apple, Google, and other platforms started supporting full-color emoji in the 2010s, Unicode retroactively promoted ☹️ to emoji status as part of Emoji 1.0 (2015).

This makes ☹️ part of an unusual club: characters that existed for decades as plain text before suddenly becoming colorful, expressive emoji. Its companion ☺ (smiling face) went through the same transformation. They're the elders of the emoji world, predating purpose-built emoji faces like 😀 (which arrived in Unicode 6.1, 2012) by nearly two decades.

Approved in Unicode 1.1 (June 1993) as U+2639U+2639 WHITE FROWNING FACE, making it one of the oldest emoji-eligible characters in existence. It predates the color emoji era by over two decades.

The character was originally a text dingbat in the Miscellaneous Symbols block (U+2600U+2600-U+26FFU+26FF), alongside ☺ (White Smiling Face), ☠ (Skull and Crossbones), and other simple pictographs. It was designed to be rendered as a monochrome outline, a circle with dot eyes and a curved-down mouth.

When Emoji 1.0 was defined in 2015, dozens of these old dingbat characters were retroactively promoted to emoji status. Adding the variation selector U+FE0FU+FE0F after the codepoint triggers emoji presentation (colorful, yellow face) on supporting platforms. Without it, some systems still render the original monochrome glyph.

The "white" in "White Frowning Face" follows Unicode naming convention where "white" means outlined/hollow and "black" means filled. It has nothing to do with skin color.

• If you're typing it: Most emoji keyboards insert the FE0F automatically, so you're usually safe.
• If you're pasting from a text editor: Check that the character takes up the full emoji width. A narrow rendering means FE0F is missing.
• If you're a developer: Always store and send U+2639 U+FE0F together. Some renderers normalise the pair, some don't.

1. 1993Unicode 1.1 encodes U+2639 White Frowning Face as a text dingbat in the Miscellaneous Symbols block (same release that renamed the adjacent Dingbats block from Zapf Dingbats to Dingbats).↗
2. 2014Unicode 7.0 adds ☹ to the emoji variation sequence list, meaning U+2639 followed by U+FE0F formally requests color emoji presentation.↗
3. 2015Emoji 1.0 retroactively promotes ☹️ to emoji status with color rendering.↗
4. 2024The 'guy smiling then frowning' meme goes viral on X, briefly reviving the frown-face as a reaction image.↗

The frown is one of the most universal facial expressions, recognized across cultures as displeasure or sadness. ☹️ translates well internationally.

However, the passive-aggressive reading of ☹️ is culturally specific. In English-language digital culture, a bare ☹️ after being told "no" can read as guilt-tripping. This interpretation is strongest among Gen Z and younger Millennials, who view simple emoji faces as potentially passive-aggressive.

In Japanese digital culture, the kaomoji (´・ω・(´・ω・)` serves a similar function to ☹️ but with a softer, more sympathetic tone. The frown in kaomoji culture is more about shared sadness than personal reproach.

The monochrome rendering of ☹️ on some platforms (since it's an old dingbat character) can look different from the yellow emoji version, which occasionally causes confusion in cross-platform communication.

• •☹️ (U+2639U+2639) was standardized in Unicode 1.1 (1993), making it roughly 32 years old. It predates Google (1998), Facebook (2004), and the iPhone (2007). The frown was digital before most of the internet existed.
• •The original name "White Frowning Face" follows Unicode convention where "white" means outlined and "black" means filled, not skin color. Samsung initially rendered it as an actual white face, misinterpreting the naming convention.
• •☹️ and its companion ☺ (White Smiling Face) are among the oldest emoticon-like characters in Unicode. They were the happy/sad pair for digital documents before purpose-built emoji faces existed.
• •On some platforms, typing ☹ without the variation selector (FE0F) renders the original monochrome dingbat instead of the colorful yellow emoji. The same character looks completely different depending on whether your system treats it as text or emoji.
• •The Unicode block that sits right next to ☹️ in the code chart, Dingbats (U+2700-U+27BF), was renamed from 'Zapf Dingbats' to just 'Dingbats' in the same June 1993 Unicode 1.1 release) that encoded ☹️. The frown's neighbours in the character table are typographic ornaments by Hermann Zapf, not other faces.
• •A 2022 Indiana University paper by Zhukova and Herring tested how different generations interpret simple face emoji. Younger users were significantly more likely to rate bare frowning and thumbs-up emoji as toxic or passive-aggressive than older users were. The research confirms what Gen Z group chats had already decided: old simple emoji like ☹️ carry more edge than their inventors intended.
• •Even with the FE0F variation selector present, macOS and some Android versions still default to the text rendering, ignoring the Unicode spec. ☹️ is one of the emoji most affected, because it lived as a text glyph for 22 years before anyone expected a yellow face.

• •The biggest risk with ☹️ is the passive-aggressive reading. A bare frown after being declined reads as guilt-tripping to many people, even if that wasn't your intent. Always pair it with words to clarify your tone.
• •☹️ can feel inadequate for serious sadness. Using it to react to genuinely heavy news (a death, a breakup, a health crisis) may come across as dismissive because the emoji is so simple and understated.
• •The monochrome vs. emoji rendering split can cause confusion. On some systems, ☹ renders as a small black-and-white symbol rather than a yellow face, which changes how it reads in conversation.

• •Codepoint: U+2639U+2639. Requires U+FE0FU+FE0F variation selector for emoji presentation on many platforms.
• •Part of the Miscellaneous Symbols block (U+2600U+2600-U+26FFU+26FF), not the Emoticons block.
• •Shortcodes: :frowning_face::frowning_face: on Slack and GitHub, :white_frowning_face::white_frowning_face: on some platforms.
• •Without the FE0F variation selector, some systems render this as a monochrome text symbol rather than a yellow emoji face. Always include FE0F if you want consistent emoji rendering.
• •One of the oldest Unicode characters used as emoji (1993). Be aware that legacy systems may handle it differently from purpose-built emoji.

See the full Emoji Developer Tools guide for regex patterns, encoding helpers, and more.