diff --git a/en-US/capture/11_proxy.md b/en-US/capture/11_proxy.md
index faf0388..a177d00 100644
--- a/en-US/capture/11_proxy.md
+++ b/en-US/capture/11_proxy.md
@@ -66,4 +66,22 @@ On the Windows system, the web proxy supports the following formats.
 
 ③ `http={ip}:{http_port};https={ip}:{http_port}`
 
-The first of these is a common format and is the default format chosen by Reqable. But some clients can't recognize this format (see this [issue](https://github.com/MatsuriDayo/nekoray/issues/104)), so Reqable provides an option to switch the format. When the web proxy type is selected, the proxy rules can be switched.
\ No newline at end of file
+The first of these is a common format and is the default format chosen by Reqable. But some clients can't recognize this format (see this [issue](https://github.com/MatsuriDayo/nekoray/issues/104)), so Reqable provides an option to switch the format. When the web proxy type is selected, the proxy rules can be switched.
+
+### Record Mode
+
+:::caution Attention
+
+If you are not familiar with this function, please keep the **VPN** mode.
+
+:::
+
+On the Android side of Reqable, we provide two`record modes`to capture network traffic:  **Proxy Mode** and **VPN Mode**。
+
+![](arts/proxy_05.png)
+
+- **Proxy Mode**
+ Configure the IP and port of Reqable's MITM server into the system's network proxy settings. If the application supports it, it will read the system's network proxy settings for network requests, allowing Reqable to capture the traffic. On the PC side, Reqable only supports this mode and can automatically configure the system proxy settings with one click. On the mobile side, you need to manually configure the system proxy, and if the application does not support proxy settings, it may not be able to capture the traffic.
+
+- **VPN Mode**
+ Also known as TUN mode, it forces the application's network traffic into the VPN virtual network card, which is undetectable by the application itself. The virtual network card automatically forwards the traffic to Reqable's MITM server for traffic analysis. Mechanically speaking, the VPN mode can automatically intercept traffic, similar to a transparent proxy, with the application itself being unaware, offering stronger operability. Currently, only the mobile side of Reqable supports VPN mode.
diff --git a/en-US/capture/arts/proxy_05.png b/en-US/capture/arts/proxy_05.png
new file mode 100644
index 0000000..3069767
Binary files /dev/null and b/en-US/capture/arts/proxy_05.png differ
diff --git a/zh-CN/capture/11_proxy.md b/zh-CN/capture/11_proxy.md
index d273eb0..61aee63 100644
--- a/zh-CN/capture/11_proxy.md
+++ b/zh-CN/capture/11_proxy.md
@@ -72,4 +72,22 @@ Reqable本身不具备绕过流量受限的能力，也无法解决流量受限
 
 ③ `http={ip}:{http_port};https={ip}:{http_port}`
 
-其中第一种是通用格式，也是Reqable选用的默认格式。但是某些客户端无法识别这种格式（参阅此[问题](https://github.com/MatsuriDayo/nekoray/issues/104)），所以Reqable提供了切换格式的选项。当选用Web代理协议的时候，代理规则可以按照下图进行切换。
\ No newline at end of file
+其中第一种是通用格式，也是Reqable选用的默认格式。但是某些客户端无法识别这种格式（参阅此[问题](https://github.com/MatsuriDayo/nekoray/issues/104)），所以Reqable提供了切换格式的选项。当选用Web代理协议的时候，代理规则可以按照下图进行切换。
+
+### 记录模式
+
+:::caution 注意
+
+如果您不了解此功能，请保持**VPN模式**。
+
+:::
+
+在Reqable的Android端，我们提供了两种`记录模式`来捕获网络流量: **代理模式** 和 **VPN模式**。
+
+![](arts/proxy_05.png)
+
+- **代理模式**
+ 将 Reqable 的 MITM 服务器的 IP 和端口配置到系统的网络代理配置中，若应用程序支持，将会读取系统网络代理配置进行网络请求，这样 Reqable 就能捕获到流量了。在 PC 端，Reqable 只支持这种模式，且能一键自动配置系统代理设置。在移动端中需要手动配置系统代理，如果应用程序不支持代理设置，可能无法捕获到流量。
+
+- **VPN模式**
+ 又称 TUN 模式，将强制应用网络流量进入 VPN 虚拟网卡，应用本身是无感知的。虚拟网卡将流量自动转发到 Reqable 的 MITM 服务器，进行流量分析。从机制上来讲， VPN 模式可以自动化拦截流量，类似透明代理，应用本身无感知，可操作性更强。目前，Reqable 只有手机端支持 VPN 模式。
diff --git a/zh-CN/capture/arts/proxy_05.png b/zh-CN/capture/arts/proxy_05.png
new file mode 100644
index 0000000..8533a23
Binary files /dev/null and b/zh-CN/capture/arts/proxy_05.png differ