docs: fix stale .png/.jpg image refs to match .webp assets in Sagitta (#2098)

Signed-off-by: MilaNad <l.nadolina@vyos.io>

39 files changed, 130 insertions, 130 deletions

diff --git a/docs/automation/terraform/terraformAWS.md b/docs/automation/terraform/terraformAWS.md
index 4a29fba3..06459403 100644
--- a/docs/automation/terraform/terraformAWS.md
+++ b/docs/automation/terraform/terraformAWS.md
@@ -9,7 +9,7 @@ lastproofread: '2024-01-11'
 With the help of Terraform, you can quickly deploy VyOS-based infrastructure in the AWS cloud. If necessary, the infrastructure can be removed using terraform.
 Also we will make provisioning using Ansible.
 
-```{image} /_static/images/aws.png
+```{image} /_static/images/aws.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 50%
@@ -28,7 +28,7 @@ AWS
 
 2 Create a key [pair] and download your .pem key
 
-```{image} /_static/images/keypairs.png
+```{image} /_static/images/keypairs.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 50%
@@ -36,13 +36,13 @@ AWS
 
 3 Create a security [group] for the new VyOS instance and open all traffic
 
-```{image} /_static/images/sg.png
+```{image} /_static/images/sg.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 50%
 ```
 
-```{image} /_static/images/traffic.png
+```{image} /_static/images/traffic.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 50%
diff --git a/docs/configexamples/fwall-and-vrf.md b/docs/configexamples/fwall-and-vrf.md
index f1be96a2..6ae38c5f 100644
--- a/docs/configexamples/fwall-and-vrf.md
+++ b/docs/configexamples/fwall-and-vrf.md
@@ -6,7 +6,7 @@ This example shows how to configure a VyOS router with VRFs and firewall rules.
 
 Diagram used in this example:
 
-```{image} /_static/images/firewall-and-vrf-blueprints.png
+```{image} /_static/images/firewall-and-vrf-blueprints.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
diff --git a/docs/configexamples/inter-vrf-routing-vrf-lite.md b/docs/configexamples/inter-vrf-routing-vrf-lite.md
index 50e666a9..2de51107 100644
--- a/docs/configexamples/inter-vrf-routing-vrf-lite.md
+++ b/docs/configexamples/inter-vrf-routing-vrf-lite.md
@@ -65,7 +65,7 @@ community(ies) into that prefix.
 
 ## Topology
 
-```{image} /_static/images/inter-vrf-routing-vrf-lite.png
+```{image} /_static/images/inter-vrf-routing-vrf-lite.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 70%
diff --git a/docs/configexamples/ipsec-cisco-policy-based.md b/docs/configexamples/ipsec-cisco-policy-based.md
index 2a12a252..4ac4b7e7 100644
--- a/docs/configexamples/ipsec-cisco-policy-based.md
+++ b/docs/configexamples/ipsec-cisco-policy-based.md
@@ -14,7 +14,7 @@ initiator role on VyOS side.
 
 ## Network Topology
 
-```{image} /_static/images/cisco-vpn-ipsec.png
+```{image} /_static/images/cisco-vpn-ipsec.webp
 :align: center
 :alt: Network Topology Diagram
 ```
diff --git a/docs/configexamples/ipsec-cisco-route-based.md b/docs/configexamples/ipsec-cisco-route-based.md
index abd4fb3e..9cad654b 100644
--- a/docs/configexamples/ipsec-cisco-route-based.md
+++ b/docs/configexamples/ipsec-cisco-route-based.md
@@ -15,7 +15,7 @@ inside the tunnel.
 
 ## Network Topology
 
-```{image} /_static/images/cisco-vpn-ipsec.png
+```{image} /_static/images/cisco-vpn-ipsec.webp
 :align: center
 :alt: Network Topology Diagram
 ```
diff --git a/docs/configexamples/ipsec-pa-route-based.md b/docs/configexamples/ipsec-pa-route-based.md
index ce21a9d3..e3dbee09 100644
--- a/docs/configexamples/ipsec-pa-route-based.md
+++ b/docs/configexamples/ipsec-pa-route-based.md
@@ -16,7 +16,7 @@ include firewall configuration.
 
 ## Network Topology
 
-```{image} /_static/images/ipsec-vyos-pa.png
+```{image} /_static/images/ipsec-vyos-pa.webp
 :align: center
 :alt: Network Topology Diagram
 ```
@@ -144,43 +144,43 @@ GUI Configuration:
 
 : Network -> Network Profiles -> IKE Crypto
 
-  ```{image} /_static/images/PA-IKE-group.png
+  ```{image} /_static/images/PA-IKE-group.webp
   :align: center
   ```
 
   Network -> Network Profiles -> IKE Gateways
 
-  ```{image} /_static/images/PA-IKE-GW-1.png
+  ```{image} /_static/images/PA-IKE-GW-1.webp
   :align: center
   ```
 
-  ```{image} /_static/images/PA-IKE-GW-2.png
+  ```{image} /_static/images/PA-IKE-GW-2.webp
   :align: center
   ```
 
   Network -> Network Profiles -> IPSec Crypto
 
-  ```{image} /_static/images/PA-ESP-group.png
+  ```{image} /_static/images/PA-ESP-group.webp
   :align: center
   ```
 
   Network -> Interfaces
 
-  ```{image} /_static/images/PA-tunnel-1.png
+  ```{image} /_static/images/PA-tunnel-1.webp
   :align: center
   ```
 
-  ```{image} /_static/images/PA-tunnel-2.png
+  ```{image} /_static/images/PA-tunnel-2.webp
   :align: center
   ```
 
-  ```{image} /_static/images/PA-tunnel-3.png
+  ```{image} /_static/images/PA-tunnel-3.webp
   :align: center
   ```
 
   Network -> IPSec Tunnels
 
-  ```{image} /_static/images/PA-IPsec-tunnel.png
+  ```{image} /_static/images/PA-IPsec-tunnel.webp
   :align: center
   ```
 
diff --git a/docs/configexamples/l3vpn-hub-and-spoke.md b/docs/configexamples/l3vpn-hub-and-spoke.md
index bdd62ada..d62e4597 100644
--- a/docs/configexamples/l3vpn-hub-and-spoke.md
+++ b/docs/configexamples/l3vpn-hub-and-spoke.md
@@ -46,7 +46,7 @@ General information can be found in the {ref}`configuration/vrf/index:L3VPN VRFs
 
 ## Topology
 
-```{image} /_static/images/L3VPN_hub_and_spoke.png
+```{image} /_static/images/L3VPN_hub_and_spoke.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
diff --git a/docs/configexamples/lac-lns.md b/docs/configexamples/lac-lns.md
index 5bf5edb2..0899247a 100644
--- a/docs/configexamples/lac-lns.md
+++ b/docs/configexamples/lac-lns.md
@@ -19,7 +19,7 @@ All users with domain **vyos.io** will be tunneled to LNS via L2TP.
 
 ## Network Topology
 
-```{image} /_static/images/lac-lns-diagram.jpg
+```{image} /_static/images/lac-lns-diagram.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 60%
@@ -102,7 +102,7 @@ accomplishes that.
 
 In this lab we use Windows PPPoE client.
 
-```{image} /_static/images/lac-lns-winclient.jpg
+```{image} /_static/images/lac-lns-winclient.webp
 :align: center
 :alt: Window PPPoE Client Configuration
 :width: 100%
diff --git a/docs/configexamples/nmp.md b/docs/configexamples/nmp.md
index 71855f89..5b15f6f2 100644
--- a/docs/configexamples/nmp.md
+++ b/docs/configexamples/nmp.md
@@ -24,43 +24,43 @@ set service snmp community router network '0.0.0.0/0'
 
 Next, you just should follow the pictures:
 
-```{image} /_static/images/nmp1.png
+```{image} /_static/images/nmp1.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
 ```
 
-```{image} /_static/images/nmp2.png
+```{image} /_static/images/nmp2.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
 ```
 
-```{image} /_static/images/nmp3.png
+```{image} /_static/images/nmp3.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
 ```
 
-```{image} /_static/images/nmp4.png
+```{image} /_static/images/nmp4.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
 ```
 
-```{image} /_static/images/nmp5.png
+```{image} /_static/images/nmp5.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
 ```
 
-```{image} /_static/images/nmp6.png
+```{image} /_static/images/nmp6.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
 ```
 
-```{image} /_static/images/nmp7.png
+```{image} /_static/images/nmp7.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
diff --git a/docs/configexamples/pppoe-ipv6-basic.md b/docs/configexamples/pppoe-ipv6-basic.md
index 9b1503f3..1314fcf1 100644
--- a/docs/configexamples/pppoe-ipv6-basic.md
+++ b/docs/configexamples/pppoe-ipv6-basic.md
@@ -16,7 +16,7 @@ please contact your ISP for more information.
 
 ## Network Topology
 
-```{image} /_static/images/pppoe-ipv6-pd-diagram.jpg
+```{image} /_static/images/pppoe-ipv6-pd-diagram.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 60%
diff --git a/docs/configexamples/qos.md b/docs/configexamples/qos.md
index c22a0a13..64332923 100644
--- a/docs/configexamples/qos.md
+++ b/docs/configexamples/qos.md
@@ -13,7 +13,7 @@ We recommend you to go through the main article about [QoS](https://docs.vyos.io
 
 Using the general schema for example:
 
-```{image} /_static/images/qos1.png
+```{image} /_static/images/qos1.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -63,7 +63,7 @@ Main rules:
 
 Check the result
 
-```{image} /_static/images/qos2.png
+```{image} /_static/images/qos2.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -71,7 +71,7 @@ Check the result
 
 Before the interface eth0 on router VyOS3
 
-```{image} /_static/images/qos3.png
+```{image} /_static/images/qos3.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -79,7 +79,7 @@ Before the interface eth0 on router VyOS3
 
 After the interface eth0 on router VyOS3
 
-```{image} /_static/images/qos4.png
+```{image} /_static/images/qos4.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -105,7 +105,7 @@ set qos interface eth0 egress 'vyos4'
 
 Next on the router VyOS2 we will change labels on all incoming traffic only from CS4-> CS6
 
-```{image} /_static/images/qos5.png
+```{image} /_static/images/qos5.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -129,7 +129,7 @@ set qos policy shaper vyos2 default queue-type 'fair-queue'
 set qos interface eth2 egress 'vyos2'
 ```
 
-```{image} /_static/images/qos6.png
+```{image} /_static/images/qos6.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -137,7 +137,7 @@ set qos interface eth2 egress 'vyos2'
 
 - 172.17.1.2/24 CS0
 
-```{image} /_static/images/qos7.png
+```{image} /_static/images/qos7.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -145,7 +145,7 @@ set qos interface eth2 egress 'vyos2'
 
 - 172.17.1.2/24 CS0 - > CS4
 
-```{image} /_static/images/qos8.png
+```{image} /_static/images/qos8.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -153,7 +153,7 @@ set qos interface eth2 egress 'vyos2'
 
 - 172.17.1.2/24 CS4 - > CS5
 
-```{image} /_static/images/qos9.png
+```{image} /_static/images/qos9.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -178,7 +178,7 @@ match VyOS3 {
 
 Check the result.
 
-```{image} /_static/images/qos10.png
+```{image} /_static/images/qos10.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
diff --git a/docs/configexamples/segment-routing-isis.md b/docs/configexamples/segment-routing-isis.md
index 76cb726c..41ba2389 100644
--- a/docs/configexamples/segment-routing-isis.md
+++ b/docs/configexamples/segment-routing-isis.md
@@ -11,7 +11,7 @@ blue print as an initial setup to get MPLS ISIS-SR working between those two
 devices.The lab was build using {abbr}`EVE-NG (Emulated Virtual
 Environment NG)`.
 
-:::{figure} /_static/images/vyos-sr-isis.png
+:::{figure} /_static/images/vyos-sr-isis.webp
 :alt: ISIS-SR network
 
 ISIS-SR example network
diff --git a/docs/configexamples/wan-load-balancing.md b/docs/configexamples/wan-load-balancing.md
index e35b9056..b3f12ff4 100644
--- a/docs/configexamples/wan-load-balancing.md
+++ b/docs/configexamples/wan-load-balancing.md
@@ -11,7 +11,7 @@ lastproofread: '2021-06-29'
 
 The setup used in this example is shown in the following diagram:
 
-```{image} /_static/images/Wan_load_balancing1.png
+```{image} /_static/images/Wan_load_balancing1.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
@@ -151,7 +151,7 @@ set protocols static route 0.0.0.0/0 next-hop 11.22.33.1
 In this example two LAN interfaces exist in different subnets instead
 of one like in the previous examples:
 
-```{image} /_static/images/Wan_load_balancing_exclude1.png
+```{image} /_static/images/Wan_load_balancing_exclude1.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
diff --git a/docs/configexamples/zone-policy.md b/docs/configexamples/zone-policy.md
index d9c22c09..be80ee55 100644
--- a/docs/configexamples/zone-policy.md
+++ b/docs/configexamples/zone-policy.md
@@ -39,7 +39,7 @@ adapted for however many NICs you have**:
 - DMZ cannot access LAN resources.
 - Inbound WAN connect to DMZ host.
 
-```{image} /_static/images/zone-policy-diagram.png
+```{image} /_static/images/zone-policy-diagram.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 80%
diff --git a/docs/configuration/firewall/flowtables.md b/docs/configuration/firewall/flowtables.md
index bc9fc457..9fab80b4 100644
--- a/docs/configuration/firewall/flowtables.md
+++ b/docs/configuration/firewall/flowtables.md
@@ -35,7 +35,7 @@ Flowtables allows you to define a fastpath through the flowtable datapath.
 The flowtable supports for the layer 3 IPv4 and IPv6 and the layer 4 TCP
 and UDP protocols.
 
-:::{figure} /_static/images/firewall-flowtable-packet-flow.png
+:::{figure} /_static/images/firewall-flowtable-packet-flow.webp
 :::
 
 Once the first packet of the flow successfully goes through the IP forwarding
diff --git a/docs/configuration/firewall/index.md b/docs/configuration/firewall/index.md
index 53c5a7fc..58903314 100644
--- a/docs/configuration/firewall/index.md
+++ b/docs/configuration/firewall/index.md
@@ -15,7 +15,7 @@ A simplified traffic flow diagram, based on Netfilter packet flow, is shown
 next, in order to have a full view and understanding of how packets are
 processed, and what possible paths traffic can take.
 
-:::{figure} /_static/images/firewall-gral-packet-flow.png
+:::{figure} /_static/images/firewall-gral-packet-flow.webp
 :::
 
 The main points regarding this packet flow and terminology used in VyOS
@@ -177,5 +177,5 @@ As the example image below shows, the device now needs rules to allow/block
 traffic to or from the services running on the device that have open
 connections on that interface.
 
-:::{figure} /_static/images/firewall-zonebased.png
+:::{figure} /_static/images/firewall-zonebased.webp
 :::
diff --git a/docs/configuration/firewall/ipv4.md b/docs/configuration/firewall/ipv4.md
index 23ff6c39..c020afb8 100644
--- a/docs/configuration/firewall/ipv4.md
+++ b/docs/configuration/firewall/ipv4.md
@@ -38,7 +38,7 @@ For transit traffic, which is received by the router and forwarded, base chain
 is **forward**. A simplified packet flow diagram for transit traffic is shown
 next:
 
-:::{figure} /_static/images/firewall-fwd-packet-flow.png
+:::{figure} /_static/images/firewall-fwd-packet-flow.webp
 :::
 
 Where firewall base chain to configure firewall filtering rules for transit
@@ -51,7 +51,7 @@ A new simplified packet flow diagram is shown next, which shows the path
 for traffic destinated to the router itself, and traffic generated by the
 router (starting from circle number 6):
 
-:::{figure} /_static/images/firewall-input-packet-flow.png
+:::{figure} /_static/images/firewall-input-packet-flow.webp
 :::
 
 Base chain is for traffic toward the router is `set firewall ipv4 input
diff --git a/docs/configuration/firewall/ipv6.md b/docs/configuration/firewall/ipv6.md
index e2db7928..9fd8988c 100644
--- a/docs/configuration/firewall/ipv6.md
+++ b/docs/configuration/firewall/ipv6.md
@@ -38,7 +38,7 @@ For transit traffic, which is received by the router and forwarded, base chain
 is **forward**. A simplified packet flow diagram for transit traffic is shown
 next:
 
-:::{figure} /_static/images/firewall-fwd-packet-flow.png
+:::{figure} /_static/images/firewall-fwd-packet-flow.webp
 :::
 
 Where firewall base chain to configure firewall filtering rules for transit
@@ -51,7 +51,7 @@ A new simplified packet flow diagram is shown next, which shows the path
 for traffic destinated to the router itself, and traffic generated by the
 router (starting from circle number 6):
 
-:::{figure} /_static/images/firewall-input-packet-flow.png
+:::{figure} /_static/images/firewall-input-packet-flow.webp
 :::
 
 Base chain is for traffic toward the router is `set firewall ipv6 input
diff --git a/docs/configuration/interfaces/bonding.md b/docs/configuration/interfaces/bonding.md
index ef6988e5..2c9ef2ba 100644
--- a/docs/configuration/interfaces/bonding.md
+++ b/docs/configuration/interfaces/bonding.md
@@ -473,7 +473,7 @@ those two devices.
 
 Lets assume the following topology:
 
-:::{figure} /_static/images/vyos_arista_bond_lacp.png
+:::{figure} /_static/images/vyos_arista_bond_lacp.webp
 :alt: VyOS Arista EOS setup
 :::
 
diff --git a/docs/configuration/interfaces/openvpn.md b/docs/configuration/interfaces/openvpn.md
index 5bd78695..1903d0db 100644
--- a/docs/configuration/interfaces/openvpn.md
+++ b/docs/configuration/interfaces/openvpn.md
@@ -33,7 +33,7 @@ interface using `set interfaces openvpn`.
 
 ## Site-to-Site
 
-:::{figure} /_static/images/openvpn_site2site_diagram.jpg
+:::{figure} /_static/images/openvpn_site2site_diagram.webp
 :::
 
 OpenVPN is popular for client-server setups, but its site-to-site mode
diff --git a/docs/configuration/interfaces/wireguard.md b/docs/configuration/interfaces/wireguard.md
index 3f69a7fe..ea97a0aa 100644
--- a/docs/configuration/interfaces/wireguard.md
+++ b/docs/configuration/interfaces/wireguard.md
@@ -14,7 +14,7 @@ information.
 
 This diagram corresponds with the example site to site configuration below.
 
-:::{figure} /_static/images/wireguard_site2site_diagram.jpg
+:::{figure} /_static/images/wireguard_site2site_diagram.webp
 :::
 
 ## Keypairs
@@ -425,7 +425,7 @@ public key. Please keep this in mind when using this convenience feature.
   will connect to. The address parameter can be used up to two times and is used
   to assign the clients specific IPv4 (/32) or IPv6 (/128) address.
 
-  .. figure:: /_static/images/wireguard_qrcode.jpg
+  .. figure:: /_static/images/wireguard_qrcode.webp
      :alt: WireGuard Client QR code
 ```
 
diff --git a/docs/configuration/loadbalancing/wan.md b/docs/configuration/loadbalancing/wan.md
index 272ba9e9..f59bf5ae 100644
--- a/docs/configuration/loadbalancing/wan.md
+++ b/docs/configuration/loadbalancing/wan.md
@@ -193,7 +193,7 @@ set load-balancing wan disable-source-nat
 Inbound connections to a WAN interface can be improperly handled when the reply
 is sent back to the client.
 
-```{image} /_static/images/sticky-connections.jpg
+```{image} /_static/images/sticky-connections.webp
 :align: center
 :width: 80%
 ```
diff --git a/docs/configuration/nat/nat44.md b/docs/configuration/nat/nat44.md
index f7357f19..37a65149 100644
--- a/docs/configuration/nat/nat44.md
+++ b/docs/configuration/nat/nat44.md
@@ -676,7 +676,7 @@ The ASP requests that all connections from this company should come from
 172.29.41.89 - an address that is assigned by the ASP and not in use at
 the customer site.
 
-:::{figure} /_static/images/nat_before_vpn_topology.png
+:::{figure} /_static/images/nat_before_vpn_topology.webp
 :alt: NAT before VPN Topology
 :scale: 100 %
 
diff --git a/docs/configuration/nat/nat66.md b/docs/configuration/nat/nat66.md
index 371da24f..34400485 100644
--- a/docs/configuration/nat/nat66.md
+++ b/docs/configuration/nat/nat66.md
@@ -102,7 +102,7 @@ Use the following topology to build a nat66 based isolated
 network between internal and external networks (dynamic prefix is
 not supported):
 
-:::{figure} /_static/images/vyos_1_4_nat66_simple.png
+:::{figure} /_static/images/vyos_1_4_nat66_simple.webp
 :alt: VyOS NAT66 Simple Configure
 :::
 
@@ -132,7 +132,7 @@ set service router-advert interface br1 prefix ::/0
 Use the following topology to translate internal user local addresses (`fc::/7`)
 to DHCPv6-PD provided prefixes from an ISP connected to a VyOS HA pair.
 
-:::{figure} /_static/images/vyos_1_5_nat66_dhcpv6_wdummy.png
+:::{figure} /_static/images/vyos_1_5_nat66_dhcpv6_wdummy.webp
 :alt: VyOS NAT66 DHCPv6 using a dummy interface
 :::
 
diff --git a/docs/configuration/policy/examples.md b/docs/configuration/policy/examples.md
index 992aa82c..926949c0 100644
--- a/docs/configuration/policy/examples.md
+++ b/docs/configuration/policy/examples.md
@@ -93,7 +93,7 @@ Routing tables that will be used in this example are:
 - `main` Routing table used by VyOS and other interfaces not
   participating in PBR
 
-:::{figure} /_static/images/pbr_example_1.png
+:::{figure} /_static/images/pbr_example_1.webp
 :alt: PBR multiple uplinks
 :scale: 80 %
 
diff --git a/docs/configuration/protocols/pim.md b/docs/configuration/protocols/pim.md
index 1768be72..30f3d49b 100644
--- a/docs/configuration/protocols/pim.md
+++ b/docs/configuration/protocols/pim.md
@@ -257,7 +257,7 @@ source-specific multicast).
 
 In the following example we can see a basic multicast setup:
 
-```{image} /_static/images/multicast-basic.png
+```{image} /_static/images/multicast-basic.webp
 :align: center
 :alt: Network Topology Diagram
 :width: 90%
diff --git a/docs/configuration/service/conntrack-sync.md b/docs/configuration/service/conntrack-sync.md
index d82459df..d35007ff 100644
--- a/docs/configuration/service/conntrack-sync.md
+++ b/docs/configuration/service/conntrack-sync.md
@@ -244,7 +244,7 @@ can be restored before conntrack state is purged.
 
 The next example is a simple configuration of conntrack-sync.
 
-:::{figure} /_static/images/service_conntrack_sync-schema.png
+:::{figure} /_static/images/service_conntrack_sync-schema.webp
 :alt: Conntrack Sync Example
 :scale: 60 %
 :::
diff --git a/docs/configuration/service/dhcp-relay.md b/docs/configuration/service/dhcp-relay.md
index 4bbee82b..d5f12b5e 100644
--- a/docs/configuration/service/dhcp-relay.md
+++ b/docs/configuration/service/dhcp-relay.md
@@ -100,7 +100,7 @@ uplink to the DHCP server.
 - Router receives DHCP client requests on `eth1` and relays them to the
   server at 10.0.1.4 on `eth2`.
 
-:::{figure} /_static/images/service_dhcp-relay01.png
+:::{figure} /_static/images/service_dhcp-relay01.webp
 :alt: DHCP relay example
 :scale: 80 %
 
@@ -195,7 +195,7 @@ show service dhcp-relay
 - Requests are forwarded through `eth2` as the `upstream interface`
 - External DHCPv6 server is at 2001:db8::4
 
-:::{figure} /_static/images/service_dhcpv6-relay01.png
+:::{figure} /_static/images/service_dhcpv6-relay01.webp
 :alt: DHCPv6 relay example
 :scale: 80 %
 
diff --git a/docs/configuration/service/snmp.md b/docs/configuration/service/snmp.md
index c4976318..e64a6b3b 100644
--- a/docs/configuration/service/snmp.md
+++ b/docs/configuration/service/snmp.md
@@ -53,7 +53,7 @@ managed devices. NMSs provide the bulk of the processing and memory resources
 required for network management. One or more NMSs may exist on any managed
 network.
 
-:::{figure} /_static/images/service_snmp_communication_principles_diagram.png
+:::{figure} /_static/images/service_snmp_communication_principles_diagram.webp
 :alt: Principle of SNMP Communication
 :scale: 20 %
 
diff --git a/docs/configuration/vpn/dmvpn.md b/docs/configuration/vpn/dmvpn.md
index 4d1525ad..79a6af7b 100644
--- a/docs/configuration/vpn/dmvpn.md
+++ b/docs/configuration/vpn/dmvpn.md
@@ -27,7 +27,7 @@ complete solution also incorporates the use of a routing protocol. BGP is
 particularly well suited for use with DMVPN.
 :::
 
-:::{figure} /_static/images/vpn_dmvpn_topology01.png
+:::{figure} /_static/images/vpn_dmvpn_topology01.webp
 :alt: Baseline DMVPN topology
 :scale: 40 %
 
@@ -186,7 +186,7 @@ This blueprint uses VyOS as the DMVPN Hub and Cisco (7206VXR) and VyOS as
 multiple spoke sites. The lab was built using {abbr}`EVE-NG (Emulated Virtual
 Environment NG)`.
 
-:::{figure} /_static/images/blueprint-dmvpn.png
+:::{figure} /_static/images/blueprint-dmvpn.webp
 :alt: DMVPN network
 
 DMVPN example network
diff --git a/docs/configuration/vpn/ipsec/ipsec_general.md b/docs/configuration/vpn/ipsec/ipsec_general.md
index ff8ac76e..6ff176fc 100644
--- a/docs/configuration/vpn/ipsec/ipsec_general.md
+++ b/docs/configuration/vpn/ipsec/ipsec_general.md
@@ -29,7 +29,7 @@ There are two IPsec modes:
     another IP datagram, and an IPsec header (AH or ESP) is
     inserted between the outer and inner headers.
 
-:::{figure} /_static/images/ESP_AH.png
+:::{figure} /_static/images/ESP_AH.webp
 :alt: AH and ESP in Transport Mode and Tunnel Mode
 :scale: 80 %
 :::
diff --git a/docs/configuration/vpn/ipsec/site2site_ipsec.md b/docs/configuration/vpn/ipsec/site2site_ipsec.md
index b813380f..153748f1 100644
--- a/docs/configuration/vpn/ipsec/site2site_ipsec.md
+++ b/docs/configuration/vpn/ipsec/site2site_ipsec.md
@@ -178,7 +178,7 @@ The result of wrong value selection can be unstable work of the VPN.
 Below flow-chart could be a quick reference for the close-action
 combination depending on how the peer is configured.
 
-:::{figure} /_static/images/IPSec_close_action_settings.png
+:::{figure} /_static/images/IPSec_close_action_settings.webp
 :::
 
 Similar combinations are applicable for the dead-peer-detection.
diff --git a/docs/configuration/vrf/index.md b/docs/configuration/vrf/index.md
index a9100ada..3c5ed2bc 100644
--- a/docs/configuration/vrf/index.md
+++ b/docs/configuration/vrf/index.md
@@ -273,7 +273,7 @@ For VRF maintenance the following operational commands are in place.
 
 The following example topology was built using EVE-NG.
 
-:::{figure} /_static/images/vrf-example-topology-01.png
+:::{figure} /_static/images/vrf-example-topology-01.webp
 :alt: VRF topology example
 
 VRF route leaking
diff --git a/docs/installation/cloud/gcp.md b/docs/installation/cloud/gcp.md
index 7144f083..495a912e 100644
--- a/docs/installation/cloud/gcp.md
+++ b/docs/installation/cloud/gcp.md
@@ -32,13 +32,13 @@ This is because the default user in the VyOS image is `vyos`, and the Google Clo
 2. Open GCP console and navigate to the **Compute Engine** > **Metadata** > **SSH Keys**. Choose
    **SSH Keys**.
 
-:::{figure} /_static/images/cloud-gcp-01.png
+:::{figure} /_static/images/cloud-gcp-01.webp
 :::
 
 3. Click **edit** and **Add item**.
 4. Paste your public ssh key and **Save**.
 
-:::{figure} /_static/images/cloud-gcp-02.png
+:::{figure} /_static/images/cloud-gcp-02.webp
 :::
 
 For more information, please visit the official Google Cloud documentation:
diff --git a/docs/installation/install.md b/docs/installation/install.md
index a02b3292..fb242046 100644
--- a/docs/installation/install.md
+++ b/docs/installation/install.md
@@ -54,7 +54,7 @@ include LTS (Long-Term Support), the associated hot-fix releases, early public
 access releases, pre-built VM images, as well as device specific installation
 ISOs. See this [article] for more information on downloads.
 
-:::{figure} /_static/images/vyosnew-downloads.png
+:::{figure} /_static/images/vyosnew-downloads.webp
 :::
 
 ### Rolling Release
diff --git a/docs/installation/virtual/gns3.md b/docs/installation/virtual/gns3.md
index d903c9a4..508bd4fc 100644
--- a/docs/installation/virtual/gns3.md
+++ b/docs/installation/virtual/gns3.md
@@ -28,56 +28,56 @@ in GNS3.
 Go to the GNS3 **File** menu, click **New template** and choose select
 **Manually create a new Template**.
 
-:::{figure} /_static/images/gns3-01.png
+:::{figure} /_static/images/gns3-01.webp
 :::
 
 Select **Quemu VMs** and then click on the `New` button.
 
-:::{figure} /_static/images/gns3-02.png
+:::{figure} /_static/images/gns3-02.webp
 :::
 
 Write a name for your VM, for instance "VyOS", and click `Next`.
 
-:::{figure} /_static/images/gns3-03.png
+:::{figure} /_static/images/gns3-03.webp
 :::
 
 Select **qemu-system-x86_64** as Quemu binary, then **512MB** of RAM
 and click `Next`.
 
-:::{figure} /_static/images/gns3-04.png
+:::{figure} /_static/images/gns3-04.webp
 :::
 
 Select **telnet** as your console type and click `Next`.
 
-:::{figure} /_static/images/gns3-05.png
+:::{figure} /_static/images/gns3-05.webp
 :::
 
 Select **New image** for the base disk image of your VM and click
 `Create`.
 
-:::{figure} /_static/images/gns3-06.png
+:::{figure} /_static/images/gns3-06.webp
 :::
 
 Use the defaults in the **Binary and format** window and click
 `Next`.
 
-:::{figure} /_static/images/gns3-07.png
+:::{figure} /_static/images/gns3-07.webp
 :::
 
 Use the defaults in the **Qcow2 options** window and click `Next`.
 
-:::{figure} /_static/images/gns3-08.png
+:::{figure} /_static/images/gns3-08.webp
 :::
 
 Set the disk size to 2000 MiB, and click `Finish` to end the **Quemu
 image creator**.
 
-:::{figure} /_static/images/gns3-09.png
+:::{figure} /_static/images/gns3-09.webp
 :::
 
 Click `Finish` to end the **New QEMU VM template** wizard.
 
-:::{figure} /_static/images/gns3-10.png
+:::{figure} /_static/images/gns3-10.webp
 :::
 
 Now the VM settings have to be edited.
@@ -85,7 +85,7 @@ Now the VM settings have to be edited.
 Being again at the **Preferences** window, having **Qemu VMs**
 selected and having our new VM selected, click the `Edit` button.
 
-:::{figure} /_static/images/gns3-11.png
+:::{figure} /_static/images/gns3-11.webp
 :::
 
 In the **General settings** tab of your **QEMU VM template
@@ -96,19 +96,19 @@ configuration**, do the following:
 - In **Category** select in which group you want to find your VM.
 - Set the **Boot priority** to **CD/DVD-ROM**.
 
-:::{figure} /_static/images/gns3-12.png
+:::{figure} /_static/images/gns3-12.webp
 :::
 
 At the **HDD** tab, change the Disk interface to **sata** to speed up
 the boot process.
 
-:::{figure} /_static/images/gns3-13.png
+:::{figure} /_static/images/gns3-13.webp
 :::
 
 At the **CD/DVD** tab click on `Browse...` and locate the VyOS image
 you want to install.
 
-:::{figure} /_static/images/gns3-14.png
+:::{figure} /_static/images/gns3-14.webp
 :::
 
 :::{note}
@@ -120,19 +120,19 @@ In the **Network** tab, set **0** as the number of adapters, set the
 **Name format** to **eth\{0}** and the **Type** to **Paravirtualized
 Network I/O (virtio-net-pci)**.
 
-:::{figure} /_static/images/gns3-15.png
+:::{figure} /_static/images/gns3-15.webp
 :::
 
 In the **Advanced** tab, unmark the checkbox **Use as a linked base
 VM** and click `OK`, which will save and close the **QEMU VM template
 configuration** window.
 
-:::{figure} /_static/images/gns3-16.png
+:::{figure} /_static/images/gns3-16.webp
 :::
 
 At the general **Preferences** window, click `OK` to save and close.
 
-:::{figure} /_static/images/gns3-17.png
+:::{figure} /_static/images/gns3-17.webp
 :::
 
 (vyos-installation)=
@@ -164,24 +164,24 @@ necessary as outlined below:
 
 **General settings** tab: Set the boot priority to **HDD**
 
-:::{figure} /_static/images/gns3-20.png
+:::{figure} /_static/images/gns3-20.webp
 :::
 
 **CD/DVD** tab: Unmount the installation image file by clearing the
 **Image** entry field.
 
-:::{figure} /_static/images/gns3-21.png
+:::{figure} /_static/images/gns3-21.webp
 :::
 
 Set the number of required network adapters, for example **4**.
 
-:::{figure} /_static/images/gns3-215.png
+:::{figure} /_static/images/gns3-215.webp
 :::
 
 **Advanced** settings tab: Mark the checkbox **Use as a linked
 base VM** and click `OK` to save the changes.
 
-:::{figure} /_static/images/gns3-22.png
+:::{figure} /_static/images/gns3-22.webp
 :::
 
 The VyOS VM is now ready to be deployed.
diff --git a/docs/installation/virtual/libvirt.md b/docs/installation/virtual/libvirt.md
index 5acefd43..5a7ba6a7 100644
--- a/docs/installation/virtual/libvirt.md
+++ b/docs/installation/virtual/libvirt.md
@@ -104,32 +104,32 @@ machines through libvirt. On the linux open
    {abbr}`VM (Virtual Machine)`
 2. Choose `Local install media` (ISO)
 
-:::{figure} /_static/images/virt-libvirt-01.png
+:::{figure} /_static/images/virt-libvirt-01.webp
 :::
 
 3. Choose path to iso vyos.iso. Operating System can be any Debian based.
 
-:::{figure} /_static/images/virt-libvirt-02.png
+:::{figure} /_static/images/virt-libvirt-02.webp
 :::
 
 4. Choose Memory and CPU
 
-:::{figure} /_static/images/virt-libvirt-03.png
+:::{figure} /_static/images/virt-libvirt-03.webp
 :::
 
 5. Disk size
 
-:::{figure} /_static/images/virt-libvirt-04.png
+:::{figure} /_static/images/virt-libvirt-04.webp
 :::
 
 6. Name of VM and network selection
 
-:::{figure} /_static/images/virt-libvirt-05.png
+:::{figure} /_static/images/virt-libvirt-05.webp
 :::
 
 7. Then you will be taken to the console.
 
-:::{figure} /_static/images/virt-libvirt-06.png
+:::{figure} /_static/images/virt-libvirt-06.webp
 :::
 
 (libvirt-virt-manager-qcow2)=
@@ -146,26 +146,26 @@ curl --url link_to_vyos_kvm.qcow2 --output /var/lib/libvirt/images/vyos_kvm.qcow
    {abbr}`VM (Virtual Machine)`
 2. Choose `Import existing disk` image
 
-:::{figure} /_static/images/virt-libvirt-qc-01.png
+:::{figure} /_static/images/virt-libvirt-qc-01.webp
 :::
 
 3. Choose the path to the image `vyos_kvm.qcow2` that was previously
    downloaded . Operation System can be any Debian based.
 
-:::{figure} /_static/images/virt-libvirt-qc-02.png
+:::{figure} /_static/images/virt-libvirt-qc-02.webp
 :::
 
 4. Choose Memory and CPU
 
-:::{figure} /_static/images/virt-libvirt-03.png
+:::{figure} /_static/images/virt-libvirt-03.webp
 :::
 
 5. Name of VM and network selection
 
-:::{figure} /_static/images/virt-libvirt-05.png
+:::{figure} /_static/images/virt-libvirt-05.webp
 :::
 
 6. Then you will be taken to the console.
 
-:::{figure} /_static/images/virt-libvirt-qc-03.png
+:::{figure} /_static/images/virt-libvirt-qc-03.webp
 :::
diff --git a/docs/installation/vyos-on-baremetal.md b/docs/installation/vyos-on-baremetal.md
index b551a811..c5d40cc5 100644
--- a/docs/installation/vyos-on-baremetal.md
+++ b/docs/installation/vyos-on-baremetal.md
@@ -32,47 +32,47 @@ motherboard).
 
 ### Pictures
 
