Independent comparison · no paid rankings
Home / Blog / Guide / Scaleway Object Storage: when to move media out of the web server

Scaleway Object Storage: when to move media out of the web server

Images, video and PDFs bloat the web server and complicate backups. Scaleway Object Storage makes sense once media volume or traffic exceeds local disk comfort.

Hébergeurs.eu Editorial Team 3 min read

An online magazine on a Scaleway VPS stores 180 GB of images in wp-content/uploads. Nightly backups exceed the maintenance window; the system disk would saturate at the next photo report. The reflex: "upgrade the VPS". Often the better reflex: move media off the web server.

Scaleway Object Storage solves a specific problem — not every site.

Media on the web server: when it holds — when it breaks

Stay local if:

  • Brochure site < 5 GB media
  • Moderate traffic, no large PDF/video
  • File + DB backup fits under 30 minutes

Offload if:

  • User uploads (marketplace, intranet)
  • Media library > 50 GB
  • Assets served from multiple fronts (web + mobile app)
  • Selective file restore without full VPS replay
SignalIndicative thresholdAction
Upload disk> 60% VPSObject Storage + plugin
Backup duration> NOC windowExternalise blobs
Bandwidthimage spikesCDN + bucket
ComplianceFR residencyfr-par region

Scaleway offers Object Storage in Paris — consistent if you already run there. See Scaleway S3 lifecycle.

The web server should run PHP and APIs — not become a public NAS.

Typical WordPress / CMS architecture

  1. Private bucket + public access via CDN or signed URLs for sensitive content.
  2. Offload plugin (Media Cloud, WP Offload Media) — test restore on staging.
  3. DB stays on VPS — only binaries move.
  4. Lifecycle rules — archive old media to cold tier if available.
  5. Backup — rclone or bucket snapshot + separate SQL dump.

Test restore: re-importing an accidentally deleted media file should take minutes, not overnight.

Common pitfalls

  • Hardcoded URLs in DB after migration — search-replace scripts required.
  • Missing CORS for SPA or mobile app.
  • Public bucket by default — leak of unpublished files.
  • No versioning — irreversible delete.
  • Misconfigured CDN — stale cache after image update.

The crux: offload without CDN just moves the bottleneck

Decide and move forward without blind spots

Measure upload size, backup duration, monthly egress. Create a test fr-par bucket, migrate one subfolder, validate performance. See the Scaleway profile and comparator. Document restore procedure in your runbook.

Frequently asked questions

When to offload media?

From ~20–50 GB uploads, slow backups, or heavy static files without CDN.

S3-compatible?

Yes. WordPress plugins and rclone — check region and IAM.

Cost impact?

Affordable storage; watch egress and API requests. CDN recommended.

Media in France?

fr-par region; also verify CDN location.


Object Storage frees the web server — if you budget delivery, not just disk.

See the Scaleway sheet

Independent scores, plans, pros/cons and alternatives to Scaleway.

Open the Scaleway sheet
Blog

Related reading

All articles →