ArduPilot · Hwurzburg · Nov 2, 2024 · Nov 1, 2024
diff --git a/common/source/docs/common-esp8266-telemetry.rst b/common/source/docs/common-esp8266-telemetry.rst
@@ -66,8 +66,8 @@ If you are using the Adafruit HUZZAH ESP8266 board and are flashing from a Windo
   - on the Config page push the gear and select the firmware downloaded above
   - on the Operation page select the "COM Port" and push the "Flash" button.  If successful the blue bar will slowly stretch from left to right and the icon on the bottom left will turn green.
 
-    .. image:: ../../../images/esp8266-telemetry-flash.jpg
-        :target: ../_images/esp8266-telemetry-flash.jpg
+    .. image:: ../../../images/esp8266-telemetry-flash.png
+        :target: ../_images/esp8266-telemetry-flash.png
 
 - Mac users should use the `esptool <https://github.com/espressif/esptool>`__
 

diff --git a/common/source/docs/common-foxeerh743v1.rst b/common/source/docs/common-foxeerh743v1.rst
@@ -5,7 +5,7 @@ Foxeer H7 MPU6000
 =================
 
 
-.. image:: ../../../images/foxeerh743.jpg
+.. image:: ../../../images/foxeerh743.png
 
 
 Where to Buy

diff --git a/common/source/docs/common-holybro-kakutef7aio.rst b/common/source/docs/common-holybro-kakutef7aio.rst
@@ -4,8 +4,8 @@
 Holybro Kakute F7 and KAKUTE F7 AIO
 ===================================
 
-.. image:: ../../../images/holybro-kakutef7aio.png
-    :target: ../_images/holybro-kakutef7aio.png
+.. image:: ../../../images/holybro-kakutef7aio.jpg
+    :target: ../_images/holybro-kakutef7aio.jpg
 
 *above image and some content courtesy of* `Holybro <http://www.holybro.com/product/kakute-f7-aio-v1-5/>`__
 

diff --git a/common/source/docs/common-imutempcal.rst b/common/source/docs/common-imutempcal.rst
@@ -146,11 +146,11 @@ graphs. One set is for the gyroscopes the other is for the accelerometers.
 
 The image below shows the results of a run on a log file for 3 IMU board:
 
-.. image:: ../../../images/tempcal_gyro.jpg
-    :target: ../_images/tempcal_gyro.jpg
+.. image:: ../../../images/tempcal_gyro.png
+    :target: ../_images/tempcal_gyro.png
 
-.. image:: ../../../images/tempcal_accel.jpg
-    :target: ../_images/tempcal_accel.jpg
+.. image:: ../../../images/tempcal_accel.png
+    :target: ../_images/tempcal_accel.png
 
 The key features of the graphs are:
 

diff --git a/common/source/docs/common-makeflyeasy-PixSurveyA2.rst b/common/source/docs/common-makeflyeasy-PixSurveyA2.rst
@@ -4,8 +4,8 @@
 makeflyeasy PixSurveyA2
 =======================
 
-.. figure:: ../../../images/PixSurveyA2.png
-   :target: ../_images/PixSurveyA2.png
+.. figure:: ../../../images/PixSurveyA2.jpg
+   :target: ../_images/PixSurveyA2.jpg
    :width: 450px
 
 
@@ -367,4 +367,4 @@ Where to Buy
 
 `makeflyeasy <https://www.makeflyeasy.com>`_
 
-[copywiki destination="plane,copter,rover,blimp"]
+[copywiki destination="plane,copter,rover,blimp"]
diff --git a/common/source/docs/common-mission-planner-gps-based-antenna-tracking.rst b/common/source/docs/common-mission-planner-gps-based-antenna-tracking.rst
@@ -351,8 +351,8 @@ Planner window. I'll then right click and say Tracker Home -> Set here.
 it. That should get me pretty close to where my antenna tracker is
 placed.*
 
-.. image:: ../../../images/mp_gps_antennatracker_10.png
-    :target: ../_images/mp_gps_antennatracker_10.png
+.. image:: ../../../images/mp_gps_antennatracker_10.jpg
+    :target: ../_images/mp_gps_antennatracker_10.jpg
 
 *After that I'll flip over to the Initial Setup tab under Antenna
 Tracker and pull down the COM port for the Pololu servo controller and

