Unaunga mkono muundo gani wa faili?

Tunaunga mkono muundo wa Chrome extension messages.json. Pakia kwa lugha yoyote ya chanzo—AI yetu huitambua kiotomatiki. Kila faili inapaswa kuwa na funguo za ujumbe zenye sehemu ya 'message', hiari 'description', na hiari 'placeholders'. Tunathibitisha muundo wakati wa kupakia na tunakataa faili zisizo sahihi.

Je, mnatfsiri vishikizo kama $PLACEHOLDER$?

Hapana—tunavihifadhi kama vilivyo. AI yetu imefunzwa kutambua sintaksia ya kishikizo cha Chrome ($PLACEHOLDER$) na kuviacha bila kuguswa katika tafsiri zote. Maandishi yanayozunguka hutafsiriwa huku vishikizo vikibaki salama.

Bei inategemea ada ya chini ya $9.99 pamoja na gharama ya kila lugha inayoongezeka kulingana na idadi ya tokeni za faili yako. Faili kubwa = bei ya juu. Pia tunatoa chaguo la Uchakataji wa Kipaumbele (+$5) kuruka foleni na kukamilisha ndani ya saa 1. Unaona bei kamili baada ya kupakia faili yako.

Tafsiri huchukua muda gani?

Kazi nyingi hukamilika ndani ya chini ya dakika 5. Tunachakata lugha zote kwa wakati mmoja kwa kutumia GPT-5. Kazi za kipaumbele huchakatwa mbele ya foleni na kwa kawaida hukamilika ndani ya dakika 1-2.

Je, mnahifadhi faili zangu?

Tunahifadhi faili yako ya chanzo na tafsiri zilizozalishwa kwa siku 7 ili uweze kuzipakua tena. Baada ya siku 7, faili zote hufutwa kabisa. Hatushiriki maudhui yako na wahusika wengine zaidi ya API ya OpenAI (inayohitajika kwa tafsiri).

Ni lugha gani zinazotumika?

Tunaunga mkono maeneo 52 yanayojumuisha lugha zote kuu za Chrome Web Store: Kijerumani, Kifaransa, Kihispania, Kiitaliano, Kireno (Brazili na Ureno), Kijapani, Kikorea, Kichina (Rahisi na Jadi), Kiarabu, Kihindi, Kirusi, na nyingine nyingi. Kila eneo hutumia msimbo sahihi wa eneo (mf., pt_BR, zh_CN).

Imeundwa mahsusi kwa viendelezi vya Chrome

Ujanibishaji wa AI kwa Viendelezi vya Chrome

Pakia messages.json yako ya chanzo, chagua lugha lengwa, lipa mara moja, kisha pakua ZIP ya _locales iliyo tayari kutumwa.

Tafsiri salama kwa vishikizo

Inalingana na Chrome messages.json

Bei iliyo wazi

