Why does my Shopify store say "Translation missing"?

Translation missing means your theme asked for a piece of text by key and no locale file in the theme holds an entry at that key, so Shopify prints the key path in place of the words. The text after the colon is the address it looked up, not an error code, and reading it tells you exactly which file to open.

There are two causes and they need different fixes, which is why the usual advice ("go and edit it in the admin") works for some people and does nothing at all for others. Either the key is missing from every locale file in the theme, which only a code edit can solve, or the key exists in the default language and is missing from a second language you added, which is a translation job rather than a code one. Everything below is about telling those two apart quickly.

What exactly does Shopify print for each locale mistake?

We tested this on a live Shopify store on 11 October 2026 rather than trusting older write ups, because two of the answers were not what this page used to say. We pushed a small unpublished theme with Shopify CLI 3.93.1, rendered each expression on the storefront, then deleted the theme. Every row below is the literal output:

Three things follow from that table. The missing message always starts with the locale code and is an ordinary string (45 characters long for en.cart.general.subtitle, which is why no filter treats it as empty). A wrong variable name is louder than a missing key, not quieter. And a group reference never says "translation" at all, so searching for that word will not find it.

What does "Translation missing: en.cart.general.title" actually mean?

Read it as an address. Shopify locale files are nested JSON, and the dots are the levels of nesting. A string like en.cart.general.title breaks into four parts:

The theme requested it with the t filter, which looks like {{ 'cart.general.title' | t }} in Liquid. Shopify resolves that against the locale file for the active language. If it finds nothing, it does not fail the page, throw an error, or leave a blank. It prints the key so a developer can see what broke, which is a sensible choice for a developer and a confusing one for a shopper looking at your cart.

Shopify separates these files by purpose, and the distinction matters when you go looking:

Shopify allows exactly one default file of each type, named with the *.default.json pattern, and the rest follow standard IETF language tags where the lowercase code is the language and an optional uppercase code is the region, so en-GB.json and fr-CA.json are both valid. If your missing key only appears inside the theme editor and never on the storefront, you are looking at the schema file, not the storefront one.

Which of the two causes do I have?

Open your Shopify admin, go to Online Store, click the menu beside the theme, and select Edit default theme content. Then use the Filter items search bar and paste in the last part of the key, for example title from cart.general.title.

That single check splits the two causes, because the language editor is built from the theme's own locale files. It can only show you rows that exist:

One more possibility worth ruling out before you edit anything: the wording might be coming from an app rather than the theme. Apps that inject storefront text through an app embed carry their own translations, and a missing string there is fixed in the app's settings, not in your locale file. If the key path starts with a group name you do not recognise and cannot find in locales/en.default.json, check which apps render on that page first.

How do I change the wording in the Shopify admin?

Shopify's own steps for the default language:

1. From your Shopify admin, go to Online Store.
2. Click the menu beside the theme that you want to edit.
3. Select Edit default theme content from the dropdown menu.
4. Click the tab or category that includes the text you want to change, or use the Filter items search bar to locate the phrase.
5. Edit the text.
6. Click Save.

Two things to know. First, this edits the theme you selected, so if you fix it and then switch themes or upload a fresh copy of the same theme, the edit does not travel with you. Second, it covers your default language only: Shopify's help centre says the theme content editor changes the wording "for your default language". For a second language (cause B), Shopify points you to the Translate & Adapt app, a CSV import, or a compatible translation app instead. We could not test what a second language shows for a missing key, because our test store publishes one language, so if you see the message only in one language, start with that language's file or the app rather than the English one.

How do I fix it in the theme code (cause A)?

Go to Online Store, Themes, Edit code, and open locales/en.default.json. Then add the key path exactly as the error prints it, minus the leading locale code. For a key printed as Translation missing: en.gift_cards.issued.title you need:

{
  "gift_cards": {
    "issued": {
      "title": "Gift card",
      "subtext": "Here's your gift card!"
    }
  }
}

Three rules that catch people out here:

• The nesting must match the dots. Do not write a flat entry named "gift_cards.issued.title" at the top level of the file. Shopify walks the structure, and in our 11 October test it refused to upload a locale file containing a dotted key at all, with the error Key 'flat.key' contains invalid characters.
• The file must stay valid JSON. A trailing comma after the last entry in a group breaks the whole file, and the symptom is that every key in the theme starts failing at once, not just the one you edited. If the page went from one missing string to dozens after your edit, that is what happened.
• Variables in the value use double braces. Shopify's t filter takes named parameters, so a value of "Use this code at checkout to redeem your {{ value }} gift card" pairs with a Liquid call of {{ 'gift_cards.issued.redeem' | t: value: gift_card.initial_value | money }}. Get the parameter name wrong and the whole string is replaced by an error that shoppers can read, for example I18n Error: Missing interpolation value "name" for "Hello {{ name }}". The fix is to make the name in the Liquid call match the name inside the braces exactly.

If the theme came from the Shopify Theme Store, note the edit somewhere, because a theme update replaces the file and takes your addition with it.

Why does my store show {"title"=>...} or [object Object] instead of a word?

