Stuck on something?

Import the file you already have rather than retyping it. Import & Export reads the same ten formats it writes — JSON, PO, iOS .strings and .xcstrings, Android XML, XLIFF 1.2, Flutter .arb, Java .properties, CSV and YAML. An import fills in what is missing and leaves existing translations alone unless you tick "Overwrite existing translations", so running the same file twice is safe.

One set of translation keys — usually one app, site or service. It can target as many languages as you like on any plan. Keys, languages and translations are never counted against you; only projects, members and screenshots are.

"All platforms" is the default and the fallback for everything. Setting a value for Web, iOS, Android or Dashboard overrides it on that platform and nowhere else. It is for the case where a phone needs shorter wording than a desktop — not for keeping separate copies of the same string.

Upload the screen on the project’s Screenshots tab and link it to the keys visible on it. The key then carries the screen it lives on, which is the difference between translating a word and translating a button.

Give it a minute, then check spam and any quarantine your company runs — Microsoft 365 tenants tend to file a first-time sender there rather than block it outright. Every sign-in email carries a six-digit code as well as a link, so if your filter rewrites or strips links you can type the code on the sign-in screen instead. Both are good for ten minutes.

Yes, within its ten minutes, and deliberately so. Corporate mail scanners follow links before you ever see them, and a strictly single-use link would already be spent by the time it reached you.

Use one of the ten single-use recovery codes you were given when you turned two-factor on — each signs you in once, and you can then re-enrol from Edit profile. If the recovery codes are gone too, email us from the address on the account and we will work out how to establish that it is you.

Set one under Edit profile in the avatar menu. It does not replace the emailed link — both keep working. If two-factor is on, every way in asks for it: password, link and typed code alike.

An admin has set the workspace policy to "required". You keep reading and exporting everything in the meantime; enrol under Edit profile and editing comes straight back. The gentler setting, "encouraged", asks but blocks nothing.

Developer access, in the avatar menu at the top right. A key starts with lz_ and works for the REST API and the MCP server alike.

Then it is gone, and so is our copy: a key is stored only as a SHA-256 hash, so we cannot show it to you again either. Revoke it and create another — it takes seconds and costs nothing.

Not for an MCP client that can sign in for itself. Point it at the server URL with no Authorization header: it registers itself, sends you to a consent screen in your browser, and you choose read-only or read and edit for that connection. Keys are still the better fit for CI, where there is no browser to consent in.

The project’s History tab records every change with its previous value and the user behind it. A call over MCP or the REST API is attributed to the person whose key or consent it ran under, exactly like a dashboard edit — so you can see what the value was before and put it back.

Import & Export inside a project, or export_translations over MCP. Pick a format and one language, or ask for all of them and get a zip. iOS .xcstrings is the exception: a single catalog always carries every language, so it ignores the language you picked.

Yes. Export works on Free, after a trial ends, after a subscription is cancelled, and while a workspace is over its limits. Your strings are never held hostage.

By default an import only fills in what is missing and leaves existing translations as they are — tick "Overwrite existing translations" if you mean to replace them. Over MCP, import_translations takes dry_run, so you can see exactly what a file would do before it does it.

Workspace roles — owner, admin, developer, translator — govern the workspace itself: billing, members, creating projects. Project roles — admin, editor, viewer — govern one project. Being in a workspace does not grant access to every project in it, and administering a project grants no authority over the workspace.

Same places as a sign-in email: spam first, then your company’s quarantine. You can see and cancel live invitations under Workspace & team and send a fresh one. Worth knowing: a pending invitation holds a member seat until it expires, so on Free three unanswered invites fill the workspace.

Yes, from the project’s Settings — but it takes admin authority over the workspace the project is leaving, not just over the project. That is deliberate: otherwise a contractor with project admin could walk off with it.

The workspace moves to Free. Nothing is deleted and nothing is locked — you keep full read and export access. If you are over the Free limits, editing pauses until you upgrade or remove what is over.

Free: one project, three members, 100 screenshots. Pro: five projects, unlimited members, 1,000 screenshots. Neither caps keys, languages or translations, and neither charges per user.

Editing pauses. Reading, exporting and deleting all keep working, so you can always get your data out or shrink back under the limit. Screenshots behave differently on purpose: passing that one blocks new uploads but never freezes the workspace.

Workspace & team, then Plan & billing. Cancelling keeps Pro until the end of the period you have already paid for, then moves the workspace to Free.

Email us with the workspace name and what the invoice needs to say — a VAT number, a company name, a different billing address. Payments run through Stripe, so card details never reach us and are not something we can read back to you.

Edit profile, then Delete account at the bottom of the dialog. It is confirmed by email, so a stray click cannot do it.

Yes — Edit profile has a switch per kind: product updates, digests, mentions and marketing. Sign-in and password emails are not on that list, because turning off the email that lets you in would lock you out.

Email us with enough detail to reproduce it. We would rather hear about it from you than not hear about it, and the Security page says plainly what is in place and what is not yet.