messages.json
Lugha ya chanzo (mfano)
{
  "appName": {
    "message": "My Extension",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
Kijerumani (matokeo)
{
  "appName": {
    "message": "Meine Erweiterung",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hallo, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}

52 locales

Inavyofanya kazi

Hatua tatu rahisi za kujanibisha Kiendelezi cha Chrome yako. Tafsiri huanza baada ya malipo—tunaweka kazi kwenye foleni na kutengeneza ZIP ndani ya dakika chache.

Pakia

Dondosha faili yako ya messages.json ya chanzo. Tunaichanganua papo hapo na kuthibitisha umbizo la Kiendelezi cha Chrome.

Chagua lugha na uone bei

Chagua kutoka lugha 52. Ona bei iliyo wazi kulingana na ukubwa wa faili yako kabla ya kulipa.

Pakua ZIP

Lipa mara moja kupitia Stripe. Tunatengeneza faili zote za _locales/{lang}/messages.json na kuzikusanya kwenye ZIP.

Imeundwa kwa ajili ya wasanidi programu

Imeundwa mahsusi kwa muundo wa eneo wa Kiendelezi cha Chrome. Si zana ya tafsiri ya jumla.

Inatambua muundo wa Chrome

Imeundwa mahsusi kwa muundo wa messages.json wa Kiendelezi cha Chrome wenye usaidizi wa message, description, na placeholders.

Ulinzi wa placeholder

Huhifadhi sintaksia ya $PLACEHOLDER$ kama ilivyo. Vigeu vyako hubaki salama katika lugha zote.

Muktadha wa maelezo

Tunasoma sehemu zako za description na kuzitumia kama vidokezo vya muktadha kwa tafsiri sahihi zaidi za AI.

Uhamishaji wa ZIP tayari

Pakua ZIP yenye muundo sahihi wa folda _locales/{lang}/messages.json. Iweke kwenye kiendelezi chako.

Uchakataji sambamba

Lugha zote hutafsiriwa kwa wakati mmoja. Kazi nyingi hukamilika ndani ya chini ya dakika 5.

Malipo ya mara moja

Hakuna usajili, hakuna ada za kila mwezi. Lipa mara moja kwa kila kazi, pakua milele.

Jinsi i18n ya kiendelezi cha Chrome inavyofanya kazi

Viendelezi vya Chrome hutangaza "default_locale" kwenye manifest.json ili kuwezesha i18n. Kisha kivinjari husoma tungo za lugha kutoka _locales/{locale}/messages.json wakati wa utekelezaji. Kila ufunguo una uga wa "message", "description" ya hiari kwa muktadha, na "placeholders" za hiari kwa thamani zinazobadilika — yote ambayo LocalePack inaelewa moja kwa moja.

Muundo wa folda ya _locales/

_locales/
├── en/
│   └── messages.json   ← default_locale
├── de/
│   └── messages.json
├── fr/
│   └── messages.json
└── ja/
    └── messages.json

messages.json

{
  "appName": {
    "message": "My Extension",
    "description": "Extension name"
  },
  "greeting": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": { "content": "$1" }
    }
  }
}

API ya wakati wa utekelezaji

chrome.i18n

Mfano wa mwito

chrome.i18n.getMessage("appName")

Inahitajika kwenye manifest

"default_locale"

Duka la Wavuti la Chrome huonyesha kiotomatiki jina na maelezo ya kiendelezi chako katika lugha ya mgeni wakati _locales/ ina folda ya lugha yao.

Jifunze muundo wa _locales →

Chrome-specific rules that break builds

Chrome's i18n system fails quietly. These are the four rules that cause most broken releases.

A fixed list of locale folders: Chrome reads only a fixed set of locale codes under _locales/. Any folder outside that list is ignored — no build error, no console warning, the strings simply never load.
Underscores, not hyphens: Chrome expects pt_BR and zh_CN. BCP-47 style pt-BR or zh-CN does not match any supported locale, so the folder is skipped and the UI falls back to default_locale.
default_locale is not optional: If an extension ships a _locales/ directory, manifest.json must declare default_locale. Omit it and the manifest fails validation outright.
getMessage() is synchronous: chrome.i18n.getMessage() reads from disk synchronously, which makes it awkward inside an async Manifest V3 service worker — unlike a popup or content script, where it behaves normally.

A key that does not exist returns an empty string and logs nothing at all. Missing translations show up as blank UI, not as errors.

Kwa nini usitumie tu zana za jumla?

Zana za tafsiri za matumizi ya jumla hazielewi muundo wa Kiendelezi cha Chrome.

	LocalePack	Tafsiri ya mkono	TMS ya jumla
Muda wa usanidi	Dakika 2	Saa kwa kila lugha	Dakika 30+
Uwazi wa gharama
Usalama wa muundo wa Chrome
Ulinzi wa placeholder
Kasi (lugha 52)	< dakika 5	Wiki	Saa
Inafaa zaidi kwa	Viendelezi vya Chrome	Miradi midogo	Programu za wavuti za makampuni

Visa vya Mafanikio

Miradi halisi iliyotumia LocalePack kufikia hadhira ya kimataifa katika hadi lugha 52.

AstrologerAI AI astrology app localized into 52 languages

AstrologerAI: an AI astrology app localized into 52 languages

How the AstrologerAI app translated its entire experience into 52 languages with LocalePack — 6.3M tokens for $58.73 — to reach a worldwide audience in their own language.

DevToys.pro developer tools web app localized into 52 languages

DevToys.pro: 400% international traffic growth across 52 languages

How the DevToys.pro web app translated its entire UI into 52 languages with LocalePack — 5.8M tokens for $58.44 — and quadrupled its international organic traffic.

DevToys New Tab Chrome extension localized into 52 languages

DevToys New Tab: a Chrome extension localized UI + store listing in 52 languages

How the DevToys New Tab Chrome extension localized both its in-extension UI and its Chrome Web Store listing into 52 languages to reach a global audience.

The LocalePack site localized into 52 languages with LocalePack

LocalePack localized itself into 52 languages — with LocalePack

We used our own tool to translate the entire LocalePack site into 52 languages — 2.9M tokens for $27.37 — so developers worldwide find us in their own language.

Tazama visa vyote vya mafanikio

Inaaminiwa na watengenezaji wa viendelezi

“Imeniokoa saa nyingi za kazi ya kuchosha. Nilipakia messages.json yangu, nikapata tafsiri kamili katika muundo uleule niliouhitaji.”

Sarah K.

Msanidi huru, kiendelezi cha AdBlock

“Hatimaye zana inayoelewa muundo wa viendelezi vya Chrome. Hakuna tena kurekebisha vishikizo vilivyovunjika baada ya kutafsiri.”

Marcus T.

Msimamizi wa kiendelezi

“Bei iliyo wazi ndiyo iliyonishawishi. Nilijua hasa nitakacholipa kabla ya kupakia chochote.”

Dev J.

Mchangiaji wa chanzo huria

Lugha zinazotumika

100%

Matokeo salama kwa vishikizo

ZIP

Tayari kusafirisha

Maswali yanayoulizwa mara kwa mara

Kila unachohitaji kujua kuhusu LocalePack.

Related developer guides

Deep dives on the formats, APIs and errors behind this page — written for developers, not translators.

How to localize a Chrome extension (complete guide)

Step-by-step guide to adding i18n to a Chrome extension: _locales structure, default_locale, messages.json syntax, chrome.i18n.getMessage(), placeholder preservation, and how to test locale switching.

chrome.i18n: the complete API reference

All four chrome.i18n methods with exact signatures and return types: which are synchronous, which return promises, what getMessage() returns when it fails, and how browser.i18n differs in Firefox and Safari.

chrome.i18n in MV3 service workers

Synchronous getMessage() is an advantage in an MV3 service worker, not a problem — a common claim that gets this backwards. What actually breaks is the DOM, global-variable caching, localStorage and XMLHttpRequest.

Best tools for Chrome extension localization

An honest comparison of tools that translate Chrome extension messages.json files: LocalePack, Crowdin, Lokalise, Phrase, POEditor, Localazy, Weblate, and Localeship — setup overhead, pricing models, and placeholder safety.

LocalePack vs Lokalise for Chrome Extensions

Honest comparison of LocalePack and Lokalise for Chrome extension messages.json translation. Lokalise is a full TMS with team workflows and a monthly subscription; LocalePack is upload → pay once → download.

Browse all guides →

Uko tayari kusambaza Kiendelezi cha Chrome yako duniani kote?

Lipa mara moja - Pakua ZIP - Sambaza duniani kote

Ijaribu LocalePack

{ "appName": { "message": "My Extension", "description": "Name" }, "welcomeMsg": { "message": "Hello, $USER$!", "placeholders": { "user": { "content": "$1" } } } }

{ "appName": { "message": "Meine Erweiterung", "description": "Name" }, "welcomeMsg": { "message": "Hallo, $USER$!", "placeholders": { "user": { "content": "$1" } } } }

Jinsi i18n ya kiendelezi cha Chrome inavyofanya kazi

_locales/ ├── en/ │ └── messages.json ← default_locale ├── de/ │ └── messages.json ├── fr/ │ └── messages.json └── ja/ └── messages.json

{ "appName": { "message": "My Extension", "description": "Extension name" }, "greeting": { "message": "Hello, $USER$!", "placeholders": { "user": { "content": "$1" } } } }

Chrome-specific rules that break builds

Chrome's i18n system fails quietly. These are the four rules that cause most broken releases.

A fixed list of locale folders

Chrome reads only a fixed set of locale codes under _locales/. Any folder outside that list is ignored — no build error, no console warning, the strings simply never load.

Underscores, not hyphens

Chrome expects pt_BR and zh_CN. BCP-47 style pt-BR or zh-CN does not match any supported locale, so the folder is skipped and the UI falls back to default_locale.

default_locale is not optional

If an extension ships a _locales/ directory, manifest.json must declare default_locale. Omit it and the manifest fails validation outright.

getMessage() is synchronous

chrome.i18n.getMessage() reads from disk synchronously, which makes it awkward inside an async Manifest V3 service worker — unlike a popup or content script, where it behaves normally.

A key that does not exist returns an empty string and logs nothing at all. Missing translations show up as blank UI, not as errors.

LocalePack

Tafsiri ya mkono

TMS ya jumla

Muda wa usanidi

Dakika 2

Saa kwa kila lugha

Dakika 30+

Uwazi wa gharama

Usalama wa muundo wa Chrome

Ulinzi wa placeholder

Kasi (lugha 52)

< dakika 5

Wiki

Saa

Inafaa zaidi kwa

Viendelezi vya Chrome

Miradi midogo

Programu za wavuti za makampuni

Related developer guides

Deep dives on the formats, APIs and errors behind this page — written for developers, not translators.

Ujanibishaji wa AI kwa Viendelezi vya Chrome

Inavyofanya kazi

Pakia

Chagua lugha na uone bei

Pakua ZIP

Kikokotoo cha bei iliyo wazi

1. Pakia faili

2. Chagua lugha

3. Makadirio yako

Imeundwa kwa ajili ya wasanidi programu

Inatambua muundo wa Chrome

Ulinzi wa placeholder

Muktadha wa maelezo

Uhamishaji wa ZIP tayari

Uchakataji sambamba

Malipo ya mara moja

Jinsi i18n ya kiendelezi cha Chrome inavyofanya kazi

Chrome-specific rules that break builds

Kwa nini usitumie tu zana za jumla?

Visa vya Mafanikio

Inaaminiwa na watengenezaji wa viendelezi

Maswali yanayoulizwa mara kwa mara

Unaunga mkono muundo gani wa faili?

Je, mnatfsiri vishikizo kama $PLACEHOLDER$?

Bei huhesabiwaje?

Tafsiri huchukua muda gani?

Je, mnahifadhi faili zangu?

Ni lugha gani zinazotumika?

Je, mnaunga mkono vivinjari vingine mbali na Chrome?

Related developer guides

Uko tayari kusambaza Kiendelezi cha Chrome yako duniani kote?

Ujanibishaji wa AI kwa Viendelezi vya Chrome

Inavyofanya kazi

Pakia

Chagua lugha na uone bei

Pakua ZIP

Kikokotoo cha bei iliyo wazi

1. Pakia faili

2. Chagua lugha

3. Makadirio yako

Imeundwa kwa ajili ya wasanidi programu

Inatambua muundo wa Chrome

Ulinzi wa placeholder

Muktadha wa maelezo

Uhamishaji wa ZIP tayari

Uchakataji sambamba

Malipo ya mara moja

Jinsi i18n ya kiendelezi cha Chrome inavyofanya kazi

Chrome-specific rules that break builds

Kwa nini usitumie tu zana za jumla?

Visa vya Mafanikio

Inaaminiwa na watengenezaji wa viendelezi

Maswali yanayoulizwa mara kwa mara

Unaunga mkono muundo gani wa faili?

Je, mnatfsiri vishikizo kama $PLACEHOLDER$?

Bei huhesabiwaje?

Tafsiri huchukua muda gani?

Je, mnahifadhi faili zangu?

Ni lugha gani zinazotumika?

Je, mnaunga mkono vivinjari vingine mbali na Chrome?

Related developer guides

Uko tayari kusambaza Kiendelezi cha Chrome yako duniani kote?