diff --git a/Fetching-pages-with-WebDriver.md b/Fetching-pages-with-WebDriver.md
index 248fc2e..4b4abba 100644
--- a/Fetching-pages-with-WebDriver.md
+++ b/Fetching-pages-with-WebDriver.md
@@ -1,2 +1,25 @@
 Javascript support / Fetching via WebDriver
 
+The backend can be configured to fetch pages via Chrome using the WebDriver network interface, this is mainly used where the pages you are watching are using Javascript to render the page content, The easiest way is to enable it is to uncomment the following in `docker-compose.yml` and restart your docker-compose. 
+
+**Note:** The `selenium/standalone-chrome-debug:3.141.59` image does **NOT** support ARM/RaspberryPi type devices, please don't make a support request that it does not work when rPi - it will be deleted.
+
+```
+#    browser-chrome:
+#        hostname: browser-chrome
+#        image: selenium/standalone-chrome-debug:3.141.59
+#       Doesnt need to be exposed on the host
+#        ports:
+#          - 4444:4444
+#        environment:
+#            - VNC_NO_PASSWORD=1
+#        volumes:
+#            # Workaround to avoid the browser crashing inside a docker container
+#            # See https://github.com/SeleniumHQ/docker-selenium#quick-start
+#            - /dev/shm:/dev/shm
+#        restart: unless-stopped
+```
+
+Then visit `/settings` and `[Fetching]` tab and enable the WebDriver/Chrome option
+
+The URL for the WebDriver interface is set with the `WEBDRIVER_URL` environment variable (`http://browser-chrome:4444/wd/hub` by default)
\ No newline at end of file