diff --git a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/be/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/bn/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index faac6782c25..9a7c660cdc6 100644
--- a/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/cs/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ Tento článek popisuje AdGuard pro Windows v8.0, multifunkční blokátor rekla
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-V části _Správa aplikací_ můžete spravovat nastavení směrování a filtrování pro všechny aplikace nainstalované ve vašem zařízení.
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-Jakmile AdGuard zjistí, že se aplikace připojila k internetu, automaticky ji přidá do _Správy aplikací_ a její provoz je přesměrován skrze AdGuard.
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-Ve výchozím nastavení AdGuard filtruje veškerý provoz, ale můžete si vybrat, co chcete vyloučit.
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-AdGuard také filtruje HTTPS provoz, protože většina webových stránek dnes používá HTTPS. To je obzvláště důležité pro blokování reklam na stránkách jako youtube.com, facebook.com a x.com, kde není možné odstranit reklamy bez filtrování HTTPS.
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-Pokud jsou pro aplikaci povoleny směrování a filtrování, ikony pod každou aplikací se zobrazí zeleně.
-
-Nastavení můžete ponechat beze změny, deaktivovat filtrování i směrování nebo je ručně doladit pro každou aplikaci. Můžete také přistupovat ke statistikám aplikace.
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.

-## “Kompatibilní” a ”nekompatibilní” aplikace
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Většina aplikací funguje po filtrování správně. Některé aplikace jsou považovány za “problematické“ a při směrování skrze AdGuard nemusí fungovat správně. Při pokusu o směrování nebo filtrování všech aplikací se může zobrazit následující varování:
+- _Exclusion lists_
-Pro zajištění správného fungování všech aplikací nainstalovaných v zařízení důrazně doporučujeme, abyste skrze AdGuard směrovali pouze kompatibilní aplikace.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/da/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 08c1e36cac8..28107cd11ef 100644
--- a/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/de/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ Dieser Artikel beschreibt AdGuard für Windows v8.0, einen umfassenden Werbebloc
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-Im Abschnitt _App-Verwaltung_ können Sie die Routing- und Filtereinstellungen für alle auf Ihrem Gerät installierten Apps verwalten.
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-Sobald AdGuard erkennt, dass eine App mit dem Internet verbunden ist, wird sie automatisch zur _App-Verwaltung_ hinzugefügt und ihr Datenverkehr wird über AdGuard geleitet.
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-Standardmäßig filtert AdGuard den gesamten Datenverkehr, aber Sie können auswählen, was ausgeschlossen werden soll.
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-AdGuard filtert auch den über HTTPS geleiteten Datenverkehr, da die meisten Websites heutzutage HTTPS verwenden. Dies ist besonders wichtig für das Blockieren von Werbung auf Websites wie youtube.com, facebook.com und x.com, bei denen es ohne HTTPS-Filterung unmöglich ist, Werbung zu entfernen.
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-Wenn Routing und Filterung für eine App aktiviert sind, werden die Symbole unter jeder App grün angezeigt.
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.
-Sie können die Einstellungen unverändert lassen, sowohl das Filtern als auch das Routing deaktivieren oder sie für jede App manuell anpassen. Sie können zudem auf die Statistiken der App zugreifen.
+
-
+## How app filtering and routing work in AdGuard for Windows v8.0
-## „Problemlose“ und „problematische“ Apps
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
-Die meisten Apps funktionieren korrekt, wenn sie gefiltert werden. Einige Apps gelten als „problematisch“ und funktionieren möglicherweise nicht richtig, wenn deren Datenverkehr über AdGuard geleitet wird. Wenn Sie versuchen, alle Apps weiterzuleiten oder zu filtern, wird möglicherweise eine Warnung wie diese angezeigt:
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
-Um den ordnungsgemäßen Betrieb aller auf Ihrem Gerät installierten Apps zu gewährleisten, empfehlen wir, nur unproblematische Apps über AdGuard zu leiten.
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
+
+- _Exclusion lists_
+
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 8b4d5a34f1f..b553e334120 100644
--- a/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/es/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ Este artículo describe AdGuard para Windows v8.0, un bloqueador de anuncios int
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-En la sección _Gestión de aplicaciones_, puedes administrar la configuración de enrutamiento y filtrado para todas las aplicaciones instaladas en tu dispositivo.
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-Una vez que AdGuard detecta que una aplicación se ha conectado, se añade automáticamente a _Gestión de aplicaciones_, y su tráfico se enruta a través de AdGuard.
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-Por defecto, AdGuard filtra todo el tráfico, pero puedes elegir qué excluir.
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-AdGuard también filtra el tráfico HTTPS, ya que la mayoría de los sitios web hoy en día usan HTTPS. Esto es especialmente importante para bloquear anuncios en sitios como youtube.com, facebook.com y x.com, donde es imposible eliminar anuncios sin el filtrado HTTPS.
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-Cuando el enrutamiento y el filtrado están habilitados para una aplicación, los íconos debajo de cada aplicación aparecerán en verde.
-
-Puede dejar la configuración como está, desactivar tanto el filtrado como el enrutamiento, o ajustarlos manualmente para cada aplicación. También puedes acceder a las estadísticas de la aplicación.
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.

