diff --git a/public/docs-static/img/manage/access-control/policy-direction.gif b/public/docs-static/img/manage/access-control/policy-direction.gif
deleted file mode 100644
index 9181ed0a..00000000
Binary files a/public/docs-static/img/manage/access-control/policy-direction.gif and /dev/null differ
diff --git a/public/docs-static/img/manage/access-control/policy-direction.mp4 b/public/docs-static/img/manage/access-control/policy-direction.mp4
new file mode 100644
index 00000000..8014f399
Binary files /dev/null and b/public/docs-static/img/manage/access-control/policy-direction.mp4 differ
diff --git a/src/pages/manage/access-control/index.mdx b/src/pages/manage/access-control/index.mdx
index e8892242..b9260a7d 100644
--- a/src/pages/manage/access-control/index.mdx
+++ b/src/pages/manage/access-control/index.mdx
@@ -221,7 +221,8 @@ In rare cases, such as callback mechanisms or notification systems, you might ne
 Understanding policy directionality is essential for implementing Zero Trust access control. How policies behave depends on whether you're connecting to **peers** (devices running NetBird) or **network resources** (internal systems accessed through routing peers).
 
 <p>
-    <img src="/docs-static/img/manage/access-control/policy-direction.gif" alt="NetBird Policy Direction" className="imagewrapper" />
+    <Video src="/docs-static/img/manage/access-control/policy-direction.mp4"
+           label="Toggling a policy between one-way and bidirectional traffic in the policy editor"/>
 </p>
 
 ### Policies Between Peers
diff --git a/src/pages/use-cases/security/implement-zero-trust.mdx b/src/pages/use-cases/security/implement-zero-trust.mdx
index 1b3d804c..4b3b40c3 100644
--- a/src/pages/use-cases/security/implement-zero-trust.mdx
+++ b/src/pages/use-cases/security/implement-zero-trust.mdx
@@ -1,4 +1,4 @@
-import {Note, Warning} from "@/components/mdx";
+import {Note, Warning, Video} from "@/components/mdx";
 import {Tiles} from "@/components/Tiles";
 
 # Implementing Zero Trust with NetBird
@@ -374,7 +374,8 @@ In NetBird:
 - Portless rules are effectively "all ports" and should be treated as wide open. These are not recommended for Zero Trust.
 
 <p>
-    <img src="/docs-static/img/manage/access-control/policy-direction.gif" alt="Policy directionality showing unidirectional and bidirectional traffic" className="imagewrapper"/>
+    <Video src="/docs-static/img/manage/access-control/policy-direction.mp4"
+           label="Policy directionality: toggling between one-way and bidirectional traffic in the policy editor"/>
 </p>
 
 Where to do this: create or edit policies in **[Access Control → Policies](/manage/access-control)**, choose **Source group**, **Destination group**, then restrict **Protocol** and **Ports**.