News here:Weblooks now supports Antigravity!Read more here…News here:Weblooks now supports Antigravity!Read more here…News here:Weblooks now supports Antigravity!Read more here…News here:Weblooks now supports Antigravity!Read more here…News here:Weblooks now supports Antigravity!Read more here…News here:Weblooks now supports Antigravity!Read more here…News here:Weblooks now supports Antigravity!Read more here…News here:Weblooks now supports Antigravity!Read more here…
Weblooks

Concepts

What is website storage?

Storage is where your site's images, videos, and downloadable files live. It is separate from the code and from the content, and it is the part people forget until an image will not load.

What counts as storage#

Think of a website as three things: code (the pages and styles), content (the words, usually in a CMS), and files (photos, logos, PDFs, videos). Storage is the home for the third group. Files are too big to keep in the code and too unstructured for a CMS database, so they live in a storage bucket and the site links to them.

Where the files actually live#

In practice storage means a cloud bucket (Cloudflare R2, Amazon S3, or an image service) fronted by a CDN so files load fast everywhere in the world. The practical questions for a site owner are: who pays for it, who can upload to it, and what happens to the images if you switch providers.

How Weblooks storage works#

Projects hosted on Weblooks get platform storage automatically: assets you upload through the editor or the native CMS are stored and served for you, and the launch readiness checklist counts it as connected. Projects on their own infrastructure can connect an external bucket (R2, S3, or Cloudflare Images) at workspace level instead. Either way, the maintenance guide handed to your client explains where their images live and how to update them.