Image-heavy WordPress sites fail in predictable ways: disk fills, pages ship 8 MB heroes, backups time out, and deploys of wp-content/uploads become huge zips. Hosting cannot make a 20 MB original “cheap” on the network. It can give you clear storage quotas and a PHP runtime that will not be the first bottleneck.
WPHost storage by plan: Starter 2 GB, Pro 10 GB, Scale 30 GB, Business 100 GB (prices $9 / $30 / $65 / $130; site caps 1 / 3 / 10 / 30). Pick the tier for the library you actually have — not the library you will have after you “definitely start resizing next month.”
Where the bytes live
Most weight is wp-content/uploads — originals plus thumbnails WordPress generates. Themes and plugins are comparatively small until someone installs a demo pack with its own media.
Deploy history keeps file releases. Giant upload trees make deploys and rollbacks heavier. That is still not a substitute for database backups — SSL and backups.
Right-size before you upload
- Shoot or export for web: widths like 1600–2400 px cover most layouts.
- Prefer JPEG/WebP for photos; PNG for graphics that need crisp edges.
- Avoid uploading RAW or camera JPEG “just in case” to production.
- Let WordPress thumbnails do mid-size work; do not stack five image-optimizer plugins.
Photographers often need originals elsewhere (Lightroom vault, DAM, client drive) and web derivatives on WordPress — photographers. Magazines and blogs: featured images are not archival storage — blog.
Offloading media
When libraries exceed comfortable plan storage — or when you want a public media CDN — use an offload plugin to S3-compatible storage or similar. The origin then stores lighter references; browsers fetch media from object storage/CDN.
WPHost has no built-in CDN product. Offload + Cloudflare (optional) is a normal pattern. Test URL rewriting on staging (Pro+) so you do not break existing posts — staging.
Performance is transfer, not only PHP
PHP 8.4 helps dynamic generation — fast hosting. Largest Contentful Paint still dies on huge heroes. Lazy-load below-fold images. Do not autoplay silent 40 MB background videos from the media library; use a video host — especially for courses — online courses.
Page builders that inline enormous backgrounds make “image-heavy” worse — designers.
Backups and migrations
Image-heavy sites turn migrations into logistics problems. Exporting a 40 GB uploads tree over a laptop cafe Wi-Fi is how weekends vanish. Strategy:
- Offload first, then migrate references, or
- Transfer uploads via the most reliable channel you have, verify counts, then cut DNS
Serialized URL replace still applies for domains — migrate. Budget temporary double storage during transition.
Backup plugins must handle large upload sets (chunking, cloud destinations). A “full backup” that never finishes is not a backup.
Choosing a plan with eyes open
| Library vibe | Likely plan |
|---|---|
| Text blog, few hundred compressed images | Starter 2 GB |
| Active blog / small portfolio | Pro 10 GB |
| Studio with many galleries (web-sized) | Scale 30 GB or offload + smaller plan |
| Agency multi-site with heavy media | Business 100 GB and/or offload |
Teams on Business help when several people upload — still teach them resize hygiene or disk dies anyway — agencies.
What we will not claim
- Infinite storage
- Magical recompression that replaces your workflow
- Built-in DAM
- One-click installer that somehow optimizes photos
- Auto plugin updates for image plugins
You update image plugins in wp-admin. Trial ~1 day. No nonprofit storage coupon. No email, no cPanel.
Galleries, Woo, and proofing
Gallery plugins multiply thumbnails — disk math sneaks up. WooCommerce product images add another tree — Woo. Client proofing plugins are application software; we do not certify them as hosting features.
Portfolios that are already static HTML might not need WordPress media libraries at all — portfolio.
Operational checklist
- Measure current
uploadssize before choosing Starter “because $9.” - Resize workflow documented for anyone with wp-admin access.
- One optimization plugin maximum if needed.
- Offload plan when growth is obvious.
- Staging tests for CDN/offload URL changes.
- Backup plugin proven on a large restore once.
- HTTPS and correct URLs so mixed-content does not break images on hard refreshes — custom domain.
Thumbnail regeneration traps
Changing theme image sizes and regenerating thumbnails can double disk usage temporarily. Run regenerators in off hours; watch free space; delete orphaned sizes when tools allow. Staging is a good place to learn how aggressive your regenerator is — staging.
Editorial guidelines worth posting in Slack
- Max upload width guideline (e.g. 2000px)
- No WhatsApp “image full quality” dumps into production
- Screenshots as PNG only when UI chrome needs it; otherwise JPEG/WebP
- Heroes under a target kilobyte budget
Hosting plans enforce quotas; culture prevents hitting them weekly. Freelancers: put the guideline in the client handbook — freelancers.
Hotlink and bandwidth adjacent issues
If your images appear on other sites via direct URLs, that is mostly an edge/CDN policy question once you add Cloudflare (optional). We do not sell a hotlink product. Focus first on not shipping 8 MB files; hotlink drama is secondary for most WordPress sites.
Choosing offload timing
Offload early if growth is obvious; offloading a 40 GB library later is a project. Test a subset of URLs on staging, then migrate. Keep a rollback note if the plugin miswrites URLs. Custom domain HTTPS must be correct first so rewritten URLs are https — custom domain.
If editors insist on “maximum quality,” show them the plan storage numbers ($9/2GB through $130/100GB) and the cost of offload storage — math ends arguments faster than taste debates.
Storage math meets WordPress reality
Plan disks are 2 GB (Starter $9), 10 GB (Pro $30), 30 GB (Scale $65), and 100 GB (Business $130). WordPress itself is small; unoptimized media libraries are not. Before you upgrade, open Media Library sort-by-file-size thinking — delete unused originals, regenerate thumbnails after changing sizes, and stop uploading 6000px PNGs for a 400px slot.
WPHost has no built-in CDN. Edge caching can help repeat views; it will not shrink a 12 MB hero. Optional Cloudflare is fine after diet. Deploy history restores files from publishes; it is not a substitute for off-site backups of uploads plus the database — SSL and backups.
Install and update discipline
Zip-install WordPress, then add only the media plugins you will maintain. We do not auto-update. Gallery plugin updates can rewrite markup — use staging with a DB copy. Lazy-loading and modern formats are theme/plugin work, not a hidden host toggle.
Schedule a quarterly uploads audit: delete unused media, confirm offload, and re-check plan headroom before a campaign dump.
FAQ
Can I host a 50 GB photo archive on Business?
Business includes 100 GB per plan capacity across your sites — still a web host, not cold archival storage. Keep masters elsewhere; serve derivatives.
Will PHP 8.4 compress my images?
No. It executes PHP faster. Compression is your export settings or a plugin.
Why did my backup plugin time out?
Likely huge uploads. Use incremental/cloud destinations or offload media first.
Is Scale enough for a magazine?
Maybe if images are web-sized and you prune. Offload when unsure.
Do deploys include all uploads?
If uploads live on the site filesystem and you zip them, yes — and the zip will be painful. Offloaded media may live outside the deploy; know your architecture.