How to Do Strikethrough: The Hidden Typing Trick Everyone Overlooks

The strikethrough—a simple line cutting through text—carries more weight than most realize. It’s not just a visual flourish; it’s a silent signal in emails, documents, and code that something is outdated, irrelevant, or intentionally crossed out. Yet despite its ubiquity, many users stumble when asked how to do strikethrough properly, especially across different devices and applications. The irony? A feature so fundamental often demands more effort to implement than its simpler counterparts like bold or italics.
Most people assume strikethrough is limited to word processors, but its applications stretch far beyond. Developers use it in code comments, designers embed it in UI mockups, and even social media platforms rely on it to mark deleted or edited content. The problem? The method varies wildly—keyboard shortcuts differ by OS, HTML requires specific tags, and mobile apps hide the option behind obscure menus. Without knowing the right approach, users either resort to manual drawing (a hacky workaround) or miss the feature entirely.
The solution lies in understanding the three core pillars of strikethrough: native application shortcuts, markup languages (HTML/CSS), and platform-specific hacks. Each has its own syntax, quirks, and hidden efficiencies. Whether you’re drafting a legal document, annotating code, or tweaking a blog post, mastering how to do strikethrough across these systems will save time and elevate clarity. The following breakdown covers every scenario—from the simplest keystroke to the most technical implementation—so you never have to guess again.
![]()
The Complete Overview of How to Do Strikethrough
Strikethrough isn’t just a formatting tool; it’s a semantic indicator. In professional writing, it signals corrections, revisions, or deprecated information. In programming, it marks commented-out code. Even in casual messaging, it can convey sarcasm or playful emphasis. The challenge is that its accessibility depends entirely on context. A writer in Microsoft Word might press `Ctrl+D` (Windows) or `Cmd+Shift+X` (Mac) without hesitation, while a developer editing HTML must manually input `The most efficient way to apply strikethrough hinges on recognizing the tool you’re using. Text editors like Google Docs or Notion offer one-click buttons in their toolbar, while coding environments require syntax awareness. Mobile apps, meanwhile, often bury the option under a "more formatting" menu. Even within desktop applications, the shortcuts can shift: `Ctrl+5` in LibreOffice but `Alt+Shift+5` in OpenOffice. The key is to categorize your workflow—whether it’s documentation, development, or communication—and then apply the corresponding method. Below, we dissect the evolution of strikethrough to understand why these inconsistencies exist.
Historical Background and Evolution
The strikethrough’s origins trace back to manual typesetting, where printers would physically draw lines through errors or outdated text. As digital typography emerged, the feature persisted as a way to replicate this physical action virtually. Early word processors like WordStar (1978) included strikethrough as a basic formatting option, but its adoption was slow due to limited hardware capabilities. The real turning point came with the rise of HTML in the 1990s, where the `Today, strikethrough is governed by two competing standards: semantic markup (used in HTML for logical meaning, like `` for deleted content) and presentational markup (like `` for purely visual strikethrough). The confusion stems from HTML5’s decision to retain `` for styling while discouraging its use for semantic purposes. Meanwhile, CSS introduced `text-decoration: line-through`, offering even more flexibility. This fragmentation explains why some platforms default to one method over another—developers prioritize semantics, while designers lean toward visual consistency. The result? A feature that’s both universally recognized and frustratingly inconsistent.
Core Mechanisms: How It Works
At its core, strikethrough is rendered by a combination of text-decoration properties and logical markup. In CSS, the `text-decoration: line-through` rule draws a line through text, while in HTML, the `` tag indicates deleted content (often styled with strikethrough by default). The difference is critical: `` conveys meaning (e.g., "this price is no longer valid"), whereas `` or CSS alone is purely aesthetic. This distinction matters in accessibility tools, where screen readers interpret `` as a semantic cue but ignore visual-only strikethrough.
Table of Contents
- The Complete Overview of How to Do Strikethrough
- Historical Background and Evolution
- Core Mechanisms: How It Works
- Key Benefits and Crucial Impact
- Major Advantages
- Comparative Analysis
- Future Trends and Innovations
- Conclusion
- Comprehensive FAQs
- Q: Why doesn’t strikethrough work in some mobile apps?
- Q: Can I use strikethrough in email signatures?
- Q: How do I strikethrough text in Markdown?
- Q: Is there a way to strikethrough text in Excel or Google Sheets?
- Q: Why does strikethrough look different in web browsers?
- Q: Can I strikethrough text in Slack or Discord?
- Q: How do I strikethrough text in LaTeX?
- Q: Is strikethrough accessible for screen readers?
Platforms like Microsoft Word and Google Docs abstract these mechanics into toolbar buttons or shortcuts, masking the underlying complexity. For example, Word’s `Ctrl+D` shortcut triggers a hidden command that applies a predefined strikethrough style, while Google Docs uses a similar approach but with `Alt+Shift+5` (Windows) or `Option+Cmd+5` (Mac). The inconsistency arises because each application defines its own shortcut hierarchy, often prioritizing frequently used functions. Understanding these mechanics—whether through markup or shortcuts—allows users to bypass limitations, such as when strikethrough isn’t available in a mobile app’s basic menu.
Key Benefits and Crucial Impact
Strikethrough’s power lies in its dual role as both a visual cue and a semantic marker. In collaborative documents, it clarifies revisions without cluttering comments, while in code, it visually separates active and deprecated logic. Even in social media, platforms like Twitter use strikethrough to indicate edited tweets, adding transparency to public discourse. The feature’s versatility extends to UI/UX design, where it can denote disabled options or temporary states. Yet its impact isn’t just functional—it’s psychological. Studies in readability show that strikethrough text is processed faster than underlined or bolded text, making it ideal for highlighting changes or errors.The psychological effect is particularly notable in legal and academic writing, where strikethrough can signal corrections without altering the original text’s integrity. For example, a lawyer might strikethrough a clause in a draft while keeping the rest intact for reference. Similarly, in software development, strikethrough in commit messages or code comments helps teams track deprecated functions. The feature’s ability to preserve context while indicating modification makes it indispensable in fields where precision matters.
"Strikethrough is the digital equivalent of a red pen—it doesn’t erase, it annotates. The difference is that in the digital age, it can be applied, undone, and version-controlled with a single keystroke." — UX Writer at a Tech Startup
Major Advantages
- Clarity in Revisions: Strikethrough visually separates old and new content, reducing ambiguity in edited documents. Unlike deletion, it retains the original text for reference.
- Code Commenting: Developers use strikethrough to mark unused code blocks or experimental logic without removing them, preserving history in version control.
- Accessibility Compliance: Semantic HTML (`
`) ensures screen readers announce deleted content, improving inclusivity for visually impaired users. - Cross-Platform Consistency: CSS’s `text-decoration: line-through` works universally, making it reliable for web design and email templates.
- Psychological Emphasis: In casual writing, strikethrough can imply sarcasm, humor, or playful correction, adding nuance to digital communication.

