Render BPMN files natively in the repository file view (like SVG/PNG)

[pablocabrera85]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Code Search and Navigation

Body

Problem
GitHub currently renders SVG and PNG files inline when you open them in a repository, giving an instant visual preview with no extra tooling. BPMN files (.bpmn, which is just XML) get no such treatment — they show as raw XML text, even though they represent visual process diagrams that are just as "renderable" as an image.

BPMN is a widely used, open standard (ISO/IEC 19510) for business process diagrams, and many teams store .bpmn files in Git alongside code to track process changes over time. Right now, understanding a diff or reviewing a process change requires opening the file in an external tool (e.g. the bpmn.io demo, or a local BPMN editor) just to see what changed visually.

Proposed solution
When a repository file has a .bpmn (or .bpmn20.xml) extension, render it as an interactive diagram in the file view — similar to how SVG is rendered today — using an open-source viewer library (e.g. bpmn-js, used for this exact purp

ose).

Why this matters

• Faster code review: reviewers can see process diagrams without leaving GitHub
• Lower barrier: no need to install/open a separate BPMN tool to inspect a file
• Consistency: brings BPMN in line with existing inline rendering for SVG, PNG, and other visual formats
• Prior art exists: community projects like render-bpmn and bpmn-visualization-examples already demonstrate rendering BPMN content pulled from GitHub repos, showing there's real demand and a viable technical approach

Happy to provide more detail or examples if helpful!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[ISMEG-ZAKARIA]

Hi @pablocabrera85!

This is a great feature request! Native BPMN rendering (similar to Mermaid or SVG previews) would make reviewing workflow diagrams directly in GitHub much easier.

Since community members don't have direct control over GitHub's roadmap, the best way to get visibility on this is for other users to upvote your post with a 👍 reaction.

Hopefully, the GitHub Product team considers adding .bpmn preview support in a future release!

[mohammadrezwankhan]

Until GitHub has a native BPMN viewer, the most reviewable workaround is to keep the .bpmn source and publish a generated static preview beside it.

For example:

diagrams/order.bpmn
diagrams/order.svg   # generated from the BPMN source

Then embed the preview from Markdown and link the source:

![Order workflow](diagrams/order.svg)
[Edit the BPMN source](diagrams/order.bpmn)

GitHub supports displaying common image formats such as SVG and PNG, and relative image paths in Markdown follow the branch being viewed. The relevant guidance is Working with non-code files and About the repository README file. A CI job can regenerate the SVG when the BPMN changes, so reviewers see the source and a visual artifact in the same commit.

For native support, a safe MVP would detect .bpmn/.bpmn20.xml, render in a sandbox with a size/time limit, keep a raw-XML tab and downloadable source, and provide accessible text/zoom. It should never execute embedded scripts or external resources. That gives the visual review benefit without removing the auditability of the XML diff.