Static Website Examples, Troubleshooting and Tips

This page shows examples, troubleshooting and tips for using buckets to host a static website.

Website configuration examples

The following scenarios demonstrate the objects that are served to you when you attempt to access them with various URLs.

Three-object bucket

Suppose a bucket named has been configured as a website with the following settings and files:

  • MainPageSuffix = "index.html"
  • NotFoundPage = "404.html"
  • The bucket contains three publicly shared objects: "index.html", "404.html", and "dir/index.html".

The following table shows the content served for selected URLs:

URL Requested Content Served
The object "index.html". The object "404.html".
The object "dir/index.html".

Two-object bucket

Suppose a bucket named has been configured as a website with the following settings and files:

  • MainPageSuffix = "main.html"
  • NotFoundPage = "404.html"
  • The bucket contains two publicly shared objects: "main.html" and "404.html".

The following table shows the content served for selected URLs:

URL Requested Content Served
The object "main.html". The object "404.html".

If an object is shared publicly, you can also view that object with the URL:[BUCKET_NAME]/[OBJECT_NAME]

For example, the URL for an index.html object would be:

For more information about working with publicly accessible data, see Accessing Public Data.

Troubleshooting a bucket configured as a website

The following are some common issues that may be encoutered when setting up a bucket to host a static website, along with the resolution to those issues.

You want your content served through HTTPS

SSL is not currently supported by the Cloud Storage webservers; thus, you can only use a CNAME redirect with HTTP and not with HTTPS. If you wish to serve content through HTTPS from your bucket, we recommend you use a third-party Content Delivery Network with Cloud Storage. Alternatively, you can serve your static website content from Firebase Hosting instead of Google Cloud Storage.

Buckets are created before verifying a domain

If you try to create a bucket for a newly created domain before it is verified, you'll receive a warning message. In this case, you should choose the verification process that doesn't involve adding a meta tag to your home page or uploading an HTML file. Instead, verify ownership using the Domain name provider verification method with a DNS TXT or CNAME record, or else directly within Search Console. This verification can be done before the bucket is created.

Access is denied

If you get the following message for a web page served by your website:

<Message>Access denied.</Message>

Check that the object is shared publicly. For an example of how to do this in Google Cloud Platform Console, see Sharing Data Publicly.

If you uploaded an object (for example, index.html), marked it as shared publicly, and then upload a new version of it, then you must reshare the object publicly because that permission is overwritten with the new upload.

Users are prompted to download content

If you specify a MainPageSuffix as an object that does not have a web content type, then instead of serving the page, site visitors are prompted to download the content. To resolve this issue, update the content-type metadata entry to a suitable value (e.g., text/html). You can do this, for instance, by using the gsutil setmeta command.

Tips for working with a bucket configured as a website

The following are some tips to keep in mind when using a bucket to host a static website.

Adding subdomains

Suppose you also want to serve content at, from a different bucket than the one that serves content at To do so:

  1. Create a new bucket Because you already verified the domain, you can create buckets to support subdomains without additional verification.

  2. Add a new CNAME record for the subdomain.

    NAME                  TYPE     DATA
    test                  CNAME

The following example shows what the subdomain bucket looks like in the Google Cloud Platform Console.

Bucket website subdomain example.
Example of a bucket configured for a website subdomain.

Setting cache parameters

You can control how or if your website assets are cached by configuring cache control headers. Generally, only set cache control headers for objects that are accessible to all anonymous users, which is a requirement for any object served from a Cloud Storage bucket as part of a static website.

Google Cloud Storage applies a cache control setting of 3600 seconds to objects that are accessible to all anonymous users, unless you specify explicit cache control settings. For examples, see the metadata page of gsutil, the setting object metadata page for the Google Cloud Platform Console, or headers reference pages for XML and JSON.

API behavior

Website configurations are only used to interpret requests directed to CNAME aliases of (that is, requests where the hostname is a custom domain). For example, only requests to show the index page.

Thus, API behavior for requests to Cloud Storage domains, such as, is preserved. For example, you can continue to list objects in the bucket as you would for any other bucket. In the case of the bucket, the object listing you receive includes 404.html and index.html.

Hosting static assets for a dynamic website

You can use Google Cloud Storage to host static assets for a dynamic website that is hosted, for example, in Google App Engine or in Google Compute Engine. Some benefits of hosting your static assets, like images or Javascript files, in a bucket include:

  • Cloud Storage behaves essentially like a Content Delivery Network (CDN) with no work on your part because publicly readable objects are, by default, cached in the Cloud Storage network.

  • Bandwidth charges for accessing content typically cost less with Google Cloud Storage.

  • The load on your web servers is lessened when serving the static content from Cloud Storage.

You can also control caching, such as disabling caching or setting cache lifetime, for your publicly readable static assets by using cache control request headers. For more information, see Setting cache parameters.

When hosting static assets for a dynamic website, you do not need to create a CNAME record and point to a bucket with the same name as you do for a static website. For example, you could have a bucket named www_example_com_assets with appropriate assets configured as shared publicly and then access those assets using the Cloud Storage domain. For example, suppose you have the JavaScript file library.js in the bucket www_example_com_assets that is shared publicly, then you can access it as

Bucket serving static assets.
Example of a bucket serving static assets.

Monitor your storage charges

If you are serving assets, either as a bucket configured as a static website, or serving static assets from a bucket for a dynamic website hosted outside of Google Cloud Storage, you should monitor the charges to your project that contains the bucket. Serving content incurs storage costs for hosting the content (per GB per Month), network egress (per GB), and retrieval operations (Class B). See the Google Cloud Storage pricing page for more details.

The simple pricing example on the pricing page can be used as an approximation for the use case of a low-traffic, static website. You can use the Pricing Calculator to generate a cost estimate based on your projected usage.

New Cloud Platform users might be eligible for a free trial.

If you are a current Cloud Platform user, you can get a detailed breakdown of your project costs on the billing page.

Send feedback about...

Cloud Storage Documentation