History
What Worlds.com was, what people did with it, and how it ended.
1995: Worlds Chat
Worlds Inc. — earlier Knowledge Adventure Worlds, later Worlds.com — built one of the first multi-user 3D virtual worlds on the internet. The first public product was Worlds Chat, in 1995. Think about what that meant at the time: modems, Windows 95, and you walking around a space station with other people who were actually there, at the same time, moving.
The client that survived to the end is the WorldsPlayer, and it is the one still in use today. There is a whole page on what is inside it.
What people actually did with it
This is the part that gets lost when a service dies, because it was never in any official material. Worlds shipped with worlds, and then the people in it made hundreds more.
GroundZero was the front door — the room everyone landed in. Beyond it: an avatar gallery, band worlds, a mall. And then whatever anybody felt like building. There is a world that is a recreation of Kowloon Walled City with a jump scare in the hallway and a clock room that says "Don't panic.....". There are vaporwave worlds, goth worlds, a wedding world, a water world, a world that is just a Sonic joke. Some of them are good. A lot of them are the kind of thing a teenager builds at two in the morning, which is exactly what makes them worth keeping.
A world address looks like this, and it is worth seeing once because it tells you how the whole thing is put together:
http://host/path/kowloon.world#killingfloor@3021.0,346.0,150.0,296.0,0.0,0.0,-1.0
A file over plain HTTP, a room name after the #, and then where
to stand. Worlds are just files somebody put on a web server. That is why the
community could keep them alive on mirrors after the fact, and it is why this
project can serve them.
Who was running it at the end
By the last years, Worlds was not really being run by Worlds Inc. in any meaningful sense. It was being run by hosters — users who ran servers on their own machines and held moderation powers over who could be there. There were around a hundred of them. That is a community keeping a service standing after the company behind it had effectively stopped participating.
It also means that when things went wrong, they went wrong in the way volunteer-run things do: worlds that quietly became unreachable, worlds removed because of who owned them, arguments about bans. Any honest history of this place includes that.
How it ended
There was no announcement, no farewell, no date circled on a calendar. It simply stopped.
6 August 2024 — the servers go offline
The WorldsPlayer servers went down. The cause reported at the time was a server misconfiguration rather than a decision to close. People assumed it would be back within days. It was never fixed. From 1998 to that morning there had been someone logging in every day; after it, the client still started, still remembered your avatar, and had nowhere to connect to.
October 2025 — the domains lapse
worlds.com and worlds.net reached their expiry date
and were not renewed. They began serving a registrar parking page. The company
behind them had been financially spent for years — a shell trading on
the over-the-counter market, long past the point of running anything.
21 November 2025 — Thom Kidrin dies
Thom Kidrin had been president and chief executive of Worlds Inc. since 1997. Whatever chance remained of someone inside the company turning the lights back on went with him.
January 2026 — the name goes
worlds.com was bought and registered by a company with no
connection to any of this. The download link for the client returns a 404. The
address that was the front door to a thirty-year-old world belongs to someone
else now.
That is the shape of it: a service that died of neglect, then outlived the person who could have saved it, then lost its own name.
Why a server and not a museum
A chat that depends on a central server cannot be archived with screenshots. When the server goes there is nothing left to run — it does not matter that you still have the client installed or that you remember your password. No server, no room.
The only way to preserve a chat room is to be able to walk back into it. So this is a server, and the guides matter as much as the code: something only one person knows how to run is not preserved either.