WordPress Media Offload: FTP Transfer and HTTPS Delivery Are Different Jobs

A full uploads folder can look like a hosting problem when it is really a media-storage problem. Before moving an entire WordPress site, it helps to separate the application from the files it serves.

Disclosure: I work on LumoWP, including Lumo FTP Media. This is a practical planning note, not a performance benchmark.

Two connections, two jobs

FTP, FTPS or SFTP transfers a file to another server. Your visitor does not use that connection to see a product photo. Their browser requests a public image URL, normally over HTTPS.

That distinction explains a common failure: the transfer succeeds, but the image is missing on the page. The destination path may not map to the public URL, a thumbnail may be absent, or the public server may require authentication.

Start with a small pilot

Choose a few representative uploads: a product photo with several generated sizes, a PDF and an image used by your page builder. Back up first and retain local copies during the pilot.

Configure the transfer destination and public media base URL. After transferring the sample, open the public URLs in a signed-out browser. Then open the actual pages. A correct original file does not prove every generated size is available.

Check desktop and mobile because the browser can select different image files. For a store, include a real product gallery in the sample.

Where our plugin fits

Lumo FTP Media provides media-transfer tools, automatic-upload rules, existing-media synchronization and output URL rewriting inside WordPress. It is intended to keep the publishing workflow in WordPress while media lives on a separate destination.

The destination still needs reliable delivery. Offloading is not image compression, a backup strategy or a guaranteed speed improvement. Keeping every local file also means you should not expect immediate local storage savings.

Decide from measurements

Record storage use and page performance before changing the setup, then repeat the same checks afterward. Expand only when the pilot behaves as expected. Local cleanup should be a deliberate final decision, after backups and remote delivery are verified.

Our FTP/SFTP setup walkthrough covers the workflow in more detail.

What tends to be the real bottleneck on the sites you maintain: storage capacity or media delivery?