diff --git a/documentation/asciidoc/computers/camera/csi-2-usage.adoc b/documentation/asciidoc/computers/camera/csi-2-usage.adoc
index 784d80478..8791dcc18 100644
--- a/documentation/asciidoc/computers/camera/csi-2-usage.adoc
+++ b/documentation/asciidoc/computers/camera/csi-2-usage.adoc
@@ -12,7 +12,7 @@ There are 3 independent software interfaces available for communicating with the
 
 NOTE: This interface is available only when using the legacy camera stack.
 
-The closed source GPU firmware has drivers for Unicam and three camera sensors plus a bridge chip. They are the Raspberry Pi Camera v1.3 (Omnivision OV5647), Raspberry Pi Camera v2.1 (Sony IMX219), Raspberry Pi HQ camera (Sony IMX477), and an unsupported driver for the Toshiba TC358743 HDMI\->CSI2 bridge chip.
+The closed source GPU firmware has drivers for Unicam and three camera sensors plus a bridge chip. They are the Raspberry Pi Camera v1.3 (Omnivision OV5647), Raspberry Pi Camera v2.1 (Sony IMX219), Raspberry Pi HQ camera (Sony IMX477), and an unsupported driver for the Toshiba TC358743 HDMI\->CSI2 bridge chip. There is no support for more recent cameras, such as the Camera Module 3 (Sony IMX708).
 
 This driver integrates the source driver, Unicam, ISP, and tuner control into a full camera stack delivering processed output images. It can be used via MMAL, OpenMAX IL and V4L2 using the bcm2835-v4l2 kernel module. Only Raspberry Pi cameras are supported via this interface.
 
@@ -64,6 +64,10 @@ Mainline Linux has a range of existing drivers. The Raspberry Pi kernel tree has
 | 12MP Camera
 | Raspberry Pi HQ camera
 
+| Sony IMX708
+| 12MP Camera
+| Raspberry Pi Camera Module 3
+
 | Toshiba TC358743
 | HDMI to CSI-2 bridge
 |
diff --git a/documentation/asciidoc/computers/camera/libcamera_apps_getting_started.adoc b/documentation/asciidoc/computers/camera/libcamera_apps_getting_started.adoc
index df9f58825..8d97c409d 100644
--- a/documentation/asciidoc/computers/camera/libcamera_apps_getting_started.adoc
+++ b/documentation/asciidoc/computers/camera/libcamera_apps_getting_started.adoc
@@ -45,6 +45,9 @@ If you do need to add your own `dtoverlay`, the following are currently recognis
 | HQ camera (IMX477)
 | `dtoverlay=imx477`
 
+| Camera Module 3 (IMX708)
+| `dtoverlay=imx708`
+
 | IMX290 and IMX327
 | `dtoverlay=imx290,clock-frequency=74250000` or `dtoverlay=imx290,clock-frequency=37125000` (both modules share the imx290 kernel driver; please refer to instructions from the module vendor for the correct frequency)
 
diff --git a/documentation/asciidoc/computers/camera/libcamera_apps_intro.adoc b/documentation/asciidoc/computers/camera/libcamera_apps_intro.adoc
index c6e1a081e..2fc148b44 100644
--- a/documentation/asciidoc/computers/camera/libcamera_apps_intro.adoc
+++ b/documentation/asciidoc/computers/camera/libcamera_apps_intro.adoc
@@ -27,7 +27,7 @@ Underneath the `libcamera` core, Raspberry Pi provides a custom _pipeline handle
 
 All this code is open source and now runs on the Raspberry Pi's ARM cores. There is only a very thin layer of code on the GPU which translates Raspberry Pi's own control parameters into register writes for the Broadcom ISP.
 
-Raspberry Pi's implementation of `libcamera` supports not only the three standard Raspberry Pi cameras (the OV5647 or V1 camera, the IMX219 or V2 camera and the IMX477 or HQ camera) but also third party senors such as the IMX290, IMX327, OV9281, IMX378. Raspberry Pi is keen to work with vendors who would like to see their sensors supported directly by `libcamera`.
+Raspberry Pi's implementation of `libcamera` supports not only the four standard Raspberry Pi cameras (the OV5647 or V1 camera, the IMX219 or V2 camera, the IMX477 or HQ camera and the IMX708 or Camera Module 3) but also third party senors such as the IMX290, IMX327, OV9281, IMX378. Raspberry Pi is keen to work with vendors who would like to see their sensors supported directly by `libcamera`.
 
 Moreover, Raspberry Pi supplies a _tuning file_ for each of these sensors which can be edited to change the processing performed by the Raspberry Pi hardware on the raw images received from the image sensor, including aspects like the colour processing, the amount of noise suppression or the behaviour of the control algorithms.