SSD Nodes Learn 🎉 VPS from $4.99/mo
Guides Matt ConnorBy Matt Connor

Can you actually game on a VPS?

Two readers, two answers. A standard VPS cannot play games for you, and here is the reason. Hosting a dedicated game server on one works well.

Can you game on a VPS? The short answer

Can you game on a VPS? Two people ask that question and they need opposite answers. If you want to play a game yourself on a rented server and watch the picture on your own screen, a standard VPS (virtual private server) cannot do it, and no configuration change fixes that. If you want to host a game server that other players connect to, a VPS is one of the best things you can rent for the money, and a small plan is often enough.

If you are here for the hosting side, go straight to picking a VPS for game servers or running a Minecraft server on a VPS. The sections below explain why the playing side does not work, because that is the answer people rarely get straight.

Why a standard VPS has no GPU

A standard VPS is a slice of a shared host: virtual CPU cores, RAM, disk, and a network port. The host is a rack server, and a rack server carries no consumer graphics card, because a gaming GPU (graphics processing unit) is built for a desktop case with its own fans and a large power budget. Your virtual machine gets a virtual display adapter so the boot console has somewhere to draw. That is the whole graphics story.

lspci | grep -i -E 'vga|3d|display'
ls -l /dev/dri

The first command prints one line, usually something like Cirrus Logic GD 5446 or Red Hat, Inc. Virtio 1.0 GPU. Those devices have no 3D engine. The second command normally answers ls: cannot access '/dev/dri': No such file or directory, because no direct rendering device exists for a program to open. On a real GPU instance the same command lists card0 and renderD128.

Mesa will still give you OpenGL through llvmpipe, its software renderer, which draws every triangle on the CPU. That is enough for a desktop or an old 2D game. A modern 3D title runs at a few frames per second, and the CPU is then busy with the one job it is worst at, so the game logic slows down as well.

Why input latency is the thing that kills remote play

Remote play is a loop. Your key press travels to the server, the server renders a frame, encodes that frame as video and sends it back, then your client decodes it and puts it on the screen. Every stage costs milliseconds, and they add up.

ChartTypical published latency for a hardware-encoded game stream, same region
The data behind this chart
[
  {
    "label": "Input capture and send",
    "typical_ms": 5
  },
  {
    "label": "Network round trip",
    "typical_ms": 15
  },
  {
    "label": "Frame render on the server",
    "typical_ms": 12
  },
  {
    "label": "Hardware video encode",
    "typical_ms": 8
  },
  {
    "label": "Decode and display on the client",
    "typical_ms": 15
  },
  {
    "label": "Sum of the stages above",
    "typical_ms": 55
  }
]

Only 15 ms of that is the network round trip, and it is the one part you improve by choosing a server closer to you. The rest is the pipeline itself, and it does not care where the server sits. The stages add to 55 ms of delay before the game has done any work of its own. These are typical published figures for a hardware encoder streaming to a client in the same region, not measurements from one machine, so read them as the shape of the problem.

That delay lands inside a feedback loop. You move the mouse, you see the result, you correct. Extra delay makes every correction arrive late, so you pass the target and correct again. Turn based games, strategy, management sims and card games survive it comfortably. Shooters, fighting games, rhythm games and racing do not.

Jitter and packet loss hurt in a different way. A video stream cannot wait for a retransmission, because the frame that packet belongs to is already late, so loss shows up as blocking artifacts or a frozen picture rather than a pause. This is also why a remote desktop is the wrong tool. VNC (virtual network computing) and plain RDP (remote desktop protocol) send changed rectangles over TCP, and a screen that changes completely 60 times a second turns that into a stream of retransmissions.

What a real cloud gaming box would need

Building this properly is possible. It needs four things at once.

  • A GPU instance with a datacenter card, because that is the only kind a provider is licensed to rent out.
  • A hardware video encoder such as NVENC, NVIDIA's built in encoder, because encoding in software costs CPU time and adds delay.
  • A streaming pair built for games rather than for desktops. Sunshine on the server with Moonlight on the client is the common open source choice.
  • A server in your own metro region, because the round trip is distance, and distance is the speed of light in fibre.

Then price it. GPU instances bill by the hour, so multiply the hourly rate by 730 to get the cost of a month left running. As of August 2026 that is a three figure monthly bill in US dollars, which buys a console outright inside a year, and you still pay for the game licences on top. What a GPU VPS actually gives you and the break even maths on renting GPU hours go through the numbers.

If you only want to play, the commercial cloud gaming services already run this exact stack from datacenters near you, with the licensing settled. One VPS in one city cannot match a network built for the job.

Anti-cheat and licensing block what is left

Even a perfect GPU box runs into rules. Riot's Vanguard requires TPM 2.0 (trusted platform module) and Secure Boot on Windows 11, and it refuses to run inside a virtual machine, so Valorant will not start on rented cloud hardware. Easy Anti-Cheat and BattlEye can detect a hypervisor as well, and several titles that use them block virtual machines or ban for it. This is deliberate: cheat developers use virtual machines to hide their tooling, so refusing to run in one is cheap protection for the game.

