Markdown Code Blocks and Syntax Highlighting

Example

Run `npm run build` before you deploy.

```python
def greet(name):
    return f"Hello, {name}!"
```

```bash
git commit -m "feat: add editor guides"
```

Run npm run build before you deploy.  (npm run build shown in a monospace pill)

  def greet(name):                     (Python, keywords colored)
      return f"Hello, {name}!"

  git commit -m "feat: add editor guides"   (Bash, colored)

Common mistakes

• The language tag goes on the same line as the opening backticks, with no space: ```js not ``` js.
• Use triple backticks, not indentation, so the language highlighting turns on.
• To show literal backticks as inline code, wrap them in a longer run of backticks, such as double backticks.

FAQ

How do I turn on syntax highlighting in Markdown?

Add the language name right after the opening triple backticks, for example ```python or ```js. Renderers like GitHub use that tag to color the code.

What is the difference between inline code and a code block?

Inline code uses single backticks around a short snippet inside a sentence. A code block uses triple backticks on their own lines and can hold many lines with highlighting.

Which languages are supported for highlighting?

Common tags include js, ts, python, bash, json, yaml, html, css, sql, and many more. If a language is unknown, the block still renders as plain monospaced code.

Related Markdown editor guides