Comparative Analysis
| Method | Use Case |
|---|---|
| Keyboard Shortcuts (e.g., `Ctrl+D` in Word, `Cmd+Shift+X` in Pages) | Quick formatting in word processors; limited to desktop apps. |
| HTML/CSS (e.g., ` |
Web development, emails, and custom styling; requires syntax knowledge. |
| Markdown (e.g., `~~text~~`) | Static site generators, README files, and lightweight documentation. |
| Mobile Apps (e.g., long-press menu in Gmail, "More" button in Notes) | On-the-go editing; often less intuitive than desktop counterparts. |
Future Trends and Innovations
As digital communication evolves, strikethrough’s role is expanding beyond static text. In collaborative tools like Notion or Figma, strikethrough is increasingly tied to version history, allowing users to revert changes while keeping a visual trail. Meanwhile, AI-driven editing tools (e.g., Grammarly, Hemingway) are beginning to auto-apply strikethrough to suggested edits, blurring the line between manual and automated formatting. Another trend is the rise of "dynamic strikethrough" in real-time editing, where lines appear and disappear as content is updated—useful in live documentation or agile workflows.The most significant innovation may come from voice-to-text integration. Imagine dictating a strikethrough command ("strike through the next sentence") and having the system automatically apply the formatting. While still experimental, this aligns with the trend of voice-controlled productivity tools. For developers, the future lies in CSS variables for strikethrough styles, enabling consistent theming across projects. As these trends mature, how to do strikethrough will shift from a manual task to an intuitive, context-aware feature—one that adapts to the user’s intent rather than requiring explicit input.

Conclusion
Strikethrough is a deceptively simple tool with profound implications. Its ability to annotate without erasing makes it a cornerstone of digital communication, yet its implementation varies so widely that even power users often overlook its full potential. The solution? Treat it as a multi-platform skill: know the shortcuts for your word processor, the markup for your code editor, and the workarounds for mobile apps. The more you understand how to do strikethrough in each context, the more efficiently you’ll communicate—whether you’re drafting a contract, debugging a script, or simply crossing out a typo in an email.The next time you wonder how to do strikethrough, pause and consider the tool at hand. Is it a keyboard? A browser? A mobile app? The answer dictates the method, and the method dictates the impact. By mastering these variations, you’re not just formatting text—you’re refining clarity, preserving context, and future-proofing your workflow.
Comprehensive FAQs
Q: Why doesn’t strikethrough work in some mobile apps?
The issue stems from app design priorities. Many mobile apps prioritize simplicity, hiding advanced formatting like strikethrough behind a "More" or "Format" button. For example, Gmail’s mobile app requires a long-press to access strikethrough, while Notes apps may only offer it in the text menu. If strikethrough is missing entirely, check for third-party keyboard apps (e.g., SwiftKey or Gboard) that support custom formatting.
Q: Can I use strikethrough in email signatures?
Yes, but the method depends on your email client. In Gmail, compose a new email, highlight text, and press `Ctrl+Shift+5` (Windows) or `Cmd+Option+5` (Mac). For Outlook, use `Ctrl+5` (Windows) or `Cmd+Shift+X` (Mac). If using HTML email templates, embed `text` or CSS (`text`). Note that some email clients (like Outlook) may render strikethrough differently based on recipient settings.
Q: How do I strikethrough text in Markdown?
Markdown uses double tildes (`~~`) to create strikethrough. For example, `~~this text~~` will render as this text. This works in platforms like GitHub, Reddit, and static site generators (e.g., Jekyll). Some flavors of Markdown (like CommonMark) also support `` tags, but `~~~~` is the most widely compatible. Always test in your target environment, as some Markdown processors may require extensions.
Q: Is there a way to strikethrough text in Excel or Google Sheets?
Neither Excel nor Google Sheets natively support strikethrough for cell text. However, you can simulate it using:
- Excel: Insert a custom border above and below the text (Home > Borders > Custom Border).
- Google Sheets: Use conditional formatting to add a colored border that mimics strikethrough when cells meet a criteria (e.g., "contains error").
Q: Why does strikethrough look different in web browsers?
Browsers apply default CSS styles to strikethrough, which can vary based on the user’s OS or browser settings. For example, Chrome may use a thin gray line, while Firefox could use a thicker black line. To standardize it, override the default with custom CSS:
s {
text-decoration: line-through;
text-decoration-color: #ff0000; / Custom color /
text-decoration-thickness: 2px; / Line thickness /
}
This ensures consistency across devices. For semantic strikethrough (`Q: Can I strikethrough text in Slack or Discord?
Neither platform supports native strikethrough, but you can use Markdown formatting with a workaround:
- Slack: Use `~~text~~` in a message or channel—Slack will render it as strikethrough if Markdown is enabled (Settings > Advanced > "Enable Markdown").
- Discord: Discord’s Markdown also supports `~~text~~`, but it only works in servers where Markdown is enabled (Server Settings > Text in Chat > "Enable Markdown").
Q: How do I strikethrough text in LaTeX?
LaTeX uses the `\sout` command from the `ulem` package. Add this to your preamble:
\usepackage{ulem}
\sout{This text will be strikethrough}
For more control, use `\uline` (underlined) or `\uwave` (wavy underline) from the same package. Note that some LaTeX compilers may require additional packages like `soul` for advanced strikethrough styles.
Q: Is strikethrough accessible for screen readers?
Semantic strikethrough (``) is fully accessible, as screen readers announce it as "deleted text." Visual-only strikethrough (`` or CSS) is ignored by assistive technologies. To ensure accessibility:
Test with screen readers like NVDA or VoiceOver to confirm compatibility.` for content that’s logically removed (e.g., outdated prices).old text`.
Leave a Comment
Comments are moderated before appearing. The data you submit is processed according to the Privacy Policy of Sac.