Security · VPN setup

BlissPoint WireGuard Config Generator

The WireGuard config generator is a free tool that makes WireGuard keys, a server wg0.conf and a config for each person in your browser, and the keys never leave your browser.

A free WireGuard VPN config generator — with keys made in your browser that never leave it, and server and client files that match the first time.

Generate your configs →What happens nextRead the setup guide

Keys never leave your browser. Nothing you type or generate is sent anywhere.

Who is this for?

Not for you if…

  • You want a consumer privacy VPN to hide your browsing or change your country. This makes configs for a server you run yourself.
  • No one on your team can patch a Linux server or keep track of keys. A managed zero-trust service is safer.

What does this WireGuard generator do?

It writes the files a WireGuard VPN needs, without you typing keys by hand or installing anything. A WireGuard VPN connects each laptop or phone to one server you control through an encrypted tunnel. Every device has its own private key, which stays on that device, and a public key, which the server uses to recognize it. The server's config file, usually called wg0.conf, lists one [Peer] block per device with that device's public key and its private address inside the VPN.

Getting those pieces right by hand is where most first setups fail: a pasted private key in the wrong place, two clients with the same address, or a missing AllowedIPs line. The generator makes the keys, numbers the addresses in order, and fills in both sides so they match.

Is it safe to make VPN keys on a website?

It is on this page, because the keys are never on a website's server at all. Your browser makes them with the X25519 support built into WebCrypto, the same standard cryptography browsers use for secure connections. The form makes no network request with what you type or what it generates, and you can confirm it yourself: open your browser's developer tools, watch the Network tab, and press Generate. Close the tab and the keys are gone, except in the files you downloaded.

If your policy says keys must be made on the server itself, that's fine: run wg genkey there and use this page only as a template for the config layout.

How do I generate WireGuard configs?

Enter your server's public address and the names of the people or devices that will connect. WireGuard (a modern open-source VPN) needs one key pair for the server and one for each client; this page makes them and fills in the configs. Then follow the step-by-step guide to setting up WireGuard on your own server.

What happens after you generate the configs?

  1. Enter the server's public address and port

    Use the server's public IP address or a DNS name that points to it, and the UDP port WireGuard will listen on (51820 is the usual choice). Open that port in the server's firewall.

  2. List one client per person or device

    Name each client after its owner and device, such as maria-laptop or front-desk-phone. One key per device means you can remove a lost phone without touching anyone else.

  3. Generate and download the files

    The page makes a key pair for the server and for each client with your browser's built-in cryptography, then fills in wg0.conf for the server and one .conf file per client.

  4. Install the server config

    Copy wg0.conf to /etc/wireguard on the server, keep it readable only by root, and start it with wg-quick up wg0. The self-hosted VPN guide walks through each command.

  5. Send each person their own file, privately

    Share client files through a password manager or in person, never by plain email or chat. Each person imports theirs into the WireGuard app on their device and turns the tunnel on.

  6. Test, then write down who has which key

    Check that each client connects and reaches what it needs. Keep a short list of names, devices and addresses so you can remove the right key the day someone leaves.

Is a self-hosted WireGuard VPN right for your team?

When this tool fits, and when something else is better
Your situationUse this generator?
You run your own Linux server and want a team VPNYes: generate configs here, then follow the setup guide
You need a fixed exit address for one app onlyMaybe: a private proxy can be simpler
Your team only uses cloud apps with single sign-onProbably not: multi-factor login may be enough
You have no one to patch a server or manage keysNo: a managed zero-trust service is safer

Not sure which kind of tool you need? The plain comparison of a VPN and a proxy explains what each one covers, and the Security hub lists every guide and free tool in one place.

Questions

Are the keys sent to your server?

No. The keys are made by your browser's built-in cryptography and the page makes no network request with them. They exist only on this page and in the files you download.

Which browsers work?

Current versions of Chrome, Edge, Firefox and Safari, which support X25519 keys. If yours doesn't, the page says so; run wg genkey on your server instead.

Can I scan a QR code with my phone?

This page offers downloads, not QR codes. Open the downloaded file in the WireGuard app, or show it as a QR code on your server with qrencode -t ansiutf8 < name.conf.

Should I use the preshared key option?

It is optional. A preshared key adds a second secret to each connection, as the WireGuard documentation describes. Keep it as private as the private key.

How do I remove someone who left the company?

Delete their [Peer] block from the server's wg0.conf, or run wg set wg0 peer <their public key> remove, then save the config. Their key stops working at once. Don't reuse the key or the address for anyone else.

Can I add more people later?

Yes. Generate a new client here with the next free address, paste its [Peer] block into the server config, and restart or reload WireGuard. Existing clients keep working.

This page is general information, not legal advice. Rules on monitoring, data retention and network use differ by country and state; check yours with a lawyer.

For your own systems and lawful use only. Don't use these guides or tools on servers, networks or accounts you don't own or aren't authorized to run.

Want us to set it up for you? See Secure Remote Access for HR Systems.