diff --git a/common/source/docs/common-msp-osd-overview-4.2.rst b/common/source/docs/common-msp-osd-overview-4.2.rst
@@ -275,8 +275,8 @@ A graphical DJI style MSP OSD simulation in a separate window will be opened wit
 .. image:: ../../../images/msp_osd_python.png
    :target: ../_images/msp_osd_python.png
 
-.. image:: ../../../images/msp_osd_python_stats.png
-   :target: ../_images/msp_osd_python_stats.png
+.. image:: ../../../images/msp_osd_python_stats.jpg
+   :target: ../_images/msp_osd_python_stats.jpg
 
 By changing the OSD panel items' parameters, a live update of their placement can be seen in this emulator.
 

diff --git a/common/source/docs/common-multiplex-rc.rst b/common/source/docs/common-multiplex-rc.rst
@@ -10,8 +10,8 @@ Multiplex RC System
 
 For a **MULTIPLEX SRXL** receiver, connect the **SPKT/DSM** port of the Pixhawk to the **B/D** port of the MULTIPLEX SRXL receiver, without using the +3,3V voltage supplied at the **SPKT/DSM** port of the Pixhawk and power the MULTIPLEX SRXL receiver separately. Note that you may also connect to the RCin pin or any appropriately configured serial port, See :ref:`common-flight-controller-wiring` 
 
-.. image:: ../../../images/multiplex_srxl_B_D_port_to_pixhawk_spkt_dsm_pinout.jpg
-    :target: ../_images/multiplex_srxl_B_D_port_to_pixhawk_spkt_dsm_pinout.jpg
+.. image:: ../../../images/multiplex_srxl_B_D_port_to_pixhawk_spkt_dsm_pinout.png
+    :target: ../_images/multiplex_srxl_B_D_port_to_pixhawk_spkt_dsm_pinout.png
 
 Details how to enable the SRXL signal on MULTIPLEX receivers can be found in:
 

diff --git a/common/source/docs/common-partners.rst b/common/source/docs/common-partners.rst
@@ -577,7 +577,7 @@ Details on the Partners Program and how to join can be found on the :doc:`Partne
             :align: center
             :target:  https://www.sdmodel.com.tw/
 
-      - .. image:: ../../../images/supporters/supporters_adti.jpg
+      - .. image:: ../../../images/supporters/supporters_adti.png
             :width: 250px
             :align: center
             :target:  https://www.adti.camera/
@@ -742,7 +742,7 @@ Details on the Partners Program and how to join can be found on the :doc:`Partne
             :align: center
             :target:  https://dh-research.com/
 
-      - .. image:: ../../../images/supporters/supporters_micoair.png
+      - .. image:: ../../../images/supporters/supporters_micoair.jpg
             :width: 250px
             :align: center
             :target:  https://micoair.com/

diff --git a/common/source/docs/common-speedybeef405wing.rst b/common/source/docs/common-speedybeef405wing.rst
@@ -87,8 +87,8 @@ User Manual
 Wiring Diagram
 ==============
 
-.. image:: ../../../images/SpeedyBeeF405WING_wiring.png
-    :target: ../_images/SpeedyBeeF405WING_wiring.png
+.. image:: ../../../images/SpeedyBeeF405WING_wiring.jpg
+    :target: ../_images/SpeedyBeeF405WING_wiring.jpg
 
 
 Default UART order

diff --git a/common/source/docs/common-srxl-receivers.rst b/common/source/docs/common-srxl-receivers.rst
@@ -68,18 +68,18 @@ To do the configuration follow the following steps:
 - Start the MULTIPLEX Launcher Software and connect PC-cable # 85149 to the PC.
 - MULTIPLEX Launcher will detect the connected device automatically and will open the “RX/RF DataManager”-Window.
 
-.. image:: ../../../images/Multiplex_Launcher_01.jpg
-    :target: ../_images/Multiplex_Launcher_01.jpg
+.. image:: ../../../images/Multiplex_Launcher_01.png
+    :target: ../_images/Multiplex_Launcher_01.png
 
 - In the “RX/RF DataManager”-Window click “Options” and the “RX Options”-Window will be opened.
 
