diff --git a/assets/images/federation/dark/zoneswitchsunstone.png b/assets/images/federation/dark/zoneswitchsunstone.png
new file mode 100644
index 000000000..54d5e031a
Binary files /dev/null and b/assets/images/federation/dark/zoneswitchsunstone.png differ
diff --git a/assets/images/federation/light/zoneswitchsunstone.png b/assets/images/federation/light/zoneswitchsunstone.png
new file mode 100644
index 000000000..5b84e9f04
Binary files /dev/null and b/assets/images/federation/light/zoneswitchsunstone.png differ
diff --git a/assets/images/zoneswitchsunstone.png b/assets/images/zoneswitchsunstone.png
deleted file mode 100644
index 04c37e7f4..000000000
Binary files a/assets/images/zoneswitchsunstone.png and /dev/null differ
diff --git a/content/product/control_plane_configuration/data_center_federation/usage.md b/content/product/control_plane_configuration/data_center_federation/usage.md
index 959f89a63..3f20939c5 100644
--- a/content/product/control_plane_configuration/data_center_federation/usage.md
+++ b/content/product/control_plane_configuration/data_center_federation/usage.md
@@ -20,7 +20,11 @@ In the upper right corner of the Sunstone page, users will see a globe icon next
 
 What’s happening behind the scenes is that the Sunstone server you are using is redirecting its requests to the OpenNebula oned process present in the other Zone. In the example above, if the user clicks on **ZoneB**, Sunstone contacts the OpenNebula listening at `http://zoneb.opennebula.front-end.server:2633/RPC2`.
 
-{{< image path="/images/zoneswitchsunstone.png" alt="Sunstone create Vrouter" align="center" width="90%" mb="20px" >}}
+{{< image
+  pathDark="images/federation/dark/zoneswitchsunstone.png"
+  path="images/federation/light/zoneswitchsunstone.png"
+  alt="Scaling provisions"
+>}}
 
 Uploading Virtual Machine Images over Sunstone works only for the main Zone to which the particular Sunstone instance belongs, not with other Zones users can switch to.
 {{% /tab %}}