VALORANT
Hardware and network requirements for playing VALORANT on Windows PC in Valor lessons.
What students need (Windows PC)
| Component | Minimum (30 FPS) | Recommended (60 FPS) | High-end (144+ FPS) |
|---|---|---|---|
| Intel processor | Core i3-540 | Core i3-4150 | Core i5-9400F, 2.9 GHz |
| AMD processor | Athlon 200GE | Ryzen 3 1200 | Ryzen 5 2600X |
| NVIDIA or Intel graphics | Intel HD 4000 | GeForce GT 730 | GeForce GTX 1050 Ti or Intel Arc A310 |
| AMD graphics | Radeon R5 220 | Radeon R7 240 | Radeon R7 370 |
| Memory | 4 GB | 4 GB | 4 GB |
| Video memory | 1 GB | 1 GB | 1 GB |
| Operating system | Windows 10 build 19041 or newer, 64-bit | Windows 10 build 19041 or newer, 64-bit | Windows 10 build 19041 or newer, 64-bit |
Source: VALORANT system requirements. All tiers also need a CPU with SSE4.2 or AVX support. Do not buy new devices at the 4 GB game minimum - Valor suggests 16 GB RAM (32 GB preferred on shared multi-game images) and the 144+ FPS tier where the budget and display justify it. Check the install size in the Riot client and leave patching headroom.
Install, Vanguard and firmware
- Install through the Riot client. Riot Vanguard is part of the deployment and cannot be left out.
- Vanguard includes a kernel-mode driver that runs at system startup. VALORANT will not run without it, so plan installation and reboot testing with IT before issuing devices to students: Vanguard architecture, security and privacy.
- On Windows 11, Riot requires TPM 2.0 and UEFI Secure Boot. Some motherboards can also trigger additional VAN restrictions: Vanguard motherboard firmware update.
- A passing CPU or GPU check is not proof that firmware and security checks will pass. Record VAN messages separately from firewall errors so firmware problems are not misdiagnosed.
- Do not disable school endpoint protection to make the game work. Resolve any conflict with the school's IT and security team.
Network requirements
Ports and protocols
- Game client: UDP 7000-8000 and 8180-8181
- Installer and patcher: TCP 8393-8400
- PvP.Net: TCP 2099, 5222, 5223
- HTTP and HTTPS: TCP 80, 443
- Spectator mode: TCP and UDP 8088
- Voice, NA and EU: UDP 27016-27024. Voice, AP and SE: UDP 54000-54012
- Voice can also use 50 TCP ports within the range 1024-65000. The exact allocation is not published, so confirm the current behaviour with Riot or your IT team, and test AP/SE voice for an Australian deployment.
Destinations
- No complete destination list is published. Allow the Riot installation, update and account flows, then observe blocked traffic during a controlled sign-in and match test.
- Ask Riot for the current regional endpoints if you need a strict allowlist.
- Broad rules such as *.riotgames.com or *.riotcdn.net are a starting scope, not a complete verified server policy.
- Do not use League of Legends IP ranges as VALORANT addresses.
Before your first lesson
- Reboot, sign in as a student, start Vanguard and VALORANT, enter the Practice Range, create or join the intended custom session, finish a full match and test approved team voice.
- Repeat on every PC behind the same school network. A single working device does not prove the class will work.
Publisher support links
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article