LocalePack
ChromeFirefoxEdgeOperaSafariSenarai CWS
Vue.jsReact
Next.jsi18nextReact Native
Panduan PembangunKisah Kejayaan
One format, every major browser

Penyetempatan AI untuk browser extensions

Muat naik messages.json sumber anda, pilih bahasa sasaran, bayar sekali, dan muat turun ZIP _locales yang sedia untuk dihantar.

Terjemahan selamat-ruang letak
Mematuhi messages.json WebExtension
Harga telus
messages.json
Bahasa sumber (contoh)
{
  "appName": {
    "message": "My Extension",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hello, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
Jerman (output)
{
  "appName": {
    "message": "Meine Erweiterung",
    "description": "Name"
  },
  "welcomeMsg": {
    "message": "Hallo, $USER$!",
    "placeholders": {
      "user": {
        "content": "$1"
      }
    }
  }
}
52 locales

Cara ia berfungsi

Tiga langkah mudah untuk menyetempatkan browser extension anda. Terjemahan dijalankan selepas pembayaran—kami beraturkan tugasan dan menjana ZIP dalam beberapa minit.

01

Muat naik

Letakkan fail messages.json sumber anda. Kami menghurainya serta-merta dan mengesahkan format browser extension.

02

Pilih bahasa & lihat harga

Pilih daripada 52 bahasa. Lihat harga telus berdasarkan saiz fail anda sebelum anda membayar.

03

Muat turun ZIP

Bayar sekali melalui Stripe. Kami menjana semua fail _locales/{lang}/messages.json dan membungkusnya ke dalam ZIP.

Demo harga langsung

Anggaran harga telus

Lihat dengan tepat apa yang anda akan bayar sebelum memuat naik. Sebut harga akhir dikira selepas muat naik berdasarkan panjang rentetan dan bahasa yang dipilih.

1. Muat naik fail

Letakkan messages.json di sini

atau klik untuk semak imbas

WebExtension messages.json format. Max 500KB.

2. Pilih bahasa

|

3 daripada 55 bahasa dipilih

3. Anggaran anda

Bahasa dipilih3

Harga akhir dikira selepas muat naik fail di halaman daftar keluar

Bayaran sekali sahaja • Tiada langganan

Dibina untuk pembangun

Dibina khusus untuk format locale browser extension. Bukan alat terjemahan generik.

Serasi dengan format WebExtension

Dibina khusus untuk struktur messages.json browser extension dengan sokongan message, description, dan placeholders.

Perlindungan placeholder

Mengekalkan sintaks $PLACEHOLDER$ tepat seperti asal. Pembolehubah anda kekal utuh merentas semua bahasa.

Konteks penerangan

Kami membaca medan description anda dan menggunakannya sebagai petunjuk konteks untuk terjemahan AI yang lebih tepat.

Eksport ZIP sedia

Muat turun ZIP dengan struktur folder _locales/{lang}/messages.json yang betul. Letakkannya ke dalam sambungan anda.

Pemprosesan selari

Semua bahasa diterjemah serentak. Kebanyakan kerja siap dalam masa kurang daripada 5 minit.

Bayaran sekali sahaja

Tiada langganan, tiada yuran bulanan. Bayar sekali bagi setiap kerja, muat turun selamanya.

Cara i18n sambungan WebExtension berfungsi

Every major browser reads the same _locales/{locale}/messages.json structure. Chrome, Edge and Opera expose the chrome.i18n namespace; Firefox and Safari expose browser.i18n. The file format, the placeholder syntax and the default_locale requirement are identical across all of them, which is why a single translated folder ships everywhere.

Struktur folder _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 Runtime

chrome.i18n / browser.i18n

Contoh panggilan

getMessage("key")

Diperlukan dalam manifest

"default_locale"

In-extension strings come from _locales/. Store listing copy is managed separately in each store's own dashboard — translating one does not translate the other.

messages.json format explained →

What actually differs between browsers

The messages.json format is shared across every major browser. Only four things vary, and none of them require re-translating your strings.

Runtime namespace
Chrome, Edge, and Opera expose chrome.i18n. Firefox and Safari expose browser.i18n. The method names and arguments are otherwise the same.
Folder location
Most browsers read _locales/ from the extension root. Build frameworks move it: WXT emits public/_locales/, and Plasmo reads locales/ rather than _locales/.
Store listing text
In-extension strings come from _locales/. Store listing copy does not — Chrome Web Store, AMO, and App Store Connect each manage listing translations in their own dashboard.
Locale-code lists
Chromium browsers accept a fixed set of underscore-separated codes and silently ignore anything else. Check your codes before shipping rather than after.

One translated _locales/ folder covers Chrome, Firefox, Edge, Opera, and Safari. The porting work is in the build, never in the strings.

Mengapa tidak gunakan alat generik sahaja?

Alat terjemahan tujuan umum tidak memahami format browser extension.

LocalePack
Terjemahan manual
TMS generik
Masa persediaan2 minitBerjam-jam setiap bahasa30+ minit
Ketelusan kos
Keselamatan format WebExtension
Perlindungan placeholder
Kelajuan (52 bahasa)< 5 minMingguJam
Paling sesuai untukCross-browser extensionsProjek kecilAplikasi web perusahaan

Kisah Kejayaan

Projek sebenar yang menggunakan LocalePack untuk mencapai audiens global dalam sehingga 52 bahasa.

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.

Lihat semua kisah kejayaan

Dipercayai oleh pembangun sambungan

“Menjimatkan saya berjam-jam kerja yang membosankan. Muat naik messages.json saya, dapat semula terjemahan yang sempurna dalam format tepat yang saya perlukan.”

Sarah K.

Pembangun indie, sambungan AdBlock

“We ship the same _locales folder to Chrome, Firefox and Edge. One translation pass covers all three.”

Marcus T.

Penyelenggara sambungan

“Harga yang telus ialah faktor penentu. Saya tahu dengan tepat berapa yang perlu saya bayar sebelum memuat naik apa-apa.”

Dev J.

Penyumbang sumber terbuka

52

Lokal yang disokong

100%

Output selamat-placeholder

ZIP

Sedia untuk dihantar

Soalan lazim

Semua yang anda perlu tahu tentang LocalePack.

Related developer guides

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

messages.json format explained (with placeholders)

A complete reference for the WebExtension messages.json format: the message, description, and placeholders fields, $PLACEHOLDER$ syntax, $1 positional substitutions, and common mistakes.

WXT i18n: @wxt-dev/i18n and messages.json

How @wxt-dev/i18n compiles YAML, JSON, JSONC, JSON5 and TOML message files into standard _locales/{lang}/messages.json — setup, nested keys, plurals, substitutions, type safety, and how to translate a WXT project.

Plasmo i18n: the locales/ folder gotcha

Plasmo does not read _locales/ at the project root. The three paths it does accept, where default_locale actually lives, the alphabetical-default trap, and how to place a translated _locales ZIP correctly.

Adding i18n to a CRXJS extension

CRXJS ships no i18n helper and its docs have no i18n page. Here is the working pattern: put _locales under public/, declare default_locale in manifest.config.ts, and call chrome.i18n directly.

Browse all guides →

Bersedia untuk menghantar browser extension anda ke seluruh dunia?

Bayar sekali - Muat turun ZIP - Hantar ke seluruh dunia

Cuba LocalePack
LocalePack
PanduanPrivasiTermaSokongan

© 2025 LocalePack. Hak cipta terpelihara.

Projek ini diterjemahkan dengan LocalePack logoLocalePack