What is a VPN?
A VPN creates a logical network over an existing network and can carry traffic between a device and a VPN gateway. It improves the connection path in some situations, but it does not remove every device, account, or destination risk.
Last reviewed:
The short answer
A virtual private network, usually called a VPN, is a logical network built over an existing network such as the public internet. A VPN client and a VPN gateway cooperate to carry traffic through a protected connection between them.
What the main parts do
The client runs on a device and applies the connection settings. The gateway is the other end of the connection and forwards traffic toward another network or service. The path between the device and gateway can be protected, while the final service still has its own security and access rules.
The exact behavior depends on the client, operating system, route configuration, network conditions, and the service on the other end. A VPN is therefore a connection mechanism, not a guarantee that every destination will behave in the same way.
A VPN name alone does not say which traffic is included. Some connection designs send most device traffic toward the gateway, while others are limited to selected traffic. The applicable client documentation and device settings define that scope; it should not be guessed from a product label.
The word private describes a logical connection boundary, not an automatic promise about every application or destination. The client, gateway, local device, and destination each keep separate responsibilities. A reader should still consider what data an application sends and which party receives it.
What a VPN does not replace
A VPN does not replace HTTPS, operating-system updates, endpoint protection, account security, or careful handling of personal data. It also cannot make a compromised device or an unsafe destination trustworthy. Check the applicable law and the terms of the services you use.
Before relying on a connection, confirm the visible basics: whether the intended client is active, whether the device has an ordinary network connection, and whether the specific application behaves as expected. These checks describe the current situation without requiring a reader to share passwords, tokens, or private configuration.
Product documentation can use similar terms for different connection designs. A useful guide separates a general networking fact from a claim about a particular product. This article explains the general concept only; readers should use the official documentation for the client or service they actually choose.
The goal is clarity about scope and responsibility, not a universal promise about any connection.