WordPress And The Comment Markdown Question

WordPress comments by default support limited HTML. Markdown support can be added via plugins, letting commenters use lightweight formatting.

The trade-offs determine whether Markdown support fits the site.

What Markdown adds

Bold and italic via **bold** and *italic* syntax.

Code blocks via backticks. Useful for technical sites where commenters share code.

Links via [text](url) syntax. Cleaner than full HTML.

Lists via dashes or numbers.

Block quotes via > prefix.

When Markdown helps

Technical sites where commenters discuss code, configurations, technical concepts. The code block formatting matters.

Sites where comments are substantive and benefit from formatting. Long thoughtful comments read better with structure.

Audiences familiar with Markdown. GitHub users, Reddit users, technical readers.

When Markdown doesn't help

Casual comment audiences. Many commenters won't know Markdown; the syntax confuses them.

Sites where comments are short reactions. Formatting matters less for one-sentence comments.

Audiences that don't include technical users.

The plugins

JP Markdown (from Jetpack): adds Markdown to comments and posts.

Dedicated comment Markdown plugins: simpler scope.

WP Markdown Editor: more comprehensive Markdown across WordPress.

The discoverability

If Markdown is supported, tell commenters. A brief hint near the comment form ("Formatting: bold, italic, code") helps commenters who know Markdown discover the support.

Without discovery, the feature gets used by the small fraction who already try.

The honest framing

Markdown comment support is a small detail that helps the right audiences. For general audiences, the default WordPress comment behavior is sufficient.

For technical audiences, adding Markdown improves the comment section's usefulness.