Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
Before submitting, make sure you've checked the following:
Linked Issue/Discussion: This PR references an existing Issue or Discussion — Closes #___ / Relates to #___. If one does not exist, create one first. PRs without a linked issue or discussion may be closed without review.
Target branch: Verify that the pull request targets the dev branch. PRs targeting main will be immediately closed.
Description: Provide a concise description of the changes made in this pull request down below.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Add docs in Open WebUI Docs Repository. Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
Dependencies: Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
Testing: Perform manual tests to verify the implemented fix/feature works as intended AND does not break any other functionality. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to make screenshots of the feature/fix and include them in the PR description.
Agentic AI Code: Confirm this Pull Request is not written by any AI Agent or has at least gone through additional human review AND manual testing. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Design & Architecture: Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
Git Hygiene: Keep PRs atomic (one logical change). Clean up commits and rebase on dev to ensure no unrelated commits (e.g. from main) are included. Push updates to the existing PR branch instead of closing and reopening.
Title Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
BREAKING CHANGE: Significant changes that may affect compatibility
build: Changes that affect the build system or external dependencies
ci: Changes to our continuous integration processes or workflows
chore: Refactor, cleanup, or other non-functional code changes
docs: Documentation update or addition
feat: Introduces a new feature or enhancement to the codebase
fix: Bug fix or error correction
i18n: Internationalization or localization changes
perf: Performance improvement
refactor: Code restructuring for better maintainability, readability, or scalability
style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
test: Adding missing tests or correcting existing tests
WIP: Work in progress, a temporary label for incomplete or ongoing work
Changelog Entry
Description
Update Russian localization strings for Open WebUI.
Added
Missing Russian translations for existing UI strings.
Changed
Refined existing Russian translations for consistency and context.
Updated Automations page strings and response generation error wording.
Deprecated
None.
Removed
None.
Fixed
Empty Russian translation entries.
Security
None.
Breaking Changes
BREAKING CHANGE: None.
Additional Information
Why existing translations were changed
The main purpose of this PR is to fill in missing Russian translations. A large number of UI strings in the Russian locale were still empty, so the first step was to provide translations for those missing entries.
After that, the existing Russian translations were reviewed in the same locale file. A small number of already translated strings were adjusted where the wording looked inconsistent, unclear, or mismatched with the UI context.
These existing-string updates are limited to Russian text only. They do not change translation keys, UI logic, routes, components, or fallback behavior.
Examples of the follow-up cleanup:
aligning common UI terms across the Russian locale;
replacing awkward or overly informal wording with neutral product language;
correcting context-sensitive strings after checking where they are used in the UI;
making the response generation error message clearer.
JSON parsing was verified.
git diff --check passed.
Screenshots or Videos
N/A.
Contributor License Agreement
By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.
Note
Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/open-webui/open-webui/pull/24728
**Author:** [@mayamsin](https://github.com/mayamsin)
**Created:** 5/14/2026
**Status:** ✅ Merged
**Merged:** 5/15/2026
**Merged by:** [@tjbck](https://github.com/tjbck)
**Base:** `dev` ← **Head:** `ru-ru-translation-update-dev`
---
### 📝 Commits (1)
- [`a2613f6`](https://github.com/open-webui/open-webui/commit/a2613f6b6b05e25e44f70e0d2287881fd19d4547) i18n: update Russian translations
### 📊 Changes
**1 file changed** (+192 additions, -192 deletions)
<details>
<summary>View changed files</summary>
📝 `src/lib/i18n/locales/ru-RU/translation.json` (+192 -192)
</details>
### 📄 Description
# Pull Request Checklist
### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
**Before submitting, make sure you've checked the following:**
- [ ] **Linked Issue/Discussion:** This PR references an existing [Issue](https://github.com/open-webui/open-webui/issues) or [Discussion](https://github.com/open-webui/open-webui/discussions) — `Closes #___` / `Relates to #___`. If one does not exist, create one first. PRs without a linked issue or discussion may be closed without review.
- [x] **Target branch:** Verify that the pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.**
- [x] **Description:** Provide a concise description of the changes made in this pull request down below.
- [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description.
- [ ] **Documentation:** Add docs in [Open WebUI Docs Repository](https://github.com/open-webui/docs). Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
- [ ] **Dependencies:** Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
- [x] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to **make screenshots of the feature/fix and include them in the PR description**.
- [x] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
- [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
- [x] **Design & Architecture:** Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
- [x] **Git Hygiene:** Keep PRs atomic (one logical change). Clean up commits and rebase on `dev` to ensure no unrelated commits (e.g. from `main`) are included. Push updates to the existing PR branch instead of closing and reopening.
- [x] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following:
- **BREAKING CHANGE**: Significant changes that may affect compatibility
- **build**: Changes that affect the build system or external dependencies
- **ci**: Changes to our continuous integration processes or workflows
- **chore**: Refactor, cleanup, or other non-functional code changes
- **docs**: Documentation update or addition
- **feat**: Introduces a new feature or enhancement to the codebase
- **fix**: Bug fix or error correction
- **i18n**: Internationalization or localization changes
- **perf**: Performance improvement
- **refactor**: Code restructuring for better maintainability, readability, or scalability
- **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- **test**: Adding missing tests or correcting existing tests
- **WIP**: Work in progress, a temporary label for incomplete or ongoing work
# Changelog Entry
### Description
- Update Russian localization strings for Open WebUI.
### Added
- Missing Russian translations for existing UI strings.
### Changed
- Refined existing Russian translations for consistency and context.
- Updated Automations page strings and response generation error wording.
### Deprecated
- None.
### Removed
- None.
### Fixed
- Empty Russian translation entries.
### Security
- None.
### Breaking Changes
- **BREAKING CHANGE**: None.
---
### Additional Information
### Why existing translations were changed
The main purpose of this PR is to fill in missing Russian translations. A large number of UI strings in the Russian locale were still empty, so the first step was to provide translations for those missing entries.
After that, the existing Russian translations were reviewed in the same locale file. A small number of already translated strings were adjusted where the wording looked inconsistent, unclear, or mismatched with the UI context.
These existing-string updates are limited to Russian text only. They do not change translation keys, UI logic, routes, components, or fallback behavior.
Examples of the follow-up cleanup:
- aligning common UI terms across the Russian locale;
- replacing awkward or overly informal wording with neutral product language;
- correcting context-sensitive strings after checking where they are used in the UI;
- making the response generation error message clearer.
- JSON parsing was verified.
- `git diff --check` passed.
### Screenshots or Videos
- N/A.
### Contributor License Agreement
- [x] By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](https://github.com/open-webui/open-webui/blob/main/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms.
> [!NOTE]
> Deleting the CLA section will lead to immediate closure of your PR and it will not be merged in.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/open-webui/open-webui/pull/24728
Author: @mayamsin
Created: 5/14/2026
Status: ✅ Merged
Merged: 5/15/2026
Merged by: @tjbck
Base:
dev← Head:ru-ru-translation-update-dev📝 Commits (1)
a2613f6i18n: update Russian translations📊 Changes
1 file changed (+192 additions, -192 deletions)
View changed files
📝
src/lib/i18n/locales/ru-RU/translation.json(+192 -192)📄 Description
Pull Request Checklist
Note to first-time contributors: Please open a discussion post in Discussions to discuss your idea/fix with the community before creating a pull request, and describe your changes before submitting a pull request.
This is to ensure large feature PRs are discussed with the community first, before starting work on it. If the community does not want this feature or it is not relevant for Open WebUI as a project, it can be identified in the discussion before working on the feature and submitting the PR.
Before submitting, make sure you've checked the following:
Closes #___/Relates to #___. If one does not exist, create one first. PRs without a linked issue or discussion may be closed without review.devbranch. PRs targetingmainwill be immediately closed.devto ensure no unrelated commits (e.g. frommain) are included. Push updates to the existing PR branch instead of closing and reopening.Changelog Entry
Description
Added
Changed
Deprecated
Removed
Fixed
Security
Breaking Changes
Additional Information
Why existing translations were changed
The main purpose of this PR is to fill in missing Russian translations. A large number of UI strings in the Russian locale were still empty, so the first step was to provide translations for those missing entries.
After that, the existing Russian translations were reviewed in the same locale file. A small number of already translated strings were adjusted where the wording looked inconsistent, unclear, or mismatched with the UI context.
These existing-string updates are limited to Russian text only. They do not change translation keys, UI logic, routes, components, or fallback behavior.
Examples of the follow-up cleanup:
aligning common UI terms across the Russian locale;
replacing awkward or overly informal wording with neutral product language;
correcting context-sensitive strings after checking where they are used in the UI;
making the response generation error message clearer.
JSON parsing was verified.
git diff --checkpassed.Screenshots or Videos
Contributor License Agreement
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.