Do I Need External Images?
Before you install anything, it is worth being honest about whether External Images is a fit for your site. It solves a specific problem very well, and for the sites that have that problem it is close to essential. For other sites it adds a dependency you do not need. This page will help you decide which camp you are in.
The problem it solves
When you import products or posts that include images, WordPress does not just store the image. It downloads the full-size file into your uploads folder and then generates a resized copy for every image size registered on your site, which is often five, ten or more copies per image. On a catalogue of a few thousand products that is tens of thousands of files, and the download-and-resize step is the slowest part of any import. It burns CPU, it fills your disk, and a bloated uploads folder and media library slow down the whole site, backups included.
Now consider where those images usually come from. If you run an affiliate store, a dropshipping store, or any feed-driven catalogue, the supplier images already live on a fast third-party CDN. Downloading a copy of every one onto your own server is wasted work: you are paying in time, disk and CPU to duplicate files that are already hosted, already fast, and maintained by someone else.
External Images fixes this by letting WordPress display images straight from their existing URLs, without downloading them. You put the image URLs into the external_image_url custom field (pipe separated, the first URL becomes the featured image) and the plugin shows them as your featured images, galleries and variation images. No download, no resizing, near-zero image storage.
Where it shines: import speed
This is the headline. Because the slow download-and-resize step is skipped entirely, imports that used to take hours can finish in a fraction of the time. If you import with WP All Import (or any tool that can set postmeta), you stop importing images the normal way and instead map your image column to the external_image_url field. WP All Import then treats it as plain text and moves on, and External Images builds the featured image and gallery on first view. For large or frequently-refreshed catalogues this is the single biggest speed win the plugin offers. There is a full walkthrough in How to alter import jobs to import external images.
The download-and-resize step is almost always the slowest part of an import. Skipping it is what turns an hours-long run into a minutes-long one. If your import tool is Super Speedy Imports, the two plugins compound: fast row inserts, and no image work at all.
Who it is for
External Images is a strong fit if you are:
- Running an affiliate store, especially with Datafeedr or a product feed, where every image already sits on the network’s CDN. See Datafeedr Integration for the specifics.
- Running a dropshipping store sourcing images from suppliers.
- Managing a very large WooCommerce catalogue where local image storage has become a real cost.
- Importing with WP All Import (or WebToffee, WP Sheet Editor, and similar) and you want imports to fly.
- Low on disk, or simply wanting a lighter, faster media library and quicker backups.
In all of these cases the images are already hosted somewhere fast, and downloading them buys you nothing.
Who probably does not need it
If you run a small store with a handful of images that you host and optimise yourself, the problem above does not really apply to you, and a normal media library is perfectly fine. There is no import bottleneck to remove and no meaningful disk saving to make.
There are also workflows where you specifically want a local copy of every image. Some image-CDN and optimisation setups work best against files in your own media library, and if that is your workflow then keeping images local is the right call. External Images can still coexist with offload-media plugins, but if the whole point of your setup is to hold and process local files, it is not the tool you are reaching for.
Be clear-eyed about the trade-off. Displaying images from a third-party URL means you depend on that host staying up: if the supplier’s CDN goes down, those images go down with it (the plugin’s fallback image covers a broken URL, but not a whole host disappearing). The one concern that often worries people, that the images “belong” to another domain and might hurt SEO, is largely handled by the SSL proxy, which serves the images through your own domain so they appear local to browsers, social scrapers and search engines. The alt text and image HTML are still on the page for Google to read, and a lighter, faster site helps SEO rather than hurting it.
External images live on someone else’s host, so their uptime is not fully in your hands. That is the honest cost of skipping the download. For affiliate and feed-driven catalogues, where the network CDN is more reliable than most self-hosted setups anyway, it is a trade almost always worth making.
Next steps
If this sounds like your site, the quickest way in is the External Images Quick Start Guide, which walks you through the one field that matters and gets you to a working setup. For the install itself, see Installation & Activation.
Comments