diff --git a/docs/ai-test-failure-analysis.md b/docs/ai-test-failure-analysis.md
index 1d0c0953d..ebcc4e2db 100644
--- a/docs/ai-test-failure-analysis.md
+++ b/docs/ai-test-failure-analysis.md
@@ -54,4 +54,9 @@ To use the AI-powered Test Failure Analysis feature, simply click on the Failure
 
 After categorizing errors, we offer a structured approach to address each failure type. You can efficiently get to the precise corrective measures or **Remedies** recommended alng with **Additional suggestions** for the particular error. This targeted approach expedites the issue resolution process, eliminating unnecessary steps and optimizing efficiency.
 
-<img loading="lazy" src={require('../assets/images/hyperexecute/features/rca/rca.gif').default} alt="Image" width="1347" height="616"  className="doc_img"/>
+<div className="storylane-iframe">
+  <script async src="https://js.storylane.io/js/v2/storylane.js"></script>
+  <div className="sl-embed">
+    <iframe loading="lazy" className="sl-demo" src="https://app.storylane.io/demo/1decserb8xfq?embed=inline" name="sl-embed" allow="fullscreen" allowfullscreen></iframe>
+  </div>
+</div>
diff --git a/docs/browser-testing-with-real-devices.md b/docs/browser-testing-with-real-devices.md
index 596584bea..e6fb146b5 100644
--- a/docs/browser-testing-with-real-devices.md
+++ b/docs/browser-testing-with-real-devices.md
@@ -45,35 +45,28 @@ Real device browser testing refers to the process of testing web applications an
 
 **Step 1:** Login to your LambdaTest account. From the left sidebar, head to Real Device and select **Browser Testing**.
 
-<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-device-browser-home.webp').default} alt="Native Mobile App Testing"  className="doc_img" width="1366" height="629"/>
-
 **Step 2**: Select the **OS** and **browser** of your choice. 
 
-<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-device-browser-browser.webp').default} alt="Native Mobile App Testing"  className="doc_img" width="1366" height="629"/>
-
 >**Note:** Certain browsers might not be supported on certain devices. 
 
 **Step 3**: Select the **real device** of your choice. You can also search the preferred real **Android** or **iOS** device in the search bar.
 
-<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-device-browser-testing-os.webp').default} alt="Native Mobile App Testing"  className="doc_img" width="1366" height="629"/>
-
-
 **Step 4**: In the case of **Android** devices, simply enter the website URL in the address bar.
-<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-browser-testing-android-url.webp').default} alt="Real Device Region Feature"  className="doc_img" width="1366" height="629"/>
 
 In the case of **iOS** devices, you can enter the website URL once the session has started. 
  
