diff --git a/docs/docs/configuration/camera_specific.md b/docs/docs/configuration/camera_specific.md
index c1b57658ca..a521468562 100644
--- a/docs/docs/configuration/camera_specific.md
+++ b/docs/docs/configuration/camera_specific.md
@@ -102,9 +102,14 @@ ffmpeg:
   input_args: -avoid_negative_ts make_zero -flags low_delay -strict experimental -fflags +genpts+discardcorrupt -rtsp_transport tcp -timeout 5000000 -use_wallclock_as_timestamps 1
 ```
 
-### Reolink 410/520 (possibly others)
+### Reolink Cameras
 
-![Resolutions](/img/reolink-settings.png)
+Reolink has older cameras (ex: 410 & 520) as well as newer camera (ex: 520a & 511wa) which support different subsets of options. In both cases using the http stream is recommended. 
+Frigate works much better with newer reolink cameras that are setup with the below options:
+
+If available, recommended settings are:
+- `On, fluency first` this sets the camera to CBR (constant bit rate)
+- `Interframe Space 1x` this sets the iframe interval to the same as the frame rate
 
 According to [this discussion](https://github.com/blakeblackshear/frigate/issues/3235#issuecomment-1135876973), the http video streams seem to be the most reliable for Reolink.
 
@@ -150,4 +155,4 @@ ffmpeg:
   output_args:
     record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -ar 44100 -c:a aac
     rtmp: -c:v copy -f flv -ar 44100 -c:a aac
-```
\ No newline at end of file
+```
diff --git a/docs/static/img/reolink-settings.png b/docs/static/img/reolink-settings.png
deleted file mode 100644
index ebb043f325..0000000000
Binary files a/docs/static/img/reolink-settings.png and /dev/null differ