diff --git a/default/fontconfig/conf.avail/50-omarchy.conf b/default/fontconfig/conf.avail/50-omarchy.conf
index 95f4f508..eecf66e0 100644
--- a/default/fontconfig/conf.avail/50-omarchy.conf
+++ b/default/fontconfig/conf.avail/50-omarchy.conf
@@ -38,6 +38,34 @@
     </edit>
   </match>
 
+  <!-- Urdu is conventionally set in Nastaliq, so keep it there. Without this
+       the untargeted Naskh rule below would capture Urdu too. Appended rather
+       than prepended so it only wins the last-resort race against that rule
+       and never displaces the family the app actually asked for. -->
+  <match target="pattern">
+    <test name="lang" compare="contains">
+      <string>ur</string>
+    </test>
+    <edit name="family" mode="append" binding="strong">
+      <string>Noto Nastaliq Urdu</string>
+    </edit>
+  </match>
+
+  <!-- Chromium and Electron resolve missing glyphs one character at a time
+       without lang on the pattern, so the rules above never fire for them and
+       fontconfig falls through to a raw charset scan that lands on Nastaliq
+       (or on Kufi, once the latin alias chains have widened the pattern).
+       Naming Naskh as a last-resort family covers that path. Appending keeps
+       it behind every family the app actually asked for, and charset matching
+       outranks family matching, so a font that does not cover the codepoint
+       can never be pulled in: Latin, monospace, emoji, Nerd Font glyphs and
+       CJK all resolve exactly as before. -->
+  <match target="pattern">
+    <edit name="family" mode="append" binding="strong">
+      <string>Noto Naskh Arabic</string>
+    </edit>
+  </match>
+
   <alias>
     <family>system-ui</family>
     <prefer>