Fried Shrimp

The 🍤 Fried Shrimp emoji was added in Unicode 6 (2010) and is drawn as a single orange-pink fried shrimp with a curled tail and visible crispy breading texture. The visual cue reads instantly as fried shrimp, the visible-seafood-comfort default, or the Japanese-coded tempura tag. By 2026 🍤 has become the go-to emoji for the fried-shrimp-coded reaction, the visible-seafood-comfort default, and the Japanese-coded tempura tag.

In modern chat 🍤 does very specific work. People send it as a literal fried-shrimp reference, as the visible seafood-comfort default, or as the Japanese-coded tempura tag. The orange-pink-fried-shrimp-with-curled-tail is the visual cue that the read is seafood-comfort-coded. Writers should pick 🍤 when the read is fried-shrimp or seafood-comfort, and avoid it when the read is sushi-coded — 🍣 fits better there.

🍤 lands on a friend's 'tempura night' message, in a work channel where someone is signing off with food-coded content, and in a dating-app DM where the sender is sending seafood-comfort content. The orange-pink-fried-shrimp anchors the read.

In close-friends chats 🍤 reads as the universal seafood-comfort default. On X the emoji punctuates seafood-coded and tempura-coded tweets. The emoji pairs with 🍣 for the layered seafood-coded stack and with 🍙 for the layered Japanese-comfort pair stack.

Skip 🍤 in any context where the read is sushi-coded — 🍣 fits better. Avoid 🍤 in work channels where the seafood-comfort read lands as off-topic. Pick 🍕 when the read is comfort-coded without seafood.

If a friend sends 🍤 on a seafood-comfort message, mirror with another 🍤 or 🍣 to match the seafood-coded energy. The fried-shrimp chain reads as solidarity.

If 🍤 lands as the tempura-coded default, reply with another 🍤 or 🍙. And if you want to send 🍤 yourself, pair it with the moment so the seafood-comfort-coded read is clear.