How Slither.io Was Made (Lowtech Studios Story)

A developer typing code on a laptop with a Python book beside in an office.

How Slither.io was made is the rare browser-game success story where a single developer built a massively multiplayer game from scratch and watched it become a phenomenon. Steve Howse, working solo under the Lowtech Studios banner, launched Slither.io in March 2016. Within months it was one of the most-played games on the web and in the app stores, and Howse’s ad income was reported at around $100,000 a day at its height.

Key takeaways

  • Slither.io was made by Steve Howse, a solo developer based in the US, under his studio Lowtech Studios.
  • The game launched in March 2016 and rode the post-Agar.io “.io games” wave.
  • By September 2017 it had been downloaded more than 68 million times on mobile and played more than 67 million times in browsers.
  • The game made its money through ads shown after a snake died, with a one-time purchase to remove them.
  • Howse was approached by buyers but kept the game under Lowtech Studios.

Who Steve Howse is

Steve Howse is an American developer, originally from Minneapolis and later based in Michigan, who founded Lowtech Studios as a one-person operation. He has stayed relatively private as a public figure; most of what’s known about him comes from a handful of interviews and the public footprint of the games.

That solo background is worth pausing on. Slither.io is a real-time multiplayer game with hundreds of simultaneous players per server, server-authoritative collision detection, and a smooth client-side interpolation layer. Building all of that as one person, in 2016, was technically aggressive in a way that the polished final product hides.

The Agar.io precedent

The .io games era kicked off in April 2015 with Agar.io, a real-time cell-eating game made by Brazilian developer Matheus Valadares. Agar.io demonstrated that a single developer could ship a browser-based MMO if the rules were simple enough: a 2D playfield, one input (mouse direction), one mechanic (consume smaller things, avoid bigger things), and a leaderboard.

Slither.io took that template and applied it to the snake format. Move with the mouse. Eat dots to grow. Run into another snake and you die; circle around another snake and it dies. The mechanical simplicity made the game readable in three seconds. The execution — smooth movement, fair collisions, instant restarts — made it stick.

The launch

Slither.io launched on March 25, 2016, in browsers and on iOS, with the Android version following two days later. The game spread on YouTube and Twitch as streamers tested it, and within weeks it was climbing the app stores’ free charts. The browser version and the mobile apps grew side by side.

The viral arc is partly explained by timing — the .io games space had a hungry audience after Agar.io, and Slither.io was the second major hit in the genre — and partly by streaming. The game’s matches were short, watchable, and easy to clip. A single growth spike or a single takedown of a giant snake made for shareable content.

The technical surface

Slither.io runs as an HTML5 client talking to game servers over WebSocket, a low-latency browser protocol. The client handles smooth interpolation between server updates, which is what gives the snakes their fluid motion even on lossy connections. The server handles collision detection — the moment a snake’s head touches another snake’s body is decided server-side, which prevents client-side cheating from determining wins.

Servers at launch supported up to 500 players each, and Howse has said the hardest part of development was making a server stable enough to handle around 600 players at a time. The technical complexity he had to manage as a solo developer was substantial, even if each individual piece (canvas rendering, WebSocket connections, server-side simulation) was well-established by 2016.

The monetization model

Slither.io ran ads. At launch, the only revenue source was an ad shown after your snake died, which mobile players could remove with a $3.99 purchase. Howse deliberately avoided selling virtual currency or power-ups, so paying players would never get an advantage. The model was low-friction because the game’s casual audience wouldn’t tolerate gates.

At its 2016 peak, reporting put Howse’s income at around $100,000 a day, a remarkable figure for a single-developer project. Lifetime totals have never been made public, and ad rates dropped after the 2016-2017 boom.

The offers to buy it

Success brought pressure. Howse said two major gaming companies approached him about buying the game, and he considered it because keeping a hit online alone was stressful. No sale was ever announced, and Slither.io stayed with Lowtech Studios.

That makes it different from Wordle, which its solo creator sold to The New York Times. Running servers for a global audience is a far heavier load than hosting a daily word puzzle, which is exactly why Howse’s decision to keep going past the game’s breakout year stands out.

What happened to the .io wave

Slither.io was the peak of the first wave of .io games. Diep.io (2016), Agar.io (2015), Mope.io (2016), Krunker.io (2018), and dozens of others followed. The genre is still active, but no single title since has matched Slither.io’s peak audience. Part of that is mobile games eating the casual web-gaming space; part of it is that the format hit a saturation point fast.

The lessons from Slither.io still apply to anyone shipping a browser multiplayer game in 2026. Keep the rules readable in three seconds. Make the matches short and watchable. Run server-authoritative collision. Lean on streaming for distribution. The format isn’t proprietary — but executing each piece well, solo, is harder than the post-hoc summary makes it sound.

Why it matters

How Slither.io was made is a counterexample to the assumption that browser multiplayer is the exclusive domain of well-funded studios. One developer, one game, tens of millions of players. The story isn’t repeatable on demand, but it proves the ceiling is higher than most solo developers assume. For a longer profile of the studio behind it, see our Lowtech Studios history; for a play-focused overview, our Slither.io review covers the current state of the game.

Frequently asked questions

Who made Slither.io?

Steve Howse, an American solo developer working under his studio Lowtech Studios, made Slither.io. He built the original game and ran its servers essentially on his own.

When did Slither.io launch?

Slither.io launched on March 25, 2016, in browsers and on iOS. The Android version followed on March 27, 2016.

How many people played Slither.io at its peak?

Exact peak player counts were never published, but by September 2017 the game had been downloaded more than 68 million times on mobile and played more than 67 million times in browsers. The Slither.io Wikipedia entry tracks the audience figures.

How did Slither.io make money?

Slither.io made money through ads shown after a snake died, plus a $3.99 purchase to remove them. There was no virtual currency and no paid power-ups. At its 2016 peak, Howse’s income was reported at around $100,000 a day.

Was Slither.io sold?

No sale has been announced. Howse said two major gaming companies approached him about buying it, and he considered the offers, but the game has remained a Lowtech Studios title.

The takeaway

How Slither.io was made is the story of a solo developer who saw the .io games opening and built the cleanest implementation of the snake format anyone had tried. Server-authoritative, mouse-controlled, mobile-portable. Tens of millions of players proved that the browser was still a viable platform for hit-scale multiplayer in 2016. For a very different kind of browser game — single-player, offline-first, built by Google’s Chrome team in 2014 — the Chrome Dino game runs at the top of this site.

🔌 Connect any AI assistant to dinogame.gg — we run an MCP server: https://dinogame.gg/mcp