Rich PlantUML support for Visual Studio Code.

Donate by Paypal | Donate by AliPay | PlantUML Document

To avoid unexpected data sharing, the latest version has removed the default value of plantuml.server.

Before you specify one (either the official or your own), server render and markdown integration won't work but prompts.

See also: Use PlantUML Server as render

Get 15X times faster export by utilizing PlantUML Server as render. How to?

• Preview Diagram, Press Alt-D to start PlantUML preview.
  • Auto update.
  • Zoom & scroll support.
  • Multi-Page Diagram support.
  • Instant preview, if diagram's been exported.
  • From local or server.
  • Snap to Border
• Export Diagrams
  • At cursor, in current file, in whole workspace, in workspace selected.
  • Concurrent export.
  • Generate URLs.
  • Multi-Page Diagram support.
  • From local or server.
  • Image map (cmapx) support.
• Editing Supports
  • Format PlantUML code.
  • All type syntax highlight.
  • All type snippets.
  • Basic auto completion & macro signature support NEW!!
  • Symbol List support.
  • Auto Include (Deprecated).
• Others
  • Multi-root Workspace Support.
  • MarkDown integrating support. View Demo
  • Extracting source from images support.

Notice: If you use customize plantuml.jar, please update to the latest version to enable Multi-Page Diagram support. (Later than V1.2017.15)

*.wsd, *.pu, *.puml, *.plantuml, *.iuml

Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.

ext install plantuml

Depend on which render you choose, plugin has diffrerent requirements.

A plantuml server. See Use PlantUML Server as render.

It's necessary to have following installed:

• Java : Platform for PlantUML running.
• Graphviz : PlantUML requires it to calculate positions in diagram.

brew cask install java
brew install graphviz

For windows user, majkinetor introduced a way to install plantuml and its dependencies easily. Run cmd.exe as Administrator, and run two commands as follow

@"%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe" -NoProfile -ExecutionPolicy Bypass -Command "iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))" && SET "PATH=%PATH%;%ALLUSERSPROFILE%\chocolatey\bin"

choco install plantuml

Plugin has integrated a copy of "plantuml.jar", you are good to go now. But if you want to use your own jar (maybe a newer version, or with many dependent jars), specify the jar location with setting plantuml.jar.

If you've installed java, but still prompts "java not installed", please add java bin path to PATH environment variable.

• Default extension settings works for independent Plantuml projects.
• If Plantuml files are only part of your project (as documetation), use plantuml.diagramsRoot and plantuml.exportOutDir to setting up the organization, for example:

"plantuml.diagramsRoot": "docs/diagrams/src",
"plantuml.exportOutDir": "docs/diagrams/out"

You'll get export results like:

Project Folder/
  docs/
    diagrams/
      src/
        architecture_overview.wsd
      out/
        architecture_overview/
          architecture_overview.png
  ...rest_of_your_project_folders/
  ...rest_of_your_project_files 

Latest version has changed the include files search logic once again. It is possible to configure includepaths now in settings.json.

The new search order is as follows:

1. The folder of the rendered file
2. The includepaths as configured in settings.json

"plantuml.includepaths": ["docs/diagrams/style","docs/diagrams/src"],

3. The diagramsRoot

The setting includeSearch is not needed anymore, since the folder of the plantuml file and the diagramsRoot are always both in the include path.

To new projects, it's recommended not to rely on diagramsRoot and configure all required includepaths explicitly.

Thanks anotherandi for the brilliant idea and implementation!

Preview page provides various zoom/pan actions and snap feature:

• Zoom operations (since version 2.7.0):
  • Zoom to select area
  • Pinch to zoom (TouchPad)
  • Click to zoom in, alt + click to zoom out
  • Ctrl + mouse scroll to zoom in/out
  • Middle mouse button click to toggle zoom
  • Zoom in / zoom out / toggle buttons of the controls bar.
• Pan operations (since version 2.7.0):
  • Right mouse button drag
  • Two-finger move to pan (TouchPad)
  • Mouse scroll
• Snap to border (since v2.8.0):
  • Scroll to most bottom/right/top/left, preview will snap to that border.

  e.g. Snap to Bottom is useful while writing long activity diagrams, which helps you keep focus in the latest part in the bottom.

Auto update:

zoom & scroll:

Multi-Page View:

Export diagram:

PlantUML formatter is disabled (since v2.8.3) if editor.formatOnSave is on. Because the formatter is not reliable enough according to user feedbacks.

This plugin integrates all type diagram snippets. They are splitted into 9 sections:

