Bandwidth Saver: Image CDN

Yes. Bandwidth Saver 2.0 serves images from your own img.pro App, so you need an img.pro account and an API key. The Free plan is enough to get started.

No. Your original files stay on your server and your database keeps its normal URLs. The plugin only uploads copies to img.pro and changes image URLs on your public pages. Deactivate it and every image loads from your server again.

Only files your pages show are copied, and each copied file counts as one image. WordPress saves a photo in several sizes, often 4 to 8, and a page that shows it offers most of them to the browser in its srcset, so a photo usually uses 4 to 6 images. Images no page shows, such as old uploads nothing links to, use none. Images your posts load from other websites count too, one image each. The settings page shows how many files are copied and how many images your App stores.

Yes. In the Media Library, choose Copy to img.pro under the image in list view, or in its details. To copy several, select them in list view and choose Copy to img.pro from Bulk actions. Every size of the image is copied. Bandwidth Saver changes image URLs in post content, widgets, featured images and images output with wp_get_attachment_image(). Images whose URL a theme or plugin reads directly, such as background images in theme CSS or a social sharing image, keep their server address; copy them and use Copy img.pro URL in their details.

Copying pauses. Images that were already copied keep loading from img.pro, and new ones keep loading from their original address. The App's owner can upgrade it in Billing on img.pro, or you can delete media you no longer use in WordPress, which deletes its copies too. Copying starts again on its own once the App has room, or you can click Try again now on the settings page. Deleting this site's images in the img.pro App itself does not make room for long: WordPress still uses those files, so Bandwidth Saver notices the missing copies (it checks up to 200 of its copies every hour, oldest first) and copies the files again. Until then, pages load those images from your server.

img.pro does not resize them. WordPress keeps creating every size, and img.pro serves each one at the same dimensions, as a high-quality copy in the same format (lossless for PNG). It removes hidden photo metadata, such as camera details and GPS location, and converts colors to sRGB. HEIC files are served as JPEG. Animated PNGs stay on your server, because img.pro shows PNGs as still images. The files you uploaded are stored unchanged.

Yes. Each image is labelled with the site it came from, and the plugin only lists or deletes images that carry its own site's label. All sites share the App's image limit.

A copy of your site keeps the original site's img.pro connection. On the copy, go to Settings > Bandwidth Saver and click Disconnect and keep images. If you want the copy to use img.pro too, connect it again afterwards (any key works, even one for the same App): it then gets its own label and copies its own images, and never touches the original site's. While a copy is still connected as the original, deleting media there also deletes the original site's copies from img.pro. Never click Delete images from img.pro and disconnect on a copy that is still connected as the original: it deletes the original site's images.

Deleting an image deletes its copies from img.pro. Editing an image (crop, rotate, scale) creates new files, which are copied the first time a page shows them, or right away with Copy to img.pro. WordPress keeps the previous files so you can restore them, and posts may still use them, so their copies stay on img.pro until WordPress deletes those files.

Go to Settings > Bandwidth Saver and click Delete images from img.pro and disconnect. This deletes every image this site uploaded and forgets the API key. Uninstalling the plugin does not delete anything on img.pro, so you can reinstall and reconnect to the same App without uploading again. If the site's address changed since it first connected, a reinstalled plugin cannot find those copies and uploads the files again, leaving the old copies in your App. To avoid that, click Delete images from img.pro and disconnect before uninstalling. On a copy of another site, such as a staging copy, use Disconnect and keep images instead.

Each image keeps a copy of its original URL, and the browser falls back to your server if img.pro does not answer. Visitors still see every image. Copying waits and tries again later, without marking your images as failed. If it waits for a long time, click Try again now on the settings page to try again right away.

Image URLs are chosen when a page is rendered, and a cached page keeps the URLs it was saved with. The first time a page is rendered after you connect, it asks for copies of its images and still shows them from your server, and your cache stores that version. Once the settings page shows nothing waiting to be copied, clear your page cache to switch those pages to img.pro.

Yes, unless you turn off Images from other websites in Settings > Bandwidth Saver. WordPress shows any image a post points to, wherever it is: an image inserted from a URL, another website's image, or your own site's images at an earlier domain. The first time a page shows one, img.pro copies it from its address, and from then on the page loads the copy. Each copy counts as one image in your App. An image at your site's earlier domain that WordPress recognizes as one of your media library files (it adds that file's sizes to the page) uses the copy of your own file instead, and so does an image at your own address with or without www. These keep loading from where they are:

• Images img.pro cannot reach, such as ones on a local or private address, and images whose website refuses or fails to send them.
• Tracking pixels and images from ad and analytics services, which have to keep reaching their own servers.
• Addresses that change from one view to the next, such as signed or expiring links.
• Images in a preview or in a post that is not published yet; they are copied once the post is public.

Not at the moment. Images are served from img.pro's own domain.

Version 2.0 replaces the old managed CDN and the self-hosted Cloudflare Worker with img.pro. Bandwidth Saver no longer uses the old service, so after updating your images load from your server until you connect an img.pro API key. Old settings, subscriptions and custom domains do not carry over.