Why does my product-image text stay English after I switch the store language?

Separate pixels from translatable fields

Inspect the product page and identify whether the English words are normal page text, an image caption or letters baked into an image file. Only the first two can change as ordinary text fields. An embedded feature diagram needs a different picture or an editable text layer rendered outside the picture.

A public Shopify user question asks how one or two text-heavy product images can switch between English and Polish. Its proposed solutions are questions, not verified requirements. Shopify’s Translate & Adapt documentation describes content localization, but do not infer that every product-media slot is automatically localizable. Confirm support on the exact resource and theme you use.

Shopify’s current Translate & Adapt limitations explicitly list product images as unsupported. Its separate manual file-localization instructions describe selecting a theme image/video and choosing Localize, then assigning a previously uploaded alternative file. That is a supported-resource workflow; it is not a promise that a product’s native gallery slot can be translated directly.

Identify the slot before implementation: normal translatable text, a supported theme file setting, or product-gallery media. For an unsupported gallery image, ask the owner to establish an actually supported theme/data mapping, or move the explanatory words into translatable page text around an accurate text-free image. Do not treat a forum app suggestion as an installed or verified integration. A prepared Polish file does not by itself make the page select it.

The public English/Polish image question documents one real request, not demand frequency or a current app compatibility test. Keep physical packaging lettering separate from the translated annotation, and use creative copy-language settings only for their actual creative task.

Define an asset-selection matrix

Use the localized image and variant review CSV as a manual record. Its sample row is fictional. Replace it with your own authorized evidence; the worksheet does not connect to or change any external account.

Choose a maintainable implementation

Consider moving short feature labels into accessible page text around a text-free image when the design permits. If separate images are necessary, use the actual supported localization mechanism and document its owner. Do not create a second store simply because one image failed to switch; compare that operational cost with a supported theme solution first.

Generate or edit each candidate using the same product evidence. Localize marketing annotations, not the physical product into a different SKU. CartVisual does not install a Shopify app or change your theme’s selection logic.

Test combined changes

Switch language, market and variant in the combinations customers actually use. Inspect both the picture and normal page text. A Polish diagram of the wrong bottle size is still a failure. Record the file URL, visible words, variant and fallback behavior. Keep an approved default for unsupported contexts and ensure that fallback does not communicate a contradictory claim.