mkcert is a simple tool for making locally-trusted development certificates. It requires no configuration.
$ mkcert -install Created a new local CA at "/Users/filippo/Library/Application Support/mkcert" 💥 The local CA is now installed in the system trust store! ⚡️ The local CA is now installed in the Firefox trust store (requires restart)! 🦊 $ mkcert example.com "*.example.org" myapp.dev localhost 127.0.0.1 ::1 Using the local CA at "/Users/filippo/Library/Application Support/mkcert" ✨ Created a new certificate valid for the following names 📜 - "example.com" - "*.example.org" - "myapp.dev" - "localhost" - "127.0.0.1" - "::1" The certificate is at "./example.com+5.pem" and the key at "./example.com+5-key.pem" ✅
Using certificates from real certificate authorities (CAs) for development can be dangerous or impossible (for hosts like
127.0.0.1), but self-signed certificates cause trust errors. Managing your own CA is the best solution, but usually involves arcane commands, specialized knowledge and manual steps.
mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates. mkcert does not automatically configure servers to use the certificates, though, that's up to you.
rootCA-key.pemfile that mkcert automatically generates gives complete power to intercept secure requests from your machine. Do not share it.
On macOS, use Homebrew
brew install mkcert brew install nss # if you use Firefox
sudo port selfupdate sudo port install mkcert sudo port install nss # if you use Firefox
On Linux, first install
sudo apt install libnss3-tools -or- sudo yum install nss-tools -or- sudo pacman -S nss
Then you can install using Linuxbrew
brew install mkcert
or build from source (requires Go 1.10+)
go get -u github.com/FiloSottile/mkcert $(go env GOPATH)/bin/mkcert
or use the pre-built binaries.
git clone https://aur.archlinux.org/mkcert.git cd mkcert makepkg -si
On Windows, use Chocolatey
choco install mkcert
or use Scoop
scoop bucket add extras scoop install mkcert
or build from source (requires Go 1.10+), or use the pre-built binaries.
If you're running into permission problems try running
mkcert as an Administrator.
Supported root stores
mkcert supports the following root stores:
- macOS system store
- Windows system store
- Linux variants that provide either
update-ca-trust(Fedora, RHEL, CentOS) or
update-ca-certificates(Ubuntu, Debian) or
- Firefox (macOS and Linux only)
- Chrome and Chromium
- Java (when
For the certificates to be trusted on mobile devices, you will have to install the root CA. It's the
rootCA.pem file in the folder printed by
On iOS, you can either use AirDrop, email the CA to yourself, or serve it from an HTTP server. After installing it, you must enable full trust in it. Note: earlier versions of mkcert ran into an iOS bug, if you can't see the root in "Certificate Trust Settings" you might have to update mkcert and regenerate the root.
For Android, you will have to install the CA and then enable user roots in the development build of your app. See this StackOverflow answer.
Using the root with Node.js
Node does not use the system root store, so it won't accept mkcert certificates automatically. Instead, you will have to set the
NODE_EXTRA_CA_CERTS environment variable.
export NODE_EXTRA_CA_CERTS="$(mkcert -CAROOT)/rootCA.pem"
Changing the location of the CA files
The CA certificate and its key are stored in an application data folder in the user home. You usually don't have to worry about it, as installation is automated, but the location is printed by
If you want to manage separate CAs, you can use the environment variable
$CAROOT to set the folder where mkcert will place and look for the local CA files.
Installing the CA on other systems
Installing in the trust store does not require the CA key, so you can export the CA certificate and use mkcert to install it in other machines.
- Look for the
- copy it to a different machine
$CAROOTto its directory
Remember that mkcert is meant for development purposes, not production, so it should not be used on end users' machines, and that you should not export or share