Localize Product Images Outside Shopify Markets’ Translation Workflow

01

1. Identify the gap accurately: product media is different from theme imagery

Do not assume that every storefront image must be managed outside Shopify’s localization tools. The limitation is narrower: native product-gallery images are not translated through Translate & Adapt, while images and videos selected through the theme editor can be replaced for different languages.

Start the workflow by recording where each asset is rendered. A homepage banner, image-with-text section, promotional block, or other theme-editor image can follow Shopify’s native localization route. A product photo, benefit panel, sizing chart, or instruction graphic uploaded into the product’s media gallery requires another implementation.

This distinction prevents unnecessary duplication. If a copy-heavy graphic does not need to sit inside the native gallery, moving it into a product-page theme section may make localization easier. Shared product photography can remain in the gallery while market-sensitive benefits, measurements, comparison tables, and instructions sit in localized blocks below or around it.

Shopify also supports market-specific theme customizations, including changes to section content and settings. Shopify currently documents market-specific online-store customization as an Advanced-plan-or-higher feature and notes that compatibility can depend on the theme and apps involved. Confirm the store’s plan and implementation before making that route part of the production brief.

02

2. Build a market-by-market image-copy matrix

Create one row for every image containing visible language or information that could change by market. The matrix is the operational source of truth connecting the creative file to its intended storefront context.

At minimum, record the product, SKU or handle, source asset, gallery position, embedded copy, copy category, default market, target market, target language, required action, legal-review status, output specification, implementation route, owner, status, approved export, and QA evidence.

Classify the required action as retain, translate, rewrite, remove, or redesign. “Translate” is not always sufficient: a claim may require different substantiation, a measurement may need conversion, a promotion may not exist in the destination market, or the photographed packaging may differ from what customers receive.

Use a durable asset ID rather than relying on names such as “French image final.” For example: PRODUCT-SKU__GALLERY-03__MARKET-CA__LANG-FR-CA__V04. The same ID should appear in the brief, editable source, copy approval, export filename, Shopify assignment record, and QA screenshot. This makes it possible to determine which storefront version came from which approved source.

The matrix should also distinguish market from language. French for Canada might not use the same approved wording, packaging, measurements, or legal language as French for France. A language-only filename can therefore hide a meaningful market difference.

1. List every product and gallery position containing embedded copy or regional information.
2. Record the current approved source file and exact visible text.
3. Add a row for each required market-language combination.
4. Assign a localization action, owner, implementation route, and review requirements.
5. Attach the approved export and storefront QA evidence before changing the row to live.

03

3. Decide which images actually require localization

Localize only when the image’s meaning, accuracy, or suitability changes by market. Keeping language out of imagery where possible reduces recurring production work.

A single global asset is usually appropriate when it contains no embedded language, the packaging and included products are consistent, and all visible measurements, marks, and claims are valid in every destination where it will appear. Lifestyle photography and straightforward product angles often fit this category.

Create a replacement when an image includes benefits, instructions, ingredients, warnings, certifications, promotional copy, local delivery language, pricing, market-specific packaging, measurement units, or claims that are not universally approved. Regional holidays, seasons, accessories, and bundle configurations can also make an otherwise reusable image inaccurate.

Where the design permits, move frequently changing text into accessible HTML rather than baking it into the image. Storefront text is easier to translate, revise, and display responsively. This will not eliminate the need for localized imagery—packaging photos, diagrams, and designed comparison panels may still require it—but it reduces the number of files that must be regenerated for every copy change.

04

4. Brief replacements from the approved source—not from the last localization

Every market variant should descend from the same controlled master. Repeatedly editing the most recent flattened export introduces copy errors, compression, and visual drift.

The brief should identify locked elements such as product angle, crop, lighting, background, logo treatment, shadows, and composition. It should separately identify editable zones for headlines, support copy, labels, units, warnings, and footnotes.

Supply approved source and target copy rather than asking a designer to infer or machine-translate the text. Include market restrictions, approved claims, required marks, packaging references, and the people responsible for brand, localization, market, and legal review. Plan for text expansion, line-break changes, and right-to-left layouts where relevant.

Preserve the layered master, approved copy record, and exported storefront asset as separate files tied to the same asset ID. Shopify’s Files area is intended for files used on the public storefront, so confidential working files, internal approvals, and editable masters should remain in the brand’s controlled asset repository.

The production brief should also define dimensions, aspect ratio, format, compression expectations, mobile safe areas, and whether the localized version must preserve the source crop exactly. If longer copy would make the design unreadable, the approved action should be a redesign rather than forced text fitting.

1. Lock the source version before localization begins.
2. Provide approved market copy and identify all editable copy zones.
3. Document packaging, claim, unit, and regulatory differences.
4. Specify export requirements and mobile readability constraints.
5. Route the output through required brand, market, localization, and legal reviews.

05

5. Choose the appropriate Shopify routing method

There is no single native product-gallery localization switch. Choose the lowest-complexity implementation that produces the required customer experience and can be maintained when the source changes.

Route A is to keep global product photography in the native gallery and move copy-heavy graphics into localized product-page sections or blocks. This works well for benefit panels, instructions, sizing graphics, comparisons, and promotional modules. Shopify’s market overrides can change section settings such as images while unaffected settings continue to inherit the default. Once a setting is overridden, however, the team must understand whether later default changes will still flow through or whether the override must be updated or reset.