-## Aplicaciones “libres de problemas” y “problemáticas”
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-La mayoría de las apps funcionan correctamente cuando se filtran. Algunas aplicaciones se consideran «problemáticas» y pueden no funcionar correctamente cuando se enrutan a través de AdGuard. Es posible que vea una advertencia como esta al intentar enrutar o filtrar todas las aplicaciones:
+- _Exclusion lists_
-Para garantizar el correcto funcionamiento de todas las aplicaciones instaladas en su dispositivo, recomendamos enrutar solo las aplicaciones sin problemas a través de AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/fa/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/fi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 93897b38090..c6b235ab341 100644
--- a/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/fr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ Cet article décrit AdGuard pour Windows v8.0, un bloqueur de publicité complet
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-Dans la section _Gestion des applications_, vous pouvez gérer les paramètres de routage et de filtrage pour toutes les applications installées sur votre appareil.
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-Une fois qu'AdGuard détecte qu’une app est en ligne, elle est automatiquement ajoutée à la _Gestion des applications_, et son trafic est acheminé via AdGuard.
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-Par défaut, AdGuard filtre tout le trafic, mais vous pouvez choisir ce qu'il faut exclure.
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-AdGuard filtre également le trafic HTTPS, car la plupart des sites Web utilisent aujourd'hui HTTPS. Ceci est particulièrement important pour bloquer les publicités sur des sites comme youtube.com, facebook.com, et x.com, où il est impossible de retirer les publicités sans filtrage HTTPS.
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-Lorsque le routage et le filtrage sont activés pour une application, les icônes situées sous chaque application apparaissent en vert.
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.
-Vous pouvez laisser les paramètres tels quels, désactiver à la fois le filtrage et le routage, ou les affiner manuellement pour chaque app. Vous pouvez également accéder aux statistiques de l'application.
+
-
+## How app filtering and routing work in AdGuard for Windows v8.0
-## Applications "sans problème" et "problématiques"
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
-La plupart des applications fonctionnent correctement lorsqu'elles sont filtrées. Certaines applications sont considérées comme "problématiques" et peuvent ne pas fonctionner correctement lorsqu'elles sont acheminées par AdGuard. Il se peut qu'un avertissement de ce type apparaisse lorsque vous essayez d'acheminer ou de filtrer toutes les applications :
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
-Pour garantir le bon fonctionnement de toutes les applications installées sur votre appareil, nous vous recommandons de n'acheminer que les applications qui ne posent pas de problème via AdGuard.
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
+
+- _Exclusion lists_
+
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/hr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/hu/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 556163a6c97..583f68d1a84 100644
--- a/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/it/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ Questo articolo descrive AdGuard per Windows v8.0, un blocca-inserzioni completo
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-Nella sezione _Gestione app_, puoi gestire le impostazioni di instradamento e filtraggio per tutte le app installate nel tuo dispositivo.
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-Quando AdGuard rileva che un'app è andata in rete, è automaticamente aggiunta a _Gestione app_, e il suo traffico è instradato tramite AdGuard.
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-Per impostazione prescelta, AdGuard filtra tutto il traffico, ma puoi scegliere cosa escludere.
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-AdGuard filtra anche il traffico HTTPS, poiché la maggior parte dei siti web oggigiorno usa HTTPS. Questo è particolarmente importante per bloccare le inserzioni in siti come youtube.com, facebook.com e x.com, dove è impossibile rimuovere le inserzioni senza il filtraggio HTTPS.
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-Quando l'instradamento e il filtraggio sono abilitati per un'app, le icone sotto ogni app diventeranno verdi.
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.
-Puoi lasciare le impostazioni così come sono, disabilitare sia il filtraggio sia l'instradamento, oppure affinarle manualmente per ogni app. Puoi anche accedere alle statistiche dell'app.
+
-
+## How app filtering and routing work in AdGuard for Windows v8.0
-## App “senza problemi” e “problematiche”
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
-La maggior parte delle app funziona correttamente quando è filtrata. Alcune app sono considerate "problematiche" e potrebbero non funzionare correttamente se instradate tramite AdGuard. Potresti vedere un avviso simile quando provi a instradare o filtrare tutte le app:
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
-Per garantire il corretto funzionamento di tutte le app installate sul tuo dispositivo, ti consigliamo di instradare tramite AdGuard solo le app che non presentano problemi.
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
+
+- _Exclusion lists_
+
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 16ccf39ad47..cdd9d3ca1cb 100644
--- a/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/ja/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## "問題のない"アプリと"問題あり"アプリ
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index f55d461cebc..0e968f95298 100644
--- a/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/ko/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## '문제가 없는' 앱과 '문제가 있는' 앱
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-대부분의 앱들은 필터링되어도 제대로 작동합니다. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/nl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/no/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/pl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 991fc98f607..0c975feee6e 100644
--- a/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/pt-BR/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ Este artigo descreve o AdGuard para Windows v8.0, um bloqueador de anúncios com
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-Na seção _Gerenciamento de apps_, você pode gerenciar as configurações de roteamento e filtragem para todos os apps instalados no seu dispositivo.
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-Uma vez que o AdGuard detecta que um aplicativo está online, ele é automaticamente adicionado ao _Gerenciamento de aplicativos_, e seu tráfego é roteado através do AdGuard.
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-Por padrão, o AdGuard filtra todo o tráfego, mas você pode escolher o que excluir.
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-O AdGuard também filtra o tráfego HTTPS, pois a maioria dos sites hoje utiliza HTTPS. Isto é especialmente importante para bloquear anúncios em sites como youtube.com, facebook.com e x.com, onde é impossível remover anúncios sem filtragem HTTPS.
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-Quando o roteamento e a filtragem estão ativados para um aplicativo, os ícones abaixo de cada aplicativo aparecerão em verde.
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.
-Você pode deixar as configurações como estão, desativar tanto a filtragem quanto o roteamento, ou ajustá-los manualmente para cada aplicativo. Você também pode acessar as estatísticas do aplicativo.
+
-
+## How app filtering and routing work in AdGuard for Windows v8.0
-## Aplicativos “sem problemas” e “problemáticos”
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
-A maioria dos aplicativos funciona corretamente quando a filtragem está ativada. Alguns aplicativos são considerados "problemáticos" e podem não funcionar corretamente quando roteados pelo AdGuard. É por isso que você poderá ver o seguinte aviso ao tentar rotear ou realizar a filtragem em todos os aplicativos:
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
-Para garantir o funcionamento adequado de todos os aplicativos instalados no seu dispositivo, recomendamos que você faça o roteamento apenas dos aplicativos sem problemas pelo AdGuard.
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
+
+- _Exclusion lists_
+
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/pt/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 378f7c17bc5..0b8607b585c 100644
--- a/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/ro/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## Aplicații „fără probleme” și „problematici”
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Cele mai multe aplicații funcționează corect atunci când sunt filtrate. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 4f953b808ec..0131385a0de 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ sidebar_position: 1
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-В разделе _Приложения_ вы можете управлять настройками маршрутизации и фильтрации для всех приложений, установленных на вашем устройстве.
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-Как только AdGuard определяет, что приложение подключилось к сети, оно автоматически добавляется в _Приложения_, а его трафик направляется через AdGuard.
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-По умолчанию AdGuard фильтрует весь трафик, но вы можете выбрать, что исключить.
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-AdGuard также фильтрует HTTPS-трафик, поскольку большинство сайтов сегодня используют HTTPS. Это особенно важно для блокировки рекламы на таких сайтах, как youtube.com, facebook.com и x.com, где невозможно удалить рекламу без HTTPS-фильтрации.
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-Если для приложения включены функции маршрутизации и фильтрации, значки под каждым приложением отображаются в зелёном цвете.
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.
-Вы можете оставить все настройки как есть, отключить фильтрацию и маршрутизацию или настроить их вручную для каждого приложения. Также вам доступна статистика приложений.
+
-
+## How app filtering and routing work in AdGuard for Windows v8.0
-## Непроблемные и проблемные приложения
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
-Большинство приложений при фильтрации работают корректно. Некоторые приложения считаются «проблемными» и могут работать некорректно при маршрутизации через AdGuard. Поэтому при попытке настроить маршрутизацию или фильтрацию всех приложений может появиться подобное предупреждение:
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
-Чтобы все приложения работали правильно, рекомендуем направлять через AdGuard только непроблемные.
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
+
+- _Exclusion lists_
+
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/sk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/sl/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/sv/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/ta/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 842f6fa1050..39908690dc4 100644
--- a/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/tr/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/uk/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/vi/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index 563a82a8391..1d420d7653c 100644
--- a/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/zh-CN/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,24 +9,80 @@ sidebar_position: 1
:::
-
+In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
-在「应用管理」部分,您可以管理设备上已安装所有应用的路由和过滤设置。
+Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
-当 AdGuard 检测到某个应用联网时,它会自动添加到「应用管理」中,其流量将通过 AdGuard 路由。
+By default, AdGuard filters all traffic, but you can choose what to exclude.
-默认情况下,AdGuard 会过滤所有流量,但您可以选择排除项。
+AdGuard also filters HTTPS traffic, as most websites today use HTTPS. This is especially important for blocking ads on sites like youtube.com, facebook.com, and x.com, where it is impossible to remove ads without HTTPS filtering.
-由于如今大多数网站都使用 HTTPS,AdGuard 也会对 HTTPS 流量进行过滤。 这对于拦截 youtube.com、facebook.com 和 x.com 等网站上的广告尤其重要,因为不经过 HTTPS 过滤就无法移除这些广告。
+When routing and filtering are enabled for an app, the icons below each app will appear green.
-当某个应用的路由和过滤都开启时,每个应用下方的图标会显示为绿色。
+You can leave the settings as they are, disable both filtering and routing, or fine-tune them manually for each app. You can also access the app’s stats.
-您可以保留默认设置,也可以同时关闭过滤和路由,或者为每个应用单独手动微调。 用户还可以查看应用的统计数据。
+
-
+## How app filtering and routing work in AdGuard for Windows v8.0
-## “「无问题」与「有问题」的应用
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
-大多数应用在过滤时都能正常工作。 有些应用被视为「有问题」,当通过 AdGuard 路由时可能无法正常运行。 当您尝试路由或过滤所有应用时,可能会看到如下警告:
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
-要确保设备上所有已安装应用的正常运行,我们建议只将无问题的应用通过 AdGuard 路由。
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
+
+- _Exclusion lists_
+
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::
diff --git a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
index dc70ebcfcf7..bdd71586bca 100644
--- a/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
+++ b/i18n/zh-TW/docusaurus-plugin-content-docs/current/adguard-for-windows-8/app-management/app-management.md
@@ -9,8 +9,6 @@ This article describes AdGuard for Windows v8.0, a comprehensive ad blocker that
:::
-
-
In the _App management_ section, you can manage routing and filtering settings for all apps installed on your device.
Once AdGuard detects that an app has gone online, it is automatically added to _App management_, and its traffic is routed through AdGuard.
@@ -25,8 +23,66 @@ You can leave the settings as they are, disable both filtering and routing, or f

