Also see: How to use HTTPS for local development.
In this post, statements about
localhost are valid for
[::1] as well, since they both describe the local computer address, also called "loopback address". Also, to keep things simple, the port number isn't specified.
So when you see
http://localhost, read it as
When developing locally, use
http://localhost by default. Service Workers, Web Authentication API, and more will work.
However, in the following cases, you'll need HTTPS for local development:
Setting Secure cookies in a consistent way across browsers
Debugging mixed-content issues
Using HTTP/2 and later
Using third-party libraries or APIs that require HTTPS
Using a custom hostname
If you need HTTPS for one of the above use cases, check out How to use HTTPS for local development.
✨ This is all you need to know. If you're interested in more details keep reading!
Why your development site should behave securely
To avoid running into unexpected issues, you want your local development site to behave as much as possible like your production website. So, if your production website uses HTTPS, you want your local development site to behave like an HTTPS site.
Warning: If your production website doesn't use HTTPS, make it a priority.
http://localhost by default
http://localhost in a special way: although it's HTTP, it mostly behaves like an HTTPS site.
http://localhost, Service Workers, Sensor APIs, Authentication APIs, Payments, and other features that require certain security guarantees are supported and behave exactly like on an HTTPS site.
When to use HTTPS for local development
You may encounter special cases where
http://localhost doesn't behave like an HTTPS site—or you may simply want to use a custom site name that's not
You need to use HTTPS for local development in the following cases:
- You need to set a cookie locally that is
SameSite:none, or has the
Securecookies are set only on HTTPS, but not on
http://localhostfor all browsers. And because
__Hostalso require the cookie to be
Secure, setting such cookies on your local development site requires HTTPS as well.
When it comes to setting
Secure cookies locally, not all browsers behave in the same way! For example, Chrome and Safari don't set
Secure cookies on localhost, but Firefox does. In Chrome, this is considered a bug.
You need to debug locally an issue that only occurs on an HTTPS website but not on an HTTP site, not even
http://localhost, such as a mixed-content issue.
You need to locally test or reproduce a behaviour specific to HTTP/2 or newer. For example, if you need to test loading performance on HTTP/2 or newer. Insecure HTTP/2 or newer is not supported, not even on
You need to locally test third-party libraries or APIs that require HTTPS (for example OAuth).
You're not using
localhost, but a custom host name for local development, for example
mysite.example. Typically, this means you've overridden your local hosts file:
In this case, Chrome, Edge, Safari, and Firefox by default do not consider
mysite.exampleto be secure, even though it's a local site. So it won't behave like an HTTPS site.
Other cases! This is not an exhaustive list, but if you encounter a case that's not listed here, you'll know: things will break on
http://localhost, or it won't quite behave like your production site. 🙃
In all of these cases, you need to use HTTPS for local development.
How to use HTTPS for local development
If you need to use HTTPS for local development, head over to How to use HTTPS for local development.
Tips if you're using a custom hostname
If you're using a custom hostname, for example, editing your hosts file:
- Don't use a bare hostname like
mysitebecause if there's a top-level domain (TLD) that happens to have the same name (
mysite), you'll run into issues. And it's not that unlikely: in 2020, there are over 1,500 TLDs, and the list is growing.
travel, and many large company names (maybe even the company you're working at!) are TLDs. See the full list here.
- Only use domains that are yours, or that are reserved for this purpose. If you don't have a domain of your own, you can use either
testdoesn't have special treatment in browsers, but
localhostdoes: Chrome and Edge support
http://<name>.localhostout of the box, and it will behave securely when localhost does. Try it out: run any site on localhost and access
http://<whatever name you like>.localhost:<your port>in Chrome or Edge. This may soon be possible in Firefox and Safari as well. The reason you can do this (have subdomains like
mysite.localhost) is because
localhostis not just a hostname: it's also a full TLD, like
With many thanks for contributions and feedback to all reviewers—especially Ryan Sleevi, Filippo Valsorda, Milica Mihajlija, Rowan Merewood and Jake Archibald. 🙌