Translate your website, without wrecking your setup
JSON for React, Next.js, Vue and Angular, XLIFF for exported website text, and Markdown for content. Recognised placeholders and file structure are checked; numbers and dates follow fixed regional rules.
Language rules and file formats
Regional number formats. Preserved placeholders.
Translate text for the language and region you need. Recognised numbers and dates follow fixed rules; technical placeholders are protected and checked.
Explore format examples
| Value | de-DE | en-US |
|---|---|---|
| Number | 1.234.567,89 | 1,234,567.89 |
| Date | 13.09.2026 | 9/13/2026 |
| Time | 17:30 | 5:30 PM |
| Percent | 12,5 % | 12.5% |
| EUR amount | 1.234,56 € | €1,234.56 |
Your variables stay usable
Recognised placeholders retain their names and types. For ICU messages, branch text is translated and the technical structure is checked.
{name} · {{count}} · %1$s · {price, number}
Check and retry what needs fixing
Missing or technically invalid translations are retried selectively. If errors remain, the file is not released as a finished translation. Budgets and retry counts are limited.
The rule data covers 1,082 language, script and region variants. This is not a claim of linguistically reviewed translation quality for that many languages.
View all rules, supported content and limitsWhat it works with
All common web frameworks, i18n libraries — and WordPress
React
react-intl, react-i18next
Next.js
next-intl, next-i18next
Vue
vue-i18n
Angular
@ngx-translate
Svelte
svelte-i18n
WordPress
WPML, Polylang (XLIFF)
JSON i18n Workflow
Easy integration into your development process
Before (en.json)
{
"greeting": "Hello, {name}!",
"welcome": "Welcome to our app"
}After (de.json)
{
"greeting": "Hallo, {name}!",
"welcome": "Willkommen in unserer App"
}Why us instead of ChatGPT?
The differences at a glance
| Feature | shipglobal | ChatGPT / DIY | Agency |
|---|---|---|---|
Translation Memory Translate once; updates are free | Tokens only the first time | New every time | New every time |
Large files No size limit | Unlimited | Token limit | No limit |
Placeholder protection {name}, %@, {{count}} remain intact | Automatic | Error-prone | Manual |
Original format JSON, XML, and .strings are preserved | Automatic | Copy-paste required | Depends on provider |
64 languages Translate all at once | Simultaneously | Individually | Expensive |
Consistency Same terms = same translation | Reuse matching translations | Inconsistent | Varies |
Price Cost per translation | $€19 per seat per month, incl. VAT | $$Time + API | $$$10-50x more expensive |
SEO-optimized translation
Better rankings in international markets
hreflang Tags
Automatic language detection for Google
Local keywords
Translations align with local search behavior
Meta Tags
Title & Description for each language
Frequently Asked Questions
- Which JSON structures are supported?
- JSON string values in flat and nested objects and arrays. Keys and non-text values are preserved. Recognised placeholders and ICU structures are checked. Special catalogue schemas require a dedicated adapter.
- Does it work with next-intl?
- Supported JSON and ICU messages can be used with libraries such as next-intl, react-intl and vue-i18n. Check custom template syntax and your application build separately.
- How does it help with SEO?
- Multilingual websites rank better for local queries. With hreflang tags, Google understands the language versions.
- Are plurals translated correctly?
- ICU arguments and branch structures are checked while the text is translated. This does not automatically adapt every framework plural file: missing Android plural categories, for example, are not added.
- Does this work with WordPress?
- Yes, through the XLIFF export of your multilingual plugin. You export the pages and posts you want translated, upload the file, pick your languages and import it back. No code, no translation script in the frontend.
- Do I need WPML, or is a free plugin enough?
- You need a plugin that can export XLIFF: WPML ships it in Translation Management, Polylang from the Pro version on. Without such a plugin WordPress does not manage a second language at all — and then the file we work on does not exist.