Download websites that use DigitalOcean Spaces

About DigitalOcean Spaces

Object storage is chosen by the person who builds the deployment pipeline, not by the person who writes the words on the page. DigitalOcean Spaces sits in that layer, holding the images, video files, backups and static bundles that a site does not want to serve from its own application server. Finding it on a domain says less about the site's content than about the team behind it and the hosting decisions they have already made.

DigitalOcean launched the service in 2017, during a wider push from plain virtual machines toward managed building blocks, and kept its interface compatible with the object storage API developers were already writing against. A team can therefore move buckets between providers without rewriting application code, and anyone reading a list of adopters as a competitive question should keep that low switching cost in mind. Licensing is Proprietary, so there is no self-hosted edition and no ambiguity about who operates the storage behind a given bucket.

Detection depends on what a browser can see. We record the service when assets load from the vendor's own storage or edge hostnames, which covers the default setup that most projects never bother to change. A project that parks a custom domain in front of its bucket disappears from that signal, and so does one that uses the service only for private backups with nothing reaching the public page. Counts here are a floor rather than a census, and the gap is widest among larger sites, because a custom asset domain is exactly the sort of polish a bigger engineering team applies.

As of September 2026 we detect the service on 91,369 sites. United States accounts for 72,066 of them, and .com is the common suffix, which fits a user base of startups, agencies and product companies rather than the national small business web that tends to sit on country domains and shared hosting. The geography also reflects where the vendor's developer community and marketing have been strongest, which is worth remembering before reading the country split as a statement about global demand.

For a researcher the useful mode is comparative. A per-domain lookup tells you that one site keeps its assets with a particular cloud provider, which is rarely worth knowing on its own. A downloadable list lets you ask population questions instead: which segments of the web run on mid-market cloud rather than hyperscale accounts, how storage choice correlates with the frameworks and analytics on the same page, and which agencies deploy an identical stack across every client they touch. Sales teams at competing storage and delivery vendors treat the list as a qualified prospect pool, since every entry has already proved it buys infrastructure by the month rather than renting a shared host. Security researchers use it differently, as a starting set for checking bucket exposure and misconfiguration across many organisations at once.