Strikethrough Keyboard Shortcut Guide
Learn how to use the strikethrough keyboard shortcut across editors, customize it, and apply fast, accessible formatting with practical, cross‑platform steps and examples.
Definition: A strikethrough keyboard shortcut toggles cross‑out formatting on selected text, enabling quick visual rejection or completion marks. Across major editors, the most common cross‑platform pairing is Ctrl+Shift+X on Windows and Cmd+Shift+X on macOS. This guide explains where it works, how to customize it, and best practices for consistent, accessible typography.
Introduction and Context
According to Shortcuts Lib, the strikethrough keyboard shortcut is a small but powerful tool for fast editing, review workflows, and collaborative drafting. In plain text, you can signal intent by wrapping text in Markdown as ~~this~~, but the real speed comes when editors provide a dedicated shortcut. This article explores where the shortcut works, how to test it in common apps, and how to tailor it to your work style for consistent, accessible formatting across projects.
Cross‑Platform Shortcuts: Windows vs macOS
The most reliable, cross‑editor pattern is to use a single, portable shortcut that many apps recognize. In widely used markdown environments and browser editors that implement Google Docs‑style shortcuts, you’ll often see Windows: Ctrl+Shift+X and macOS: Cmd+Shift+X. You can verify this in the editor’s help or shortcut settings. When you enable a Markdown mode or a word processor with rich text, the same mapping appears in many popular configurations, helping your workflow stay fluid across machines and teams.
{
"editor": {
"name": "Google Docs / Markdown editors",
"windows": "Ctrl+Shift+X",
"macos": "Cmd+Shift+X"
}
}Practical Editor Examples: Real‑world Usage
Here are concrete examples across common environments. In a Markdown editor, you can wrap text with the syntax that survives export, and the shortcut simply toggles or highlights that syntax when supported by the app.
- Complete tasks
- Review items ~~Done~~In a Google Docs or Word‑style rich text editor, the shortcut instantly toggles the strikethrough style on the selected text. The following JSON demonstrates how a Markdown extension might bind a key to a toggle command in VS Code or a similar editor:
{
"key": "Ctrl+Shift+X",
"command": "markdown.extension.toggleStrikethrough",
"when": "editorTextFocus && editorLangId == 'markdown'"
}If your editor does not include a native toggle, you can add a macro or extension to provide the same functionality. The snippet below illustrates a YAML‑style configuration for a hypothetical Markdown editor:
editor:
plugin: markdown-strikethrough
shortcut: "Ctrl+Shift+X"Customization, Remapping, and Alternatives
Not every app ships with a built‑in strikethrough toggle, so many power users remap or extend shortcuts. OS‑level remapping or a small scripting tool can offer a universal alias that works everywhere. The following AutoHotkey example demonstrates a Windows remap to insert a strikethrough wrapper in Markdown for quick editing:
; AutoHotkey remap: Ctrl+Shift+X inserts Markdown strikethrough syntax around selection
^+x::
Clip := GetClipboard()
Send, ~~{Clipboard}~~
Clipboard := Clip
returnOn macOS, you can use a similar approach with the built‑in Shortcuts app or a third‑party utility. The goal is to create a predictable, cross‑app shortcut so you spend less time hunting for the right command and more time writing.
Accessibility and Best Practices
When applying strikethrough, consider how screen readers interpret the content. In Markdown export, the semantic meaning is preserved in the syntax, but in rich text, ensure the escaping behavior is predictable across platforms. If you rely on strikethrough for task lists or reviews, communicate clearly with collaborators about the visual meaning (completed vs. canceled items). Keep contrast in mind so crossed‑out text remains legible for all readers. A quick preview check in your editor’s accessibility mode is worth the extra step.
Steps
Estimated time: 15-25 minutes
- 1
Choose your primary editor
Pick an editor you use daily that supports strikethrough (Markdown editors, Google Docs, Word). Verify it accepts either a native toggle or a predictable syntax.
Tip: Start with the editor you already know; consistency beats perfection. - 2
Confirm the built‑in shortcut
Check the editor’s help or shortcuts panel to confirm the exact keys for strikethrough. Note any differences between Windows and macOS.
Tip: Document the mapping for your team to avoid confusion. - 3
Test in a sample document
Open a sample note and apply the shortcut to a few lines. Observe whether the text is crossed out or a syntax is inserted.
Tip: Test across different content types (lists, headings, links). - 4
Add a fallback method
If your editor lacks a native shortcut, implement a small macro or a system shortcut remapping tool.
Tip: Keep a quick reference sheet for your favorite editors. - 5
Audit accessibility
Preview the document for screen readers and ensure the meaning of crossed out text is clear and accessible.
Tip: Prefer semantic markers (like completed task states) over purely decorative styling.
Prerequisites
Required
- A modern editor that supports strikethrough (Windows/macOS)Required
- If you work with Markdown, enable Markdown syntax support or an appropriate extensionRequired
- Familiarity with platform shortcuts (Windows and macOS)Required
Optional
- Optional: OS or editor automation tools (AutoHotkey on Windows, Keyboard Maestro on macOS)Optional
Keyboard Shortcuts
| Action | Shortcut |
|---|---|
| Toggle strikethrough in Google Docs / Markdown editorsCommon in Docs-like editors and many Markdown environments | Ctrl+⇧+X |
| Wrap selected text with Markdown strikethrough syntaxIf the editor supports native toggling, otherwise use a macro | Ctrl+⇧+X |
| Remap a global shortcut to strikethroughUseful when your app lacks a built‑in toggle | See AutoHotkey example |
Questions & Answers
Is there a universal strikethrough shortcut that works in all editors?
No universal shortcut exists for every editor. Shortcuts vary by application and platform. In many Markdown editors and Google Docs‑like environments, Ctrl+Shift+X on Windows and Cmd+Shift+X on macOS are common defaults to toggle strikethrough.
There isn’t a single universal shortcut; it depends on the editor you use. Look up the app’s shortcuts or enable a Markdown mode to get consistent behavior across tools.
How do I apply strikethrough in Markdown?
In Markdown, you apply strikethrough by wrapping text with two tildes on each side, for example, ~~struck through~~. This rendering works in most Markdown processors and export targets, making it portable across platforms.
In Markdown, you wrap text with two tildes on each side to strike it through.
Can I customize or remap the shortcut?
Yes. If your editor lacks a native option, use a macro or a remapping tool (AutoHotkey on Windows, Keyboard Maestro on macOS) to assign a consistent shortcut that triggers the strikethrough command or inserts the Markdown syntax.
You can remap the shortcut with a macro tool if the editor doesn’t support it natively.
Which editors typically support strikethrough well?
Editors with solid strikethrough support include Google Docs, Microsoft Word, and many Markdown editors like Obsidian or Typora. Markdown preview modes also reflect the syntax, making it easy to export consistent documents.
Google Docs, Word, and most Markdown editors usually support strikethrough.
What are best practices for accessibility?
Use strikethrough to indicate completed tasks or deprecated items, not as a decorative effect. Ensure there is sufficient contrast and provide textual hints or state indicators for screen readers.
Use it meaningfully with attention to contrast and screen reader context.
What should I do if the shortcut conflicts with another app?
Change the shortcut in the conflicting app or disable the conflicting global hotkey, then map a universal remap to preserve your workflow.
If a conflict occurs, remap or disable one of the hotkeys to avoid clashes.
Main Points
- Learn the default cross‑platform shortcut for strikethrough
- Verify editor support and syntax across apps
- Consider customization when native shortcuts are missing
- Use strikethrough consistently for accessibility and clarity