You've got the text right, but the moment you paste it into another app, the line disappears. A crossed-out note in Google Docs turns into plain text in Slack, or a struck price in Word shows up untouched in a web form. That's the problem with strike through text, it isn't one feature, it's a family of implementations that only behave consistently when you respect where the text is going, not just where it started.
The practical fix is to choose the version that survives the move. Sometimes that means a native shortcut in a desktop editor, sometimes semantic HTML for published content, and sometimes a Markdown-friendly workflow that keeps the meaning intact across tools. If you're choosing a writing environment for longer documents, Compare book writing software options is useful context because formatting behavior becomes a real workflow issue once you leave a single app. For clipboard-heavy work, it also helps to keep a clipboard history workflow handy so you can recover the original and formatted versions when one app strips the styling.
Practical rule: if the line has meaning, preserve the meaning. If it's only visual, keep the styling lightweight and expect it to break somewhere.
Why Strikethrough Formatting Breaks When You Switch Apps
A lot of people learn one shortcut, cross something out once, and assume the job is done. Then they paste the same text into a CMS, a chat app, or a form field, and the formatting vanishes. That isn't user error, it's the result of different tools storing strike through text in different ways.
Visual effect versus semantic meaning
On the web, strikethrough can be stored as semantic HTML with <s> or <del>, or as pure styling with CSS text-decoration: line-through.[^1] In office tools, it might live as document formatting metadata, and in some apps it's just plain text with no strike state at all.[^1][^4] That's why the same crossed-out phrase can survive one paste operation and disappear on the next.
The important distinction is meaning. <s> signals text that is no longer accurate, while <del> signals text that was removed or revised.[^1] Those are not the same thing, even if the line looks identical in the browser. If you flatten everything into plain text, downstream tools and assistive technologies lose the context.
Why the line disappears in transit
Some apps don't support rich text natively, so users work around the gap by generating the strike elsewhere and pasting it in.[^2] That's common in messaging and lightweight workflows. It works until the receiving app strips formatting, converts the text, or treats the line as decoration rather than content.
If you live in manuscript or editorial work, the formatting question becomes part of the tool choice itself. Editors need to know whether a strike is a revision mark, an outdated option, or just a visual cue. Keep that distinction in mind when you move between drafts, comments, and publishing systems, because the same visual line can mean three different things.
Keyboard Shortcuts and Menu Paths for Popular Productivity Apps
Desktop editors are still the easiest place to apply strike through text quickly. The exact shortcut depends on the app, and in some cases the menu path is more reliable than the keyboard. That difference matters when you're jumping between Word, Google Docs, Sheets, Excel, Gmail, Slack, or a chat app that doesn't support formatting at all.[^1][^3]
| Application | Windows Shortcut | Mac Shortcut | Menu Path |
|---|---|---|---|
| Microsoft Word | Dedicated Strikethrough command, or use the ribbon | Command+Shift+X[^6] |
Home tab, Font section[^6] |
| Google Docs | Alt+Shift+5[^1] |
Cmd+Shift+X[^1] |
Format menu, then Text, then Strikethrough[^1] |
| Google Sheets | Alt+Shift+5[^1] |
Cmd+Shift+X[^1] |
Format menu, then Text, then Strikethrough[^1] |
| Excel | Ctrl+5[^4] |
Cmd+Shift+X[^6] |
Home tab, Font area, or Format Cells[^6] |
| Gmail | Varies by browser and compose mode, use the formatting toolbar when available | Varies by browser and compose mode | Composer toolbar, formatting options when enabled |
| Slack | Markdown-like text entry in some contexts, but native formatting support is limited by surface | Same as Windows in browser and desktop app | Formatting menu in supported message fields |
The shortcuts that actually save time
Microsoft Word has a dedicated Strikethrough command and a separate Double strikethrough option, which tells you the feature is a real formatting primitive, not a decorative afterthought.[^1] In Word, the ribbon path lives under Home and Font.[^6] In Excel, Ctrl+5 is the shortcut people remember because it's the fastest way to mark a cell as done without deleting the value.[^4]
Google Docs and Sheets are straightforward on desktop. Alt+Shift+5 on Windows or ChromeOS, and Cmd+Shift+X on Mac, will usually apply the strike immediately.[^1] If you prefer clicking, the Format menu path is there.
In apps that don't support the feature natively, the safest workaround is to create the formatted text in a supported editor and paste it in, but don't assume the target app will preserve it.[^2]
That's especially true for iMessage and Messages, where users have long resorted to pasting struck text generated elsewhere because built-in formatting wasn't available in the discussion thread cited above.[^2] If you need a message to land with the visual cue intact, test it in the destination app before you rely on it.
Applying Strikethrough in HTML and CSS for Web Content
On the web, strike through text is never just about appearance. It carries meaning into accessibility tools, export pipelines, and whatever app receives the content next.[^1][^5] A page can render correctly and still send the wrong signal if the markup does not match the intent.
As noted in section 1, choose <s> for outdated text and <del> for revisions.
Pick the right HTML element
Use <s> for text that is no longer accurate or no longer relevant.[^3] Use <del> for text that was removed or revised as part of the content history.[^3] Keep that choice consistent so the document stays meaningful after copy, paste, or export.
Avoid the deprecated <strike> element.[^3] It still appears in old code and pasted snippets, but it is not the right choice for current HTML. If the strike is only visual, CSS is the cleaner path because it keeps presentation separate from the underlying content.
Use CSS when the strike is only decorative
For styling, CSS uses text-decoration-line: line-through or the shorthand text-decoration.[^4] That works well for UI labels, temporary states, and crossed-out display text that does not need deletion semantics. The markup stays cleaner, and downstream systems are less likely to misread the intent.
For teams moving content from Markdown into HTML, keep the formatting rules predictable during conversion instead of flattening everything into plain text. The Markdown to HTML conversion guide is a useful reference when you need consistent output across publishing tools.
Some layout work needs more control than a standard line-through gives you. Developers also use pseudo-elements, gradients, clip-path, and SVG to create oblique or diagonal strike lines when the default line does not fit the typeface or layout.[^7] That comes up in custom typography, localized interfaces, and right-to-left content where the default line can collide with font metrics. Use those techniques when the visual treatment needs precision, not because the built-in strike is broken.
Markdown and Cross Platform Strikethrough Techniques
Markdown is one of the few places where strike through text has a simple, widely recognized syntax. The convention is double tildes, written as ~~text~~, and that pattern is treated as the basic Markdown form in many editor and collaboration workflows.[^2] It's easy to type, easy to scan, and often portable enough for developer docs, issue comments, and lightweight notes.
Markdown versus rich text versus Unicode tricks
Markdown wins when the destination understands it. It fails when the field is plain text or the platform strips formatting on paste. Rich text is better for preserving the visual strike in supported editors, but it still depends on the receiving app honoring the metadata.
Unicode strikethrough generators are the bluntest workaround. They produce text with combining characters, which can display the strike even in places that don't support rich text. The trade-off is real, because the output may be awkward for screen readers, search, and alignment, especially in mixed-font or right-to-left environments.[^4][^7]
The cross-platform reality
That's why cross-platform strike through text is really a portability problem. A Markdown note may render perfectly in one app and show literal tildes in another. A generated Unicode string may survive a paste into a chat field but look misaligned in a document editor. A rich-text paste may keep the strike in one browser and lose it in a different client.
When portability matters, test the actual journey. Copy the text, paste it into the destination, and confirm that the strike survives without mangling the surrounding content. If the meaning matters more than the line, prefer a semantic format over a generator that only approximates the effect.
The Markdown editor tool is a sensible place to validate how your double tildes render before you move text into another system.
Accessibility and Semantic Considerations for Strikethrough Text
A visible line through text is useful for sighted readers, but it can be meaningless if someone is using a screen reader or another assistive tool. Accessibility guidance recommends adding context with visually hidden text, aria-label, or aria-describedby, and using aria-hidden="true" only when the strike is decorative.[^8] The line alone is not enough when the meaning matters.
What screen readers and downstream tools need
CSS line-through styling does not reliably announce deletion, correction, or obsolescence on its own.[^4][^8] That's why semantic tags matter. If the text was removed, del communicates that intent. If it's just outdated, s says the content is no longer relevant rather than removed.[^3]
That difference becomes critical in collaborative tools, publishing systems, and review workflows. A reviewer can see the line and infer the change, but an assistive technology user may only hear the underlying words unless you provide explicit context. That's where accessible labeling earns its keep.
Keep meaning attached to the markup
If the strike is only decoration, don't force extra announcements into the experience. Mark it hidden from assistive tech and keep the message simple. If the strike carries editorial meaning, pair it with text that says what happened, so the reader doesn't have to infer the state.
Practical rule: if someone needs to know why the text is crossed out, say it in text, not just in style.
This matters in resume workflows too, where a visual strike can easily become confusing if the document is exported, converted, or read aloud. The resume formatting guide is useful if you're comparing how different document formats preserve meaning during export and editing.
Troubleshooting Common Strikethrough Problems
Most strike through text problems come from the same pattern, the style exists in one system but not the next. The fix usually isn't to click harder, it's to find where the formatting metadata got lost. Once you know the symptom, the root cause is usually obvious.
Common failures and quick fixes
- The strike disappears after paste. The receiving app likely stripped rich text metadata. Paste into an editor that supports formatting, or use semantic HTML / Markdown when the destination supports it.
- Markdown shows literal tildes. The field doesn't parse Markdown. Switch to a supported editor or use the app's native formatting controls.
- CSS line-through doesn't show in an email client. The client is overriding or dropping the style. Use a more conservative HTML structure, and test the exact client before sending.
- Unicode strike text looks crooked. The font or script doesn't handle the combining characters cleanly. Use native formatting instead of generator output.
- Strikethrough appears on cells you didn't format. In spreadsheet tools, a hidden rule or formatting state is usually the cause, not random behavior.
The underlying issue is often semantic loss. Styling alone does not preserve deletion, revision, or status changes across systems.[^4] If the strike needs to survive export, copy, or paste, keep the original markup/format metadata instead of flattening it into plain text.[^4]
What usually fixes the issue fastest
In desktop apps, reapply the format in the source editor and copy again. In web publishing, choose semantic tags instead of pure styling when the content meaning matters. In message-based workflows, test the exact app combination before you depend on the effect.
If the same file or message is moving through several tools, stop treating strike through text as a visual garnish. Treat it as data that needs to survive transport.
Choosing the Right Strikethrough Method and Tools for Your Workflow
A practical workflow starts with where the text is going, whether the strike carries meaning or just marks a visual edit, and how often the content has to survive copy-paste across apps. If the text is headed for publishing or structured content, semantic HTML keeps the meaning intact better than a purely visual effect. If you are working in docs or comments, Markdown or native editor shortcuts are usually enough. For quick one-off messages, a temporary generator can work, but only after you test the paste path in the destination app.
Match the method to the job
Use semantic HTML when the crossed-out text is part of published content and the meaning needs to survive beyond the browser. Use Markdown when you are writing in docs, issue trackers, or tools that already understand ~~text~~. Use native app shortcuts when you are inside Word, Google Docs, or Excel and speed matters more than portability. Use Unicode or generator output only when the destination cannot handle richer formatting and you accept the trade-offs that come with it.
A privacy-first browser tool helps when you are formatting sensitive content and want the work to stay local. Digital ToolPad fits that workflow well, with client-side tools that avoid the usual server-side friction. For teams handling private drafts, client notes, or internal documentation, that local-first setup can save time and reduce data-handling headaches.
If you format strike through text across documents, web content, and messages, Digital ToolPad is a useful browser-based option for testing formatting on your own device and keeping the workflow simple. It can help you move text cleanly between tools and avoid the guesswork that comes from copying styled text into the wrong app.