Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Troubleshooting

Weglot Media Translation Not Working: Causes and How to Fix It

Weglot Media Translation Not Working: Causes and How to Fix It

Short answer

Turn on media translation in your Weglot dashboard, then visit the translated page so Weglot detects the image. If the original still shows, the browser is probably loading a srcset size, a lazy loading attribute, or a CSS background that Weglot does not swap. Clear every cache after changes.

Key takeaways

  • Media translation must be switched on in the Weglot dashboard.
  • Weglot only lists images it has seen on a translated page.
  • WordPress srcset sizes can override the translated src URL.
  • Lazy loading and CSS backgrounds can hide images from Weglot.
  • Images added by JavaScript or sliders may not be translated.
  • Clear page, server and CDN caches after each change.

Why is Weglot media translation not working?

Weglot media translation usually fails because the media option is off, the image is not detected yet, the browser loads a srcset size instead, or the image comes from CSS, lazy loading or scripts.

Media translation lets you show a different image, video or file for each language. It is useful for screenshots, banners with text, and product images that show local packaging.

When it fails, visitors on the translated page still see the original image. The cause is rarely Weglot itself. It is usually about how the image is placed in the page.

This guide covers the settings first, then the technical causes. For basic setup, see our guide on how to use the Weglot plugin.

Is media translation switched on?

Open your Weglot dashboard, go to the project's translation settings and make sure the media translation option is enabled; without it, image URLs are never listed for translation.

Media translation is off by default on many projects. When it is off, Weglot translates text but leaves image URLs alone.

After switching it on:

  1. Save the setting.
  2. Visit a translated page on your live site so Weglot scans it.
  3. Open the translations list in the dashboard.
  4. Filter by media to see the detected image URLs.

Media features can depend on your plan. Check the Weglot pricing page if the option is missing from your dashboard.

Weglot's article on media translation explains how the feature is meant to work.

Has Weglot detected the image yet?

Weglot only lists images it has seen on a translated page, so visit each translated page after enabling media translation, then look for the image in the dashboard.

If you added an image recently, Weglot may not have scanned it. Load the page in the translated language, wait a moment, then refresh the dashboard list.

When the image shows up:

  • Open its entry in the translations list.
  • Replace the URL with the image for that language.
  • Save, then clear caches and reload the translated page.

Upload language-specific images to your Media Library first. Copy their full URLs from there so the address is exact.

Is srcset overriding your translated image?

Yes, this is the most common cause; WordPress adds a srcset list of image sizes, and browsers often pick a file from srcset instead of the translated src, so the original still shows.

WordPress creates several sizes of every image and lists them in a srcset attribute. The browser chooses the best size for the screen.

The problem is simple. You translate the main src URL, but the browser ignores it and loads a size from srcset, which still points at the original image.

How the attributes behave:

AttributeWhat it holdsEffect on translation
srcThe main image URLWeglot can swap it
srcsetA list of sizes for different screensBrowser may load these instead of src
sizesHints for choosing from srcsetDecides which srcset file loads
data-srcLazy loading placeholderMay not be seen as an image

MDN's reference for the img element explains how src and srcset work together.

Fixes to try:

  • Translate the srcset URLs as well, if they appear in your translations list.
  • Insert the image at full size without responsive sizes on that page.
  • Ask a developer to remove srcset for specific images using the wp_calculate_image_srcset filter.

Is lazy loading hiding the image from Weglot?

Lazy loading plugins often move the real image URL into an attribute such as data-src, so Weglot may not treat it as an image and the swap never happens.

WordPress has native lazy loading that keeps the src attribute, which is fine. Some optimization plugins replace src with a placeholder and store the real URL elsewhere.

To test it:

  1. Turn off lazy loading in your optimization plugin.
  2. Clear the cache.
  3. Load the translated page and check the image.

If the translated image now appears, exclude that image from lazy loading. Most plugins let you exclude by class or file name. Our guide on lazy loading images in WordPress explains how the different methods work.

Is the image a CSS background?

Background images set in CSS, including many hero sections and page builder backgrounds, are not part of the page's image tags, so Weglot's media translation does not pick them up.

Page builders often place hero banners as backgrounds. These URLs live in style attributes or CSS files rather than img tags.

Ways around it:

  • Replace the background with a normal image element where possible.
  • Use a language-specific CSS class and set a different background for each language.
  • Build a separate section for each language and show it only on that language.

Weglot adds a language attribute to the page's html tag on translated pages. CSS can target that attribute to change a background per language.

Is the image loaded by JavaScript or a slider?

Images inserted by JavaScript after the page loads, such as many sliders, galleries and product zoom tools, may not be translated because they never pass through Weglot's normal scan.

Check whether the image appears in the page source. Right-click the page, choose view source, and search for the image file name.

  • Found in the source: Weglot should be able to see it. Look at srcset or lazy loading.
  • Not in the source: a script loads it later. Weglot may not translate it.

For sliders, many plugins let you create a separate slider per language. Show the right one with a language condition, or build different page versions.

Is caching serving the old image?

A page cache or CDN can keep serving the old HTML with the original image, so clear every cache layer after changing a media translation.

Caching affects Weglot translations in general. After you save a new image URL in the dashboard, the change will not show until cached pages are refreshed.

Clear the cache in your caching plugin, your host's server cache and your CDN. Then load the page in a private window. Our guide on clearing the cache in WordPress covers each layer.

Browsers cache images too. A hard refresh helps confirm what visitors really see.

Are image alt text and titles translated?

Alt text is translated as normal text, separate from the image file, so a translated image can still carry the original alt text until you translate it.

Check the alt text entry in your translations list. Update it to describe the language-specific image accurately.

Good alt text helps screen reader users and image search. Our guide on optimizing images for SEO covers how to write it.

Is the Weglot plugin set up correctly?

Make sure the Weglot plugin is updated, connected with the right API key and not conflicting with another translation or optimization plugin.

Quick checks:

  • Update the Weglot plugin to the latest version.
  • Confirm the API key in the plugin matches your Weglot project.
  • Remove other translation plugins, which can clash with Weglot.
  • Test with optimization plugins off, since minify and rewrite features can change image tags.

If the image still will not swap, contact Weglot support with the page URL, the language and the image URL. That lets them check what their system sees.

If images fail to load at all, not just in translations, see our guide on fixing images not showing.

Frequently asked questions

How do I translate images with Weglot?

Turn on media translation in your Weglot project settings, visit the translated page so the image is detected, then find the image in the translations list. Replace its URL with the address of the image for that language and save.

Why does the original image still show after I translated it?

The browser is probably loading a size from the srcset attribute, which still points at the original image. Translate those URLs too, insert the image without responsive sizes, or ask a developer to remove srcset for that image.

Can Weglot translate background images?

Not through normal media translation, since background images live in CSS rather than image tags. Use a regular image instead, or target the page language in CSS and set a different background for each language version.

Does Weglot translate image alt text?

Yes. Alt text is treated as text and appears in your translations list. It is separate from the image file itself, so translate the alt text when you swap an image so it describes the new picture accurately.

Is media translation included in every Weglot plan?

Plan features change over time. If you cannot find the media translation option in your project settings, check the Weglot pricing page or ask Weglot support whether your current plan includes it.

Sources

  1. Media translation: how to translate your website images Weglot
  2. Weglot Translate WordPress.org
  3. The Image Embed element MDN
  4. wp_calculate_image_srcset hook WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.