-.. image:: ../../../images/Multiplex_Launcher_02.jpg
-    :target: ../_images/Multiplex_Launcher_02.jpg
+.. image:: ../../../images/Multiplex_Launcher_02.png
+    :target: ../_images/Multiplex_Launcher_02.png
 
 - In the “RX-Options” Window scroll down to “More Settings”. In the “More Settings” section double-click “* Options…” to open the “More setting”-Window and select “Serial servodata SRXL” as data output at B/D port. Close the “More setting”-Windows by clicking “Accept”.
 
-.. image:: ../../../images/Multiplex_Launcher_03.jpg
-    :target: ../_images/Multiplex_Launcher_03.jpg
+.. image:: ../../../images/Multiplex_Launcher_03.png
+    :target: ../_images/Multiplex_Launcher_03.png
 
 - Upload data to the receiver by clicking “Send data” in the “RX Options”-Window.
 
@@ -92,5 +92,5 @@ To do the configuration follow the following steps:
 - Connect receivers to the autopilot as described :ref:`here <common-rc-systems>`.
 - Test and adjust servo channel assignments in Mission planner if required. MULTIPLEX radios without free servo assignment (e.g. Cockpit SX) have the following standard servo assignment:
 
-.. image:: ../../../images/Multiplex_SRXL_Receivers_Standard_Servo_Assignment.jpg
-    :target: ../_images/Multiplex_SRXL_Receivers_Standard_Servo_Assignment.jpg
+.. image:: ../../../images/Multiplex_SRXL_Receivers_Standard_Servo_Assignment.png
+    :target: ../_images/Multiplex_SRXL_Receivers_Standard_Servo_Assignment.png
diff --git a/common/source/docs/common-thecube-overview.rst b/common/source/docs/common-thecube-overview.rst
@@ -63,8 +63,8 @@ The Cube connector pin assignments
 ==================================
 This section details the pin assignments of the standard carrier board of The Cube. There are other types of carrier boards available, please refer to the manufacturer pages for pinouts of specific carrier board.
 
-.. image:: ../../../images/thecube/pixhawk2-pinout.jpg
-    :target: ../_images/pixhawk2-pinout.jpg
+.. image:: ../../../images/thecube/pixhawk2-pinout.png
+    :target: ../_images/pixhawk2-pinout.png
     :width: 240px
 
 **TELEM1, TELEM2 ports**

diff --git a/common/source/docs/common-vio-tracking-camera.rst b/common/source/docs/common-vio-tracking-camera.rst
@@ -36,8 +36,8 @@ Hardware Setup
 - Connect the PiConnectLite's power cable to the battery (7V to 30V)
 - Connect the PiConnectLite's serial cable to one of the autopilot's telemetry ports (i.e. Telem1, Telem2). The only signals used in this cable are TX, RX and GND. The other signals are NC.
 
-.. image:: ../../../images/t265-mount.png
-    :target: ../_images/t265-mount.png
+.. image:: ../../../images/t265-mount.jpg
+    :target: ../_images/t265-mount.jpg
     :width: 500px
 
 `David Sastre's T265 mount <https://www.dropbox.com/s/e3ias30czsn2q4t/Intel_RealSense_Tracking_Camera_T265_holder.STL?dl=0>`__

