Magento product image alt text
A review workflow for Magento 2 product image alt text
Editing one product image in Commerce is straightforward. Open the product, expand Images and Videos, select the image, and enter a short description in the Alt Text field. The work gets slow when a catalog has several views for every product.
I separate writing from publishing. AltCaption handles the draft and review queue without Commerce credentials. Commerce stays in charge of the final store value.
This is a preparation workflow for a merchandiser, catalog manager, or developer who already controls the Commerce store. It keeps the review work recoverable while leaving catalog permissions and publishing decisions in the existing admin or deployment process.
Quick answer
Adobe Commerce and Magento Open Source let you edit alt text in each product image's detail view. For a larger catalog, I prepare and review the drafts in AltCaption first, keep the work in a local manifest, then copy only approved text into Commerce.
Start with the images that need work
Collect the public URLs for the product images you want to review. Start with a limited set of important products or one category instead of sending the whole catalog through a new process at once.
Keep the SKU, product name, store view, and image role beside each URL in your source sheet. AltCaption uses the image URL for generation. Those catalog fields remain your reference when you copy an approved description back into Commerce.
AltCaption needs an HTTP or HTTPS image URL it can fetch. Do not paste Commerce admin credentials, session URLs, or private media links into the queue. If the catalog images are not public, keep the review inside an approved internal process instead of opening access just for generation.
Decide what each gallery image contributes before generating text. The base image may need the product name and main visible attributes. A detail view should identify the material, fastening, label, or feature it shows. A size chart or comparison graphic may need its important information in nearby page text instead of a long alt attribute.
Adobe assigns product images roles such as Base, Small, Thumbnail, and Swatch. One uploaded image can have more than one role, so keep the role in your source sheet for review; do not paste role names into every description unless the role changes what a customer needs to know.
- Keep each gallery view as a separate row.
- Record the SKU and store view outside the generated alt text.
- Prioritize blank, repeated, or generic descriptions.
- Leave decorative images out of the writing queue.
Use the local review workspace
Paste the image URLs into the AltCaption bulk Review workspace. Occurrence rows stay separate when the same URL appears more than once, which is useful when an image needs different review notes or page context.
Generate only the selected rows. Edit the drafts, mark their status, filter the queue, and remove rows that do not need text. The workspace resumes from local browser storage, and the versioned Alt text manifest JSON gives you a file you can save and import later.
I use statuses to keep generation and approval separate. A generated draft is not ready just because it exists. I check it against the product record and image role, edit it, then mark the row approved only when the wording can be copied into Commerce.
The manifest keeps the occurrence rows, statuses, edits, and review metadata on the device. There is no account sync or shared review queue. Export the JSON when you need a recovery copy, then import that file into the Review workspace on the browser where you will continue.
- Use context hints as review notes, not as instructions sent to the image model.
- Check product names, colors, materials, angles, and visible text.
- Give different gallery images descriptions that identify the useful view or detail.
- Export the manifest before switching browsers or handing the approved rows to another process.
Write the approved text back in Commerce
Adobe's current catalog guide puts the Alt Text field in the product image detail view. Open Catalog, edit the product, expand Images and Videos, select the image, enter the approved description, and save the product.
Store views need an extra check. Adobe Commerce and Magento Open Source can inherit the default image alt text or keep a store-view-specific value. Confirm the Store View selector before replacing a translation or an intentional local description.
Review the default scope before translating a batch. A useful source sheet has one row for the default description and separate rows only where a store view needs different wording. That makes inherited values visible and avoids copying the same English draft over localized text.
Work through a small product set first. Copy the approved text, save the product, and reload the storefront product page. Inspect the rendered image element and confirm that its alt attribute contains the expected text for the selected store view.
If the admin value and storefront value differ, stop the batch and trace the theme or storefront rendering path. Fixing the saved catalog field is only useful when the customer-facing page renders it on the intended image.
- Use the product image detail view for the final value.
- Check whether Use Default Value is enabled for the selected store view.
- Save a small batch before continuing with the catalog.
- Inspect the storefront image element and confirm the approved alt text is rendered.
Where this workflow stops
AltCaption does not connect to Adobe Commerce or Magento Open Source, write through the API, install an extension, or update the catalog. The manifest is a local review artifact that Commerce cannot import.
For a catalog that needs automatic writes, use a reviewed API script or a Commerce extension with the permissions and rollback path your team accepts. The local workflow is useful when you want to check the descriptions before granting another system catalog access.
Adobe's product image import guide covers associating image files with products through image columns in a CSV. I do not treat that image-upload procedure as proof of a supported bulk alt-text update. Use the admin for the documented manual path, or verify a separate update method against the Commerce version and permissions you run.
Examples
- Main image: "Aster white mesh running shoe with blue sole, three-quarter front view"
- Gallery detail: "Close-up of the blue rubber sole and white mesh upper"
- Packaging view: "Aster running shoes beside a white box with the size label visible"
- Decorative texture used behind product copy: alt=""
Common questions
Where do I add product image alt text in Magento 2?
In Adobe Commerce or Magento Open Source Admin, open the product, expand Images and Videos, select an image, and enter the description in the Alt Text field.
Does AltCaption update Magento products?
No. AltCaption drafts and stores the review work locally. Copy approved text into Commerce through the admin or an update process you control.
Should every product gallery image use the product name?
Use the product name when it helps identify the item, then describe the view or visible detail that makes that image different. Do not repeat one generic description across the whole gallery.
How should I handle multiple store views?
Check the active Store View and the Use Default Value setting in the image detail view. Keep a store-specific description when the language or catalog context changes.
Which Magento products should I review first?
Start with a small category, a high-value product set, or products whose gallery images have blank or repeated descriptions. Finish the generation, approval, Commerce update, and storefront check for that set before expanding the queue.
Related guides
Sources
Prepare the Magento image review queue
Open the bulk tool, switch to Review workspace, and add the public product image URLs you want to check. The manifest stays in your browser until you export it.