Hosting a website from cloud storage

It used to work, every provider removed it, and what replaced it is better.

Consumer storage services used to serve a folder as a website. Every one of them removed it, and the guides describing it are all out of date.

A page file opened from storage rendering inside a file viewer rather than as a page.
A page file opened from storage rendering inside a file viewer rather than as a page.

What happens now

A page file in a sync folder opens in the service's viewer. You see the markup, or a preview panel, or a download prompt.

Stylesheets and scripts referenced by the page do not resolve, because the addresses the viewer produces are not the folder structure the page expects. The result is either the source code or an unstyled page.

Nothing about this is fixable from your side. The capability was withdrawn.

Product Serves a website
Consumer sync folder No
Document suite storage No
Object storage (developer) Yes, with configuration
Static hosting Yes, designed for it
Repository hosting Yes

Why it went away

Three reasons, all of them reasonable.

Abuse. A trusted domain serving arbitrary pages is ideal for phishing, and the volume was substantial.

Cost. Serving a popular page is bandwidth, and the storage plans were not priced for it.

It was never the product. Storage sells space and sync. Hosting is a different business with different obligations.

Object storage is a different thing

Developer object storage does host static sites properly, with custom domains and certificates, and it is a normal way to run a site.

It is not a sync folder. It has its own concepts, its own access configuration, and a pricing model based on requests and transfer. Confusing the two is the usual source of the belief that storage can host a site.

A storage link beside a static host address, with what each provides.
A storage link beside a static host address, with what each provides.

What static hosting gives you that storage never did

A real address. On your own domain, rather than a storage link containing an identifier.

Correct serving. The entry page loads at the folder address, paths resolve, and the site behaves as a site.

A certificate. Automatic, renewed, no warning screens.

No viewer frame. Your page is the page, not a panel inside somebody else's interface.

Most of it is free at the volume a small site produces, so the practice did not survive its removal for a reason.

If this is near what you are doing, Sharing from a sync folder and Free static website hosting, compared honestly cover the cases on either side.

Put it at an address

Stop planning around storage serving pages, use static hosting instead, keep object storage separate in your thinking, check that a custom domain is included, and upload the folder with its structure intact.

Questions people ask

Can I host a site from cloud storage?

Not from consumer sync services. They all removed public site serving years ago, and links now open a file viewer rather than render a page.

Why did they stop?

It was heavily used for phishing and malicious files, it cost bandwidth they were not charging for, and it was never the product.

What happens if I try?

The page opens inside the service’s viewer, styles and scripts do not resolve, and shared links change form when files move.

What about object storage?

That is different and does host static sites properly. It is a developer product with its own configuration, not a sync folder.

What should I use instead?

Static hosting. It is designed for exactly this, frequently free at small volumes, and includes a custom domain and a certificate.

Keep reading