-:::{figure} /_static/images/1u_vyos_back.jpg
+:::{figure} /_static/images/1u_vyos_back.webp
 :alt: CSE-505-203B Back
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front.jpg
+:::{figure} /_static/images/1u_vyos_front.webp
 :alt: CSE-505-203B Front
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front_open_1.jpg
+:::{figure} /_static/images/1u_vyos_front_open_1.webp
 :alt: CSE-505-203B Open 1
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front_open_2.jpg
+:::{figure} /_static/images/1u_vyos_front_open_2.webp
 :alt: CSE-505-203B Open 2
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front_open_3.jpg
+:::{figure} /_static/images/1u_vyos_front_open_3.webp
 :alt: CSE-505-203B Open 3
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front_10ge_open_1.jpg
+:::{figure} /_static/images/1u_vyos_front_10ge_open_1.webp
 :alt: CSE-505-203B w/ 10GE Open 1
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front_10ge_open_2.jpg
+:::{figure} /_static/images/1u_vyos_front_10ge_open_2.webp
 :alt: CSE-505-203B w/ 10GE Open 2
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front_10ge_open_3.jpg
+:::{figure} /_static/images/1u_vyos_front_10ge_open_3.webp
 :alt: CSE-505-203B w/ 10GE Open 3
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/1u_vyos_front_10ge_open_4.jpg
+:::{figure} /_static/images/1u_vyos_front_10ge_open_4.webp
 :alt: CSE-505-203B w/ 10GE Open
 :scale: 25 %
 :::
