Strikethrough on Discord, Instagram and WhatsApp

Notation or Unicode strokes?

For a Discord or WhatsApp message, start with the app’s native formatting. For a plain-text field that does not interpret that notation, try a short Unicode stroke sample and check the result. Neither method guarantees the same appearance in every bio, caption or username field.

The difference is in what you enter. ~~Monday~~ is a formatting instruction for a compatible renderer. M̶o̶n̶d̶a̶y̶ is a sequence containing extra combining characters. It does not carry a document deletion record or an edit history.

Native message syntax and Unicode output

• Discord message: try ~~Monday~~. This is native message formatting, as documented by Discord.
• WhatsApp message: try ~Monday~, one tilde per side, as documented for messages.
• Instagram bio or caption: try a short Unicode Standard Strikethrough sample, and check acceptance, glyph placement and clipping in the actual field.
• Display name or account username: keep a readable plain name first. These are different fields and can have different restrictions.
• GitHub Flavored Markdown: ~~Monday~~ is supported tilde syntax, not a Discord-exclusive shortcut.

Choose by the actual receiving field, not just the app's name.

Discord’s message-formatting guide documents double tildes. WhatsApp’s formatting help documents a tilde on each side. The GitHub Flavored Markdown specification supports one or two matching tildes. These references describe notation, not every client’s clipboard behavior.

Make a Unicode sample with the right style

1. Open the Strikethrough Text Generator.
2. Enter A 1 in Original text.
3. Compare Standard Strikethrough with the slash and wrapper outputs. Standard adds U+0336. Long Slash Overlay adds U+0338; it is not a double horizontal strike.
4. Choose Copy Standard Strikethrough. If clipboard access fails, select the named output box and copy manually.
5. Paste into the intended field, inspect it, and keep a readable original nearby.

Exact generator outputs, with the original space left plain

Input and operation	Complete output	UTF-16 units
A 1, Standard	A̶ 1̶	3 input, 5 output
A 1, Long Slash	A̸ 1̸	3 input, 5 output
A 1, Bracket Wrapper	[ A 1 ]	3 input, 7 output
á!, Standard	á̶!̶	3 input, 5 output

In the last row, the input uses a followed by U+0301, then an exclamation mark. The accent sequence stays contiguous; one stroke is appended after each of its two non-whitespace grapheme clusters. These counts explain the generated strings, not a destination’s character budget.

The generator leaves spaces, tabs and physical line endings plain. It preserves complete input clusters before adding marks, including joined sequences, but a font may position the new mark poorly on a complex cluster. Existing marks are retained and can stack. The Unicode combining-mark chart identifies the marks; it does not certify platform rendering.

A correction that stays understandable

Suppose a meeting moves from Monday to Tuesday. In a Discord message, try the literal input Old date: ~~Monday~~. New date: Tuesday. using native message formatting. For a plain-text field, generate only Monday with Standard Strikethrough and place it beside the same readable labels.

Keep New date: Tuesday in ordinary text. Someone should understand the update even if the stroke is clipped, filtered or poorly announced. A completed task similarly needs a plain Completed status; decoration should not carry the whole meaning.

Test the paste, and avoid the usual mistakes

Use a short draft or a test message before updating an important profile:

1. Confirm whether you copied typed notation, a rendered selection or a generator output.
2. Paste into a plain-text editor to inspect the characters, then try the intended receiving field.
3. Check the submitted or saved result when the field changes its preview after saving.
4. Look for missing strokes, unexpected tildes, clipping and field-limit errors.
5. Fall back to the plain original or native formatting if the result is hard to read.

Copying a rendered selection can transfer different data from copying source notation. Do not assume that tildes always reappear, always disappear or that rich formatting survives a plain-text paste. A successful generator Copy reports its clipboard write, not the destination’s acceptance.

• Calling every preset strikethrough: X, brackets, parentheses, dashes and slashes are literal wrappers. They leave the inner letters unchanged.
• Applying marks repeatedly: Existing diacritics remain, so regenerating already decorated text stacks more marks. Start from the original.
• Treating counts as app limits: Local UTF-16 counts differ from whatever rules a receiving field applies. Test that field rather than relying on a generic platform checklist.
• Using decoration for document edits: Use appropriate native document features. For HTML, del marks deletion, while s represents content that is no longer relevant or accurate.

The generator allows up to 25,000 UTF-16 units and 5,000 grapheme clusters. Oversized or incomplete Unicode input shows an error without shortened results; Sample or Clear helps you recover. Real fonts, speech behavior, field restrictions and browser clipboard handling still need their own tests.

For a different operation, compare the Underline Text Generator, or use the Brackets Generator for custom delimiters and wrapping modes. Those tools solve distinct tasks; adding a wrapper does not create a stroke.

Reviewed October 12, 2026: the native syntax against the official documentation, and the examples against the generator. Live acceptance in every Instagram, Discord or WhatsApp field is not claimed.