Formatting text with Markdown Follow

all plans


Markdown is a simple markup language you can use to easily add formatting, links, and images to plain text. Markdown is available in the following places:

  • Ticket comments (from the agent interface)
  • Macros
  • Agent signatures

For agents to use Markdown, an administrator has to enable it in your account. For more information, see Enabling formatting options for agents.

Note: Markdown is not available in email.

Topics covered in this article:

Adding Markdown to text

The following table shows examples of how you can use Markdown to add common formatting.

Note: These examples demonstrate one way you can add certain formatting. There might also be additional ways you can achieve the same formatting. There are also many more formatting options you can add with Markdown. For more options and information, see the complete Markdown syntax documentation.

You can also watch this short video.

Using Markdown in a Ticket (01:41)
Table 1. Examples of Markdown syntax
Formatting Entered text Published text
Bold This is how you **bold** text.
Italics This is how you *italicize* text.
Bulleted lists * Bullet one (don't forget a space after the asterisk)

* Bullet two

Numbered lists 1. Step one

2. Step two

Note: Do not use a hashtag (#) when creating numbered lists in Markdown, as the symbol is used for other formatting.
Nested lists * This is the first level of this list.

* To make a second level, add two spaces before the asterisk or number.

Note: You can add things like images, quote blocks, or links to a nested list in addition to just text.
Headings # Heading level one (with a space after the #)

## Heading level two

### Heading level three

You can add up to six heading levels.

Block quotes

> Block quotes have to start and end with a blank line

> And each line of the quote starts with a right angle bracket and a space


Inline code Here is some `inline code.`
Code blocks ```

This is a code block.


Note: Creating a blank line and then indenting the next line or lines with four spaces creates a code block too.
Images ![Optional alternative text if image doesn't load](

Community tip! Evan shares a simple tip in our forums for embedding an image that's not hosted.

Links [Link display text](
Images that are also links [![alt text](imageurl)](linkurl)
Horizontal rule line



Note: You must type a line break before and after the hyphens.


Line break

Line 1



Line 2



Note: You must type two line breaks before each  .
Line 1


Line 2

Previewing Markdown in ticket comments

When you use Markdown in a ticket comment, you can preview your formatting before submitting the comment. You enter your comment with Markdown formatting, like in the example below.

Then, click Preview to view how your ticket comment will look when posted.

Have more questions? Submit a request


  • 0

    Hi, we are preparing a ticket form with dynamic content to duplicate it in multiple help centers. Could a link be clickable on the "Description (optional)" of a ticket field? We put a dynamic content in it with the classic link but it doesnt seem to work...

  • 0

    Like Andrea - I believe tables in markdown would be a valuable addition! I'm off to find that feature request… +1

  • 0


    Markdown looks like it is going out of fashion at Zendesk. Check out this section:

    This will allow agents to paste tables into tickets and allow text formatting without preview or learning Markdown.

  • 0


    Markdown is not supported in Triggers and Automations, but you can use HTML.

    Let us know if anything else comes up.

  • 0

    Hi Graeme,

    I saw that shortly after posting the above comment :) Looking forward to it rolling out!

  • 0

    It would be great to have support for markdown tables. They are very useful

  • 0

    Hi Tomás,

    You might be interested a beta we are currently running that adds a WYSIWYG editor to tickets -- this editor will support tables. You can find out more about it here:

  • 0

    Sorry Laura but we are not very interested in that feature. We use markdown because of the speed and we want to continue using it. I think that the new Rich Comments feature you mentioned could be a threat to markdown (developers start focusing on that feature and markdown support is left behind or even dropped), so I'm not very excited about it

  • 0

    While I would not be as emphatic as Tomás, I agree that Markdown does have some real efficiency and maintenance advantages over WYSIWYG HTML. Also, I'd be very reluctant to switch to a WYSIWYG editor as ill-behaved as the current HC HTML editor (though it is an improvement over the execrable Forum editor which preceded it, so the trajectory is good!)

  • 0

    Hey guys!

    I did some checking on this and here's what I was able to find out: If you add Markdown to the ticket on it's own (ie: through cut/paste, text expander, etc) it will not render properly in the WYSIWYG editor. However, if you add the Markdown to your ticket using a Macro, it will render correctly - it gets converted to HTML before it's applied to the ticket. So Markdown will be supported in that context. I'm also a big fan of Markdown over WYSIWYG, so I understand your concerns. Hopefully that helps to ease your minds a little bit!

    Please let me know if you have any other questions!

  • 0

    I have a very real need to use Outlook as a mail client to send support email via ZenDesk due to my accessibly software to support my dyslexia, so I do not want to use the Web Interface where possible. I would dearly love to see formatting preserved from Outlook (and other email clients) to the end customer, and better integration with these email clients.

  • 0

    How can I use markup to display the first and last elements of a nested dropdown selection but without the :: in there? I have a custom field that I pull through to certain macros- this dropdown field contains information nested in the following format-Company name::Site. I would like the macro to pull from this field and display the following format in text- Company Name Site (without the ::) but I can't seem to create this (I have it set up to display the last selection from a custom dropdown field in other areas of the macro but I can't seem to add both the first and last in that format). Can someone help me please? Many thanks.

  • 0

    @Ellie Elstob-Wardle

    You cannot remove the :: characters using mark down discussed here. But you can using Liquid Markup (confusing isn't it?) Liquid is discussed here:

    In your macro, you will already have discovered how to find the custom field value:


    Where 24724112 is the custom field ID found on the edit custom field screen.

    Remove the offending :: characters and replace with a single space with Liquid as follows:

    {{ticket.ticket_field_option_title_24724112 | replace:'::',' '}}
  • 0


    Thanks- that's great! Ah yes, still confusing markdown and Liquid markup obviously. This was really helpful, thank you.

  • 0
    anyone able to figure out how to resize the image url? I can link the image and its URL but its too huge so i wonder if there is a way to resize it
  • 0
    Hi Joel! When you're adding the URL to your markdown the length of the URL isn't really going to matter because the image itself will render in the ticket. However, if you still want to shorten your URLs, I'd recommend checking out some third party URL shorteners.
  • 0

    Hi, Can you change the size of text using Markdown? Thanks!

  • 0

    Hi James,

    You can use the header formatting options (on both Markdown and the rich text editor in tickets), but there's no way to change the size of the normal paragraph font, no.


  • 0

    @Erin, @Jessie:

    Triple-quoted code blocks on the website have stopped wrapping again (they truncate). They still seem to be wrapping ok in notification emails.

    If you need to see an example, please feel free to look at our ticket 62399.

  • 0

    Hey Jonathan, I'm going to open a Support ticket on your behalf so we can dig a little deeper on this one. We'll follow up there shortly!

  • 0

    Thanks, Madison. For the record, my bug report was rejected "Working as Designed". I've opened a feedback thread here:

    "Code blocks no longer wrap online -- good or bad?"

    and would welcome input from other users.

  • 0

    I'm setting up some macros and the first line is:

    # Product Repair


    The problem I'm having is that it is putting a line space above the heading line.  Is there a way to not have that line...?

  • 0

    Hey Brad!

    Can you post a screenshot of what you're putting in the macro, and how it looks when applied? I'm not sure I understand what you're describing.

  • 0

    Hi Jessie,

    Just noticed what must be a very new bug in markdown rendering. After a bulleted or numbered indented list, the expected blank line is omitted before the following paragraph. My ugly short-term workaround is to insert a paragraph containing only a single period character. Thanks!

  • 0

    Thanks for the heads up @Jonathan. We're looking into it. Looks like the margin was removed there by another change that over applied. 

  • 0

    Ditto to what Jonathan said. Hope this gets fixed soon.

  • 0

    FTR, ZenDesk devs (via support) suggested a better workaround: beginning the following paragraph wtih a line containing ` `. I had forgotten that HTML special chars are  usable in Markdown, so that works great.

  • 0

    Thanks Jonathan!

  • 0

    Thanks for coming back and sharing that, Jonathan!

  • 0

    @Jonathan @Patrisha we just released a fix for this issue with ol/ul margins missing in markdown.

Please sign in to leave a comment.

Powered by Zendesk