diff --git a/docs/software/mqtt/index.mdx b/docs/software/mqtt/index.mdx
index 8242a0f5..a1ef38e4 100644
--- a/docs/software/mqtt/index.mdx
+++ b/docs/software/mqtt/index.mdx
@@ -7,6 +7,8 @@ sidebar_position: 6
 
 ## Bridging networks
 
+![Common MQTT Layout](/img/software/mqtt/mqtt.png)
+
 Meshtastic networks in different locations beyond the reach of LoRa can be easily bridged together using MQTT. The simplest option is to connect your mesh to the official Meshtastic MQTT broker. This makes your devices appear on the world map, and provides a copy of your mesh traffic, translated into JSON. All you have to do to join the public MQTT server is to Enable MQTT and set Uplink and Downlink on the channels that you want to share over MQTT. The default device configuration using the public MQTT Server is encrypted.
 
 You can also share channel settings with a remote network. If you use the default Meshtastic MQTT server, packets are always encrypted. If you use a custom MQTT broker (ie set `mqtt.address`), the `mqtt.encryption_enabled` setting applies, which by default is false. You can also specify your own private MQTT broker and specify authentication for that broker to bridge several mesh networks together, via the internet (or just a local IP network).
diff --git a/static/img/software/mqtt/mqtt.png b/static/img/software/mqtt/mqtt.png
new file mode 100644
index 00000000..98d7d5b5
Binary files /dev/null and b/static/img/software/mqtt/mqtt.png differ