Multilingual WordPress websites often require more than translating visible paragraphs. Images, videos and PDFs also carry titles, alternative text, captions and descriptions that can affect how content is understood in each language. WPML can handle these media fields as part of the translation workflow, while its Media Translation functionality can also support different media files for different languages.
The important distinction is between translating media metadata and replacing the underlying file. These are related, but they are not the same operation. The exact workflow can depend on the editor, page builder, theme, content type and installed WPML components. For that reason, a controlled test on representative content is useful before applying automatic translation across a larger production site.
What WPML Media Translation Actually Handles
Metadata versus the media file
WPML supports translation of media metadata for images, videos and PDFs. The documented fields include alternative text, captions, descriptions and titles. In a typical workflow, this text is translated together with the page, post, product or other content that uses the media.
This does not mean that every media file is automatically replaced with a translated version. Translating the alternative text of an image changes its associated text, not the physical image itself. If a website needs a different image, video or PDF for a particular language, the relevant WPML Media Translation functionality is used to assign language-specific media.
WPML’s documented behavior also distinguishes language-specific metadata handling from duplication of underlying image files. Media-text records may be created or duplicated according to how the media is referenced, but this should not be described as creating another physical copy of every image. Custom media fields and integrations may require separate verification.
Translate Image Alt Text and Captions with WPML
The page or post translation workflow
The main workflow starts with the content that contains the media. In WPML’s Translation Dashboard, send the relevant page, post, product or other content for translation. When the content is opened in the Advanced Translation Editor, WPML can present the media text alongside the surrounding content.
Depending on the content structure, this may include:
- Alternative text for an image.
- Captions displayed with the media.
- Descriptions associated with the media.
- Titles stored for the image, video or PDF.
Translate the fields in context rather than treating them as unrelated library entries. A caption may need to match the wording of the page, while alternative text should accurately describe the relevant media in the target language. Before publication, review the result for meaning, accessibility and brand accuracy.
Automatic translation can process media text together with surrounding content, but it should not be assumed that every image field, featured image or custom media field will behave identically in every integration. The available controls and exact labels may vary by WPML version, installed components, editor and content type.
Display Different Images by Language
Replacing media for a target language
Some websites need more than translated text. A business may use a different image for a regional audience, or a document may have a language-specific edition. WPML can support different images, videos or PDFs by language when the WPML Media Translation add-on is installed and configured.
The documented setup sequence is:
- Install and activate the WPML Media Translation add-on and complete its setup.
- Open WPML → Media Translation.
- Select the required target language.
- Use the add-media control to upload or select alternative media.
- Adjust the metadata for that language and save the translation.
The translated content can then use the language-specific image, video or PDF. This is separate from simply translating the original media’s alt text or caption. After saving, check the translated page on the front end and confirm that the intended file appears in the intended language.
The result may depend on how a page builder, block or theme stores the media reference. A workflow that works for a standard image may not behave in the same way for a background image, custom block attribute or another specialized content structure. Test a limited set of representative pages before making language-specific media changes throughout a site.
When WPML Duplicates Media Text
Media Library references and inline content
WPML’s handling of media text can differ according to where that text is stored. When a page builder retrieves image text from the Media Library, WPML may duplicate the media text during translation. When the text is stored directly inside the page content, WPML translates the text in place instead.
This distinction explains why two visually similar images may expose different translation behavior in the Advanced Translation Editor. The difference is not necessarily caused by the image itself. It can result from the way the editor, builder or content type references the media and its associated fields.
WPML recommends keeping the option that automatically detects the best options for translating image texts enabled, where that option is available. Its purpose is to help determine whether media-text duplication is necessary for the way the content is stored.
In this context, duplication refers to media text or related database records, not necessarily another physical image file. Do not assume that enabling or disabling a duplication-related setting guarantees a particular front-end result. Elementor, Divi, Beaver Builder, Gutenberg and WooCommerce contexts may store media references differently, so the relevant workflow should be checked in the actual site configuration.
Automatic Media Translation Settings
Choosing automation with review control
For media metadata, review the media translation settings in WPML. Where available, keep the option that automatically detects the best options for translating image texts enabled. This allows WPML to determine whether media-text duplication is needed instead of requiring the site owner to manage that decision manually for every content structure.
For broader automation, WPML’s Translate Everything Automatically mode can process existing and future content from the default language to secondary languages. Media text may be processed as part of the surrounding content. The automatic workflow also includes choices about publication, such as publishing translations immediately or holding them for review.
A practical approach is to begin with representative pages containing the media structures used by the site. Include the types of content that matter to the project, rather than assuming that one successful test covers every editor or custom field.
Choosing automation with review control
When review is required, hold translated content for checking before publication. Review alternative text, captions, descriptions and titles in the target language, then inspect the front end to confirm that the correct media and text appear together. If immediate publication is selected, the same checks should still be performed on representative content before the workflow is expanded.
Automatic translation is a workflow option, not a guarantee that every translation or integration will be accurate. Exact setting labels and available controls may vary by WPML version, installed components, editor and content type. Test on a staging site or a limited set of pages before applying the process broadly to production content.
Compatibility Checks and Pre-Publication Checklist
A practical validation checklist
Media translation depends partly on how an editor or builder exposes media references. For page-builder content and Gutenberg block attributes, media IDs or media URLs may need to be exposed in a form that WPML can process. Background images and custom block attributes may therefore require specific handling rather than the same workflow as a standard image inserted into page content.
The official workflow is general and should not be treated as a complete compatibility matrix for every editor, page builder, theme or WooCommerce extension. WPML is not the developer or official support provider for Elementor, Gutenberg, WooCommerce, Divi, Beaver Builder or other third-party products. Verify the behavior of the actual combination used on the website.
Before publication, check the following items:
- Confirm that the intended image, video or PDF appears for each language.
- Review translated alternative text, captions, descriptions and titles.
- Test content created with the relevant editor, builder or block.
- Check pages that use different media references, including language-specific media.
- Review automatic translations for meaning, accessibility and brand accuracy.
- Test representative content before extending the workflow to a larger production set.
If a media field does not appear as expected, first establish where the text or media reference is stored. The distinction between Media Library data and text stored inside page content can explain different results. Custom fields and specialized blocks should be treated as scenarios requiring validation, not as universally supported cases.
WPML can translate media metadata such as alternative text, captions, descriptions and titles, and its Media Translation functionality can support language-specific images, videos and PDFs. The key is to separate translated text from replacement media and to understand how the editor stores each reference. Media-text duplication may be appropriate in one structure and unnecessary in another, which is why automatic detection, review and testing matter. Use a staging site or limited content set before scaling an automated workflow, then check each language on the front end. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.