@@ -198,56 +198,56 @@ noise.
 
 #### Rack Mount
 
-:::{figure} /_static/images/apu4_rack_1.jpg
+:::{figure} /_static/images/apu4_rack_1.webp
 :alt: APU4 rack closed
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/apu4_rack_2.jpg
+:::{figure} /_static/images/apu4_rack_2.webp
 :alt: APU4 rack front
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/apu4_rack_3.jpg
+:::{figure} /_static/images/apu4_rack_3.webp
 :alt: 'APU4 rack module #1'
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/apu4_rack_4.jpg
+:::{figure} /_static/images/apu4_rack_4.webp
 :alt: 'APU4 rack module #2'
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/apu4_rack_5.jpg
+:::{figure} /_static/images/apu4_rack_5.webp
 :alt: 'APU4 rack module #3 with PSU'
 :scale: 25 %
 :::
 
 ##### VyOS custom print
 
-:::{figure} /_static/images/apu4_rack_vyos_print.jpg
+:::{figure} /_static/images/apu4_rack_vyos_print.webp
 :alt: APU4 custom VyOS powder coat
 :scale: 25 %
 :::
 
 #### Desktop / Bench Top
 
-:::{figure} /_static/images/apu4_desk_1.jpg
+:::{figure} /_static/images/apu4_desk_1.webp
 :alt: APU4 desktop closed
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/apu4_desk_2.jpg
+:::{figure} /_static/images/apu4_desk_2.webp
 :alt: APU4 desktop closed
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/apu4_desk_3.jpg
+:::{figure} /_static/images/apu4_desk_3.webp
 :alt: APU4 desktop back
 :scale: 25 %
 :::
 
