Use of paid services for product localization
Mozilla’s localization model has always been community-first. Volunteer contributors and community managers are the foundation of how our products are translated, reviewed, and maintained across the world.
As Mozilla grows in new markets and launches new initiatives, there are occasional situations where release timelines and business requirements call for additional support. To improve transparency and reduce ambiguity, this page documents when and how paid localization services may be temporarily used.
This documentation does not represent a change in our current workflow. It clarifies a structured and limited approach to ensure product availability in priority markets while preserving long-term community ownership.
When is paid localization service used?
Temporary localization service by a Language Service Provider (LSP) may be considered only when both of the following conditions apply:
- Business priority: A locale is required for market expansion, product launch, or another defined strategic initiative.
- Community bandwidth gap: The current community does not have sufficient active capacity to meet required timelines or completion levels.
Paid localization service is not used to replace active communities or override community decisions. If either condition is not met, paid localization service is not necessary.
What does paid localization service include?
Depending on the situation, paid localization service may include:
- Translating and reviewing missing strings.
- Reviewing pending suggestions.
- In-context linguistic QA (LQA).
- Terminology alignment within the defined scope.
The scope is defined in advance and limited to specific products and timeframes. Community-developed terminology and style guidelines will be adhered to during paid engagements.
How does this affect community ownership?
Paid localization service is temporary, scoped to specific products or releases, used to meet defined timelines, and designed to transition back to community ownership.
After the defined work is completed, normal community contribution and review activities resume. Communities may review, refine, and improve translations after initial delivery.
How are communities informed?
Communication is intended to ensure transparency and avoid overlapping work. Before paid localization service begins:
- Notify community managers and active translators
- Explain the business rationale
- Share the scope and expected duration
Frequently Asked Questions
Does this mean the community is being replaced?
No. Paid localization service is short-term, temporary, and limited to specific deliverables. Community ownership remains the long-term model.
Will paid translators override community decisions?
No. Paid localization service focuses on meeting delivery timelines within a defined scope. Community defined terminology and style will continue to guide localization, and ultimate ownership by the community will remain unchanged. Communities can review and refine translations after the scoped work is completed.
What if the community disagrees with the decision to implement temporary paid localization service?
Decisions are based on documented business priorities and delivery timelines. While we aim to communicate in advance and welcome feedback, some initiatives may require action within defined release schedules. Paid localization service remains limited and time-bound.
Why not wait for volunteers instead of using paid translators?
Volunteer contributions are central to Mozilla localization. However, when product launches or market initiatives have defined timelines, missing them may affect user experience and strategic goals. Paid localization service is used only when timelines cannot be met through available volunteer capacity.
Will paid translators maintain the product afterward?
No. Paid localization service is structured around specific scopes and timelines. Long-term ownership and maintenance remain community-driven.
Can communities request paid localization service?
Paid localization service is implemented when both business priorities and community capacity gaps are present.
Is paid localization becoming the default model?
No. Mozilla remains committed to community-driven localization. Paid localization service is used selectively and only when a business need encounters a capacity gap.
Couldn’t Mozilla pay community members instead?
No. Mozilla cannot engage individual contributors through direct payment for localization work. When paid support is needed, we are required to work with vetted language service providers that meet legal and procurement requirements. Community contribution is the heart of Mozilla localization and vital to our mission. We continue to invest in and advocate for resources that support contributors, such as events and community engagement initiatives.