diff --git a/guides/_subsections/analyze-a-thread-dump.md b/guides/_subsections/analyze-a-thread-dump.md
new file mode 100644
index 0000000..b92681a
--- /dev/null
+++ b/guides/_subsections/analyze-a-thread-dump.md
@@ -0,0 +1,46 @@
+## [Analyze a Thread Dump](#analyze-a-thread-dump)
+<ol>
+    <li>
+      <p>
+        The <i>Visualize Thread Dumps</i> page
+        allows you to visualize captured thread dumps from a <code>target</code> <b>JVM</b>, looking for common problems
+        and analyzing for deadlocks. Thread Dumps can be analyzed from the archives or selected from a dropdown.
+      </p>
+    </li>
+    <li>
+    {% include howto_step.html
+      summary="Select a Thread Dump"
+      image-name="4.2.0/analyze-a-thread-dump-1.png"
+      caption="
+        The dropdown menu will be populated with Thread Dumps from the archives for the currently selected target. If there are no <code>Thread Dumps</code> to source data from, capture one   then return back to this view.
+      "
+    %}
+  </li>
+  <li>
+    {% include howto_step.html
+      summary="Request analysis"
+      image-name="4.2.0/analyze-a-thread-dump-2.png"
+      caption="
+        Click the analysis process button in the corner of the drawer panel.
+      "
+    %}
+  </li>
+  <li>
+    {% include howto_step.html
+      summary="View aggregated data"
+      image-name="4.2.0/analyze-a-thread-dump-3.png"
+      caption="
+        Once a thread dump has been selected the view will be populated with the analyzed data. There are pie charts displaying aggregation by thread state, running methods, and lock instances. 
+      "
+    %}
+  </li>
+  <li>
+    {% include howto_step.html
+      summary="View detailed thread information"
+      image-name="4.2.0/analyze-a-thread-dump-4.png"
+      caption="
+        Once a thread dump has been selected the view will be populated with the analyzed data. There is as a table for specific patterns found in the data, and deadlocks detected as well as detailed thread information. The thread information table rows can be expanded to view the stack trace and lock instances held by a thread. 
+      "
+    %}
+  </li>
+</ol>
\ No newline at end of file
diff --git a/guides/index.md b/guides/index.md
index 8a1e7db..7ebad29 100644
--- a/guides/index.md
+++ b/guides/index.md
@@ -63,5 +63,7 @@ common actions and workflows of interest and why they are useful.
 
 {% include_relative _subsections/capture-a-heap-dump.md %}
 
+{% include_relative _subsections/analyze-a-thread-dump.md %}
+
 [comment]: # ## [Analyze Recordings Online](#analyze-recordings-online)
 [comment]: # TODO
diff --git a/images/4.2.0/analyze-a-thread-dump-1.png b/images/4.2.0/analyze-a-thread-dump-1.png
new file mode 100644
index 0000000..7f80565
Binary files /dev/null and b/images/4.2.0/analyze-a-thread-dump-1.png differ
diff --git a/images/4.2.0/analyze-a-thread-dump-2.png b/images/4.2.0/analyze-a-thread-dump-2.png
new file mode 100644
index 0000000..4c6c386
Binary files /dev/null and b/images/4.2.0/analyze-a-thread-dump-2.png differ
diff --git a/images/4.2.0/analyze-a-thread-dump-3.png b/images/4.2.0/analyze-a-thread-dump-3.png
new file mode 100644
index 0000000..14f89df
Binary files /dev/null and b/images/4.2.0/analyze-a-thread-dump-3.png differ
diff --git a/images/4.2.0/analyze-a-thread-dump-4.png b/images/4.2.0/analyze-a-thread-dump-4.png
new file mode 100644
index 0000000..604273a
Binary files /dev/null and b/images/4.2.0/analyze-a-thread-dump-4.png differ