diff --git a/docs/zwus.md b/docs/zwus.md
index 201d0ee..e35a88b 100644
--- a/docs/zwus.md
+++ b/docs/zwus.md
@@ -10,6 +10,11 @@ Choosing the right ZWUS base involves balancing **payload size** against **platf
 - **Compatibility Trade-off:**
   The higher the base, the larger the alphabet of zero-width Unicode characters required. Certain messaging apps, web services, or platforms may strip, sanitize, or fail to hide some of these characters properly (sometimes rendering visible space or placeholder boxes). If a platform alters or rejects certain characters, lower bases like **ZWUS-6** or **ZWUS-3** offer higher compatibility by restricting the alphabet to a smaller, safer subset of zero-width characters.
 
+> **Developer Advice:**
+> - **ZWUS-8:** Only pick ZWUS-8 if you are using lots of Asian or non-standard Unicode characters (where high code points benefit most from base-8 compression).
+> - **ZWUS-6:** The sweet spot for English text if the target website or platform supports it.
+> - **ZWUS-3:** Only use ZWUS-3 if you want to be as safe as possible across strict platforms.
+
 ## Automatic Detection with Sign
 
 If you enable **Sign** when encoding, an invisible, collision-free signature is attached to the secret message. When decoding—either in the extension popup or via the on-screen overlay—inØsight automatically identifies and switches to the correct base and cipher every time. You never need to remember or guess which standard was used.