github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-17 17:02:01 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #13785] feat: Add support for Vazirmatn font for Persian and Arabic UI text #17032

New Issue
Closed
opened 2026-04-19 22:48:51 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-19 22:48:51 -05:00
Owner
Copy Link

Originally created by @sizadbakhsh on GitHub (May 11, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13785

Check Existing Issues

  • I have searched the existing issues and discussions.

Problem Description

Currently, the default font used in Open WebUI does not render Persian or Arabic scripts with optimal readability or aesthetics. As a result, the user interface appears less polished for native speakers of these languages, affecting usability and user experience.

Desired Solution you'd like

Please consider including the Vazirmatn font as the default font for content rendered in Persian or Arabic. Vazirmatn is a modern, well-designed, and actively maintained font optimized for readability in these scripts. It’s open source and has good multilingual fallback handling, making it suitable for integration into web-based UIs.

Notably, the Grok chatbot project has recently added support for Vazirmatn, significantly improving the UI for right-to-left language users. It would be a great enhancement if Open WebUI also provided a similar improvement.

Ideally, Open WebUI could either:

Automatically apply Vazirmatn when detecting Persian/Arabic content.

Or offer a configuration option to choose fonts per language.

Alternatives Considered

Using the browser’s default fallback fonts — but they are inconsistent across platforms and often lack typographic quality for Persian/Arabic.

Custom user CSS injection — not feasible for non-technical users or those running Open WebUI in controlled environments.

Additional Context

GitHub repo for Vazirmatn: https://github.com/rastikerdar/vazirmatn

Google Fonts link: https://fonts.google.com/specimen/Vazirmatn

The font is licensed under SIL Open Font License 1.1, which is compatible with open source projects.

This change would greatly improve accessibility and visual experience for a significant portion of the user base in regions using RTL scripts.

The Grok chatbot UI already includes Vazirmatn for Persian/Arabic, which shows how much of an impact this simple change can have.

Originally created by @sizadbakhsh on GitHub (May 11, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/13785 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Currently, the default font used in Open WebUI does not render Persian or Arabic scripts with optimal readability or aesthetics. As a result, the user interface appears less polished for native speakers of these languages, affecting usability and user experience. ### Desired Solution you'd like Please consider including the [Vazirmatn](https://github.com/rastikerdar/vazirmatn) font as the default font for content rendered in Persian or Arabic. Vazirmatn is a modern, well-designed, and actively maintained font optimized for readability in these scripts. It’s open source and has good multilingual fallback handling, making it suitable for integration into web-based UIs. Notably, the Grok chatbot project has recently added support for Vazirmatn, significantly improving the UI for right-to-left language users. It would be a great enhancement if Open WebUI also provided a similar improvement. Ideally, Open WebUI could either: Automatically apply Vazirmatn when detecting Persian/Arabic content. Or offer a configuration option to choose fonts per language. ### Alternatives Considered Using the browser’s default fallback fonts — but they are inconsistent across platforms and often lack typographic quality for Persian/Arabic. Custom user CSS injection — not feasible for non-technical users or those running Open WebUI in controlled environments. ### Additional Context GitHub repo for Vazirmatn: https://github.com/rastikerdar/vazirmatn Google Fonts link: https://fonts.google.com/specimen/Vazirmatn The font is licensed under SIL Open Font License 1.1, which is compatible with open source projects. This change would greatly improve accessibility and visual experience for a significant portion of the user base in regions using RTL scripts. The Grok chatbot UI already includes Vazirmatn for Persian/Arabic, which shows how much of an impact this simple change can have.
GiteaMirror commented 2026-04-19 22:48:52 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (May 11, 2025):

Already implemented with the latest.

<!-- gh-comment-id:2870019138 --> @tjbck commented on GitHub (May 11, 2025): Already implemented with the latest.
GiteaMirror commented 2026-04-19 22:48:53 -05:00
Author
Owner
Copy Link

@sizadbakhsh commented on GitHub (May 11, 2025):

Thank you for including Vazirmatn in the latest version — it’s a great step forward!

However, I’ve tested the current implementation and noticed a couple of important points:

Output font (response area):
While Vazirmatn is included in the font-family list, it appears at the end of the stack, after fonts like Inter, Segoe UI, Roboto, etc. Since these fonts are commonly available on most systems, the browser never actually reaches Vazirmatn when rendering Persian or Arabic text. This leads to suboptimal readability and spacing issues.

Input field (user typing area):
The input box currently uses the Archivo font, which is not designed for RTL languages and causes issues with character rendering and alignment. This breaks the consistency of the UI and makes typing in Persian/Arabic less comfortable.
<!-- gh-comment-id:2870036462 --> @sizadbakhsh commented on GitHub (May 11, 2025): Thank you for including Vazirmatn in the latest version — it’s a great step forward! However, I’ve tested the current implementation and noticed a couple of important points: Output font (response area): While Vazirmatn is included in the font-family list, it appears at the end of the stack, after fonts like Inter, Segoe UI, Roboto, etc. Since these fonts are commonly available on most systems, the browser never actually reaches Vazirmatn when rendering Persian or Arabic text. This leads to suboptimal readability and spacing issues. Input field (user typing area): The input box currently uses the Archivo font, which is not designed for RTL languages and causes issues with character rendering and alignment. This breaks the consistency of the UI and makes typing in Persian/Arabic less comfortable.
GiteaMirror commented 2026-04-19 22:48:54 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (May 11, 2025):

4c06683e95 might've addressed your concern, testing wanted here.

<!-- gh-comment-id:2870117784 --> @tjbck commented on GitHub (May 11, 2025): 4c06683e95630bd03d50165e736849697cc90abf might've addressed your concern, testing wanted here.
GiteaMirror commented 2026-04-19 22:48:54 -05:00
Author
Owner
Copy Link

@sizadbakhsh commented on GitHub (May 11, 2025):

Confirmed! The fix in 4c06683 works for me. Thank you!

<!-- gh-comment-id:2870200256 --> @sizadbakhsh commented on GitHub (May 11, 2025): Confirmed! The fix in 4c06683 works for me. Thank you!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#17032
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?