Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What is a cookie-free domain? I've seen these words many times but I never understood what it is.

share|improve this question

migrated from Oct 26 '09 at 4:54

This question came from our site for professional and enthusiast programmers.

up vote 13 down vote accepted

A domain that serves no cookies. The idea here is that you use a cookie-free domain to serve images, CSS files, scripts and whatnot, so that your users don't waste time and bandwidth transmitting cookies for them. SO uses for the purpose, for example.

The main reason the concept is of any note is that most people can't use a subdomain of their main domain to do this (like SO couldn't use because they serve cookies that are valid across the entire second-level domain.

share|improve this answer
Also, some proxies won't cache a request that includes cookies, so a cookie-free domain can improve cacheability and save you more bandwidth than just cutting out the size of the cookies themselves. – stevemegson Oct 24 '09 at 20:35
The cookies are that much huge enemy of bandwidth ? – Tarik Oct 25 '09 at 4:58
In fact, yes. They add up to every HTTP request, no matter if the request is for html, image, css or js. The mere existence of cookie headers can change the behaviour of the proxy servers too. – Michał Szajbe Nov 13 '15 at 8:12

When the browser makes a request for a static image and sends cookies together with the request, the server doesn't have any use for those cookies. So they only create network traffic for no good reason. You should make sure static components are requested with cookie-free requests. Create a subdomain and host all your static components there.

If your domain is, you can host your static components on However, if you've already set cookies on the top-level domain as opposed to, then all the requests to will include those cookies. In this case, you can buy a whole new domain, host your static components there, and keep this domain cookie-free. Yahoo! uses, YouTube uses, Amazon uses and so on.

Another benefit of hosting static components on a cookie-free domain is that some proxies might refuse to cache the components that are requested with cookies. On a related note, if you wonder if you should use or for your home page, consider the cookie impact. Omitting www leaves you no choice but to write cookies to *, so for performance reasons it's best to use the www subdomain and write the cookies to that subdomain


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.