New pt-BR translations for items introduced in the latest releases, plus a consistency/quality pass across existing strings (grammar, tone, capitalization, pluralization). Placeholders and hotkeys preserved. No logic changes.
Pull Request Checklist
First-time contributor note acknowledged.
Target branch: PR targets dev.
Description: Included (see above and changelog).
Changelog: Entry provided below following Keep a Changelog.
Documentation: N/A (translation-only change; no docs impacted).
Dependencies: None added/changed.
Testing: Manual validation performed (see steps below).
Add missing pt-BR strings for new UI items introduced recently and refine existing translations for clarity and consistency. Improves UX for Brazilian Portuguese users; zero impact on application logic.
Added
New pt-BR strings for recently introduced menus, tooltips, settings, and notifications.
Changed
Standardized tone (second-person “você”), capitalization, and punctuation.
Improved clarity of error/success messages and helper texts.
Harmonized terminology (e.g., Model → Modelo, Context window → Janela de contexto, Workflow → Fluxo de trabalho).
Preserved and repositioned placeholders where needed to fit natural pt-BR order.
Deprecated
N/A
Removed
N/A
Fixed
Minor typos, inconsistent pluralization, and stray whitespace in several strings.
A few ambiguous translations replaced with domain-accurate wording.
Security
N/A
Breaking Changes
None. No keys renamed or removed; only values adjusted.
Testing
How to validate
Go to Settings → Language and select Português (Brasil).
Trigger both error and success states (e.g., invalid inputs, completed actions) to review messaging.
Verify placeholders like {name}, {count} and keyboard shortcuts render correctly.
Local checks performed
JSON lint and build pass.
Visual verification of long labels to avoid overflow/cut-off.
No layout regressions observed on common screens.
Additional Information
Scope limited to i18n files (pt-BR locale).
If maintainers prefer a style guide for pt-BR (capitalization for buttons, confirmation tone, etc.), I can submit a follow-up PR with a concise glossary and conventions.
Screenshots or Videos
(Optional) I can attach screenshots of key screens upon request.
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.
🔄 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/21527
**Author:** [@joaoback](https://github.com/joaoback)
**Created:** 2/17/2026
**Status:** ✅ Merged
**Merged:** 2/19/2026
**Merged by:** [@tjbck](https://github.com/tjbck)
**Base:** `dev` ← **Head:** `patch-27`
---
### 📝 Commits (1)
- [`49b7f37`](https://github.com/open-webui/open-webui/commit/49b7f37085dfec5a85dfbc8b5746fd2d26fd99be) i18n: pt-BR - add translations for newly added UI items + consistency pass
### 📊 Changes
**1 file changed** (+118 additions, -118 deletions)
<details>
<summary>View changed files</summary>
📝 `src/lib/i18n/locales/pt-BR/translation.json` (+118 -118)
</details>
### 📄 Description
… pass
Translate all remaining untranslated strings to Brazilian Portuguese (pt-BR)
Translated ~100 previously untranslated entries (empty "" values) across the Open WebUI i18n JSON file. Changes include:
Translated UI labels, form fields, tooltips, and error messages Kept brand/product names unchanged where appropriate (e.g., Bing, Brave, Gemini, OpenAI, YouTube) Translated technical terms with context-appropriate Brazilian Portuguese equivalents (e.g., "Timeout" → "Tempo limite", "Config" → "Configuração", "Endpoint URL" → "URL do Endpoint") Added translations for search engine integrations (Kagi, Perplexity, SerpApi, Tavily, Yacy, Yandex, etc.) Translated plural forms for source retrieval messages (sources_one, sources_many, sources_other) No untranslated entries remain in the file.
# i18n(pt-BR): add translations for newly added UI items + consistency pass
New **pt-BR** translations for items introduced in the latest releases, plus a consistency/quality pass across existing strings (grammar, tone, capitalization, pluralization). Placeholders and hotkeys preserved. No logic changes.
---
## Pull Request Checklist
> First-time contributor note acknowledged.
* [x] **Target branch:** PR targets `dev`.
* [x] **Description:** Included (see above and changelog).
* [x] **Changelog:** Entry provided below following *Keep a Changelog*.
* [x] **Documentation:** N/A (translation-only change; no docs impacted).
* [x] **Dependencies:** None added/changed.
* [x] **Testing:** Manual validation performed (see steps below).
* [x] **Code review:** Self-review done; keys unchanged; JSON validated.
* [x] **Prefix:** `i18n` used in title.
---
## Changelog Entry
### Description
Add missing **pt-BR** strings for new UI items introduced recently and refine existing translations for clarity and consistency. Improves UX for Brazilian Portuguese users; zero impact on application logic.
### Added
* New **pt-BR** strings for recently introduced menus, tooltips, settings, and notifications.
### Changed
* Standardized tone (second-person “você”), capitalization, and punctuation.
* Improved clarity of error/success messages and helper texts.
* Harmonized terminology (e.g., *Model* → **Modelo**, *Context window* → **Janela de contexto**, *Workflow* → **Fluxo de trabalho**).
* Preserved and repositioned placeholders where needed to fit natural pt-BR order.
### Deprecated
* N/A
### Removed
* N/A
### Fixed
* Minor typos, inconsistent pluralization, and stray whitespace in several strings.
* A few ambiguous translations replaced with domain-accurate wording.
### Security
* N/A
### Breaking Changes
* **None.** No keys renamed or removed; only values adjusted.
---
## Testing
**How to validate**
1. Go to **Settings → Language** and select **Português (Brasil)**.
2. Smoke test key areas affected by recent changes:
* Settings (general/models/privacy/import/export)
* Workflows/Executions
* Playground and Prompt helpers/tooltips
* Conversations/History (bulk actions, confirmations)
3. Trigger both **error** and **success** states (e.g., invalid inputs, completed actions) to review messaging.
4. Verify placeholders like `{name}`, `{count}` and keyboard shortcuts render correctly.
**Local checks performed**
* JSON lint and build pass.
* Visual verification of long labels to avoid overflow/cut-off.
* No layout regressions observed on common screens.
---
## Additional Information
* Scope limited to i18n files (`pt-BR` locale).
* If maintainers prefer a style guide for pt-BR (capitalization for buttons, confirmation tone, etc.), I can submit a follow-up PR with a concise glossary and conventions.
## Screenshots or Videos
* (Optional) I can attach screenshots of key screens upon request.
---
## Contributor License Agreement
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.
---
<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/21527
Author: @joaoback
Created: 2/17/2026
Status: ✅ Merged
Merged: 2/19/2026
Merged by: @tjbck
Base:
dev← Head:patch-27📝 Commits (1)
49b7f37i18n: pt-BR - add translations for newly added UI items + consistency pass📊 Changes
1 file changed (+118 additions, -118 deletions)
View changed files
📝
src/lib/i18n/locales/pt-BR/translation.json(+118 -118)📄 Description
… pass
Translate all remaining untranslated strings to Brazilian Portuguese (pt-BR)
Translated ~100 previously untranslated entries (empty "" values) across the Open WebUI i18n JSON file. Changes include:
Translated UI labels, form fields, tooltips, and error messages Kept brand/product names unchanged where appropriate (e.g., Bing, Brave, Gemini, OpenAI, YouTube) Translated technical terms with context-appropriate Brazilian Portuguese equivalents (e.g., "Timeout" → "Tempo limite", "Config" → "Configuração", "Endpoint URL" → "URL do Endpoint") Added translations for search engine integrations (Kagi, Perplexity, SerpApi, Tavily, Yacy, Yandex, etc.) Translated plural forms for source retrieval messages (sources_one, sources_many, sources_other) No untranslated entries remain in the file.
i18n(pt-BR): add translations for newly added UI items + consistency pass
New pt-BR translations for items introduced in the latest releases, plus a consistency/quality pass across existing strings (grammar, tone, capitalization, pluralization). Placeholders and hotkeys preserved. No logic changes.
Pull Request Checklist
dev.i18nused in title.Changelog Entry
Description
Add missing pt-BR strings for new UI items introduced recently and refine existing translations for clarity and consistency. Improves UX for Brazilian Portuguese users; zero impact on application logic.
Added
Changed
Deprecated
Removed
Fixed
Security
Breaking Changes
Testing
How to validate
Go to Settings → Language and select Português (Brasil).
Smoke test key areas affected by recent changes:
Trigger both error and success states (e.g., invalid inputs, completed actions) to review messaging.
Verify placeholders like
{name},{count}and keyboard shortcuts render correctly.Local checks performed
Additional Information
pt-BRlocale).Screenshots or Videos
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.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.