If your Salesforce org serves users in multiple languages, a change is coming that you need to know about. As part of the Summer '26 release, Salesforce is updating the default translations for standard object names, tab labels, and field names across 12 languages. These changes will apply automatically to all orgs when the release deploys to your instance.
While this is a routine translation refinement — not a breaking change — it can catch administrators off guard if they aren't prepared. Updated labels can affect how users navigate the interface, how reports display data, and even how automation references standard objects. The good news? Salesforce provides straightforward tools to review, accept, or revert any changes you don't want.
In this guide, we'll walk you through exactly what's changing, which languages are impacted, how to prepare your org, how to revert changes if needed, and best practices for managing multilingual Salesforce environments going forward.
Salesforce periodically refines the default translations for standard labels to improve linguistic accuracy, cultural relevance, and consistency across the platform. In Summer '26, this update touches standard object names, tab labels, and field names — the core UI elements that users interact with daily.
The following 12 languages will see updated translations:
| Language | Language Code | Region |
|---|---|---|
| Chinese (Simplified) | zh_CN | China |
| Dutch | nl_NL | Netherlands |
| Finnish | fi | Finland |
| German | de | Germany/Austria/Switzerland |
| Hebrew | iw | Israel |
| Italian | it | Italy |
| Japanese | ja | Japan |
| Korean | ko | South Korea |
| Norwegian | no | Norway |
| Russian | ru | Russia |
| Spanish | es | Spain/Latin America |
| Spanish (Mexico) | es_MX | Mexico |
The updates apply to three categories of standard labels:
Important: These changes only affect the display labels — the translated text users see in the interface. API names, field-level security, object relationships, and underlying data remain completely unchanged.
Languages evolve. Business terminology shifts. A translation that was correct five years ago may now feel outdated or ambiguous. Salesforce regularly reviews translations with native-speaking linguists to ensure terms reflect current usage.
Different regions may prefer different terms for the same concept. For example, the word for "Opportunity" in a business context can vary between Spanish-speaking countries. These updates help align labels with regional business conventions.
As Salesforce adds new features and objects, they ensure that translation patterns remain consistent. If a newer object uses a more accurate translation for a concept, older objects may be updated to match.
Clear, accurate labels reduce confusion and support adoption — especially important for organizations onboarding new users in non-English markets.
The Summer '26 release follows Salesforce's standard phased rollout:
| Phase | Date | What Happens |
|---|---|---|
| Sandbox Preview | May 8, 2026 | Sandboxes begin upgrading — test here first |
| 1st Production Wave | May 15, 2026 | Early production instances receive the update |
| 2nd Production Wave | June 5, 2026 | Broader deployment across more instances |
| Final Deployment | June 12–13, 2026 | All remaining production orgs are upgraded |
Pro tip: Bookmark your instance's Trust Status page and check it regularly during release windows. Dates can shift, so stay current.
Being proactive is the best strategy. Here's how to review the label changes before they reach your production org:
Once the sandbox preview begins on May 8, 2026, your sandbox environments will be upgraded to Summer '26. This is your testing ground.
Salesforce publishes a detailed knowledge article titled "Review Summer '26 Updated Label Translations" on Salesforce Help. This article lists the specific translations that have changed, organized by language and object.
Use Translation Workbench to export current translations for comparison:
Before the release hits production, take screenshots or export a record of your current translated labels. This creates a baseline for comparison and makes it easier to identify exactly what changed.
If any updated translations don't work for your organization — whether due to internal terminology preferences, training material alignment, or user familiarity — you can revert them using the Rename Tabs and Labels feature.
Reference: Rename Object, Tab, and Field Labels | Considerations for Renaming Tab and Field Labels
While label changes don't affect API names or data, they can still have downstream effects. Use this checklist to assess your org's exposure:
Start by understanding how many users are affected and in which languages. In Setup, check Company Information for the default language, then review user records filtered by language preference. Create a quick report showing user count by language and focus your preparation on the most widely used affected languages.
As soon as sandboxes are upgraded (starting May 8, 2026):
Prepare a brief communication for your user community covering what's changing, when it's happening (share your specific instance's deployment date), the expected impact, and what action users should take if they notice confusing label changes.
If there are labels your organization has strong preferences for (e.g., you've trained users on specific terminology), set custom overrides before the release using Rename Tabs and Labels. Custom overrides take precedence over Salesforce defaults, preventing unwanted changes from appearing to users.
Schedule a quick validation window after the release deploys to production:
For organizations with complex multilingual requirements, Translation Workbench provides more granular control than Rename Tabs and Labels.
Translation Workbench is a native Salesforce tool that lets you manage translations for custom labels, custom fields, picklist values, record types, and more. While Rename Tabs and Labels handles standard object and field label overrides, Translation Workbench covers the broader translation ecosystem.
If you haven't enabled it yet:
Whether Summer '26 label changes affect you minimally or significantly, these best practices help maintain a smooth multilingual Salesforce experience long-term:
Create and maintain a centralized glossary of your organization's preferred translations for key business terms. This becomes the reference when resolving any translation disputes or inconsistencies.
For every major Salesforce release (three times per year): review the release notes for translation changes, test in sandbox with each supported language, document changes and communicate to stakeholders, and schedule post-deployment validation.
This is critical for avoiding label-related breaks. In Flows, reference fields by API name, not display label. In SOQL queries, always use API names (they never change with translations). In Apex code, use Schema methods to get labels dynamically if needed. In reports, while column headers may display translated labels, the underlying field references use API names.
Create a simple mechanism — a Slack channel, a Chatter group, or a quick form — where users in non-English markets can report translation issues. This feedback loop helps you catch problems early and improves the overall experience.
Keep a record of every label you've customized using Rename Tabs and Labels. This documentation is invaluable when onboarding new administrators, troubleshooting translation inconsistencies, planning for future release updates, or migrating to new orgs or sandboxes.
No. The Summer '26 translation updates only affect standard object names, tab labels, and standard field names. Custom objects, custom fields, and any translations you've created through Translation Workbench remain unchanged.
Yes. Once your sandbox is upgraded (starting May 8, 2026), you can log in with a user profile set to each affected language and compare the labels. Salesforce also publishes a knowledge article titled "Review Summer '26 Updated Label Translations" with specific details.
No. If you've already customized a standard label using Rename Tabs and Labels, your override takes precedence. Salesforce's updated default translations only apply to labels you haven't customized.
If all your users have English set as their language preference and your org's default language is English, these translation changes will not affect your org. The changes only apply to the 12 languages listed in this guide.
The same label changes apply to the Salesforce mobile app. Users accessing Salesforce on mobile devices with one of the 12 affected languages will see the updated labels after the release deploys to your instance.
No. API names (e.g., Account.Name, Opportunity.StageName) and all security configurations remain completely unchanged. Only the display labels — the text users see in the UI — are updated.
You can immediately override any incorrect or unwanted translation using the Rename Tabs and Labels feature in Setup. For more complex translation needs, use Translation Workbench. You can also report translation issues to Salesforce Support.
The Summer '26 label translation update is a routine but meaningful maintenance item for any organization operating Salesforce in multiple languages. By understanding what's changing, testing proactively in your sandbox, communicating clearly with your users, and leveraging tools like Rename Tabs and Labels and Translation Workbench, you can ensure a smooth transition with zero disruption to your business processes.
The key takeaway: don't wait for the changes to surprise you. Use the sandbox preview window starting May 8, audit your multilingual footprint, and establish the overrides you need before the production rollout reaches your instance.
Need help preparing your Salesforce org for Summer '26? Vantage Point specializes in Salesforce administration, multi-language org management, and release readiness. Our team can audit your org's translation setup, implement proactive overrides, and ensure your users experience a seamless transition. Contact us at vantagepoint.io to get started.
Vantage Point is a certified Salesforce and HubSpot consulting partner specializing in CRM implementation, integration, and optimization for businesses of all sizes. With deep expertise in Salesforce (Sales Cloud, Service Cloud, Experience Cloud, Data Cloud), HubSpot CRM, MuleSoft integration, and AI-powered solutions, Vantage Point helps organizations maximize their technology investments and drive measurable business results. Learn more at vantagepoint.io.