diff --git a/dev/source/docs/ros.rst b/dev/source/docs/ros.rst
@@ -13,8 +13,8 @@ ArduPilot capabilities can be extended with `ROS <http://www.ros.org/>`__ (aka R
 ROS1 is being replaced by `ROS 2 <http://design.ros2.org/articles/why_ros2.html>`__
 
 
-.. image:: ../images/logos/ros2_logo.jpg
-    :target: ../_images/logos/ros2_logo.jpg
+.. image:: ../images/logos/ros2_logo.png
+    :target: ../_images/logos/ros2_logo.png
 
 The tutorials below are split between ROS 1 and ROS 2.
 If you aren't sure which version to use, the ArduPilot development team recommends ROS 2 because ROS 1 is end-of-life in 2025.

diff --git a/dev/source/docs/ros2.rst b/dev/source/docs/ros2.rst
@@ -4,8 +4,8 @@
 ROS 2
 =====
 
-.. image:: ../images/logos/ros2_logo.jpg
-    :target: ../_images/logos/ros2_logo.jpg
+.. image:: ../images/logos/ros2_logo.png
+    :target: ../_images/logos/ros2_logo.png
 
 ArduPilot capabilities can be extended with `ROS <http://www.ros.org/>`__ (aka Robot Operating System).
 

diff --git a/dev/source/docs/sitl-with-morse.rst b/dev/source/docs/sitl-with-morse.rst
@@ -83,8 +83,8 @@ The following steps will get you running with the Skid Rover example.
 
 - A window like below should appear:
 
-  .. image:: ../images/morse_rover_sitl.jpg
-    :target: ../_images/morse_rover_sitl.jpg
+  .. image:: ../images/morse_rover_sitl.png
+    :target: ../_images/morse_rover_sitl.png
 
 - Use the ArduPilot SITL console to control the vehicle (i.e. "arm throttle" to arm the vehicle, "rc 3 1800" to raise throttle to 80%, etc)
 
@@ -119,8 +119,8 @@ To run the Quadcopter example:
 
 - A window like below should appear:
 
-  .. image:: ../images/morse_quad.jpg
-    :target: ../_images/morse_quad.jpg
+  .. image:: ../images/morse_quad.png
+    :target: ../_images/morse_quad.png
 
 Note that in the image above a wire-frame view is shown instead of a
 rendered 3D view. That is configured by setting fastmode=True in the

diff --git a/dev/source/docs/sitl-with-xplane.rst b/dev/source/docs/sitl-with-xplane.rst
@@ -59,8 +59,8 @@ default). If using loopback (ie. 127.0.0.1) then you also need to make
 sure the "port that we send from" is not 49001. In the example below
 49002 is used.
 
-.. figure:: ../images/xplane-network-data.jpg
-   :target: ../_images/xplane-network-data.jpg
+.. figure:: ../images/xplane-network-data.png
+   :target: ../_images/xplane-network-data.png
 
 You will also need to output data from X-Plane. Click on *Settings*, then *Data Input & Output*. Copy at least 1 setting from the screenshot below. ArduPilot will then send commands to X-Plane that will enable all of the output data fields that it needs to operate.
 

