diff --git a/protocols/_images/Google_Drive_OAuth_2_Authentication.png b/protocols/_images/Google_Drive_OAuth_2_Authentication.png
deleted file mode 100644
index a8fa7c1d..00000000
Binary files a/protocols/_images/Google_Drive_OAuth_2_Authentication.png and /dev/null differ
diff --git a/protocols/_images/Google_Storage_OAuth_Token.png b/protocols/_images/Google_Storage_OAuth_Token.png
deleted file mode 100644
index 124aa7f2..00000000
Binary files a/protocols/_images/Google_Storage_OAuth_Token.png and /dev/null differ
diff --git a/protocols/googlecloudstorage.md b/protocols/googlecloudstorage.md
index 204e4a5c..2307b2f7 100644
--- a/protocols/googlecloudstorage.md
+++ b/protocols/googlecloudstorage.md
@@ -29,11 +29,7 @@ You must obtain the project ID (`x-goog-project-id`) of your project from the Go
 
 ![Project ID Bookmark Configuration](_images/Project_ID_Bookmark_Configuration.png)
 
-In the login prompt of Cyberduck, you enter the `x-goog-project-id` for the username. The authorization code will be submitted to Cyberduck automatically.
-
-![Cyberduck OAuth Permissions](_images/Google_Storage_OAuth_Token.png)
-
-You access the page with the authorization code from the link displayed in the login prompt. Click it to open it in a web browser window. You only need to get the authorization code from the website on the first login attempt. Subsequent OAuth authentications will use a refresh token retrieved from the service.
+In the login prompt of Cyberduck, you enter the `x-goog-project-id` for the username. The authorization code will be submitted to Cyberduck automatically. You access the page with the authorization code from the link displayed in the login prompt. Click it to open it in a web browser window. You only need to get the authorization code from the website on the first login attempt. Subsequent OAuth authentications will use a refresh token retrieved from the service.
 
 ```{attention}
 Using *[Advanced Protection Program](https://support.google.com/accounts/answer/7539956#non-goog_apps&zippy=%2Ccan-i-use-non-google-apps-services-or-apps-script-with-advanced-protection)* will cause the OAuth login flow to fail. 
diff --git a/protocols/googledrive.md b/protocols/googledrive.md
index 00fbd8b3..847ac6c7 100644
--- a/protocols/googledrive.md
+++ b/protocols/googledrive.md
@@ -18,8 +18,6 @@ Connect to your [Google Drive](http://drive.google.com/) to store plain files.
 
 Google Drive uses OAuth 2 to allow Cyberduck to access your files on Google Drive. Choose your account email as the username in the bookmark and choose *Allow* on the website opened in your default web browser to allow Cyberduck to *View and manage the files in your Google Drive*. The authorization code will be submitted to Cyberduck automatically. Subsequent connections will not require authorization, unless the refresh token itself is expired due to inactivity.
 
-![OAuth 2 Authentication](_images/Google_Drive_OAuth_2_Authentication.png)
-
 ```{attention}
 Using *[Advanced Protection Program](https://support.google.com/accounts/answer/7539956#non-goog_apps&zippy=%2Ccan-i-use-non-google-apps-services-or-apps-script-with-advanced-protection)* will cause the OAuth login flow to fail. 
 ```