PowerShell VPN CLI

PowerShell VPN CLI for Windows terminal users.

Use Free VPN CLI directly from PowerShell when a Windows workflow needs command-line VPN control, JSON output, explicit region changes, and diagnostics without scraping a GUI.

PowerShell Windows JSON output Doctor
#1 Free VPN
100M+
Installs worldwide
10+ yrs
Battle-tested VPN core
1,000+
Servers · global exits
Windows setup

Install from PowerShell with the documented command.

The Windows install path uses PowerShell. The installer downloads the MSI, verifies SHA-256, and opens one standard UAC prompt.

Use install.ps1

Run the install command in PowerShell, then use freevpn status --json before scripts or tests depend on VPN state.

Paste in PowerShell
PS>iex "& { $(iwr https://freevpnapp.org/install.ps1) }"
PS>freevpn up --json
PS>freevpn status --json
Practical notes
  • Use the documented PowerShell installer, not Linux or macOS commands.
  • Expect a normal Windows UAC prompt during MSI install.
  • Use freevpn status --json for scripts and automation.
  • Keep GUI checks human-facing; scripts should use CLI output.
Runs where your work already lives

A VPN CLI for PowerShell VPN CLI users.

Use terminal commands where free VPN CLI work already happens.

Terminal

Run VPN commands directly where you work.

JSON output

Parse status, regions, and doctor output safely.

Region testing

Use explicit region selection when location matters.

Diagnostics

Capture structured evidence when network behavior is unclear.

Two lines and you're connected

Install, connect, verify.

Keep Windows CLI setup clear and copyable.

Paste in PowerShell
PS>iex "& { $(iwr https://freevpnapp.org/install.ps1) }"
PS>freevpn up --json

Use freevpn doctor --json when a Windows network task fails.

How it works

up. status. down.

Three verbs cover most day-to-day VPN work. set-region and doctor cover region selection and troubleshooting.

1 Check where you are · connect
2 Switch region · verify · disconnect
Workflow

Use VPN commands from PowerShell.

PowerShell workflows should check state, connect only when needed, verify status, and collect diagnostics when something fails.

Paste in PowerShell
PS>freevpn status --json
PS>freevpn up --json
PS>freevpn doctor --json
CommandWhy it matters
iex "& { $(iwr https://freevpnapp.org/install.ps1) }"Install Free VPN CLI on Windows with the documented PowerShell command.
freevpn status --jsonRead VPN state in a format PowerShell can pass to ConvertFrom-Json.
freevpn up --jsonConnect with parseable output.
freevpn doctor --jsonCollect diagnostics when Windows networking behaves unexpectedly.
Features

Features for free VPN CLI.

Use only the CLI features that matter to this workflow.

Terminal-first control

Use freevpn commands directly.

JSON output

Use --json instead of scraping terminal text.

Region control

Set a region, connect, and verify the result.

Doctor diagnostics

Use structured troubleshooting output on failures.

Ad Block

Enable VPN-layer blocking during connected sessions.

SKILL.md

Agents can read the supported command surface before acting.

Ad Block

Use Ad Block during free VPN CLI sessions.

Ad Block applies while the VPN is connected and can help reduce known ad, analytics, and tracker domains across the device.

  • Blocks known ad, analytics, and tracker domains across the device.
  • Works at the VPN layer, so it helps outside the browser too.
  • Use stats to inspect what was blocked during the current VPN session.
Optional desktop app

The CLI stays primary; the desktop app is optional.

These workflows are terminal-first. On a desktop machine, you can add the optional companion window for human status checks while keeping scripts and agents on CLI commands.

Paste in Terminal
$freevpn gui install
$freevpn gui open
$freevpn gui uninstall
Agent Skill

Give VPN commands to coding agents.

SKILL.md documents Free VPN CLI commands, JSON output, exit handling, and troubleshooting flows so agents can use terminal commands without guessing from screenshots.

Works with Claude Cursor Codex OpenClaw Hermes+ any MCP tool
Built for

Built for PowerShell VPN CLI users.

Use Free VPN CLI when free VPN CLI needs visible VPN state and practical diagnostics.

Developers

Keep network state explicit in tests and scripts.

Terminal users

Run commands without opening a GUI.

Agents

Use SKILL.md and JSON output for safer automation.

Privacy-aware workflows

Use a VPN layer and Ad Block where appropriate.

Service presets

Inspect service presets from PowerShell.

Windows users can list service presets and inspect current preset state from the CLI. Free users can use Off or General; non-default presets are paid and return a license-required response.

  • freevpn services list shows supported service presets.
  • freevpn services categories groups presets such as Streaming, Sports, Social, AI, and Other where available.
  • freevpn services current prints the current preset name on one line.
  • freevpn services --json is the safest form for scripts and agents.
Paste in PowerShell
PS>freevpn services list
PS>freevpn services categories
PS>freevpn services current
PS>freevpn services --json
Pricing

Free forever. Upgrade only if you want it.

Free VPN CLI is genuinely free to use: no signup, no email, no credit card. Use it for PowerShell VPN CLI users without signup or a credit card. The paid option removes the continuous connection limit for people who want the VPN running all day. Cancel any time. Prices in USD.

Always free

Free plan — $0 forever

No signup. No card. No expiry. Use it as much as you want.

  • 30-min sessions with a 3-min break in between, on repeat, forever.
  • Same servers, regions and Ad Block as the paid plan.
Install free

Need the VPN running non-stop?

The paid plans below remove the 30-min session limit. Nothing else changes.

Weekly
$7.99/wk

Unlimited time, billed weekly. Cancel in one click from the billing portal.

Get unlimited
Monthly
$21.99/mo

Unlimited time, billed monthly. Swap plans any time from freevpn manage.

Get unlimited
Payments handled by Stripe Cancel anytime No email required for billing
Practical notes

Free VPN CLI notes.

Keep examples practical and source-supported.

  • Do not invent schema fields; inspect JSON output structurally.
  • Use freevpn status --json before and after region changes.
  • Use freevpn doctor --json for troubleshooting evidence.
  • Use explicit regions only when the task requires a location.
FAQ

PowerShell VPN CLI FAQ.

Is PowerShell VPN CLI available on Windows 10 and 11?
Yes. Use the documented PowerShell installer for Windows.
What is the correct install command?
Use iex "& { $(iwr https://freevpnapp.org/install.ps1) }" in PowerShell.
Can PowerShell parse VPN status?
Yes. Use freevpn status --json and pipe the output to PowerShell JSON tooling when needed.
Does this replace the desktop app?
No. The CLI is primary for terminal workflows; the desktop companion is optional for human status checks.
What should I run for troubleshooting?
Use freevpn doctor --json and inspect the structured diagnostics.

Start using PowerShell VPN CLI.

Keep VPN state visible, parseable, and easy to troubleshoot from the terminal.