-:::{figure} /_static/images/apu4_desk_4.jpg
+:::{figure} /_static/images/apu4_desk_4.webp
 :alt: APU4 desktop back
 :scale: 25 %
 :::
@@ -303,7 +303,7 @@ HDMI mode.
 
 ## Partaker i5
 
-:::{figure} ../_static/images/600px-Partaker-i5.jpg
+:::{figure} ../_static/images/600px-Partaker-i5.webp
 :::
 
 I believe this is actually the same hardware as the Protectli. I purchased it
@@ -328,10 +328,10 @@ port is eth0 and the right-most "LAN1" port is eth3.
 
 ## Acrosser AND-J190N1
 
-:::{figure} ../_static/images/480px-Acrosser_ANDJ190N1_Front.jpg
+:::{figure} ../_static/images/480px-Acrosser_ANDJ190N1_Front.webp
 :::
 
-:::{figure} ../_static/images/480px-Acrosser_ANDJ190N1_Back.jpg
+:::{figure} ../_static/images/480px-Acrosser_ANDJ190N1_Back.webp
 :::
 
 This microbox network appliance was build to create OpenVPN bridges. It can
@@ -398,16 +398,16 @@ i3-N305 CPU and 2x 25GbE!
 
 ### Pictures
 
-:::{figure} ../_static/images/gowin-01.png
+:::{figure} ../_static/images/gowin-01.webp
 :::
 
-:::{figure} ../_static/images/gowin-02.png
+:::{figure} ../_static/images/gowin-02.webp
 :::
 
-:::{figure} ../_static/images/gowin-03.png
+:::{figure} ../_static/images/gowin-03.webp
 :::
 
-:::{figure} ../_static/images/gowin-04.png
+:::{figure} ../_static/images/gowin-04.webp
 :::
 
 ### Cooling
diff --git a/docs/operation/boot-options.md b/docs/operation/boot-options.md
index ea077c8a..810bc08a 100644
--- a/docs/operation/boot-options.md
+++ b/docs/operation/boot-options.md
@@ -14,7 +14,7 @@ To add an option, select the desired image in GRUB menu at load
 time, press **e**, edit the first line, and press **Ctrl-x** to boot when
 ready.
 
-```{image} /_static/images/boot-options.png
+```{image} /_static/images/boot-options.webp
 :align: center
 :width: 80%
 ```