Licensing sits on top of that. NVIDIA's licence for its GeForce drivers restricts datacenter use, which is why providers rent datacenter cards and not desktop ones. Windows needs a licence that allows running on hardware you do not own. Storefront terms cover where a copy may run. Any one of these is survivable on its own. Together they mean the hand built cloud gaming rig will not run most of the competitive games people want it for.

What a CPU only VPS runs very well

Now the other reader. A dedicated game server never draws a frame. It simulates the world, applies each player's input, and sends state updates back over the network. The players' own machines do the drawing. No rendering means no GPU is needed, so the box that is useless for playing is the right shape for hosting.

  • Dedicated servers for Minecraft, Valheim, Terraria, Factorio, Rust, Project Zomboid and most other titles that ship a headless server build.
  • Voice chat. A Mumble server is light enough to sit beside the game server on the same small plan.
  • Mod and map downloads over plain HTTP, plus the web panel your players use to see who is online.
  • Matchmaking, stats, leaderboards, Discord bots, and the database behind them.
  • Scheduled world backups that leave the box, so a corrupted save costs an hour and not the whole map.

RAM is usually the binding limit, and single core speed matters more than core count for many of these games, because the main simulation tick of a Minecraft or Factorio server runs on one thread. A plan with eight slow cores loses to a plan with four fast ones. Bandwidth moves with player count more than CPU does, and providers meter transfer, so read the allowance before you pick a plan.

Open the right ports, and remember that most in game traffic is UDP (user datagram protocol) rather than TCP.

sudo ufw allow 25565/tcp
sudo ufw allow 27015/udp
sudo ufw status

ufw status should list each rule with ALLOW beside it. If the port is open here and the server is still unreachable, check your provider's control panel for a separate network firewall, because a rule inside the machine has no effect on the filter sitting in front of it.

Keep it running without you. A systemd unit or a Docker restart policy brings the server back after a reboot, and a compose stack that starts itself on boot is the usual pattern. Pair that with scheduled off box backups so the world file survives the disk.

How to check a VPS before you host on it

Latency to your players decides whether the server feels good, and it is measurable. Ask the provider for a test address in the region you want, then run these from a player's network, not from the server.

ping -c 20 203.0.113.10
mtr -r -c 100 203.0.113.10

ping finishes with a summary line such as rtt min/avg/max/mdev = 18.4/19.1/24.6/1.2 ms. The last number is jitter. A steady average with low jitter feels better in game than a lower average that swings. mtr prints loss per hop, and you should read the loss on the final line only, because routers in the middle give their own ICMP (internet control message protocol) replies the lowest priority and often report loss that real traffic never suffers.

Then check whether the host is oversubscribed.

vmstat 1 5

The st column is steal time: the share of time your virtual CPU was ready to run while the physical host handed those cycles to another guest. A steady non zero value there means your tick rate will wobble under load, whatever the plan page says. Steal time and noisy neighbours covers how to read it, and benchmarking a VPS yourself covers the rest of the numbers to collect before you commit to a year.

The straight answer to both questions

If you want to play, keep the game on hardware you can touch, or use a service built for streaming games. A general purpose VPS cannot render, and a GPU instance costs more than the hardware while still losing to anti-cheat. If you want to host, rent the VPS. It is a genuinely good fit at a small price, and the same box will run other things between game nights.

FAQ

Can I install Steam on a VPS and play my games?

You can install the Steam client on a Linux VPS and it will download games. Playing them is the part that fails. A standard plan has no GPU, so 3D titles fall back to CPU rendering at a few frames per second, and many modern games refuse to start without a supported renderer. Streaming whatever does render back to your screen then adds the encode and network delay on top. Steam Remote Play is built to stream from a real gaming machine you own, and it expects that machine to have a graphics card.

Will a GPU VPS let me play any game I own?

It removes the rendering problem and none of the others. You still need a hardware encoder, a low latency client such as Moonlight, and a server close enough that the round trip stays small. Anti-cheat is the wall: Riot's Vanguard refuses to run in a virtual machine, and Easy Anti-Cheat and BattlEye can detect a hypervisor, so competitive shooters are out. Single player and slower paced games are the realistic use, at a monthly cost above the price of local hardware.

What size VPS do I need for a Minecraft server for ten friends?

A vanilla Java server for ten players is comfortable on 2 vCPU and 4 GB of RAM. Give the JVM (Java virtual machine) about 3 GB with -Xmx3G and leave the rest to the operating system, because the JVM will use every byte you allow it and the kernel still needs memory for page cache. A large modpack changes the answer: plan for 6 GB to 8 GB of heap alone, and choose the plan with the faster single core, because the main world tick runs on one thread.

Why does a remote desktop feel fine but a game does not?

A desktop changes a small part of the screen at a time, and nobody notices if a window redraw arrives 100 ms late. A game changes every pixel dozens of times a second and closes a feedback loop through your hands. VNC and plain RDP send changed rectangles over TCP, so a screen in constant motion becomes retransmissions and stalls. Even a proper video stream leaves the input delay in place, and that delay is what you feel when you try to aim.

#gaming#vps#gpu#game-servers#cloud-gaming