-
-<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-browser-ios-url.webp').default} alt="Real Device Region Feature"  className="doc_img" width="1366" height="629"/>
-
 **Step 5**: Select the **Tunnel** option in the top right corner to test your locally hosted and privately hosted websites. 
 
 Check out our detailed [support documentation](https://www.lambdatest.com/support/docs/testing-locally-hosted-pages/) to learn how to activate the LT Tunnel.
 
-<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-device-browser-tunnel.webp').default} alt="Real Device Tunnel"  className="doc_img" width="1366" height="629"/>
-
 **Step 6**: Click on Start to run your test session.
 
+<div className="storylane-iframe">
+  <script async src="https://js.storylane.io/js/v2/storylane.js"></script>
+  <div className="sl-embed">
+    <iframe loading="lazy" className="sl-demo" src="https://app.storylane.io/demo/olydgivozpsz?embed=inline"  name="sl-embed" allow="fullscreen" allowfullscreen></iframe>
+  </div>
+</div>
 
 <nav aria-label="breadcrumbs">
   <ul className="breadcrumbs">
diff --git a/docs/hyperexecute-running-your-first-job.md b/docs/hyperexecute-running-your-first-job.md
index 86daac76e..fd1e846d0 100644
--- a/docs/hyperexecute-running-your-first-job.md
+++ b/docs/hyperexecute-running-your-first-job.md
@@ -91,17 +91,13 @@ We will be taking care of everything one by one, just follow the steps given bel
 
 **Step 2:** Choose your test automation framework, Select **Run on Local System** and click on **Get Started**. 
 
-  <img loading="lazy" src={require('../assets/images/hyperexecute/getting_started/run-first-job/4.png').default} alt="Image"  className="doc_img"/>
-
 **Step 3:** Download our sample project by clicking on **Download Sample**. (Skip this step if you already have a project you want to test)
 
 **Step 4:** Download the [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) as per the OS that you are on.
 
 **Step 5:** Select the OS on which you want to run your tests and then download the [HyperExecute YAML](/support/docs/deep-dive-into-hyperexecute-yaml/) file shown on screen. This contains all the configurations required for running tests on HyperExecute. 
 
-<video class="right-side" width="100%" controls id="vid">
-<source src= {require('../assets/videos/hyperexecute/getting-started/run-first-job/local-system.mp4').default} type="video/mp4" />
-</video>
+
 
    > **Note**: Your Yaml file should be in the root directory of your project. If you are renaming it, also change the file name in the execution script as well. You can learn more about the advanced configurations [here](/support/docs/deep-dive-into-hyperexecute-yaml/), however for the given sample projects you can simply download the file using the small icon on top right. 
 
@@ -111,6 +107,13 @@ We will be taking care of everything one by one, just follow the steps given bel
 
 **Step 8:** Once your Job is running, you can click on **View Test Results** to navigate to HyperExecute Dashboard where you can see the job getting executed along with the test results.
 
+<div className="storylane-iframe">
+  <script async src="https://js.storylane.io/js/v2/storylane.js"></script>
+  <div className="sl-embed">
+    <iframe loading="lazy" className="sl-demo" src="https://app.storylane.io/demo/qn3z533xbk7l?embed=inline" name="sl-embed" allow="fullscreen" allowfullscreen></iframe>
+  </div>
+</div>
+
 :::note
 The generic command required to initiate test execution is given below. You will need to insert the name of your YAML file in place of the `RELATIVE_PATH_OF_YOUR_YAML_FILE` before running this command. (Skip if you already used the command from Step 6. )
 
diff --git a/docs/hyperexecute-task-metrics.md b/docs/hyperexecute-task-metrics.md
index 897991ff9..9fc05cab4 100644
--- a/docs/hyperexecute-task-metrics.md
+++ b/docs/hyperexecute-task-metrics.md
@@ -51,10 +51,6 @@ The task level view provides insights into the CPU and memory consumption at the
 
 By analyzing the task level view, you can pinpoint any tasks that may be causing high CPU or memory usage issues, allowing you to optimize their performance for better overall results.
 
-<video class="right-side" width="100%" controls id="vid">
-<source src= {require('../assets/videos/hyperexecute/task-metrics/task-level-metrics.mp4').default} type="video/mp4" />
-</video>
-
 ## Stage Level View
 
 In the stage level view of HyperExecute, the analysis is segmented into three distinct phases: pre-stage, scenario stage, and post-stage.
@@ -65,6 +61,10 @@ In the stage level view of HyperExecute, the analysis is segmented into three di
 
 - **Post-Stage :** The post-stage view concentrates on resource consumption and actions taken after completing the main test scenario. By reviewing the post-stage metrics, you can evaluate resource management efficiency and ensure system stability post-test scenario execution.
 
-<video class="right-side" width="100%" controls id="vid">
-<source src= {require('../assets/videos/hyperexecute/task-metrics/stage-level-metrics.mp4').default} type="video/mp4" />
-</video>
+<div className="storylane-iframe">
+  <script async src="https://js.storylane.io/js/v2/storylane.js"></script>
+  <div className="sl-embed">
+    <iframe loading="lazy" className="sl-demo" src="https://app.storylane.io/demo/ujyqd8y01zch?embed=inline" name="sl-embed" allow="fullscreen" allowfullscreen></iframe>
+  </div>
+</div>
+