diff --git a/assets/images/preloaded-chrome/addmore-ex.webp b/assets/images/preloaded-chrome/addmore-ex.webp
deleted file mode 100644
index a4b4adf42..000000000
Binary files a/assets/images/preloaded-chrome/addmore-ex.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/chrome.webp b/assets/images/preloaded-chrome/chrome.webp
deleted file mode 100644
index dbbbc1461..000000000
Binary files a/assets/images/preloaded-chrome/chrome.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/chromeex-icon.webp b/assets/images/preloaded-chrome/chromeex-icon.webp
deleted file mode 100644
index 796eef79e..000000000
Binary files a/assets/images/preloaded-chrome/chromeex-icon.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/delete-dialog.webp b/assets/images/preloaded-chrome/delete-dialog.webp
deleted file mode 100644
index ef3ac32d7..000000000
Binary files a/assets/images/preloaded-chrome/delete-dialog.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/kebab.webp b/assets/images/preloaded-chrome/kebab.webp
deleted file mode 100644
index 173b25808..000000000
Binary files a/assets/images/preloaded-chrome/kebab.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/no-extension.webp b/assets/images/preloaded-chrome/no-extension.webp
deleted file mode 100644
index 9ade0d86a..000000000
Binary files a/assets/images/preloaded-chrome/no-extension.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/noextension.webp b/assets/images/preloaded-chrome/noextension.webp
deleted file mode 100644
index 378d1436b..000000000
Binary files a/assets/images/preloaded-chrome/noextension.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/note-section.webp b/assets/images/preloaded-chrome/note-section.webp
deleted file mode 100644
index 2d02fead3..000000000
Binary files a/assets/images/preloaded-chrome/note-section.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/pin.webp b/assets/images/preloaded-chrome/pin.webp
deleted file mode 100644
index a85d51441..000000000
Binary files a/assets/images/preloaded-chrome/pin.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/remove-ex.webp b/assets/images/preloaded-chrome/remove-ex.webp
deleted file mode 100644
index 082b6fc90..000000000
Binary files a/assets/images/preloaded-chrome/remove-ex.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/step-2.webp b/assets/images/preloaded-chrome/step-2.webp
deleted file mode 100644
index 763535646..000000000
Binary files a/assets/images/preloaded-chrome/step-2.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/step-3.webp b/assets/images/preloaded-chrome/step-3.webp
deleted file mode 100644
index c59b91f90..000000000
Binary files a/assets/images/preloaded-chrome/step-3.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/step-4.webp b/assets/images/preloaded-chrome/step-4.webp
deleted file mode 100644
index a4d59b655..000000000
Binary files a/assets/images/preloaded-chrome/step-4.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/step-5.webp b/assets/images/preloaded-chrome/step-5.webp
deleted file mode 100644
index 46b058b54..000000000
Binary files a/assets/images/preloaded-chrome/step-5.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/step-6.webp b/assets/images/preloaded-chrome/step-6.webp
deleted file mode 100644
index 5b9cbbb9b..000000000
Binary files a/assets/images/preloaded-chrome/step-6.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/step-7.webp b/assets/images/preloaded-chrome/step-7.webp
deleted file mode 100644
index c8797d05e..000000000
Binary files a/assets/images/preloaded-chrome/step-7.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/tango.webp b/assets/images/preloaded-chrome/tango.webp
deleted file mode 100644
index c105a23e8..000000000
Binary files a/assets/images/preloaded-chrome/tango.webp and /dev/null differ
diff --git a/assets/images/preloaded-chrome/vm.webp b/assets/images/preloaded-chrome/vm.webp
deleted file mode 100644
index b75d98283..000000000
Binary files a/assets/images/preloaded-chrome/vm.webp and /dev/null differ
diff --git a/assets/images/real-time-testing/key-features/add-chrome-extension.mp4 b/assets/images/real-time-testing/key-features/add-chrome-extension.mp4
new file mode 100644
index 000000000..ace8d7a75
Binary files /dev/null and b/assets/images/real-time-testing/key-features/add-chrome-extension.mp4 differ
diff --git a/assets/images/real-time-testing/key-features/remove-chrome-extension.mp4 b/assets/images/real-time-testing/key-features/remove-chrome-extension.mp4
new file mode 100644
index 000000000..625344acd
Binary files /dev/null and b/assets/images/real-time-testing/key-features/remove-chrome-extension.mp4 differ
diff --git a/docs/getting-started-with-desktop-browser-real-time-testing.md b/docs/getting-started-with-desktop-browser-real-time-testing.md
index 33589e3a0..ba5c92dee 100644
--- a/docs/getting-started-with-desktop-browser-real-time-testing.md
+++ b/docs/getting-started-with-desktop-browser-real-time-testing.md
@@ -48,8 +48,9 @@ Real-Time Desktop Web Browser Testing is the process of testing websites and web
## Launch the Virtual Machine
-Navigate to the Real Time Testing section and select **Desktop** from the **Web Browser Testing** section. To test a website, enter its URL and select your **Operating System**, **browser**, **browser version**, and **screen resolution**.
-
-Afterwards click on the **Start** button to initiate the testing process.
+- Navigate to the Real Time Testing section.
+- Select **Desktop** from the **Web Browser Testing** section.
+- To test a website, enter its URL and select your **Operating System**, **browser**, **browser version**, and **screen resolution**.
+- Afterwards click on the **Start** button to initiate the testing process.
\ No newline at end of file
diff --git a/docs/getting-started-with-mobile-app-real-time-testing.md b/docs/getting-started-with-mobile-app-real-time-testing.md
index 2f4032954..f859fa317 100644
--- a/docs/getting-started-with-mobile-app-real-time-testing.md
+++ b/docs/getting-started-with-mobile-app-real-time-testing.md
@@ -48,8 +48,9 @@ Real-Time Mobile App Testing is the process of testing mobile applications direc
## Launch the Virtual Machine
-Navigate to the Real Time Testing section and select **Virtual Mobile** from the **App Testing** section. To test your application, enter its URL or upload your application from your local machine and select your **Device** - Andoroid, iOS, or [ChromeOS](/support/docs/chrome-os-testing/), and its version.
-
-Afterwards click on the **Start** button to initiate the testing process.
+- Navigate to the Real Time Testing section.
+- Select **Virtual Mobile** from the **App Testing** section.
+- To test your application, enter its URL or upload your application from your local machine and select your **Device** - Andoroid, iOS, or [ChromeOS](/support/docs/chrome-os-testing/), and its version.
+- Afterwards click on the **Start** button to initiate the testing process.
\ No newline at end of file
diff --git a/docs/getting-started-with-mobile-browser-real-time-testing.md b/docs/getting-started-with-mobile-browser-real-time-testing.md
index c4e4d90db..8fa5e5a72 100644
--- a/docs/getting-started-with-mobile-browser-real-time-testing.md
+++ b/docs/getting-started-with-mobile-browser-real-time-testing.md
@@ -48,8 +48,9 @@ Real-Time Mobile Web Browser Testing is the process of testing websites and web
## Launch the Virtual Machine
-Navigate to the Real Time Testing section and select **Virtual Mobile** from the **Web Browser Testing** section. To test a website, enter its URL and select your **Device** - Andoroid, iOS, or [ChromeOS](/support/docs/chrome-os-testing/), and its version.
-
-Afterwards click on the **Start** button to initiate the testing process.
+- Navigate to the Real Time Testing section.
+- Select **Virtual Mobile** from the **Web Browser Testing** section.
+- To test a website, enter its URL and select your **Device** - Andoroid, iOS, or [ChromeOS](/support/docs/chrome-os-testing/), and its version.
+- Afterwards click on the **Start** button to initiate the testing process.
\ No newline at end of file
diff --git a/docs/pre-loaded-chrome-extension.md b/docs/pre-loaded-chrome-extension.md
index 5a013f66b..0bb9cabf9 100644
--- a/docs/pre-loaded-chrome-extension.md
+++ b/docs/pre-loaded-chrome-extension.md
@@ -1,9 +1,9 @@
---
id: pre-loaded-extension
-title: Pre-Loaded Extension For Chrome
-hide_title: true
+title: Pre-Loaded Extension for Chrome
+hide_title: false
sidebar_label: Pre-Loaded Extension
-description: Install your favourite Chrome extensions using the Pre-loaded Extension feature before launching the test session. Eliminate the hassle of repetitively installing Chrome extensions inside VMs.
+description: Learn how to install and manage Chrome extensions during real-time testing on LambdaTest. Enhance your manual testing sessions with ad blockers, debugging tools, and more.
keywords:
- lambdatest pre loaded chrome extension
- lambdatest pre loaded extension for chrome
@@ -36,100 +36,46 @@ slug: pre-loaded-chrome-extension/
})
}}
>
+The Pre-Loaded Chrome Extensions feature in LambdaTest's real-time testing allows users to install and use Chrome extensions during your testing sessions. This capability provides the flexibility to test web applications with various extensions, such as ad blockers, password managers, and developer tools, replicating real user environments more accurately.
-# Pre-Loaded Chrome Extension
-***
+> The Pre-Loaded Extension is only accessible on **Chrome** browsers.
-The LambdaTest Pre-loaded Chrome Extension lets you add your favourite Chrome extensions before initiating the test session, thereby allowing you to access the same Chrome extension within the test session. This eliminates the need to log in and add Chrome extensions inside VMs repeatedly.
+## Prerequisites
+- A LambdaTest account.
+- Access to the real-time testing feature in the LambdaTest platform.
+- Chrome extensions to be tested
-
+## Accessing the Chrome Extensions Feature
-This quick guide will explain how to add your favourite Chrome extension using the Pre-loaded Extension.
+**Step 1:** Select on the **Real Time** > Desktop Web Browser Testing from the sidebar.
->**Important**: The *Preloaded Extension* is only accessible on Chrome browsers.
+**Step 2:** Click on the Chrome Extension drop down button in the dashboard.
-## Adding the Chrome Extension
-***
+**Step 3:** Click on the **Add New Extension** button and then paste the url of the chrome extension that you want to apply and click on the + icon. Your chrome extension will be added.
-1. Login to your LambdaTest account.
+**Step 4:** Now again click on the Chrome Extension drop down button and select all the extensions that you want to apply for your testing purpose and click on the **Apply** button.
-2. Once you are in the user Dashboard, select **Real Time Testing** from the sidebar menu.
+
-
+## Removing the Chrome Extension
-3. From the **Browser Testing** tab, enter the test URL, choose testing type - Desktop/Mobile, select Chrome browser, its VERSION, OS, and, RESOLUTION.
+**Step 1:** Navigate to Real Time Desktop Web Browser Testing console.
-
+**Step 2:** Unselect all those extensions that you want to remove, and click on **Apply** button.
-4. From the **EXTENSION** category, click **Add Extension**.
+
-
+## Use Cases for Chrome Extensions in Real-Time Testing
+- **Testing with Ad Blockers :** Ensure that your web application functions correctly when ad blockers are enabled.
+- **Testing Third-Party Integrations:** Validate integrations with password managers, video downloaders, or custom automation scripts.
+- **Debugging with Developer Tools :** Use developer-focused extensions like Lighthouse, React DevTools, or Web Developer to inspect your web application.
+- **Accessibility Testing :** Install extensions such as Axe or WAVE to perform accessibility audits during manual testing.
-5. A pop-up box will appear asking you to add Chrome extensions. In the provided field, enter the link to the Chrome extension you'd like to add.
-
-
-
-6. Select the + icon and then click **Add**.
-
-
-
->**Note**: Add multiple extensions to the provided fields if you have more than one. Additionally, you can add more fields from Chrome extensions by clicking on **+ ADD MORE**.
-
-
-In the **EXTENSION** category, you'll find the selected Chrome extension.
-
-
-
-7. Now click on the extension that you just added and press **START**.
-
-
-
-It will launch a test session where you can see the extension's sign up page. Sign up for the extension and you are good to go!
-
-
-
-
-## Removing The Chrome Extension
-***
-
-1. Navigate to Real Time Testing console. From the EXTENSION category, select the extension you want to remove and click on 'x' that says *Remove*.
-
-.default})
-
-2. A confirmation dialog box will appear. Click **Delete**.
-
-.default})
-
-## Launching The Tests Without Extensions
-***
-
-If you wish to run the live-interactive tests without a Chrome extension, then follow these steps:
-
-1. Repeat the steps 1 to 3 mentioned in *Adding the Chrome Extension*.
-
-2. From the **EXTENSION** category, click **No Extension**.
-
-.default})
-
-3. Now click **START**.
-
-
.default})
.default})
.default})