diff --git a/dev/source/images/logos/ros2_logo.jpg → dev/source/images/logos/ros2_logo.png b/dev/source/images/logos/ros2_logo.jpg → dev/source/images/logos/ros2_logo.png
diff --git a/dev/source/images/morse_quad.jpg → dev/source/images/morse_quad.png b/dev/source/images/morse_quad.jpg → dev/source/images/morse_quad.png
diff --git a/dev/source/images/morse_rover_sitl.jpg → dev/source/images/morse_rover_sitl.png b/dev/source/images/morse_rover_sitl.jpg → dev/source/images/morse_rover_sitl.png
diff --git a/dev/source/images/xplane-network-data.jpg → dev/source/images/xplane-network-data.png b/dev/source/images/xplane-network-data.jpg → dev/source/images/xplane-network-data.png
diff --git a/images/Multiplex_Launcher_01.jpg → images/Multiplex_Launcher_01.png b/images/Multiplex_Launcher_01.jpg → images/Multiplex_Launcher_01.png
diff --git a/images/Multiplex_Launcher_02.jpg → images/Multiplex_Launcher_02.png b/images/Multiplex_Launcher_02.jpg → images/Multiplex_Launcher_02.png
diff --git a/images/Multiplex_Launcher_03.jpg → images/Multiplex_Launcher_03.png b/images/Multiplex_Launcher_03.jpg → images/Multiplex_Launcher_03.png
diff --git a/...L_Receivers_Standard_Servo_Assignment.jpg → ...L_Receivers_Standard_Servo_Assignment.png b/...L_Receivers_Standard_Servo_Assignment.jpg → ...L_Receivers_Standard_Servo_Assignment.png
diff --git a/images/PixSurveyA2.png → images/PixSurveyA2.jpg b/images/PixSurveyA2.png → images/PixSurveyA2.jpg
diff --git a/images/SpeedyBeeF405WING_wiring.png → images/SpeedyBeeF405WING_wiring.jpg b/images/SpeedyBeeF405WING_wiring.png → images/SpeedyBeeF405WING_wiring.jpg
diff --git a/images/dronecode-logo.jpg → images/dronecode-logo.png b/images/dronecode-logo.jpg → images/dronecode-logo.png
diff --git a/images/esp8266-telemetry-flash.jpg → images/esp8266-telemetry-flash.png b/images/esp8266-telemetry-flash.jpg → images/esp8266-telemetry-flash.png
diff --git a/images/foxeerh743.jpg → images/foxeerh743.png b/images/foxeerh743.jpg → images/foxeerh743.png
diff --git a/images/holybro-kakutef7aio.png → images/holybro-kakutef7aio.jpg b/images/holybro-kakutef7aio.png → images/holybro-kakutef7aio.jpg
diff --git a/images/mp_gps_antennatracker_10.png → images/mp_gps_antennatracker_10.jpg b/images/mp_gps_antennatracker_10.png → images/mp_gps_antennatracker_10.jpg
diff --git a/images/msp_osd_python_stats.png → images/msp_osd_python_stats.jpg b/images/msp_osd_python_stats.png → images/msp_osd_python_stats.jpg
diff --git a/...l_B_D_port_to_pixhawk_spkt_dsm_pinout.jpg → ...l_B_D_port_to_pixhawk_spkt_dsm_pinout.png b/...l_B_D_port_to_pixhawk_spkt_dsm_pinout.jpg → ...l_B_D_port_to_pixhawk_spkt_dsm_pinout.png
diff --git a/images/supporters/supporters_adti.jpg → images/supporters/supporters_adti.png b/images/supporters/supporters_adti.jpg → images/supporters/supporters_adti.png
diff --git a/images/supporters/supporters_micoair.png → images/supporters/supporters_micoair.jpg b/images/supporters/supporters_micoair.png → images/supporters/supporters_micoair.jpg
diff --git a/images/t265-mount.png → images/t265-mount.jpg b/images/t265-mount.png → images/t265-mount.jpg
diff --git a/images/tempcal_accel.jpg → images/tempcal_accel.png b/images/tempcal_accel.jpg → images/tempcal_accel.png
diff --git a/images/tempcal_gyro.jpg → images/tempcal_gyro.png b/images/tempcal_gyro.jpg → images/tempcal_gyro.png
diff --git a/images/thecube/pixhawk2-pinout.jpg → images/thecube/pixhawk2-pinout.png b/images/thecube/pixhawk2-pinout.jpg → images/thecube/pixhawk2-pinout.png
diff --git a/plane/source/docs/quadplane-auto-mode.rst b/plane/source/docs/quadplane-auto-mode.rst
@@ -95,8 +95,8 @@ within :ref:`RTL_RADIUS <RTL_RADIUS>` of the return point. That makes
 it easier to plan missions with a VTOL landing from anywhere in the
 flying area.
 
-.. image:: ../images/quadplane_RTL.jpg
-    :target: ../_images/quadplane_RTL.jpg
+.. image:: ../images/quadplane_RTL.png
+    :target: ../_images/quadplane_RTL.png
 
 Mixing VTOL and Fixed Wing Flight
 ---------------------------------
@@ -125,8 +125,8 @@ your quadplane will handle loiter commands in :ref:`GUIDED mode
 <guided-mode>` and in AUTO missions as a VTOL aircraft. For example, the
 following mission:
 
-.. image:: ../images/quadplane-loiter-time.jpg
-    :target: ../_images/quadplane-loiter-time.jpg
+.. image:: ../images/quadplane-loiter-time.png
+    :target: ../_images/quadplane-loiter-time.png
 
 the aircraft will pause while hovering for 10 seconds at
 waypoint 3. It will fly the rest of the mission as a fixed wing

diff --git a/...e/source/images/quadplane-loiter-time.jpg → ...e/source/images/quadplane-loiter-time.png b/...e/source/images/quadplane-loiter-time.jpg → ...e/source/images/quadplane-loiter-time.png
diff --git a/plane/source/images/quadplane_RTL.jpg → plane/source/images/quadplane_RTL.png b/plane/source/images/quadplane_RTL.jpg → plane/source/images/quadplane_RTL.png