Support UML diagrams in markdown with plantuml syntax

I often have the need for creating UML diagrams when explaining and discussing code, and the plantuml project (see provides a simple syntax for creating such as text. There is a plugin for the Confluence wiki platform that support using this in wiki pages, and it would be great if github’s markdown dialect could support something similar.


Thanks for this feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list. Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.


Do you have ticket accessible publicly to track PlantUML feature implementation in GitHub Markdown?

Can you please share the progress?


Hi @victor-letunovsky,

We do not have a public repo for this. We track our feature requests internally. As @lee-dohm mentioned, we can’t guarantee anything or share a timeline for if or when this might be implemented. 

If you’d like to keep up to date on new releases and updates to GitHub, I recommend following our blog:


1 Like

If that helps, have a look at embedding images from plantuml servers (slow but it works) :

1 Like

Constantly getting requests for this gitlab do it, I think, but not really a fan. Would be a great help for project planning, issues etc. ATM version control the source and the PNG.

You can also try to draw UML diagrams via markdown. For example something like this:

![Example UML]([Customer]->[Billing Address])

will render into:


You can edit this example at[Customer]->[Billing Address]


Just thought I’d add a note to bump this suggestion. It would be quite useful to be able to track UML changes in a the file increasing transparency and community collaboration on open source software architecture.


I’m using plantuml proxy with asciidoc instead of markdown on github. See

I agree, should be a good additional feature. Gitlab has it integrated as well and I must say it works effectivly



In response to “our internal feature request list”, I offer the following user story.

User Story

As a professional software developer, I would like more transparency into the GitHub feature request process, and the opportunity to contribute open source soultions to address such feature requests.

Acceptance Criteria

  1. Feature requests for GitHub are managed in public forum, with ability to up-vote, comment and propose PRs.

  2. GitHub has a clearly defined process for accepting contributions, and adding new features to the SaaS.

Best regards,



Is this something that could be solved by the new features of “Github actions” ?

Thank you kindly for the outline and feedback! I’ve taken your suggestion and passed it along to the appropriate teams.
I don’t have an ETA on when or if this request will be implemented but this is in good hands.

I’d love to see this supported.

Be it using PlantUML or yUML or something else

 doesn’t matter much (yet). As long as it works :slight_smile:


I am also interrested in using such integration to document specifications stored in a GitHub Repository and potentially publish it to a web site.

I would also like to see this added. Especially since we just moved from Gitlab to Github and Gitlab does not provide PlantUML integration on out of the box.

To save someone a click, the most straightforward way is ![alternative text]( for public repos, and ![alternative text](…) for private repos (i.e. append ?token=…). 

You can get the URL with token by clicking the  Raw link when viewing the diagram file. 

However this has the major drawback of expiring the token whenever the diagram file is edited. 

1 Like

@jean wrote:

To save someone a click, the most straightforward way is ![alternative text](

If you want to have images automatically reflect the latest version of the diagrams, it’s best to insert a flag to not use caching: e.g., 


1 Like


While github developers track this feature implementation ticket internally, can somebody from dev team please share progress and ETA?



I would love to see this as well. We currently store separate .wsd files and convert them to .png using PlantUML so that we can embed them in markdown. This works, but having them rendered directly by GitHub would be great.