• diagram: snippets for general diagrams elements.
• activity: snippets for activity diagrams.
• class: snippets for class diagrams.
• component: snippets for component diagrams.
• state: snippets for state diagrams.
• usecase: snippets for usecase diagrams.
• sequence: snippets for sequence diagrams.
• ui: snippets for salt diagrams.
• egg: snippets for some funny diagrams, like sudoku, earth.

For exsample, type acife (short version) to trigge following snippet (activity➤if・else):

if (cond1?) then (val1)

else (val2)

endif

Press Ctrl+Shift+O to list all diagrams in the file. You can name the diagram when diagram starts.

@startuml diagram name sudoku @enduml

Plugin supports two renders: Local and PlantUMLServer.

Local is the default and traditional way. If you care more about export speed, you should try PlantUMLServer.

Local: 6 documents, 9 digrams, 14 files exported in 24.149 seconds
PlantUMLServer: 6 documents, 9 digrams, 14 files exported in 1.564 seconds

Advantages:

• 15X times faster export and much quicker preview response.
• Don't have to set local enviroments if you have a server in your team.
• You don't need plantuml.exportConcurrency, because it's unlimited in concurrency.

Disadvantages:

• Cannot render very-large diagrams (HTTP 413 error).
• Cannot render diagrams with !include in it.
• Less format support: png, svg, txt.
• Some settings are not applicable: plantuml.jar, plantuml.commandArgs, plantuml.jarArgs.

• You may already have a PlantUML server in your team, find the server address, like: http://192.168.1.100:8080.

• If don't have one, set up following the instructions, run with Docker is recommended. Find the server address, like: http://localhost:8080, or http://192.168.1.100:8080 which is ready for sharing to your team.

• Open user setting, and configure like:

"plantuml.server": "http://192.168.1.100:8080",
"plantuml.render": "PlantUMLServer",

Notice: AutoInclude is deprecated since the include search has been improved, that the include path is consistent between files, and provide better flexibility.

Translations are welcome. lang.nls.json, package.nls.json

@startuml / @enduml is still recommended, so that PlantUML code in Markdown can be managed by other function of this plugin.

This extension contributes the following settings.

Render Select:

• plantuml.render: Select diagram render for both export and preview.

PlantUMLServer Render Settings:

• plantuml.server: PlantUML server to generate UML diagrams on-the-fly.

Local Render Settings:

• plantuml.java: Java executable location.
• plantuml.commandArgs: commandArgs allows you add command arguments to java command, such as -DPLANTUML_LIMIT_SIZE=8192.
• plantuml.jar: Alternate plantuml.jar location. Leave it blank to use integrated jar.
• plantuml.jarArgs: jarArgs allows you add arguments to plantuml.jar, such as -config plantuml.config.
• plantuml.includepaths: Specifies the include paths besides source folder and the diagramsRoot.
• plantuml.includes: Files or folders to include before preview/export diagrams. You don't have to write "!include path/to/include.wsd" for every single diagram any more.

Export Settings:

• plantuml.diagramsRoot: Specifies where all diagram files located (releative to workspace folder).
• plantuml.exportOutDir: Exported workspace diagrams will be organized in this directory (releative path to workspace folder).
• plantuml.fileExtensions: File extensions that find to export. Especially in workspace settings, you may add your own extensions so as to export diagrams in source code files, like ".java".
• plantuml.exportFormat: format to export. default is not set, user may pick one format everytime exports. You can still set a format for it if you don't want to pick.
• plantuml.exportSubFolder: export diagrams to a folder which has same name with host file.
• plantuml.exportConcurrency: decides concurrency count when export multiple diagrams.
• plantuml.exportMapFile: Determine whether export image map (.cmapx) file when export.

Preview Settings:

• plantuml.previewAutoUpdate: Dedecides if automatically update the preview window.

URL Generating Settings:

• plantuml.urlFormat: URL format. Leave it blank to pick format everytime you generate a URL.
• plantuml.urlResult: URL result type. Simple URL or ready for MarkDown use.

Please post and view issues on GitHub

• Kohei Arao
• zhleonix
• Eward Song
• Martin Riedel

• Japanese: Kohei Arao
• Tranditional Chinese: Alan Tsai
• German: Fabian F.
• French: Zepmanbc, FlorianKempenich
• Danish: Mikkel O. Laursen

Thanks for your encouragements!

Claus Appel, 三島木​一磨, 富吉​佑季, 黒田悦成, Jared Birdsall, Suleyman Cabir Ciplak, Malcolm Learner, Сысоев Максим, Gokan Kenichi

Enjoy!