Because the key you asked for exists, but it points at a group rather than at a piece of text. In a file where cart contains title, empty and item_count, a Liquid call of {{ 'cart' | t }} resolves to the whole group. On a real Shopify storefront, as our 11 October test showed, the group is printed as Ruby style text with => arrows, such as {"title"=>"Your cart"}, right where the word "Cart" belongs. A JavaScript preview tool rendering the same theme prints [object Object] instead, which is how we first met it, on 4 May 2026, in a generated header shown in our own preview.

The fix is always the same: use the full dotted path down to the text itself, so {{ 'cart.title' | t }} rather than {{ 'cart' | t }}. It is worth checking for deliberately, for two reasons. The word "translation" never appears, so searching for it will not help. And shopify theme check does not flag it: in our test it reported every missing key but said nothing about 'cart' or 'cart.general', because those keys do exist. Our locale base file currently has 6 top level groups and 10 group paths that hold other groups rather than text, so there are 10 keys in a theme of ours that would produce this if a section asked for them directly.

Will the default filter hide it?

No, and this is the most common wasted fix. Writing {{ 'cart.general.title' | t | default: 'Cart' }} looks like a safety net and does nothing, because default only substitutes when the value is empty, false or nil. "Translation missing: en.cart.general.title" is a perfectly good non empty string as far as Liquid is concerned, so it passes straight through the filter and onto the page. We confirmed it on a live store on 11 October 2026: the fallback text never appeared, and piping the same missing key into size returned 45, the length of the message.

If you want a label to show nothing on purpose, give the key an empty value ("") in the locale file. That renders as nothing, with no message, and keeps the key available for a translator later.

If you genuinely want a fallback rather than a fix, the honest version is to drop the filter and write the literal text, which is what we do for every section name and setting label in our own themes: 297 schema labels, all literal English, zero translation keys. That is a deliberate trade. It means those labels cannot be translated for a merchant working in another language, and in exchange the theme editor can never show a raw key where a setting name should be.

Does theme check catch this before it reaches a shopper?

Yes, and it is worth running before you upload anything, because this is one of the few Shopify faults that is completely invisible until a real page renders. Shopify's theme check ships four rules that cover locale files:

Three of the four are error level in Shopify's default configuration. TranslationKeyExists is cause A caught at build time, and ValidSchemaTranslations is the theme editor equivalent. MatchingTranslations is the one that finds cause B, because it compares your language files against each other and reports the entries one of them is missing. Run it with shopify theme check from the theme folder.

Here is what it reported on our 11 October test theme, which had several deliberate mistakes in its Liquid and a French file missing five entries. The messages are worth knowing word for word, because they are what you will paste into a search bar:

So a clean theme check run is necessary but not sufficient. The last two rows only show up when a real page renders.

What we found auditing our own themes

We build Shopify themes with AI, which means every | t call in a generated section is written by a model and every locale entry has to be generated alongside it. That is an obvious place for this bug to breed, so on 14 September 2026 we parsed it rather than assuming.

Across 33 generated themes in our build archive we scanned 1,218 Liquid files containing 1,254 calls to the t filter. Unresolvable keys: zero. Keys pointing at a group instead of a string: zero. Our hand written boilerplate on its own accounts for 51 Liquid files, 57 t calls and 25 distinct keys against a locale base of 36 entries, and all 25 resolve.

That is the current state and not the historical one. On 2 July 2026 the gift card page of every theme we shipped rendered "Translation missing" five times over, because gift_card.liquid called gift_cards.issued.title, .subtext, .redeem, .expires_on and .shop_link, and the locale base file had no gift_cards group at all. Five keys, one page, and nobody had seen it because the gift card page only renders when a gift card is actually issued. The fix was adding the five entries. The reason it does not recur is that the generation prompt now carries a rule that every {{ 'foo.bar' | t }} call must have a matching key path in the theme's locale data, with an explicit instruction to use a literal string instead when in doubt.

The broader lesson holds for hand built themes too. This bug survives every check that does not actually render the page, which is why it tends to be found by a customer rather than by you.

The short version

1. Read the key. The text after the colon is the address the theme looked up.
2. Search for its last segment in Edit default theme content.
3. A row exists means a language gap. Fill it in for that language in Translate & Adapt or that language's file.
4. No row exists means the key was never defined. Add it to locales/en.default.json, nested to match the dots, never as one dotted key.
5. If it prints {"title"=>...} (or [object Object] in a preview tool), your key stops one level short of the text. Add the final segment.
6. If it prints I18n Error: Missing interpolation value, the variable name in the Liquid call does not match the one in braces.
7. The default filter will not rescue it. The missing message is a non empty string.
8. Run shopify theme check before uploading. TranslationKeyExists is an error level rule and catches missing keys in seconds, but not group references or wrong variable names.

This sits in the same family as the other Shopify faults that produce no error message anywhere: a section that never appears in the Add section list, which is a missing presets array, and an empty Apps tab in the block picker, which is a missing @app declaration. If a locale edit stops the theme uploading altogether, the cause is usually a JSON or schema error in the ZIP rather than the translation itself. Every theme in our free theme gallery ships a complete locale file, and each one has a live preview you can open before installing anything.