diff --git a/website/source/docs/post-processors/vsphere-template.html.md b/website/source/docs/post-processors/vsphere-template.html.md
index e72dc19cc..511224cfd 100644
--- a/website/source/docs/post-processors/vsphere-template.html.md
+++ b/website/source/docs/post-processors/vsphere-template.html.md
@@ -1,7 +1,7 @@
 ---
 description: |
-    The Packer vSphere Template post-processor takes an artifact from the VMware-iso builder built on ESXi (i.e. remote)
-    and allows to mark a VM as a template and leaving it in a path of choice. 
+    The Packer vSphere Template post-processor takes an artifact from the VMware-iso builder, built on ESXi (i.e. remote)
+    or an artifact from the vSphere post-processor and allows to mark a VM as a template and leaving it in a path of choice.
 layout: docs
 page_title: 'vSphere Template - Post-Processors'
 sidebar_current: 'docs-post-processors-vSphere-template'
@@ -11,8 +11,9 @@ sidebar_current: 'docs-post-processors-vSphere-template'
 
 Type: `vsphere-template`
 
-The Packer vSphere template post-processor takes an artifact from the VMware-iso builder built on ESXi (i.e. remote) and
-allows to mark a VM as a template and leaving it in a path of choice.
+The Packer vSphere Template post-processor takes an artifact from the VMware-iso builder, built on ESXi (i.e. remote)
+or an artifact from the [vSphere](/docs/post-processors/vsphere.html) post-processor and allows to mark a VM as a
+template and leaving it in a path of choice.
 
 ## Example
 
@@ -51,3 +52,31 @@ Optional:
 -   `folder` (string) - Target path where the template will be created. 
 
 -   `insecure` (boolean) - If it's true skip verification of server certificate. Default is false  
+
+## Using the vSphere Template with local builders
+
+Once the [vSphere](/docs/post-processors/vsphere.html) takes an artifact from the VMware builder and uploads it
+to a vSphere endpoint, you will likely want to mark that VM as template. Packer can do this for you automatically
+using a sequence definition (a collection of post-processors that are treated as as single pipeline, see
+[Post-Processors](/docs/templates/post-processors.html) for more information):
+
+``` json
+{
+  "post-processors": [
+    [
+      {
+        "type": "vsphere",
+         ...
+      },
+      {
+        "type": "vsphere-template",
+         ...
+      }
+    ]
+  ]
+}
+```
+
+In the example above, the result of each builder is passed through the defined sequence of post-processors starting
+with the `vsphere` post-processor which will upload the artifact to a vSphere endpoint. The resulting artifact is then
+passed on to the `vsphere-template` post-processor which handles marking a VM as a template.