Route B is to store approved files in product metafields and use theme logic to select the correct file for the active country, language, or market. Shopify supports file-reference metafields and exposes localization context in Liquid. A compatible theme may connect a metafield through a dynamic source; a specialized gallery or fallback rule may require development. Define what happens when a local asset is missing: showing an approved default is usually safer than producing an empty position or broken layout.

Route C is to create separate market-specific products when packaging, gallery content, merchandising, URLs, claims, bundles, or configurations are materially different. Shopify catalogs can control which products are available in a market. This route gives each product an independent gallery but adds operational overhead around duplicate records, inventory setup, search visibility, maintenance, and URL governance.

Do not select a route based only on the first launch. Consider how frequently the source creative changes, how many markets are planned, who can maintain theme logic, and whether the same localization rules apply consistently across the catalog.

06

6. Upload, assign, and document the approved asset

Treat upload and assignment as controlled deployment steps. An approved export is not useful if it is attached to the wrong product, market, block, metafield, or gallery position.

Before upload, compare the filename and version with the matrix. Check that obsolete prices, dates, delivery promises, and promotional language have been removed. Confirm that the photographed packaging, included accessories, measurements, and product configuration match what customers in the target market receive.

After assignment, record the Shopify location in the matrix: product media position, theme section, block, metafield, or market-specific product. If a developer implemented selection logic, record the expected default and missing-file behavior as well.

Do not store layered masters or confidential internal review material in Shopify merely for convenience. Keep the working source in the controlled creative repository and place only the approved public-facing export in the storefront system.

07

7. Localize and verify alt text separately

Replacing visible text in an image does not automatically provide an appropriate accessible description. Alt text needs its own localization and review.

Write alt text to describe the image and the information it communicates, not its internal asset ID or filename. Shopify recommends concise, descriptive alt text and identifies it as important for customers using assistive technology.

For developer- or app-led workflows, Shopify’s developer changelog states that image alt text became available as a translatable resource in Admin API version 2025-10. That capability does not make the product image itself translatable through Translate & Adapt; it only provides a technical route for translating the image’s text alternative.

Add an alt-text field to the matrix, including its language, approval state, and verification result. If the same visual is reused but its meaningful embedded copy changes, review whether the alternative text should change too.

08

8. Run QA in the final market and language context

Approve the rendered storefront, not merely the exported file. Localization can fail through incorrect assignment, inheritance, gallery ordering, variant behavior, or fallback logic even when the image itself is correct.

Shopify’s theme preview can show selected country and language contexts. Use previews and customer-facing selectors to inspect each required market-language combination. Shopify also provides market-context controls for reviewing product availability and pricing, but imagery still needs visual storefront inspection.

Check the product and URL, hero image, gallery order, thumbnails, mobile and desktop crops, zoom behavior, variant-image behavior, localized alt text, packaging, measurements, claims, availability, pricing context, and selector behavior. Look specifically for a default-language image appearing halfway through an otherwise localized gallery.

Test intentional fallback cases. If no localized asset exists, confirm that the approved global image appears rather than an outdated translation, broken image, empty slot, or layout shift. Capture screenshots or preview evidence and attach them to the matrix.

A practical completion rule is that a row cannot become “live” until creative approval, Shopify assignment, and storefront verification are all complete. This separates production completion from deployment completion.

1. Open the intended country and language context.
2. Confirm the correct product, URL, availability, and surrounding localized content.
3. Inspect every gallery position and localized content block on desktop and mobile.
4. Test variants, zoom, thumbnails, selectors, and missing-localization fallbacks.
5. Capture QA evidence and record the deployed asset version.

09

9. Treat source updates as localization change requests

When a default product image changes, identify all localized derivatives before publishing. Otherwise, markets can silently drift onto outdated packaging, claims, layouts, or product details.

Use a change sequence such as: source updated; affected assets and markets identified; localized copy reconfirmed; replacement files produced; approvals completed; files assigned; storefront QA completed; previous versions archived.

Theme inheritance requires particular attention. A default setting might flow into a market automatically, while an existing override may continue displaying its previous value. Record whether each localized placement inherits the default or is independently overridden.

Do not overwrite the previous source without retaining its version relationship. Historical traceability helps the team understand which markets were updated, which intentionally retained an older treatment, and which require follow-up.

10

10. Use ATIYO for creative context, not Shopify configuration

ATIYO can organize the roadmap, localization briefs, brand context, source assets, market variants, iterations, and reusable learnings behind this workflow. Shopify should remain the source of truth for product records, market availability, prices, theme configuration, and deployed storefront files.

A practical ATIYO setup would connect the master creative direction to separate market briefs and iterations while keeping naming conventions, copy decisions, and review context reusable. This reduces reliance on scattered messages and ambiguous filenames without pretending that ATIYO controls Shopify Markets.

ATIYO does not connect to ad accounts, buy media, calculate ROAS, or automatically know performance. Media performance remains in the ad platform, and ATIYO preserves creative context and learnings when a user records them. It also does not replace storefront QA or confirm which asset Shopify is currently rendering.

If you need a shared operating system for these briefs, assets, iterations, and learnings, start ATIYO’s card-confirmed seven-day trial; billing begins afterward on the selected plan.