Reseller runbook · Allowance management · an hour for the backlog
How to optimize images for the web — Your Clients Are Uploading Your Disk Allowance Away
One client uploading phone photographs straight from the camera roll can consume more of your allowance than twenty sites that behave.
Straight answer first
Automate image handling inside every client account instead of teaching clients to resize, because the instruction never survives contact with a busy person and a deadline. WebP conversion and optimisation are built in and cost nothing, so the fix is a setting in the build rather than a habit you have to police.
The reason a reseller cares more than a site owner is arithmetic: a reseller package gives you 30 GB, 60 GB or 100 GB of NVMe to divide between 100, 250 or 500 client accounts. Camera originals at several megabytes each are how that allowance leaves without anybody deciding to spend it.
Written by the Hosting Seller staff · Checked 24 August 2026
Beginner
Skill assumed
Quick
Bench time
5
Runbook stages
24/7
Cover for you and your clients
Image weight reaches a reseller through two doors at once: page speed on client sites, and the disk allowance you are dividing between everybody. The second one is the expensive one and nobody watches it.
The answer is not education. It is automation in the build, one pass over the backlog, and a quiet look at the accounts whose disk use does not match their size.
Where a 30 GB allowance actually goes
Look at the sums before deciding this is a small problem. A reseller package carries 30 GB, 60 GB or 100 GB of NVMe depending on which plan you bought, and that is shared across every client account you create. A single client site with a few thousand unoptimised camera originals can occupy a share of it that is completely out of proportion to the site's traffic or its invoice.
The accounts to look at are rarely the ones you would guess. It is not the busy shop; it is the local business that has been posting phone photographs to a news page since 2019, and the estate agent whose property galleries were never resized. One WHM glance at disk per account finds them in about a minute.
The upload habit you have to design around
You cannot fix this by asking. A client uploading a 4000-pixel file into an 800-pixel slot is not being careless; they are doing the only thing their workflow offers, and the person who does it is usually not the person who attended your handover. Telling them to resize first works for one week.
So design around the behaviour. Optimise on upload, generate the display sizes automatically, serve WebP, and lazy-load anything below the fold. Once that is in the build, the client's habit stops mattering — which is the only sustainable position when the uploading is being done by somebody you have never met.
Automating it once per account rather than teaching everyone
WebP image optimisation is built in and costs nothing extra, and the cache plugin handles both the conversion and the serving. Put that configuration into the standard build for every account so it is present from the first upload rather than applied after somebody notices.
Compression at around quality 80 looks identical to the original at roughly half the bytes, which is the free lunch of this entire subject. Combined with generating the sizes actually displayed and deferring below-the-fold images, it turns the worst-behaved client site into an ordinary one without a single conversation.
The back-catalogue pass, quoted as a job
New uploads are handled by the build; the years of existing originals are not. A bulk optimisation pass converts the whole library in one go, and on a long-established client site it is usually the largest single weight reduction available anywhere on the list — and the largest disk saving too.
Quote it as a job rather than absorbing it. It is measurable, explicable and easy to demonstrate: before and after figures for page weight and disk use. Clients buy work they can see the result of, and this is one of the few optimisations where the result fits in one line of a message.
Optimisation included, not upsold
WebP image optimisation is built in and costs nothing extra, so the fix for the most common weight problem on client sites is a setting rather than a purchase.
Underneath, NVMe storage means the images that do have to be served come off fast disk — and the reseller packages give you 30 GB, 60 GB or 100 GB to divide as you see fit.
- WebP optimisation built in, at no cost
- NVMe storage across every account
- 30, 60 or 100 GB to divide between clients
- LiteSpeed caching in front of the lot
Why Hosting Seller
On every plan, as standard
Costed against your allowance
The page starts from the disk you bought and are dividing, which is the reseller consequence nobody measures.
Designed around client behaviour
The advice assumes clients will keep uploading camera originals, because they will.
Automated in the build
Everything here goes into the standard account build rather than into a client instruction sheet.
Backlog priced as work
The historical pass is treated as a billable, demonstrable job with before-and-after figures.
Included at no extra charge
WebP optimisation is built in, so the standard costs nothing per account to apply.
Help at any hour
Support answers for you and for your clients, including mid-pass on a large library.
First Steps
From choosing to live
- 1
Sort your accounts by disk use first
One look at the WHM list finds the outliers, and they are rarely the accounts you would have guessed. Start where the allowance is actually going rather than where the traffic is.
- 2
Put optimisation in the build, not the handover
Automatic conversion, generated display sizes and lazy loading configured on every new account. Instructions to clients about resizing work for exactly one week.
- 3
Serve WebP and compress to around quality 80
Quality 80 is visually indistinguishable at roughly half the bytes, and the cache plugin handles both conversion and serving. This is the single highest-return setting on the page.
- 4
Defer everything below the fold
Images outside the first screen load as the visitor scrolls. The first paint stops paying for the footer, which is the part of the page nobody sees before deciding it is slow.
- 5
Quote the back-catalogue pass as a job
One bulk run over years of originals, with before-and-after page weight and disk figures. It is the largest single reduction available on most established client sites, and it is easy to sell because the result is visible.
In the Box
Packed with every plan
- WebP image optimisation built in and costing nothing extra
- NVMe SSD underneath and LiteSpeed cache in front, at every price point
- 30 GB, 60 GB or 100 GB of NVMe to divide between client accounts
- Client-account allowances of 100, 250 or 500, depending on the package
- cPanel, the panel your clients and your contractors already know
- WordPress Toolkit, with updates applied for you
- WHM for you, and a cPanel of their own for every client account
- Real people answering, for you and for your clients, at any hour
- Upgrades applied to the account in place, with no migration between plans
- Packages you build, name and price yourself
Across the Counter
Things people ask us all the time
How much of my reseller storage do client images take?
On established sites, usually the majority of it. A reseller package carries 30 GB, 60 GB or 100 GB of NVMe divided across every account you create, and a few thousand camera originals on one site can consume a share wildly out of proportion to its traffic. Sorting accounts by disk use in WHM finds them in a minute.
Should I limit upload sizes on client accounts?
Automate rather than restrict. A hard limit produces a support ticket the moment a client cannot post their photograph; automatic conversion, generated sizes and compression produce the same disk outcome and no ticket at all. Restrict only where an account is genuinely out of control.
Is WebP conversion included on the accounts I create?
Yes — WebP image optimisation is built in and costs nothing extra, and the cache plugin handles conversion and serving. That means the standard can go into every account you build without a licence cost per client, which is what makes it worth standardising.
Can I bill for a one-off image optimisation pass?
Yes, and it is one of the easier optimisations to sell because the result is measurable. Quote it as a job with before-and-after page weight and disk figures. On a long-established client site it is usually the single largest weight reduction available.
Read next
Email Hosting
Mailboxes for a client whose website lives somewhere else entirely.
WordPress Hosting
The WordPress tier most client sites belong on, with the toolkit included.
Moving your site to another host? Start with this checklist.
A step-by-step order of work for a move your visitors never spot: which files to copy first, how to carry email across without losing one message, the right moment to repoint DNS, and the two mistakes behind nearly every hour of downtime people ring us about.
Stop client uploads eating your allowance.
WebP optimisation built in, NVMe storage underneath, and 30, 60 or 100 GB to divide between client accounts as you choose.
See Email Hosting plans