Shrug Kaomoji Japanese Faces Blog
← Back to blog

Shrug Copy Compatibility: A Troubleshooting Checklist

· Updated

A successful copy means the browser reported a clipboard write. It does not test every receiving app. Use this checklist to find where the result changes, without assuming that text always looks identical across devices.

1. Compare the plain text first

Copy ¯\_(ツ)_/¯ and paste into a plain-text draft. The complete drawing is nine Unicode characters: macron, backslash, underscore, opening parenthesis, katakana ツ, closing parenthesis, underscore, slash and macron.

If the browser blocks clipboard access, use the manual field. Select its full contents and use your device’s Copy command. Do not keep clicking a success-looking control if the destination has not changed.

2. A backslash disappeared

A markup processor may interpret the backslash as an escape. In an editor supporting code spans, try a code-formatted draft and inspect its preview. Different chat and publishing apps use different rules, so do not assume one escaped string works everywhere.

If you are placing the drawing inside a program or JSON string, follow that language’s string escaping rules as well. A backslash in stored text and a backslash in source code are different layers.

3. A character became a box or shifted

That can indicate missing font coverage or fallback. Try another font or the strict ASCII alternative \_(o_o)_/. The classic shrug is not ASCII-only: ¯ and ツ are outside ASCII.

For long faces, check whether a line break split the drawing. A shorter face or a separate line can help when the destination does not support a no-wrap style.

4. The graphic emoji split into pieces

The base 🤷 is a different character from the text drawing. Emoji forms can include skin-tone modifiers or joiners, and unsupported sequences may render as separate pieces. Unicode’s emoji specification describes these sequence types; it does not guarantee that a particular app supports them.

5. Record the actual destination

When reporting a display problem, include the exact copied text, the destination app, device, font if known, and which character changed. A comparison between two real drafts is more useful than saying it fails “everywhere”. You can choose another form after identifying the constraint.