In short. Select a store language in the PrestaShop product editor, enter the translated product name, Summary, Description and image captions, then save the product.
Definition: PrestaShop product translation uses the product editor's language selector to edit content for a chosen store language. The translated product name, Summary and Description are entered in the fields for that language and saved with the product.
As of 17 October 2026, the workflow below follows PrestaShop's version 8 product management documentation. A separate guide covers the newer product editor introduced in version 8.1.
Key facts
- PrestaShop's Managing Products guide says the language selector loads the content available in the selected language and allows switching languages before saving.
- The Translations documentation provides an “Add or update a language” button for adding a store language.
- The new product page guide distinguishes “Save” from “Save and publish” in the newer editor's footer.
Where are the translated fields edited?
The new product page guide gives this catalog menu path:
Catalog > Products
For an existing product, translation takes place in its product editor. PrestaShop's Managing Products documentation places the language selector next to the product type selector. Selecting a language updates the editor with the content available in that language. The editor initially displays the store's default language.
The documented procedure is to select the target language, enter the translated content, and repeat for the store's other supported languages. Switching languages is possible without saving between each switch. A product name in at least the default language is required before the product can be saved.
Which product text needs translation?
The Managing Products guide places Summary and Description in the Basic settings tab. Summary holds the short description; Description holds the full text displayed directly on the product page. Both fields belong in the translation review alongside the product name.
Summary has a default limit of 400 characters. Exceeding it produces a red warning below the field. The “Max size of product summary” option on the Products preferences page changes this limit, so a translation's length needs checking against the store's setting.
The same guide also calls for translating image captions. It describes the caption as the image's alternative text, the text represented by its HTML alt attribute. A product translation review therefore includes captions as well as the main description fields.
How are translations saved and checked?
In the Managing Products guide, Save records product changes and keeps the editor on its current tab. Preview opens the storefront product page, including for a disabled product. These controls support checking the saved text and its presentation on the product page.
The version 8.1 editor guide documents different footer wording: Save applies when creating a product or when it is offline; Save and publish saves the product and publishes it on the store. The button label matters when preparing translated content for an unpublished product.
Related terms
- How do I edit a PrestaShop product's search metadata?
- Should translated pages have separate URLs?
- HTML lang attribute
FAQ
How do I add a missing language?
In International > Translations, select the language and click “Add or update a language,” as described in the Translations guide. Then return to the product editor to enter the product's translated content.
Must I save before changing the editor's language?
You can switch languages without saving between them, according to Managing Products. Save the product after completing the edits.
Where do I translate theme labels?
Select “Theme translations” on International > Translations. The Translations guide identifies this category as the strings customers see while browsing the store.
Sources
- PrestaShop Project, "Managing Products", undated
- PrestaShop Project, "New product page (PrestaShop 8.1)", undated
- PrestaShop Project, "Translations", undated
Check how a page reads to answer engines. Open the GEO score analyzer