-## “Problem-free” and “problematic” apps
+## How app filtering and routing work in AdGuard for Windows v8.0
+
+AdGuard for Windows v8.0 introduces updated logic for handling apps. It helps prevent compatibility issues while still giving you control over which apps are filtered. Let’s break down how it works.
+
+There are “problem-free” and “problematic” apps. Some work correctly when filtered, while others may not function when their traffic is processed by AdGuard. This can be caused by features like HTTPS interception or proxying.
+
+To avoid breaking apps out of the box, AdGuard does not filter everything indiscriminately. Instead, it relies on a compatibility list — a set of apps that are known to work correctly with filtering enabled.
+
+:::note
+
+“Not filtering everything” does not mean “filter nothing.” Trusted apps (like browsers) are always filtered.
+
+:::
+
+Each app has three independent processing layers: traffic routing through AdGuard, filtering (blocking ads and trackers), and HTTPS filtering (interception of encrypted traffic).
+
+These are determined by three sources:
+
+- _Compatibility list_
+
+ Apps that have been tested by our team and are confirmed to work correctly with filtering.
+ This list is updated through internal testing and user reports in the [dedicated repository for listing AdGuard compatibility issues](https://github.com/AdguardTeam/CompatibilityIssues).
-Most apps work correctly when filtered. Some apps are considered “problematic” and may not work correctly when routed through AdGuard. You may see a warning like this when trying to route or filter all apps:
+- _Exclusion lists_
-To ensure the proper operation of all apps installed on your device, we recommend routing only problem-free apps through AdGuard.
+ Separate lists for routing, filtering, and HTTPS filtering. These include apps known to break when filtering is applied.
+
+- _Filter unknown apps_
+
+ This setting defines how all other apps (not present in any list) are handled.
+
+:::info
+
+The compatibility lists are continuously updated — and you can help improve them. If you notice that an app does not work correctly with filtering enabled, **report it on [GitHub](https://github.com/AdguardTeam/CompatibilityIssues)** or contact support via the app. Your feedback helps improve AdGuard for everyone.
+
+:::
+
+## Filter unknown apps
+
+
+
+The _Filter unknown apps_ setting is enabled by default and determines how AdGuard handles new apps that are not yet present in the compatibility or exclusion lists
+
+When enabled, app traffic is routed through AdGuard, regular filtering is applied, and **HTTPS filtering is NOT enabled automatically**. This is intentional: HTTPS interception is the most sensitive part of traffic processing and may affect app behavior.
+
+When disabled, new apps are not processed by AdGuard — you will need to manually configure routing for them.
+
+Here is a quick overview of how different app categories behave depending on this setting:
+
+| App category | Toggle on (default) | Toggle off |
+| ----------------------------------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------- |
+| Compatible, or problem-free (e.g., browsers) | · Routing ✅
· Filtering ✅
· HTTPS filtering ✅ | Same behavior — does not depend on toggle |
+| Problematic (from exclusion lists, filtering may cause issues) | · Routing ❌
· Filtering ❌
· HTTPS filtering ❌ | Same behavior — does not depend on toggle |
+| Others / (newly detected, unknown, not in lists) | · Routing ✅
· Filtering ✅
· HTTPS filtering ❌ | Not routed through AdGuard, must be enabled manually |
+
+:::info What happens on reset
+
+If you click **Reset to default**, two things happen:
+
+1. All app-specific permissions are cleared (set to “not configured”).
+2. Predefined rules are applied to known safe apps (such as browsers), including HTTPS filtering.
+
+:::