⌘ K
wraps lines or words in ~~strikethrough~~

Generate ~~strikethrough~~ Markdown

Wrap text in GFM strikethrough markers — per line for whole sentences or per word for granular crossing-out.

Strikethrough
Input
113 B
5 lines
Output
133 B
5 lines
Status
ready
live
Ratio
1.18×
out/in
input · text
output · struck
~~This text~~
~~Will be struck out~~
~~Old paragraph that's now obsolete~~
~~Deprecated function reference~~
~~Removed feature note~~
Quick Start

How to add Markdown strikethrough

Wraps text in ~~ … ~~ per line or per word. Renders as crossed-out text in GFM and most modern Markdown flavors.

  1. 01

    Paste text

    Lines of text you want to mark as obsolete.

    Parsing runs through marked with GFM extensions enabled — tables, task lists, strikethrough, and fenced code blocks all match GitHub’s rendering.

    inputGFMmarkedCommonMarklive
    input · markdownraw · GFM
    Old text
    loaded · GFMGFM · ready
  2. 02

    Pick scope

    Per-line for sentences, per-word for finer control.

    Soft-break behaviour is configurable: by default a single newline becomes a space (CommonMark), toggle on for chat-style <br> insertion.

    scopesoft-breaksoptionsconfiglive
    mode · optionsline/word · live
    ~~~~
    options applied · livelive
  3. 03

    Live wrap

    Each unit gets ~~ markers around it.

    The preview is scoped under a .mde class so its CSS doesn’t bleed into the rest of the page. Output HTML is whitespace-controlled for clean diffs.

    wrappreviewscoped CSSrenderstable
    out · renderedgfm · ready
    ~~Old text~~
    rendered · liverendered
  4. 04

    Paste into Markdown

    Most renderers (GitHub, GitLab) honor GFM strikethrough.

    Export covers both raw Markdown and rendered HTML; downloads stream as text/markdown or text/html via Blob + object URL.

    exportclipboard.md.htmlblob
    ✓ · exportedgfm · done
    ✓ rendered
    shipped · ready to shipsuccess
Pro tips

Author Markdown that renders everywhere

GFM is the safe default

GitHub-Flavored Markdown is the de-facto baseline (tables, task lists, strikethrough). CommonMark is stricter but ubiquitous as a fallback.

Soft-break behaviour varies

A single newline is a space in CommonMark, a <br> in GFM. Toggle soft breaks when source matters.

Escape inside code fences

Backticks inside fenced blocks need a longer fence — three becomes four. Use ~~~ if your content has many backticks.

Anchors are slugified

GitHub lowercases, strips punctuation, and joins with hyphens. Duplicate headings get -1, -2 suffixes.

Tables need a header row

The dash row sets alignment (:---, :-:, ---:). Use Table Aligner for diff-friendly columns.

Front matter is YAML

Triple-dash blocks at the top of files are parsed by static-site generators. Use the Front-Matter Validator to catch syntax errors.

Related toolsEscapeFormatterCaseCommentsEditorCheatsheet
Use Cases

When to use strikethrough

Visually mark text as obsolete without deleting it.

Deprecation notes

Mark deprecated API references in changelogs. Render path uses marked with GFM extensions enabled (tables, task lists, strikethrough, autolinks), so what you preview matches what GitHub publishes bit-for-bit. Soft-break behaviour is configurable for chat-style vs prose Markdown.

GFM-compliant

Pricing updates

Show old prices alongside new ones in marketing. Pairs cleanly with the Markdown Cheatsheet for syntax you can't quite remember — callout blocks, footnotes, definition lists. Output stays diff-friendly so style-only changes don't drown out real edits in PRs.

GitHub-perfect

TODO lists

Strike done items in informal task lists without checkboxes. Cross-platform safe: anchors, code fences, and tables behave identically on GitHub, GitLab, Bitbucket, and Gitea. Heading-anchor slugs follow GitHub's lowercase-and-hyphenate rules so deep links survive a docs migration.

diff-friendly

Edit suggestions

Propose deletions visibly during review. No server roundtrip — perfect for proprietary content you can't paste into a public tool. The full marked + GFM bundle ships with the page, so it works offline once loaded.

render-stable

Sales / events

Cross out sold-out items or past dates in event lists. Front matter (YAML / TOML / JSON) passes through unchanged so static-site pipelines (Jekyll, Hugo, Astro, Eleventy) read it correctly. Pair with the Front-Matter Validator to catch syntax errors before deploy.

cross-platform

Spec drafts

Show removed requirements without losing context. Output is reproducible: identical input always produces identical Markdown, so doc-generation scripts can rely on it for snapshot tests and embedded into release workflows.

SEO-friendly
FAQ

Frequently asked questions

GFM. ~~…~~ is a GitHub-Flavored Markdown extension; CommonMark proper doesn't have strikethrough.
Yes — anywhere GitHub renders Markdown (READMEs, comments, wikis).
Slack uses ~text~ (single tilde) and Discord uses ~~text~~. Use the MD to Slack tool for Slack output.
No — most parsers don't nest. One layer per region is safest.
No. The wrap runs locally in your browser.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!