One language file in. 64 languages out.

Placeholders, plurals and structure come back untouched. On the next release you only pay for the strings that changed: the engine sees the difference before any model is asked.

  • 64 languages
  • €19 per month, incl. VAT
  • €10 per million tokens
  • Bring your own model key
  • iOS · Android · React · Vue · WordPress
  • .json · .strings · .xml · .xliff · .xcstrings · .md

The account is free.

Creating it costs nothing. You start the subscription afterwards, in your account: €19 per month, cancellable monthly.

Create account

No allowance, nothing expires, cancel at the end of the period.

€19 per month incl. VAT, cancellable monthly.

The proof sheet

You pay tokens only for what is new.

Every string gets a mark: + new, = in memory, ~ source changed. Only + and ~ go to the model and cost tokens. The = never costs anything, not even on the tenth release.

First upload
0,98 €
Everything is new
Next release
0,01 €
15 of 3,627 strings
de.json3.627 Keys · 172.402 Zeichen
wiederverwendet:settings.titleEinstellungen13
wiederverwendet:common.cancelAbbrechen9
geändert:paywall.headlineJetzt freischalten18
neu:onboarding.step3Fast geschafft14
wiederverwendet:errors.networkKeine Verbindung16
+
neu12
=
wiederverwendet3.612
~
geändert3
Example: a real de.json

What survives

Translation is the easy part. Not breaking your file is the hard part.

Placeholders stay placeholders

%@, %lld, {name}, {{count}} come back exactly as they went in. A translated placeholder is a crash.

Plurals stay plurals

ICU plural forms and .xcstrings variations survive the round trip. Polish has four plural forms; we keep all four.

Your file comes back as your file

Nesting, key order, comments. Your string catalog keeps every language it already had — we add, we do not overwrite.

Nothing goes missing

Every key you upload is in the file you download. If one is missing, the download stops instead of shipping you an incomplete file.

Reach

You maintain one file. Not sixty-four.

Your string catalog goes to every store you ship to: iOS, Android, web. Same keys, same structure, same placeholders — in all 64 languages.

Languages
64
Files you maintain
1

How it runs

Three steps, no setup.

File in, file out. No project to set up, no plugin to install, no integration to build — WordPress included.

  1. 01

    Upload

    Your string file, as it is. No project setup, no config.

  2. 02

    Review

    The plan shows every string and its mark before a model runs. You pay for measured tokens — nothing with your own key.

  3. 03

    Ship

    Download the same file, now in every language you picked.

What you buy

You buy the engine. You pick the model.

Anyone can call a model. The work sits before and after it: the comparison against the memory, the format work, the placeholder and plural validation, writing everything back intact. That is what the base fee pays for. The model is your choice.

Our access

No contract with a provider needed on your side. The text passes through our request to the model and is not stored on the way. You are billed for what was measured.

€10 per million tokens

Your own key

The request goes straight from your machine to the provider. We never see it and charge nothing for it.

no token cost with us

Your own model

Running a model inside your own network? The engine talks to it. Your text then goes to no provider, and certainly not to us — all that comes from us is the answer to whether the licence is valid.

no translation data reaches us

The same engine all three ways, the same formats, the same 64 languages. The only difference is who provides the model. The app reaches our servers exactly once: at startup, for the licence check. Nothing else travels over that wire.

No lock-in

Nothing keeps you here.

The things others would hold you with are on your machine. That is not a stance, it is a design decision — four of them are here, each one checkable on its own.

Your text stays where it is
With your own key or your own model your source text never reaches our servers — only the licence check arrives there, and it knows your key, not your file. If it runs through our access, the text passes through the request and is not stored.
The translation memory lives with you
In your project folder, next to the files it describes — not in our database. It is the reason your second run costs almost nothing, and it is yours. Whoever leaves takes it along, because it was never anywhere else.
There is no export
Standard formats in and out: .xcstrings, .strings, .stringsdict, strings.xml, JSON, XLIFF, Markdown/MDX. No proprietary format, no database you would have to extract anything from.
Cancel at the end of the period
No annual contract, no quota that expires, no minimum. Whoever stops, stops — and pays for what was used until then, not for what was once estimated.

Is this a fit?

Is ShipGlobal for you?

Three questions. One of them can come out as No — we do a lot, but not everything, and saying so up front is cheaper for both of us.

Question 1 of 3

What are you translating?

Price

€19 per month, per seat. Incl. VAT.

The €19 pays for the engine. Through our key, €10 per million tokens comes on top, incl. VAT; with your own key, nothing. Whatever is already in your memory never costs a thing.

See the numbers

Create an account. Upload a file. See the number.

€19 per month incl. VAT, cancel monthly. No quota to expire — and with your own model key you pay no usage at all.

Create account