+ Add Question

Markdown Support?

I would like to know if Todoist currently supports or plans to support "Markdown" formatting in the future? http://daringfireball.net/projects/markdown/

Bill Gelbaugh

All responses

David Trey  staff
Replied on Jul 30, 2012 - 12:35 UTC

Hello Bill,

you can currently format the name of your task with bold, italic, underlined or highlighted text. For more details, please refer to this page: https://todoist.com/Help/viewHelp?page=format_syntax

You're welcome to add your vote for this request in our Votebox: http://todoist.com/Vote/showProposal/440/

Best regards,

John Winstanley  premium
Replied on Dec 15, 2012 - 10:48 UTC


I realist that for the majority of your users markdown means nothing but for some of us it is almost muscle memory now and it would be great to have the option to not have to learn another syntax.

I've voted. Thanks.

Replied on Jul 24, 2013 - 16:28 UTC

I agree with John, changing the bold and italic, etc to be the same as markdown shouldn't be too much work and a lot of people (like us) would be eternally grateful

Kakaxa  premium
Replied on Jul 26, 2013 - 21:36 UTC


Justin Maxwell  premium
Replied on Aug 27, 2013 - 00:32 UTC

+1, please add support for markdown, it is an industry standard whereas the markup todoist uses now is not. Exactly what John W. said — muscle memory. I'm a paid user if that matters any.

Mike Greiner  premium
Replied on Nov 17, 2013 - 20:44 UTC

+1, agree. Also, the current keyboard shortcuts conflict with keyboard navigation on the Mac -- particularly ctrl-b.

Replied on Nov 17, 2013 - 21:15 UTC

Keyboard shortcuts should be customizable, they also conflict with Sublime Text.

Mathias Böni  premium
Replied on Apr 12, 2014 - 17:06 UTC

+1 :-)

Jonathan Dewe
Replied on May 24, 2014 - 05:45 UTC


Steve Clarke  premium
Replied on May 24, 2014 - 14:34 UTC


修平 永田  premium
Replied on Jun 30, 2014 - 10:22 UTC


Sergei Kuharev
Replied on Jul 19, 2014 - 12:05 UTC


Shawn Lee  premium
Replied on Aug 04, 2014 - 15:10 UTC


David Rodrigues  premium
Replied on Aug 05, 2014 - 04:23 UTC


David Rodrigues  premium
Replied on Aug 05, 2014 - 18:58 UTC

Full support for Markdown is not necessary, really.
But be cool to support it in the task contents itself.

What could be supported initially:

* Bold: using **hello** instead of !!hello!!;
* Italic: using *hello* instead of __hello__;
* Italic Bold: using ***hello*** instead of __!!hello!!__ (I don't know if it works);
* Monospaced: using `hello`;
* Links: [check it](http://google.com/);

And the priority and tags continues to work normally.


David Rodrigues  premium
Replied on Aug 05, 2014 - 18:59 UTC

The only problem is that it would be necessary to convert the formatting applied to all currently existent projects, since both styles are incompatible.

PA Buisson  premium
Replied on Oct 12, 2014 - 13:21 UTC

The link syntax is particularly annoying when you're used to markdown. I always need to search through Todoist documentation to find the appropriate syntax.

Graham Nanke  premium
Replied on Oct 17, 2014 - 21:48 UTC

love this idea,

you could have a selection on what is used for formatting (to remove the incompaatablities of the todoist language and Markdown)

In settings:

I would like to author my tasks in:
[ ] markdown
[ ] todoist code

+2 Voted!

John Winstanley  premium
Replied on Nov 11, 2014 - 19:58 UTC

Any news on MD support yet? Thanks

Noah Kareus  premium
Replied on Nov 14, 2014 - 07:08 UTC

It's surprising to see that this request is two years old now.


It would be great to have markdown support

Vadim Zee  premium
Replied on Jan 04, 2015 - 08:21 UTC

Voting +1!
Markdown support in task notes сould be really helpful

Jamie Jenkins  premium
Replied on Jan 27, 2015 - 21:11 UTC


Jamie Jenkins  premium
Replied on Jan 27, 2015 - 21:11 UTC


Adrian  premium
Replied on Feb 04, 2015 - 06:42 UTC

+whateverittakes, appending Graham Nanke's suggestion

joshharder  premium
Replied on Feb 08, 2015 - 20:00 UTC


Graham Nanke  premium
Replied on Feb 12, 2015 - 23:48 UTC

3 months later and i am +1'ing my own post... again